Below show some common fields required to map ORDERS IDOC, for both EDIFACT ORDERS and X12 850 message type.

SD Business Field Meaning Source EDIFACT ORDERS segment Source X12 850 segment Target IDOC ORDERS/ORDERS05 segment
Header PO Number BGM+220 BEG E1EDK02-BELNR with qualifier 001
Header PO Date DTM+137 BEG E1EDK02-DATUM with qualifier 001
Header Currency CUX CUR E1EDK01-CURCY
Header Sold-To Party NAD+BY N1+BT E1EDKA1-PARTN with PARVW 'AG'
Header Ship-To Party NAD+ST N1+ST E1EDKA1-LIFNR with PARVW 'WE'
Item Quotation Nunber RFF+PO REF+PR E1EDP02-BELNR with qualifier 004
Item Customer Part Number LIN/PIA with qualifier BP PO1 with qualifier BP E1EDP19-ITDNR with qualifier 001
Item Vendor Part Number LIN/PIA with qualifier VP PO1 with qualifier VP E1EDP19-ITDNR with qualifier 002
Item Ordered Quantity QTY+21 PO1 E1EDP01-MENGE
Item Unit of Measurement QTY+21 PO1 E1EDP01-MENEE
Item Unit Price PRI+AAA PO1 E1EDP01-VPREI
Schedule Line Quantity QTY+21 after SCC+1 SCH E1EDP20-WMENG
Schedule Line Date DTM after SCC+1 SCH E1EDP20-EDATU

Example EDIFACT ORDERS
UNA:+.? ‘
UNB+UNOA:1+<Sender ID>+<ReceiverID>+<YYMMDD>:<HHMM>+<ICN#>++ORDERS’
UNH+1+ORDERS:D:97A:UN:EDPO04′
BGM+220+<Header PO Number>+9′
DTM+137:<Header PO Date>:102′
NAD+BY+<Customer Name/Code>::91′
NAD+SE+<Vendor Name/Code>::92′
NAD+ST+<Ship-to location>::92′
CUX+2:<Currency>:9′
LIN+1++<Vendor Part Number>:VP::91′
PIA+1+<Buyer/Customer Part Number>:BP::92′
QTY+21:<Quantity>:PCE’
PRI+AAA:<Unit Price>:CT::<Unit Price Basic>:PCE’
SCC+1′
QTY+21:<Schedule Line Quantity>:PCE’
DTM+2:<Schedule Line Date>:102′
UNS+S’
UNT+18+1′
UNZ+1+<ICN#>’

EDIFACT ORDERS and X12 850 to IDOC ORDERS Basic Type ORDERS05
Tagged on:                     

2 thoughts on “EDIFACT ORDERS and X12 850 to IDOC ORDERS Basic Type ORDERS05

  • November 8, 2015 at 7:06 am
    Permalink

    Hi,
    Do you have any mapping document for ANSI X12 850 to Orders05 ? Because we are getting issue while repeating same segment with different logic currently we are creating duplicate segment.
    Also do you have any idea about Codelist in B2B cockpit ? how we can call into mapping level after creating code list in b2b TPM.

    Reply
    • November 11, 2015 at 10:05 am
      Permalink

      In this post did included brief source-target mapping for x12 850 as well. If you want to have different logic for same target field, suggest using right click, “Duplicate subtree” feature, then each subtree map it as you like, normally is take some value based on qualifier, and make each subtree independent, this way is easier to extend new different logic for same target field.

      Codelist? Is it like qualifier “BP”,”VP”? not sure how is your requirement “call into mapping level”, normally i just hard-coded those qualifier.

      Regards,
      Yee Loon

      Reply

Leave a Reply

Your email address will not be published.

Time limit is exhausted. Please reload CAPTCHA.