Issue 6.4, December agreed-upon by EDI Working Group of ECR Poland
|
|
- MargaretMargaret Roberts
- 8 years ago
- Views:
Transcription
1 Polska THE ORDERS MESSAGE 97/ D.96A Issue 6.4, December 2012 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed and accepted by the members of EDI Working Group of ECR Poland. The segments and data elements are used and required from commerce partners while exchanging EDI messages. This document is compliant to the standard INVOIC / message. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 1 of 41
2 Document Summary Document Item Current Value Document Title THE ORDERS MESSAGE 97/ D.96A Date Last Modified December 2012 Current Document Issue Issue 6.4 Status Approved Document Description Log of Changes in Issue 6.4 Issue No. Date of Change Changed By Summary of Change 6.0 I 2007 EDI GROUP 6.1 IV 2008 EDI GROUP 6.2 VII 2009 Infinite 6.3 VIII 2012 Infinite 6.4 XII 2012 Comarch Segment addition: FTX registration court, registration number, initial capital, invested capital Segment change: SG 2 NAD buyers name Segment attribute change: SG 2 SG 3 RFF NIP of buyer Segment addition: SG 2 NAD buyer s corporate office NAD segments examples correction Segment addition: PIA: for 14 used as identification for higher level packaging NAD: UD ultimata customer Segments extension: SG 2 NAD supplier identification SG 2 NAD delivery point identification Segment addition: SG 25 FTX product description on line level Qualifiers addition: - BGM segment Blanket order - PRI segment - INF - Information Qualifier addition: - in FTX segment (line level) AAI general information December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 2 of 41
3 Important notices Important: TAX SEGMENT RULE In order to limit the redundancy of data in the documents the EDI Working Group has devised a business rule concerning TAX segments. The rule defined that it is not correct to transmit a tax rate and exemption qualifier in one segment. The following examples define correct EDI segments: TAX+7+VAT +++:::22+S' TAX+7+VAT +++:::7+S' TAX+7+VAT +++:::3+S' TAX+7+VAT +++:::0+S' TAX+7+VAT ++++E' (tax exemption) The following are examples of incorrect segments (containing tax rate and exemption qualifier) : TAX+7+VAT +++:::22+E' TAX+7+VAT +++:::7+E' TAX+7+VAT +++:::3+E' TAX+7+VAT +++:::0+E' Disclaimer Whilst every effort has been made to ensure that the guidelines to use the GS1 standards contained in the document are correct, GS1 and any other party involved in the creation of the document HEREBY STATE that the document is provided without warranty, either expressed or implied, of accuracy or fitness for purpose, AND HEREBY DISCLAIM any liability, direct or indirect, for damages or loss relating to the use of the document. The document may be modified, subject to developments in technology, changes to the standards, or new legal requirements. Several products and company names mentioned herein may be trademarks and/or registered trademarks of their respective companies. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 3 of 41
4 Table of Contents 1. MESSAGE STRUCTURE CHART SEGMENTS LAYOUT Annex 1 : Other qualifiers December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 4 of 41
5 1. MESSAGE STRUCTURE CHART Purchase Order Heading Section UNH - MESSAGE HEADER BGM - Beginning of message DTM - Date of the document DTM - required date of delivery FTX - Free text FTX Free text (registration court and registration number, initial capital, invested capital) SG 1 RFF - Promotion deal number (Message sender reference number) SG 1 DTM reference date SG 2 NAD - Identification of the supplier SG 2 FII - Bank account number SG 2 SG 3 RFF - VAT registration number SG 2 SG 3 RFF additional supplier identification SG 2 NAD - Identification of the buyer SG 2 FII - Bank account number SG 2 SG 3 RFF - VAT registration number SG 2 SG5 CTA- Contact information SG 2 NAD - Identification of the buyer s corporate office SG 2 NAD - Identification of delivery party SG 2 NAD - Identification of the party from where goods will be or have been shipped SG 2 NAD - Identification of ultimate customer SG 7 CUX - currencies SG 9 TDT details of transport Purchase Order Detail Section SG 25 LIN - Line item SG 25 PIA - Additional product id SG 25 IMD - Item description SG 25 QTY - Quantity SG 25 QTY Number of consumer units in the traded unit SG 25 FTX product description on line level SG 25 SG 28 PRI - Net price SG 25 SG 29 RFF - Promotion deal number (Message sender reference number) SG 25 SG 30 PAC Package Purchase Order Summary Section UNS - SECTION CONTROL CNT - Number of line items in message CNT - Total value of the quantity segments at line level in a message UNT - MESSAGE TRAILER Note: The segments agreed as mandatory are written in bold. Note: The mandatory segments that must appear either in Heading Section or in Detail Section are written in bold italic. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 5 of 41
6 Notes: 1. The segments are presented in the sequence in which they appear in the message. The segment or segment group tag is followed by the (M)andatory / (C)onditional indicator, the maximum number of occurrences and the segment description. 2. Reading from left to right, in column one, the data element tags and descriptions are shown, followed by in the second column the status (M or C), the field format, and the picture of the data elements. These first pieces of information constitute the original segment layout. Following the information, specific information is provided in the third, fourth, and fifth columns. In the third column a status indicator for the use of (C)onditional data elements (see 2.1 through 2.3 below), in the fourth column the restricted indicator (see point 3 on the following page), and in the fifth column notes and code values used for specific data elements in the message. 2.1 (M)andatory data elements in segments retain their status in. 2.2 Additionally, there are five types of status for data elements with a (C)onditional status, whether for simple, component or composite data elements. These are listed below and can be identified when relevant by the following abbreviations: - REQUIRED R Indicates that the entity is required and must be sent. - ADVISED A Indicates that the entity is advised or recommended. - DEPENDENT D Indicates that the entity must be sent in certain conditions, as defined by the relevant explanatory note. - OPTIONAL O Indicates that the entity is optional and may be sent at the discretion of the user. - NOT USED N Indicates that the entity is not used and should be omitted. 2.3 If a composite is flagged as N, NOT USED, all data elements within that composite will have blank status indicators assigned to them. 3. Status indicators detailed in the fourth column which directly relate to the code values detailed in the first column may have two values; - RESTRICTED * A data element marked with an asterix (*) in the fourth column is (are) the only codes available for use with this data element, in this segment, in this message. - OPEN All data elements where coded representation of data is possible and a restricted set of code values is not indicated are open (no asterix in fourth column). The available codes are listed in the Data Elements and Code Sets Directory. Code values given in tables have been agreed by the EDI Working Group. The use of other values should be bilaterally agreed. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 6 of 41
7 2. SEGMENTS LAYOUT UNH - M 1 - MESSAGE HEADER Function : To head, identify and specify a message. Segment number : Message reference number M an..14 M Sender's unique message reference. Sequence number of the messages in the interchange. DE 0062 in the UNT will be exactly the same. Sender generated. S009 MESSAGE IDENTIFIER M M 0065 Message type identifier M an..6 M * ORDERS = Purchase order message 0052 Message type version number M an..3 M * D = Draft directory 0054 Message type release number M an..3 M * 96A = Version 96A 0051 Controlling agency M an..2 M * UN = UN/ECE/TRADE/WP.4, United Nations Standard Messages (UNSM) 0057 Association assigned code C an..6 R * 008 = Version control number. This segment is used to head, identify and specify a message. This segment is mandatory. DE's 0065, 0052, 0054, and 0051: Indicate that the message is an UNSM Purchase Order based on the D.96A directory under the control of the United Nations. DE 0057: Indicates that the message is the version 008 of the UNSM Purchase Order. UNH+ME ORDERS:D:96A:UN:008' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 7 of 41
8 BGM - M 1 - Beginning of message Function : To indicate the type and function of a message and to transmit the identifying number. Segment number : 2 C002 DOCUMENT/MESSAGE NAME C R 1001 Document/message name, coded C an..3 R * 220 = Order 1131 Code list qualifier C an..3 N 3055 Code list responsible agency, coded C an..3 D * 1000 Document/message name C an..35 O 50E = Cross docking 221 = Blanket order 1004 Document/message number C an..35 R Order Number assigned by document sender. Cross-docking order number 1225 Message function coded C an..3 R 9 = original 5 = replace 1 = cancellation This segment is mandatory. DE 1004: It is recommended that the length of document number should be restricted to a maximum of 17 characters. BGM December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 8 of 41
9 DTM - M 35 - Date/time/period Function : To specify date, and/or time, or period. Segment number : 3 C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 M * 137 = Document/message date/time 2380 Date/time/period C an..35 R 2379 Date/time/period format qualifier C an..3 R 102 = CCYYMMDD This segment is mandatory. DE 2005: Identification of the 'Document/message date/time' (code value 137) is mandatory in the purchase order message. DTM+137: :102' This example dates the message as the 30th of August December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 9 of 41
10 DTM - M 35 - Date/time/period Function : To specify date, and/or time, or period. Segment number : 3 C507 DATE/TIME/PERIOD M M 2005 Date/time/period qualifier M an..3 M * 2 = Delivery date/time, requested 2380 Date/time/period C an..35 R 63 = Delivery date/time, latest 64 = Delivery date/time, earliest 200 = Pick-up/collection date/time of cargo 2379 Date/time/period format qualifier C an..3 R 102 = CCYYMMDD 203 = CCYYMMDDHHMM This segment is used to specify requested dates concerning the delivery of the goods. DTM+2: :102' This example dates the delivery on the 30th of August December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 10 of 41
11 FTX - C 99 - Free text Function : To provide free form or coded text information Text subject qualifier M an..3 M AAI = general information ZZZ = mutually defined 4453 Text function, coded C an..3 O * 1 = Text for subsequent use. The occurrence of this text does not affect message processing. C107 TEXT REFERENCE C X * 4441 Free text, coded M an..3 M 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O C108 TEXT LITERAL C X 4440 Free text M an..70 M 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 3453 Language, coded C an..3 X ISO 639 two alpha code Segment Notes: This segment is used to provide free form or coded text information for the entire purchase order. Example: FTX+ZZZ+1+001' (e.g. standard text code 001=Special prices effective first of month) Segment Notes (for the segments with X attribute) The complex data element C107 is used providing that trade partners have declared common previously defined code values. The complex data element C108 is used providing that a free text coded usage is impossible. The complex element data 3453 is used providing that uncoded free text was given in C108 data element. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 11 of 41
12 FTX - C 99 - Free text Function : To provide free form or coded text information Text subject qualifier M an..3 M OSI = other service information 4453 Text function, coded C an..3 O * 1 = Text for subsequent use. The occurrence of this text does not affect message processing. C107 TEXT REFERENCE C X * 4441 Free text, coded M an..3 M 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O C108 TEXT LITERAL C X 4440 Free text M an..70 M 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 3453 Language, coded C an..3 X ISO 639 two alpha code Segment Notes: This segment is used to provide free form or coded text information for the entire purchase order. It contains the following information: 1. registration court and registration number, 2. initial capital, invested capital According to Polish Law 1 this segment must be used in the message if the issuer of the message is obliged by the law. Przykład: FTX+OSI+1++ KRS Sąd Rejonowy w Poznaniu: XXI Wydział Gospodarczy Krajowego Rejestru Sądowego: initial capital PLN: invested capital PLN+PL ' 1 Dz.U nr 208 poz Ustawa z dnia 18 października 2006 r. o zmianie ustawy o Krajowym Rejestrze Sądowym oraz niektórych innych ustaw December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 12 of 41
13 SG1 - C 10 - RFF-DTM RFF - M 1 - Reference Function : To specify a reference. Segment number : 7 C506 REFERENCE M M 1153 Reference qualifier M an..3 M PD = Promotion deal number VN = order number supplier 1154 Reference number C an..35 R Segment Notes: This segment is used to provide other references concerning the purchase order e.g. promotion number. RFF+PD ' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 13 of 41
14 SG2 - C 99 - NAD-LOC-SG3-SG5 NAD - M 1 - NAME AND ADDRESS Function: To specify the name/address and their related function Segment number: 9 C * DESCRIPTION OM 3035 Party qualifier M an..3 M SU = Supplier CO82 PARTY IDENTIFICATION C A DETAILS 1131 Party id. identification M M GS1 (former ) Location Number - Format n13 an Code list qualifier C N an Code list responsible agency, C an..3 R * 9 = GS1 (former ) (International Article coded Numbering Association) C058 NAME AND ADDRESS C N C080 PARTNER NAME C R 3036 Partner name M an 35 M Full or abbreviated partner name 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3045 Partner name format, coded C an 3 O C059 STREET C R Street and number in a readable format 3042 Street and number M an..35 M 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3164 City C an..35 R City in a redable format 3229 Voivodship C an..9 N 3251 Postal code C an..9 R 3207 Country, coded C an..9 R Two-character code ISO3166 PL Poland Segment notes This segment is used to identify trading partners participating in the ordering process. Identification of the supplier. This segment is mandatory. Example: NAD+SU ::9++Firma ABC::::: +ul. Baby Jagi 1:::+Poznań PL December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 14 of 41
15 SG2 - C 99 - NAD-LOC-FII - SG3-SG5 FII - C 5 - Financial institution information Function : To identify an account and a related financial institution. Segment number : Party qualifier M an..3 M RB = Receiving financial institution C078 ACCOUNT IDENTIFICATION C R 3194 Account holder number C an..35 R This segment is used to indicate the suppliers' bank account to which the payment should be done. FII+RB ' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 15 of 41
16 SG2 - C 99 - NAD-LOC- FII - SG3-SG5 SG3 - C 10 - RFF RFF - M 1 - Reference Function : To specify a reference. Segment number : 12 C506 REFERENCE M M 1153 Reference qualifier M an..3 M * VA = VAT registration number 1154 Reference number C an..35 R This segment is used to specify reference numbers related to the party specified in the previous NAD segment. It is used to provide information on VAT registration number of the supplier. The number should be given as a set of digits or as a set of digits separated with hyphens. RFF+VA: ' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 16 of 41
17 SG2 - C 99 - NAD-LOC- FII - SG3-SG5 SG3 - C 10 - RFF RFF - M 1 - Reference Function : To specify a reference. Segment number : 12 C506 REFERENCE M M 1153 Reference qualifier M an..3 M * API = Additional Party Identification 1154 Reference number C an..35 R This segment is used to specify the number of the delivering party according to the buyer (e.g. delivery party number according to MAKRO). The number should be given as a set of digits or as a set of digits separated with hyphens. RFF+API:AB123456' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 17 of 41
18 SG2 - C 99 - NAD-LOC-SG3-SG5 NAD - M 1 - NAME AND ADDRESS Function: To specify the name/address and their related function Segment number: 9 C * DESCRIPTION OM 3035 Party qualifier M an..3 M BY = buyer CO82 PARTY IDENTIFICATION C A DETAILS 1133 Party id. identification M M GS1 (former ) Location Number - Format n13 an Code list qualifier C N an Code list responsible agency, C an..3 R * 9 = GS1 (former ) (International Article coded Numbering Association) C058 NAME AND ADDRESS C N C080 PARTNER NAME C R 3036 Partner name M an 35 M Full or abbreviated partner name 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3045 Partner name format, coded C an 3 O C059 STREET C R Street and number in a readable format 3042 Street and number M an..35 M 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3164 City C an..35 R City in a redable format 3229 Voivodship C an..9 N 3251 Postal code C an..9 R 3207 Country, coded C an..9 R Two-character code ISO3166 PL Poland Segment notes This segment is used to identify trading partners participating in the ordering process. Identification of recipient and supplier of goods and services is obligatory in the ORDERS message. According to Polish Law this segment must contain full address and name of the company issuing an ORDER message. Both parties are identified by means of GS1 (former ) Global Location Numbers and their full or abbreviated names and addresses. According to Polish Law 2 this segment must be used in the message if the issuer of the message is obliged by the law. Example: NAD+BY ::9++Firma ABC::::: +ul. Baby Jagi 1:::+Poznań PL 2 Dz.U nr 208 poz Ustawa z dnia 18 października 2006 r. o zmianie ustawy o Krajowym Rejestrze Sądowym oraz niektórych innych ustaw December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 18 of 41
19 SG2 - C 99 - NAD-LOC-FII - SG3-SG5 FII - C 5 - Financial institution information Function : To identify an account and a related financial institution. Segment number : Party qualifier M an..3 M PB = Paying financial institution C078 ACCOUNT IDENTIFICATION C R 3194 Account holder number C an..35 R This segment is used to indicate the buyers bank account to which the payment should be done. Should be sent for control purposes. FII+PB ' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 19 of 41
20 SG2 - C 99 - NAD-LOC- FII - SG3-SG5 SG3 - C 10 - RFF RFF - M 1 - Reference Function : To specify a reference. Segment number : 12 C506 REFERENCE M M 1153 Reference qualifier M an..3 M * VA = VAT registration number 1154 Reference number C an..35 R This segment is used to specify reference numbers related to the party specified in the previous NAD segment. It is used to provide information on VAT registration number of the buyer. The number should be given as a set of digits or as a set of digits separated with hyphens. According to Polish Law 3 this segment must be used in the message if the issuer of the message is obliged by the law. RFF+VA: ' 3 Dz.U nr 208 poz Ustawa z dnia 18 października 2006 r. o zmianie ustawy o Krajowym Rejestrze Sądowym oraz niektórych innych ustaw December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 20 of 41
21 SG2 - C 99 - NAD-LOC-FII - SG3-SG5 SG5 - C 5 - CTA- CTA - M 1 - Contact information Function : To identify a person or a department to whom communication should be directed. Segment number : Contact function, coded C an..3 R OC = Order contact C056 DEPARTMENT OR EMPLOYEE DETAILS C O 3413 Department or employee identification C an..17 O 3412 Department or employee C an..35 O This segment is used to identify contact details (name or company department) for the party specified in the previous NAD segment responsible for placing this order. CTA+OC+:PETER FORGET' PETER FORGET is the person to whom any questions concerning this order should be asked. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 21 of 41
22 SG2 - C 99 - NAD-LOC-SG3-SG5 NAD - M 1 - NAME AND ADDRESS Function: To specify the name/address and their related function Segment number: 9 C * DESCRIPTION OM 3035 Party qualifier M an..3 M BCO = buyer s corporate office CO82 PARTY IDENTIFICATION C A DETAILS 1135 Party id. identification M M GS1 (former ) Location Number - Format n13 an Code list qualifier C N an Code list responsible agency, C an..3 R * 9 = GS1 (former ) (International Article coded Numbering Association) C058 NAME AND ADDRESS C N C080 PARTNER NAME C R 3036 Partner name M an 35 M Full or abbreviated partner name 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3045 Partner name format, coded C an 3 O C059 STREET C R Street and number in a readable format 3042 Street and number M an..35 M 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3164 City C an..35 R City in a redable format 3229 Voivodship C an..9 N 3251 Postal code C an..9 R 3207 Country, coded C an..9 R Two-character code ISO3166 PL Poland Segment notes This segment is used to identify trading partners participating in the ordering process. Parties are identified by means of GS1 (former ) Global Location Numbers and their full or abbreviated names and addresses. According to Polish Law 4 this segment must be used in the message if the issuer of the message is obliged by the law. Example: NAD+BCO ::9++Firma ABC::::: +ul. Baby Jagi 1:::+Poznań PL 4 Dz.U nr 208 poz Ustawa z dnia 18 października 2006 r. o zmianie ustawy o Krajowym Rejestrze Sądowym oraz niektórych innych ustaw December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 22 of 41
23 SG2 - C NAD-LOC- FII - SG3-SG5 NAD - M 1 - NAME AND ADDRESS Function: To specify the name/address and their related function Segment number: 9 C * DESCRIPTION OM 3035 Party qualifier M an..3 M DP = Delivery party CO82 PARTY IDENTIFICATION C A DETAILS 1137 Party id. identification M M GS1 (former ) Location Number - Format n13 an Code list qualifier C N an Code list responsible agency, C an..3 R * 9 = GS1 (former ) (International Article coded Numbering Association) C058 NAME AND ADDRESS C N C080 PARTNER NAME C R 3036 Partner name M an 35 M Full or abbreviated partner name 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3036 Partner name C an 35 O 3045 Partner name format, coded C an 3 O C059 STREET C R Street and number in a readable format 3042 Street and number M an..35 M 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3042 Street and number/post-box no. C an..35 O 3164 City C an..35 R City in a redable format 3229 Voivodship C an..9 N 3251 Postal code C an..9 R 3207 Country, coded C an..9 R Two-character code ISO3166 PL Poland This segment is used to identify the delivery party. NAD+DP ::9++Firma ABC::::: +ul. Baby Jagi 1:::+Poznań PL December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 23 of 41
24 SG2 - C 99 - NAD-LOC- FII - SG3-SG5 NAD - M 1 - Name and address Function : To specify the name/address and their related function Segment number : Party qualifier M an..3 M SF = Ship from C082 PARTY IDENTIFICATION DETAILS C A 3039 Party id. identification M an..35 M GS1 (former ) Location Number - Format n Code list qualifier C an..3 N 3055 Code list responsible agency, coded C an..3 R * 9 = GS1 (former ) (International Article Numbering association) This segment is used to identify the party from where goods will be or have been shipped. NAD+SF ::9' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 24 of 41
25 SG2 - C 99 - NAD-LOC- FII - SG3-SG5 NAD - M 1 - Name and address Function : To specify the name/address and their related function Segment number : Party qualifier M an..3 M UD = Ultimate Customer C082 PARTY IDENTIFICATION DETAILS C A 3039 Party id. identification M an..35 M GS1 (former ) Location Number - Format n Code list qualifier C an..3 N 3055 Code list responsible agency, coded C an..3 R * 9 = GS1 (former ) (International Article Numbering association) This segment is used to identify the party which is the final recipient of goods. NAD+UD ::9' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 25 of 41
26 SG7 - C 1 - CUX - DTM CUX - M 1 - Currencies Function : To specify currencies used in the transaction and relevant details for the rate of exchange. Segment number : 16 C504 CURRENCY DETAILS C R 6347 Currency details qualifier M an..3 M * 2 = waluta odniesienia 6345 Currency, coded C an..3 R ISO 4217 trzy znakowy, alfanumeryczny kod 6343 Currency qualifier C an..3 R * 9 = waluta zamówienia Segment Notes: This segment is used to specify currency information for the complete order. The CUX segment is mandatory for international exchanges. It can be omitted when transaction is not international. The code for the Polish currency is PLN according to ISO. Examlpe: CUX+2:PLN:9' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 26 of 41
27 SG9 - C 10 - TDT TDT - C 1 - Details of transport Function : To specify the transport details such as mode of transport, means of transport, its conveyance reference number and the identification of the means of transport. Segment number : Transport stage qualifier M an..3 M 20 = Main-carriage transport 8028 Conveyance reference number C an..17 O Reference Number covering the transport C220 MODE OF TRANSPORT C A 8067 Mode of transport, coded C an..3 R 10 = Maritime transport 20 = Rail transport 30 = Road transport 40 = Air transport 60 = Multimodal transport 8066 Mode of transport C an..17 N C228 TRANSPORT MS C N C040 CARRIER C O 3127 Carrier identification C an 17 R GLN of the carrier 1131 Code list qualifier C an 17 O 3055 Code list responsible agency, coded C an 3 R 9 = GS1 ( International) Segment Notes: This segment is used to specify transport instructions for the whole Purchase Order, such as requesting an express transport service. Example: TDT ' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 27 of 41
28 SG25 - C LIN-PIA-IMD-MEA-QTY-ALI-DTM-MOA-GIN-QVR-FTX-SG28-SG29-SG30-SG33-SG34- SG35-SG39-SG45 LIN - M 1 - Line item Function : To identify a line item and configuration. Segment number : Line item number C n..6 R Application generated number of the count of the order lines Action request/notification, coded C an..3 N C212 ITEM NUMBER IDENTIFICATION C D 7140 Item number C an..35 R Format n..14-8, UPC-A, -13, or this is the number of the article being ordered Item number type, coded C an..3 R * EN = EU =.UCC Segment Notes: This segment is used to identify the item being ordered. This segment is mandatory. For the trade item identification /UCC Global Trade Item Numbers should be used. Segment Notes for data elements with attribute D: Complex element C212 is used only to identify /UPC codes. Example: LIN :EU' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 28 of 41
29 SG25 - C LIN-PIA-IMD-MEA-QTY-ALI-DTM-MOA-GIN-QVR-FTX-SG28-SG29-SG30-SG33-SG34- SG35-SG39-SG45 PIA - C 25 - Additional product id Function : To specify additional or substitutional item identification codes. Segment number : Product id. function qualifier M an..3 M * 1 = Additional identification C212 ITEM NUMBER IDENTIFICATION M M 7140 Item number C an..35 R 7143 Item number type, coded C an..3 R BP = Buyer's part number SA = Supplier's article number 1131 Code list qualifier C an..3 N EN Code list responsible agency, coded C an..3 O 91 = Assigned by supplier or supplier's agent 92 = Assigned by buyer or buyer's agent 9 = This segment is used to specify additional or substitutional item identification codes such as a buyer's, or seller's item number Segment 7143 wit qualifier is used to identify higher level of packaging goods. Example: PIA+1+AEX0143:BP' PIA :EN::9 December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 29 of 41
30 SG25 - C LIN-PIA-IMD-MEA-QTY-ALI-DTM-MOA-GIN-QVR-FTX-SG28-SG29-SG30-SG33-SG34- SG35-SG39-SG45 IMD - C 99 - Item description Function : To describe an item in either an industry or free format. Segment number : Item description type, coded C an..3 O * B = Code and text 7081 Item characteristic, coded C an..3 O C273 ITEM DESCRIPTION C A C = Code (from industry code list) ANM = article name 7009 Item description identification C an..17 O CU = Consumer unit (GS1 (former ) Code) 1131 Code list qualifier C an..3 O VQ = Variable quantity product (GS1 (former ) Code) 3055 Code list responsible agency, coded C an..3 O 9 = GS1 (former ) (International Article Numbering association) 7008 Item description C an..35 O Article name 7008 Item description C an..35 O This segment is used to describe the current line item. It is recommended that this segment only be used for coded descriptions. Data element 7008 in clear text should only be used when no product code is available or when free-form descriptions are required by trading partners. If the coded description is used, the qualifiers provided in Annex should be used. IMD+C+CU' IMD+B++:::CORN CRISPIES:CASE' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 30 of 41
31 SG25 - C LIN-PIA-IMD-MEA-QTY-ALI-DTM-MOA-GIN-QVR-FTX-SG28-SG29-SG30-SG33-SG34- SG35-SG39-SG45 QTY - C 10 - Quantity Function : To specify a pertinent quantity. Segment number : 51 C186 QUANTITY DETAILS M M 6063 Quantity qualifier M an..3 M * 21 = Ordered quantity 59 = Number of consumer units in the traded unit 192 = Free goods quantity 6060 Quantity M n..15 M 6411 Measure unit qualifier C an..3 D KGM = kilogram This segment is used to specify the total quantity ordered for the current line identified in the LIN segment. This segment is mandatory. QTY+21:48:KGM' DE 6411: This DE is only used if the product ordered is a variable quantity product, see Annex. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 31 of 41
32 FTX - C 99 - Free text Function : To provide free form or coded text information Text subject qualifier M an..3 M ZZZ = mutually defined AAI = general information 4453 Text function, coded C an..3 O * 1 = Text for subsequent use. The occurrence of this text does not affect message processing. C107 TEXT REFERENCE C X * 4441 Free text, coded M an..3 M 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 O C108 TEXT LITERAL C X 4440 Free text M an..70 M 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 4440 Free text C an..70 O 3453 Language, coded C an..3 X ISO 639 two alpha code Segment Notes: This segment is used to provide free form or coded text information for the entire purchase order. Example: FTX+ZZZ+1++GREEN+PL' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 32 of 41
33 SG25 - C SG28 - C LIN-PIA-IMD-MEA-QTY-ALI-DTM-MOA-GIN-QVR-FTX-SG28-SG29-SG30-SG33-SG34- SG35-SG39-SG PRI-CUX-DTM PRI - M 1 - Price details Function : To specify price information. Segment number : 58 C509 PRICE INFORMATION C R 5125 Price qualifier M an..3 M AAA = Calculation net* INF = Information ** 5118 Price C n..15 R 5375 Price type, coded C an 3 O 5387 Price type qualifier C an 3 R NTP = Net unit price RTP = Retail price 5284 Unit price basis C an 3 D 6411 Measure unit qualifier C an 3 D KGM = kilogram This segment is used to detail the price for the current product identified in the LIN segment. * - the price stated is the net price including all allowances and charges and excluding taxes. ** - the price stated is for information PRI+AAA:14.58' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 33 of 41
34 SG25 - C LIN PIA IMD MEA QTY ALI DTM MOA GIN QVR FTX SG28 SG29 SG30 SG33 SG34 SG35 SG39 SG45 SG29 - C 29 - RFF-DTM RFF - M 1 - Reference Function : To specify a reference. Segment number : 7 C506 REFERENCE M M 1153 Reference qualifier M an..3 M PD = Promotion deal number 1154 Reference number C an..35 R Segment Notes: This segment is used to provide promotion deal number for each line item in the message. RFF+PD ' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 34 of 41
35 SG25 - C SG30 - C LIN PIA IMD MEA QTY ALI DTM MOA GIN QVR FTX SG28 SG29 SG30 SG33 SG34 SG35 SG39 SG PAC MEA QTY DTM PAC - M 1 - Function : To describe the number and type of packages/physical units. Segment number : Number of packages C n..8 O Number of packages of ordered item C531 PACKAGING DETAILS C A Packaging level, coded C an..3 N 7233 Packaging related information, coded C an..3 O 7073 Packaging terms and conditions, coded C an..3 O 3 = Packaging cost not charged (returnable) C202 PACKAGE TYPE C O 7065 Type of packages identification C an..17 R CT Carton 1131 Code list qualifier C an..3 O 3055 Code list responsible agency, coded C an..3 D 7064 Type of packages C an..3 O C402 PACKAGE TYPE IDENTIFICATION C N 7077 Item description type, coded M an Type of packages M an Item number type, coded C an Type of packages C an Item number type, coded C an..3 C532 RETURNABLE PACKAGE DETAILS C D 8395 Returnable package freight payment responsibility, coded C an..3 O 1 = Paid by customer 3 = Paid by supplier 8393 Returnable package load contents, coded C an..3 N December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 35 of 41
36 Segment Notes: This segment is used to provide information weather the packaging is returnable. Example: PAC + +::3+ BS++ 3' Data Elements with D attribute notes: C532 element is used only if the packaging is returnable. This element defines the party who pays for the return of packaging. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 36 of 41
37 UNS - M 1 - SECTION CONTROL Function : To separate header, detail, and summary sections of a message. Segment number : Section identification M a1 M * S = Detail/summary section separation This segment is used to separate the detail and summary sections of the message. This segment is mandatory. UNS+S' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 37 of 41
38 CNT - C 10 - Control total Function : To provide control total. Segment number : 93 C270 CONTROL M M 6069 Control qualifier M an..3 M * 2 = Number of line items in message 6066 Control value M n..18 M This segment is used to provide message control totals. This segment is mandatory. CNT+2:4' There are four LIN segments in the current message. December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 38 of 41
39 CNT - C 10 - Control total Function : To provide control total. Segment number : 93 C270 CONTROL M M 6069 Control qualifier M an..3 M * 1 = Total value of the quantity segments at line level in a message 6066 Control value M n..18 M This segment is used to provide message control totals. This segment is mandatory. CNT+1:4' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 39 of 41
40 UNT - M 1 - MESSAGE TRAILER Function : To end and check the completeness of a message. Segment number : Number of segments in a message M n..6 M The total number of segments in the message is detailed here Message reference number M an..14 M The message reference numbered detailed here should equal the one specified in the UNH segment. This segment is a mandatory UN/ segment. It must always be the last segment in the message. This segment is mandatory. UNT+48+ME000001' December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 40 of 41
41 3. Annex 1 : Other qualifiers The qualifers listed below are suggested to be used in segments occuring in the message. The use of them requires bilateral agreement between the exchange partners. Segment DTM 3 DE 2005: Date/time/period Other recommended qualifiers: 10 = Shipment date/time, requested 11 = Despatch date and or time 15 = Promotion start date/time - Note 1 37 = Ship not before date/time 38 = Ship not later than date/time 61 = Cancel if not delivered by this date 63 = Delivery date/time, latest 64 = Delivery date/time, earliest 69 = Delivery date/time, promised for 77 = Requested for delivery week commencing (GS1 (former ) Code) 200 = Pick-up/collection date/time of cargo 263 = Invoicing period 282 = Confirmation date lead time 43E = Cancel if not shipped/despatched by this date (GS1 (former ) Code) Note 1: Code value 15 should only be used in this position in the message where no promotion reference exists or is not yet available SG 2 NAD 9 DE 3035: Party qualifier Other recommended qualifiers: OB = Ordered by DP = Delivery party SF = Ship from SG 25 IMD 41 DE 7009: Other recommended qualifiers: CU = Consumer unit (GS1 (former ) Code) DU = Despatch unit (GS1 (former ) Code) TU = Traded unit (GS1 (former ) Code) VQ = Variable quantity product (GS1 (former ) code) SG 25 QTY 43 DE 6411: Unit of measure Other recommended qualifiers: KGM = kilogram MTK = square metre LTR = litr PCE = piece PR = pair TNE = metric ton (1000kg) December 2012, Issue 6.4 All contents copyright Instytut Logistyki I Magazynowania Page 41 of 41
Issue 6.7, April 2010. agreed-upon by EDI Working Group of ECR Poland
Polska THE CORRECTING INVOICE MESSAGE EAN97/EDIFACT D.96A Issue 6.7, April 2010 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed
More informationIssue 1.9, April 2010. agreed-upon by EDI Working Group of ECR Poland
Polska THE DESADV MESSAGE EANCOM97/EDIFACT D.96A Issue 1.9, April 2010 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed and accepted
More informationTHE INVOIC MESSAGE EANCOM97/EDIFACT D.96A
Polska THE INVOIC MESSAGE EAN97/EDIFACT D.96A Issue 1.0, 12.2013 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed and accepted
More informationIssue 1.1, February 2009. agreed-upon by EDI Working Group of ECR Poland
Polska THE REMADV MESSAGE EAN97/EDIFACT D.96A Issue 1.1, February 2009 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed and accepted
More informationTHE INVOIC MESSAGE EANCOM97/EDIFACT D.96A
Polska THE INVOIC MESSAGE EAN97/EDIFACT D.96A Issue 9.0, 10.2015 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed and accepted
More informationPARTY INFORMATION MESSAGE. PARTIN Version 1.0. agreed-upon by EDI Working Group of ECR Poland
PARTY INFORMATION MESSAGE PARTIN Version 1.0 EAN 97/EDIFACT D.96A agreed-upon by EDI Working Group of ECR Poland The document contains only these that segments and data elements that were agreed and accepted
More informationPRICE/SALES CATALOGUE MESSAGE PRICAT. Version 1.0. agreed-upon by EDI Working Group of ECR Poland
PRICE/SALES CATALOGUE MESSAGE PRICAT Version 1.0 EAN 97/EDIFACT D.96A agreed-upon by EDI Working Group of ECR Poland The document contains only these that segments and data elements that were agreed and
More informationINVENTORY REPORT MESSAGE INVRPT. Version 1.2. agreed-upon by EDI Working Group of ECR Poland
INVENTORY REPORT MESSAGE INVRPT Version 1.2 EANCOM 97/EDIFACT D.96A agreed-upon by EDI Working Group of ECR Poland The document contains only these that segments and data elements that were agreed and
More informationPURCHASE ORDER RESPONSE
EDI GUIDELINE for PURCHASE ORDER RESPONSE Message Type ORDRSP Version 1 Release 921 07/00 Seite 1 Table of Contents PURCHASE ORDER RESPONSE Message Layout Diagram... 3 Explanatory Requirements... 3 Segment
More informationORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version 92.1. 02/2011 Page 1
EDI GUIDELINE for ORDERS 92.1 Message Type ORDERS, ORDCHG Version 1 Release 921 02/2011 Page 1 Table of Contents PURCHASE ORDER Message Layout Diagram... 3 Explanatory Requirements... 3 Segment / Element
More informationEANCOM D.96A Version: 007 Print: 01.12.98 EAN ORDERS D.96A DE
UNB INTERCHANGE HEADER M 1 Is used to start, identify and specify an interchange. S001 Syntax identifier M 0001 Syntax identifier M a4 Use of the character set UNOC (Version 2) 0002 Syntax version number
More informationBulk EDIFACT ASN MESSAGE FORMAT
Bulk EDIFACT ASN MESSAGE FORMAT A TECHNICAL GUIDE FOR SUPPLIERS 9 th October, 2008 Page 1 of 17 Issue 2.1 TABLE OF CONTENTS 1. OVERVIEW... 3 1.1 Introduction... 3 2. SEGMENTS LAYOUT... 4 2.1 Legend...
More informationMedia Saturn EDI Application Documentation
Media Saturn EDI Application Documentation ORDRSP D.01B Outbound VMI Rules Message structure Segment details Version: 2.0 Date: June 8, 2011 Status: Final SA2 Exchange GmbH 1 Media Saturn ORDRSP D.01B
More informationT.8 USING THE INVOICE FOR BILLING AND FOR DEBIT AND CREDIT NOTES
T.8 USING THE INVOICE FOR BILLING AND FOR DEBIT AND CREDIT NOTES SECTION T.8 IS TO BE REGARDED AS PROVISIONAL: A FULL REVISION WILL BE ISSUED EARLY IN 1998. T.8.1 PRINCIPLES The INVOIC message may be used
More informationPurchase Orders Message ORDERS (EDIFACT D97A)
Purchase Orders Message ORDERS (EDIFACT D97A) VERSION: 1.0 Author: Seagate B2B Notes: EDIFACT ORDERS Message to be d with OEM, Distribution or Retail partners. ORDERS Purchase Order Message... Page UNB
More informationGlobal EDI Clearing Center (GECC)
Global EDI Clearing Center (GECC) INVOIC UN D96A Page 1 of 124 INVOIC Invoice Message Introduction: A message claiming payment for goods or services supplied under conditions agreed between the seller
More informationEDI Guideline KION Group Orders based on EDIFACT ORDERS D.96A Version 1.04 13.02.2014
EDI Guideline KION Group Orders based on Version 1.04 13.02.2014 IT-Solutions for the KION Group Page 1 of 37 EDI Guideline KION Group Orders History: Version 1.0-08.10.2010 Initial release Version 1.01-08.07.2011
More informationORDERS. Purchase order message. Edition 2014
EANCOM 2002 S4 Edition 2014 1. Introduction... 2 2. Message Structure Chart... 3 3. Branching Diagram... 6 4. Segments Description... 18... 26 6. Example(s)... 138 EANCOM 2002 S4 The Messages 1. Introduction
More informationMagyar Hipermarket Kft. EDI guide PURCHASE ORDER MESSAGE ORDERS EDIFACT D.96A
1 Magyar Hipermarket Kft. EDI guide PURHASE ORDER MESSAGE ORDERS EDIFAT D.96A UNH - M 1 - MESSAGE HEADER Function: To head, identify and specify a message 0062 Message reference number an..14 M Senders
More informationHella EDIFACT ORDERS
Message Implementation Documentation Hella EDIFACT ORDERS based on ORDERS Purchase order message UN D.96A S3 Structure Chart Branching Diagram Segment Details Version: 96 Variant: A Issue date: 14.11.2006
More informationAdobe - EDIFACT D97.A ORDERS
Adobe - EDIFACT D97.A ORDERS Purchase Order Message Shrink Wrap Product Version: UNEDIFACT D97A ORDERS Company: Adobe Modified: 9/30/2015 Table of Contents ORDERS Purchase order message... 1 UNB INTERCHANGE
More informationThis document is for EDI-administrators who will implement this EDI-guide to be able to receive EDIFACT orders from Bosch Rexroth AG.
Who should read this document? This document is for EDI-administrators who will implement this EDI-guide to be able to receive EDIFACT orders from Bosch Rexroth AG. Explanation of usage: First of all,
More informationEDI F GROUP A/S INVOICE. Fona. Document: EDIFACT UserGuide GB-INVOIC_IBM-draft1 Date: 5/94-2008 Version: V1.0.0A Page 0 of 43. ecommerce ServiceCenter
EDI INVOICE Fona Page 0 of 43 HANCOM DESCRIPTION F GROUP INVOICE Content This document describes the requirements to an EDIFACT INVOIC from a supplier to. The message can be generated in version D93A or
More informationPayment on Receipt EDIFACT INVOIC D97.A
Payment on Receipt EDIFACT INVOIC D97.A EDI Implementation Guideline Version 2.5 / January 2004 Authors : Ulrich Freimuth Patrick Emminghaus This document provides the specific description of a subset
More informationORDCHG Purchase Order Change Message Subject for application in the European Steel Industry
ORDCHG Purchase Order Change Message Subject for application in the European Steel Industry Version January 2000 Corporate Factory Ph. D. Sarraute EDIFER WORKING GROUP - Message development PURCHASE ORDER
More information5.0 Detailed guidelines of purchase order response (ORDRSP Version 1 EDIFACT D 96B) usage within Volvo.
5.0 Detailed guidelines of purchase order response (ORDRSP Version 1 EDIFACT D 96B) usage. 5.1 General. This document describes Volvo s application of the EDIFACT message for purchase order response (ORDRSP)
More informationINVOIC Invoice message
INVOIC Invoice message EDIFACT/D98B/INVOIC: INVOIC Invoice message Version: 1. Final Author: DSV EDI team Company: DSV Publication: 16-4-21 16-4-21 Invoice message - INVOIC Table of Contents INVOIC Invoice
More informationZF Group North American Operations. EDI Implementation Guide
EDI Implementation Guide EDIFACT DESADV D.97A Version 1.4 Authors: ZF NAO EDI Team Publication Date: April 10, 2003 Created: April 10, 2003 Modified: June 7, 2005 Table of Contents Introduction... 1 ZF
More informationORDERS Purchase Order Message
ORDERS Purchase Order Message UN/EDIFACT Version D.93A ERICO International 31700 Solon Rd. Solon, OH 44139 ii Preface Purpose and Scope The purpose of this guide is to provide ERICO s trading partners
More informationDESADV DESPATCH ADVICE. BCBG Profile. Message Implementation Guidelines Version: 1.2 Draft
DESADV DESPATCH ADVICE BCBG Profile Message Implementation Guidelines Version: 1.2 Draft Author: Carrefour/Agnès Martin Publication: April 24 th 2007 otes: DESADV EACOM D.96A List of See page 2 modifications
More informationHella EDIFACT INVRPT
Message Documentation Hella EDIFACT INVRPT based on INVRPT Inventory report message UN D.97A S3 Structure Chart Branching Diagram Segment Details Version: 97 Variant: A Issue date: 28.08.2007 Top of Page
More informationAleph Requirements for EDI -Outgoing and Incoming Messages
Aleph Requirements for EDI -Outgoing and Incoming Messages CONFIDENTIAL INFORMATION The information herein is the property of Ex Libris Ltd. or its affiliates and any misuse or abuse will result in economic
More informationTHE DELIVERY FORECAST MESSAGE DELFOR EDIFACT D.96A
THE DELIVERY FORECAST MESSAGE DELFOR EDIFACT D.96A Version 1.1 Author: Torbjörn Grahm / Encode AB Change log: 2015-03-02 Hans Sturesson Added status 3 on G12/SCC 1 P a g e THE DELIVERY FORECAST MESSAGE
More informationEANCOM INVOICES CROSS DOCK MESSAGE FORMAT A TECHNICAL GUIDE FOR SUPPLIERS
EANCOM INVOICES CROSS DOCK MESSAGE FORMAT A TECHNICAL GUIDE FOR SUPPLIERS B2B70.13.17 Page 1 of 26 15/07/2013 TABLE OF CONTENTS 1. OVERVIEW...3 1.1 Introduction...3 2. SEGMENTS LAYOUT...4 3. SAMPLE OF
More informationINVOIC. Invoice message. Edition 2014
EANCOM 2002 S3 Edition 2014 1. Introduction... 2 2. Message Structure Chart... 3 3. Branching Diagram... 6 4. Segments Description... 18... 27 6. Example(s)... 135 EANCOM 2002 S3 The Messages 1. Introduction
More informationS.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT
S.2 STRUCTURE OF AN EDIFACT TRANSMISSION This section is substantially based on the ISO 9735 document: EDIFACT application level syntax rules, first released on 1988-07-15, amended and reprinted on 1990-11-01,
More informationEDIFACT DESADV D.97A for suppliers (Benteler Europe)
Message Implementation Guideline suppliers (Benteler Europe) based on DESADV Despatch advice message UN D.97A S3 Version: 1.1 Variant: 1 Issue date: 17.03.2015 Author: Benteler Deutschland GmbH 1 Introduction.
More informationEDI specifications. between. BLANCO GmbH + Co KG referred to in the following as BLANCO. and its business partners (suppliers)
EDI specifications For the INTERFACE between BLANCO GmbH + Co KG referred to in the following as BLANCO and its business partners (suppliers) 1/13 1. INTRODUCTION 1.1. What is EDI? EDI stands for Electronic
More informationEDIFACT ORDRSP D99.B Formal Description of Segments Segment: Serial. No.: Level: Service string advice UNA Description: UNA
Formal Description of Segments UNA Serial. No.: 1 Level: 0 Service string advice UNA UNA UNA C M UNA UNA1 Component data element separator M an1 M : UNA2 Data element separator M an1 M + UNA3 Decimal notation
More informationORDERS Purchase Order
ORDERS Purchase Order APEX Profile Message Implementation Guidelines Version: 1.3 Final Author: Carrefour/K.Gnaba Publication: June 25 th 2008 Notes: ORDERS EANCOM D.01B List of See page 2 modifications
More informationRevision : 1 Date : 98-09-08
UN/EDIFACT UNITED NATIONS STANDARD MESSAGE (UNSM) EDI data tracking message Message Type : DATRAK Version : 0 Release : 0 Contr. Agency: UN Revision : 1 Date : 98-09-08 SOURCE: Development Group D13 CONTENTS
More informationEDI Guideline KION Group DESADV based on EDIFACT DESADV D.96A Version 1.20 29.10.2014
EDI Guideline KION Group DESADV based on Version 1.20 29.10.2014 IT-Solutions for the KION Group Page 1 of 36 EDI Guideline KION Group History: Version 1.00-19.03.2014 Initial release Version 1.10-08.08.2014
More informationDELJIT D97A / CALDEL
CALL-OFF DELJIT D97A / CALDEL Message Implementation Guideline The detail description of DELJIT / CALDEL D97A message used for EDI communication between ŠKODA AUTO a. s. and its suppliers Call-offs of
More informationEconomic and Social Council
UNITED NATIONS E Economic and Social Council ECONOMIC COMMISSION FOR EUROPE Distr. RESTRICTED TRADE/WP.4/R.1149 20 June 1995 Working Party on Facilitation of International Trade Procedures (Item 4 of the
More informationE A N C O M - MESSAGE
EANCO-essage: ORDERS Page 1 of 10 dm drogerie markt GmbH Günter-Bauer-Straße 1 5073 Wals-Himmelreich E A N C O - ESSAGE O R D E R S D.01B EANCO-essage: ORDERS Page 2 of 10 Table of contents 1 Prerequisites
More informationGrundfos EDIFACT D.96.A
Grundfos EDIFACT D.96.A Title INVRPT - Documentation (Forecast) Create Date 29-05-2007 Last Update 31-10-2014, version 1.09 Author Grundfos EDI Team Owner Grundfos Group EDI Team 1 Prologue Introduction
More informationDESADV. Despatch advice message. Edition 2014
EANCOM 2002 S4 Edition 2014 1. Introduction... 2 2. Message Structure Chart... 7 3. Branching Diagram... 9 4. Segments Description... 18... 23 6. Example(s)... 95 EANCOM 2002 S4 The Messages 1. Introduction
More informationMessage Implementation Guideline ORDERS Purchase Order PHARMA Initiative Austria EANCOM 2002 Syntax 3 Version 1.1. Directory Version:
Message Implementation Guideline ORDERS Purchase Order PHARMA Initiative Austria EACOM 2002 Syntax 3 Version 1.1 Message Type: Message Version: Responsible Agency: Directory ame: Directory Version: ORDERS
More informationEDI Implementation Guidelines for Library Book Supply Changes, since issue 1.2
EDI Implementation Guidelines for Library Book Supply Changes, since issue 1.2 CONTENTS LIST Guidelines for Library Book Supply all formats... 2 Dates... 2 ISBN-13 in PIA segments... 2 Handling books carrying
More informationContents 1. Introduction 2. Segment description 4. Summary of segments used 13. Summary of segments not used 13. Comparison VDA 4906 => ODETTE 13
INVOIC EDI von Rechnungs- und Gutschriftsdaten EDI of and self-billed data VDA Arbeitskreis Elektronischer Geschäftsverkehr VDA Empfehlung 4932 (Nachfolgelösung für VDA Empfehlung 4906/4908) (Deutsche
More informationADOBE - EDIFACT D97A INVOIC
ADOBE - EDIFACT D97A INVOIC EDIFACT/D97A/INVOIC: INVOIC Invoice message Version: 1.0 Author: Adobe Systems Modified: 06/15/2009 INVOIC Invoice message Message Status=2 A message claiming payment for goods
More informationUser Guide for international trade of building materials. Nordic ebuilding EDI guide for EDIFACT INVOIC
User Guide for international trade of building materials Nordic ebuilding EDI guide for EDIFACT INVOIC EDIFACT-message: INVOIC EDIFACT-version: D EDIFACT-release: 03A EDIFACT-status: Ready for distribution
More informationDELFOR. Forecast/Calloff outbound UNH M 1 UNS M 1 UNB BGM M 1 UNS M 1 UNT UNZ M 1 M 1 M 1 SG18 R 9999 SG1 SG2 R 5 D 4 RFF NAD DTM LIN M 1 R 1 M 1 M 1
0 UNB UNH BGM UNS UNS UNT UNZ 1 SG1 D 4 SG2 R 5 SG18 R 9999 DTM R 1 RFF NAD LIN 2 SG3 O 2 SG19 D 4 SG20 R 50 SG20 R 50 SG20 R 50 SG24 R 1 CTA PIA D 10 FTX C 5 RFF QTY QTY QTY NAD 3 COM R 3 DTM R 2 SG21
More informationR.2 STRUCTURE OF AN EDIFACT TRANSMISSION
R.2 STRUCTURE OF AN EDIFACT TRANSMISSION This section is substantially based on the ISO 9735 document: EDIFACT application level syntax rules, first released on 1988-07-15, amended and reprinted on 1990-11-01,
More informationGLOBAL INVOIC (EDIFACT INVOIC D.07A / VDA4938)
SBI INVOICE GLOBAL INVOIC (EDIFACT INVOIC D.07A / VDA4938) Guideline Release: 1.0 Date: 7.10.2014 Detailed description of GLOBAL INVOICE message used for EDI between Skoda Auto a. s. and partners within
More informationINTRODUCTION TO EDIFACT. presented by EIDX
INTRODUCTION TO EDIFACT presented by EIDX 1 CONTENTS! Definitions! Data Mapping! Organizations! X12/EDIFACT Differences! Basic Components (Messages, Segments, Composites, Data Elements)! Codes and Qualifiers
More informationEDI Guideline Orders for configurable materials based on EDIFACT ORDERS D.96A Version 1.07 20.09.2011
EDI Guideline Orders for configurable materials based on EDIFACT ORDERS D.96A Version 1.07 20.09.2011 IT-Solutions for the KION Group Page 1 of 33 EDI Guideline Orders for configurable materials EDIFACT
More informationEDIFACT DELFOR D99B Guideline
EDIFACT DELFOR D99B Guideline 17.09.2013 Version 1.0 www.powersolutions.danfoss.com Introduction... 2 Legend:... 3 UNB - INTERCHANGE HEADER... 5 UNH - MESSAGE HEADER... 6 BGM - BEGINNING OF MESSAGE...
More informationEDIFACT. Version 1.7
IFTMIN D 96A Version 1.7 Document control Change record Version Date By Company Changes 1.0 16-03-06 F. Houben Janssen Distribution Description for external use Services 1.1 03-04-06 R.M. van Eijk Janssen
More informationMapping orders from your library management system to EDI
Mapping orders from your library management system to EDI Input by Simon Edwards, e4libraries consultant simon.edwards@dial.pipex.com, 07742988391 Most Library Management Systems (LMS) are capable of sending
More informationCOPRAR EDIFACT User Guide Page 2
PR04049-STEIN_MN12 Version: 1.0 Date: 30/09/2006 ! COPRAR EDIFACT User Guide Page 2 1 // INTRODUCTION.... 4 1.1 // PURPOSE... 4 1.2 // CONTENTS... 4 1.3 // REFERENCE DOCUMENTS... 4 1.4 // SHORTHANDS...
More informationPost Danmark and DPD
UNA Service String advice M1 M 1 UNA 1 COMPONENT DATA, ELEMENT SEPARATOR M an1 M : (colon) UNA 2 DATA ELEMENT SEPARATOR M an1 M + (plus) UNA 3 DECIMAL NOTATION M an1 M. (dot) UNA 4 RELEASE INDICATOR M
More informationManor EDI-Manuel. Purchase Orders ORDERS D96.A EANCOM. Manor AG EDI : Purchase Orders EINFÜHRUNG. 1. Manor Adresse Identifikation. 2.
EINFÜHRUNG 1. Manor Adresse Identifikation Manor EDI-Manuel GLN Manor: UNB : 7612096000005 NAD/BY : (s. GLN Liste) Alle andere GLN (Global Location Number) von Manor Filialen und/oder Manor Verteilzentrale
More informationDSV IFTMIN S93A. Message Implementation Guideline. based on. IFTMIN Instruction message UN S.93A S3
Message Guideline DSV IFTMIN S93A based on IFTMIN Instruction message UN S.93A S3 Version: 3.9 Variant: rev 1.7 Issue date: 2015-01-08 Author: EDI Support SE 1 Message Structure... 6 2 Branching Diagram...
More informationStatus Message (EDIFACT IFTSTA) Business Integration for the Port of Hamburg. Mattentwiete 2 20457 Hamburg www.dakosy.de
Message Guide IMP IFTSTA Status Message IMP Status Message (EDIFACT IFTSTA) Business Integration for the Port of Hamburg Message Guide Version 2.2/E (Valid from 26.08.2015) Mattentwiete 2 20457 Hamburg
More informationEDI GUIDELINES. Motor Carrier Load Tender 204 VERSION 004010
EDI GUIDELINES otor Carrier Load Tender 204 VERSION 004010 ASC X12 Version 4010 1 April 5, 2007 204 otor Carrier Load Tender Functional Group ID=S Introduction: This Draft Standard for Trial Use contains
More informationEDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X.12-4010 Draft
EDI 210 Invoice Motor Freight 210 Invoice with Stop Offs Version: 1.0 ANSI X.12-4010 Draft Motor Freight Invoice 210 EDI Transaction. ANSI X.12 Standards Version 4010 1 Table of Contents 210 Motor Carrier
More informationGS1 Germany EDI Recommendation
GS1 Germany EDI Recommendation for the textile sectors CFB-Connecting Fashion Business V2.1 () based on EANCOM 2002 S3 1. Introduction... 2 2. List of business terms... 5 3. Message structure chart...
More information810 Invoice ANSI ASC X12 Version 4010
810 Invoice ANSI ASC X12 Version 4010 ERICO International 31700 Solon Rd. Solon, OH 44139 7/15/2009 Purchase Order Acknowledgment Invoice-810-855 ii 7/15/2009 Purchase Order Acknowledgment Invoice-810-855
More informationGENERAL MOTORS DE MEXICO SPOM
GENERAL MOTORS DE MEXICO SPOM SERVICE PARTS OPERATION EDIFACT IMPLEMENTATION GUIDELINE D97.A FOR DESADV MESSAGE DESPATCH ADVICE (ASN) MESSAGE This Guideline issued by: GENERAL MOTORS DE MEXICO S DE RL
More informationSCTS-AIS Swedish Customs Technical Specifications for Automated Import System ICS phase 1 Appendix C Codelists Version 1.0.
SCTS-AIS Swedish Customs Technical Specifications for Automated Import System ICS phase 1 Appendix C lists Version 1.0.5 1 Interchange/message level codes... 3 K101 Application reference (an..14)... 3
More informationRANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010
RANDOM HOUSE EDI Implementation Guide X12 Version 4010 Effective: 6-26-2006 Notes: The Random House EDI Implementation Guide for the 850 transaction documents only the segments and elements used by the
More informationEANCOM- Spezifikation ORDERS D 96A (EDI-Nachrichtenstandard 2)
EANCOM- Spezifikation ORDERS D 96A (EDI-Nachrichtenstandard 2) Diese Dokumentation orientiert sich an der ORDERS-Message-Dokumentation des ECC's. Wie im EDI-Nachrichtenstandard üblich besteht jede Nachricht
More informationANSI X12 version 4010 856 Advance Ship Notice
ANSI X12 version 4010 856 Advance Ship Notice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 05/01/07 Trading Partner: All 856 All Partners 4010 Outbound.rtf 1 856 Ship Notice/Manifest Functional
More informationBusiness Document Specification Issue date: 2011-03-01 Version: 1.61 Invoice 20.1.6 Belonging message specification: MS 35
This business document is used when invoicing delivered and returned trade items. One invoice corresponds to one delivery or one return. The transaction is also used when crediting. If a calloff has been
More informationCUSRES Customs Response Message
CUSRES Customs Response Message Introduction: This Customs Response Message (CUSRES) permits the transfer of data from a customs administration: - to acknowledge the receipt of the message - to indicate
More information850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft
850 Purchase Order X12/V4030/850: 850 Purchase Order Version: 1.0 Draft Author: Supplier Automation Trading Partner: Ross Stores, Inc. Notes: This is the standard guide prepared by JPMC/Xign for Merchandise
More information214 Transportation Carrier Shipment Status Message - LTL
214 Transportation Carrier Shipment Status Message - LTL Lowe's 214 - LTL Shipment Status Message Version: 4010 Author: Lowe's Companies, Inc Modified: 2/27/2013 Notes: This 214 Implementation Guide should
More informationEDIFACT MESSAGE IMPLEMENTATION GUIDELINES RECEP:0:2:FH:
EDIFACT MESSAGE IMPLEMENTATION GUIDELINES RECEP:0:2:FH: Version Number: 1.5 Issue Date: 3 rd April 2000 Message Type : RECEP Version : 0 Release : 2 Controlling Agency : FH Assoc Assigned Code : Crown
More information860 Purchase Order Change Request Buyer Initiated
860 Purchase Order Change Request Buyer Initiated Set Number - 860 Set Name Purchase Order Change Request Buyer Initiated Functional Group - PC This Draft Standard for Trail Use contains the format and
More informationProduce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN)
Produce Traceability Initiative Why and How to Use EDI 856 Advance Ship Notice/Manifest Transaction Set (ASN) About this Guidance Document (Revision 1.0) Guidelines are generally accepted, informally standardized
More informationPos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT1 200000 0100 IT1 Baseline Item Data M 1 0600 PID Product / Item Description M 1 1000
810 Invoice Introduction: Functional Group ID=IN This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data
More informationANSI X12 ASN 856 Version 002040
ADVANCE SHIP NOTICE MESSAGE ANSI X12 ASN 856 Version 002040 V01 23/08/12 Page 1/36 Property of VALEO Duplication Prohibited Table of Contents 1 THE ADVANCE SHIP NOTICE MESSAGE...4 1.1 Introduction...4
More informationEDI GUIDELINES PURCHASE ORDER 850 VERSION 4010
EDI GUIDELINES PURCHASE RDER 850 VERSIN 4010 Rev. 7/23/2013 GLSSARY F TERS BLACKHAWK NETWRK s 850 GUIDELINES Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each
More informationBORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE
BORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE 1 Implementation Guideline 830 3-Jun-15 830 BorgWarner Material Release v004010 Functional Group ID=PS Introduction: This Standard contains
More informationPortland General Electric Implementation Standard
Portland General Electric Implementation Standard for Electronic Data Interchange TRANSACTION SET 810 Ver/Rel 004010 Invoice Inbound from Vendor 8104010I 1 August 18, 2004 810 Invoice Functional Group
More informationDart Container Corporation. EDI 810 Outbound Invoice Version 4010
Dart Container Corporation EDI 810 Outbound Invoice Version 4010 HEADER SECTION ST - Transaction Set Header 01 Transaction Set Identifier N0 1/10 810 02 Transaction Set Control Number AN 4/9 Unique Sequence
More information2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY
2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY INFORMATION TMM REQUIRES FROM TRADING PARTNER SCOPE THIS INFORMATION INCLUDES START-UP INFORMATION SPECIFIC TO TRADING PARTNER. APPROACH
More informationInvoice. Transaction Set (810) (Outbound from TI)
Invoice Transaction Set (810) (Outbound from TI) ANSI X12 Version Format: 3020 Date: October 1996 Copyright 1996 Texas Instruments Inc. All Rights Reserved The information and/or drawings set forth in
More informationNAF Nätverk för Affärsutveckling i Försörjningskedjan
VCC EDI DEMANDS Training session in Chengdu and Shanghai 2012 ----------------------------------------------------- Eric Ristenstrand VCC Elsa Nylander VCC Yang Huang (Tony) VCC Sten Lindgren Odette Sweden
More informationTable of contents A X T E D I 2. version: AXT EDI Filter 2.0.3
AXT EDI Table of contents 1 Description...3 2 Dependencies...3 3 Installation...3 4 Conversion...4 5 AXT configuration...5 6 EDI2XML configuration...8 7 Segments and elements...11 7.1 Record specification
More informationEPIC. EDI Core Standards VM-0001-11
EPIC EDI Core Standards VM-0001-11 Copyright Data Interchange Plc Peterborough, England, 2012. All rights reserved. No part of this document may be disclosed to third parties or reproduced, stored in a
More informationDIGITAL SIGNATURE FOR EANCOM MESSAGES
Digital Signatures for EACOM Messages DIGITAL SIGATURE FOR EACOM MESSAGES GS1 Implementation Guidelines EACOM TDT DOCUMET v1.0 Page 1 Digital Signatures for EACOM Messages TABLE OF COTETS 1 Introduction...
More informationGuidelines of Implementation for EDIFACT SUBSET. EDITEC Invoice
Guidelines of Implementation for EDIFACT SUBSET EDITEC Invoice INVOIC / D.96B Version 3.3 / November 2005 Table of Contents Page 1 Table of Contents Subset Invoice : 1 Introduction... 1 2 Instructions
More informationAdditional rules and comments for the transfer of container movements to DAKOSY with the EDIFACT-message CODECO/COARRI
EDI-Handbuch EDI Guide Additional rules and comments for the transfer of container movements to DAKOSY with the EDIFACT-message CODECO/COARRI Version 1.8 /E Compiled by : S. Elze on: 12.01.2006 Changed
More informationTABLE OF CONTENTS. 1. Message structure INVOIC... 4 2. BUSINESS TERMS... 5 3. Segment description INVOIC... 9 4. Example INVOIC...
REWE ITERATIOAL STADARD IVOIC Commercial invoice without a consolidated paper Invoice according to new legislation from 01.1.2013 Definition EACOM 2002 Syntax 3 Author: Ewald Arnold Version: 010 from:
More informationEDIFACT Standards Overview Tutorial Learn About Key E-commerce Trends and Technologies at Your Own Pace
A G X S T U T O R I A L EDIFACT Standards Overview Tutorial Learn About Key E-commerce Trends and Technologies at Your Own Pace Welcome!...3 How To Use This Tutorial...3 Tutorial Objectives...3 Part 1:
More informationEDIFACT Standards Overview Tutorial
EDIFACT Standards Overview Tutorial Learn About Key e-commerce Trends and Technologies at Your Own Pace A GXS Tutorial for the Active Business Welcome!... 3 How To Use This Tutorial... 3 Tutorial Objectives...
More informationElectronic Data Interchange
Electronic Data Interchange Transaction Set: 850 Supplier Purchase Order ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply
More information856 Advanced Shipping Notices (ASN)
NEXTEER Supplier Information Packet 856 Advanced Shipping Notices (ASN) Revised March, 2010 s GENERAL INFORMATION This packet is to provide information to Nexteer and SteeeringMex Direct Suppliers who
More information