Rahul -

There is a maximum of 1 N1 segment within each N1 loop, but there can be
an indefinite number of N1 loops within the 820 document. So, you have
to map two N1 loops to accommodate your two N1 segments. I have mapped
only inbound documents, so I cannot offer you low-level mapping advice
for an outbound document. However, I know that this kind of thing is
covered in the Inovis documentation under the heading of "Mapping
Repeating Items".

I hope this helps.

Regards,

Steve Becker
Sports, Inc.

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of
rahul_151
Posted At: Monday, July 17, 2006 6:04 AM
Posted To: Inbox
Conversation: SPAMWARNING:sent
to:SMTP:[EMAIL PROTECTED];:66.163.187.181: [EDI-L] more than one
N1 segments in 820
Subject: SPAMWARNING:sent
to:SMTP:[EMAIL PROTECTED];:66.163.187.181: [EDI-L] more than one
N1 segments in 820


Group,

I am doing an outbound 820 map for WACHOVIA using TLi Visual Mapper. 
Their test file contains two separate N1 segemnts for payer and payee.
However the standards say Maximum use 1 time for this segment. Can 
this be overriden? If yes, how? I dont know how to do this using TLi 
Visual Mapper. Any guidence on this is appriciated.







...
Please use the following Message Identifiers as your subject prefix:
<SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work:
<JOBS> IS REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links



 







...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 


Reply via email to