Hi Douglas,

Thanks for the reply. I understand that there should be two segments of HL, one 
for shipment and other for Item level.But to map the 
orders_unpacked_item_4000_4900 and the packed items in outer_container_5600 
segment on the application side to the EDI side, do I need to  keep two HL_line 
segments one for 4000-4900 level and other for 5600 level. If only one is good 
enough then how should I do the mapping of two levels on application side to 
one on output.Please advise.Thanks a lot once again.

Thanks,
Prav Gad.


----- Original Message ----
From: Art Douglas <[EMAIL PROTECTED]>
To: Art Douglas <[EMAIL PROTECTED]>; prav gad <[EMAIL PROTECTED]>; 
[email protected]
Sent: Tuesday, May 1, 2007 1:41:50 PM
Subject: RE: [EDI-L] <TECH>EDI ASNO 856 outbound transaction help


My typing mistake, HL01 should not duplicate, so the example should look
like this instead:

ST...
BSN...
DTM...
HL*1**S*1
<shipment segments>
HL*2*1*I*0
LIN...
HL*3*1*I*0
LIN...
HL*4*1*I*0
LIN...
...
CTT...
SE...

Art Douglas
Chief Consultant
Blackwater Network
877-464-8915

-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Art
Douglas
Sent: Tuesday, May 01, 2007 10:35 AM
To: 'prav gad'; [email protected]
Subject: RE: [EDI-L] <TECH>EDI ASNO 856 outbound transaction help

Gad,

By checking the IG or the X12 standards you can answer this question.  Note
that the HL segment can repeat, whereas the LIN segment has a max of 1
occurance.  From this you can infer that your outbound ASN should look
something like this:

ST...
BSN...
DTM...
HL*1**S*1
<shipment segments>
HL*2*1*I*0
LIN...
HL*3*1*I*0
LIN...
HL*3*1*I*0
LIN...
...
CTT...
SE...

Therefore, you need two _levels_ of HL statements, but multiple occurances,
one for each shipment, one for each line within each shipment.  It doesn't
matter to the HL whether it is a line of packed items, or not.

I hope this answers your question.

Art Douglas
Chief Consultant
Blackwater Network
877-464-8915
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of prav
gad
Sent: Tuesday, May 01, 2007 7:40 AM
To: [email protected]
Subject: [EDI-L] EDI ASNO 856 outbound transaction help

Hi Guys,

Can anyone please guide me regarding the mapping of ASNO using X12. I am
using gentran AI mapper for mapping. Acc to the spec I need to build a ASNO
map with two HL segments one for Shipment and other for Item level.I am not
sure how to deal with the line level HL segment. Do I need to keep two
segments HL item level (4500 level for unpacked items) and other for HL item
level (7000 packed items in container) or should I just keep one HL item
level and map all of application item level fields directly to it.

Anyone help will be really appreciated.

Thanks,
Prav Gad.





...
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



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Non-text portions of this message have been removed]



...
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/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> 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