• Standards Versions Used in Supporting Documentation
• Abbreviations and Conventions Used:
  • EDIFACT and X12 Abbreviations
  • OAGIS Abbreviations
  • RosettaNet Abbreviations
• References to Data Groups, Segments and Elements
  • EDIFACT Segments
  • X12 Segments
• References to Response Transactions/Messages

Standards Versions Used in Supporting Documentation
Data segment and element positions referred in most supporting documentation are particular to ASC X12 Version 003020 or 004010, UN EDIFACT Version/Release 92.1 or D97A, or OAGIS version 8.0. Users of these documents may need to adapt information when applying these recommendations to other standards versions or directories.  For RosettaNet, the version is assigned at the PIP level, so not all PIPs are on the same version.  Reasonable attempts will be made to identify the version being described in the EIDX supporting documentation.  

Abbreviations and Conventions Used When Describing  X12 and EDIFACT

Note:

1. Part, product, product identification, product ID are usually used interchangeably in these documents.
2. The terms ‘code’ and ‘identifier’ are used synonymously.
3. X12/UN refers to the ASC X12 standard and the UN EDIFACT standard. UN is often used since it is a shorter notation than EDIFACT.

Abbreviations and Conventions Used When Describing OAGIS

Abbreviations and Conventions Used When Describing  RosettaNet

UML Notation for Multiplicity (a/k/a cardinality)

References to Data Groups, Segments and Elements

UN/EDIFACT Segments
The UN/EDIFACT segments listed below are referenced on this Web site and in downloadable documents. Their three character code is referenced without a description of the segment. Readers who are not familiar with the UN EDIFACT standard can reference this table as needed.

ASC X12 Segments
The ASC X12 segments listed below are referenced on this web site and in downloadable documents. These are segments which are used in many transactions or have commonly used elements. For example, the N1 Name segment is used in most ASC X12 transactions to convey "Name." The PO1, POC, LIN and others that are used in different transactions have a similar function to convey line item information. They all contain DE235/234 pairings which are used to convey product identification information. Their two or three character codes are referenced without a description of the segment. Readers who are not familiar with the ASC X12 standard can reference this table as needed.

ASC X12 Data Elements are often referenced on this web site and in downloadable documents. The reference to its number may be used without its description.

Sample Segment Table:

Click here to view a larger image.

Sample Segment Detail:

Click here to view a larger image.

References to Response Transactions/Messages
One transaction initiates an entire process between trading partners. The original receiving party often responds with another transaction.   The appropriate response transaction/message depends on context - the business process scenario and/or the results of processing.  For example, the response to a purchase order is usually a purchase order acknowledgment.  However, if the item ordered is being shipped immediately, a ship notice saying that the item has shipped means the order is legally accepted, and the buyer knows the ship date.  In this context, the PO acknowledgment is redundant.

Few transactions/messages use the same response regardless of context.   When the term ‘Response Transaction’ is used in this document, it is referring to the type of transactions/message below.