IBM Support

Common EDI Standards

Question & Answer


Question

Common EDI Standards

Answer

Common EDI Standards

Table 1. Common North American EDI Standards
StandardIndustry Since
EDIATransportation1979
UCSGrocery1982
WINSWarehousing1982
ANSI X12Cross-industry1983
PIDXPetroleumN/A
RosettaNetIT Supply ChainN/A

RosettaNet

The RosettaNet standard is basedon XML and defines message guidelines business processes and interfaceand implementation frameworks for interactions between companies.The PIDX standard is an extension of the RosettaNet standard for thePetroleum industry. IBM? SterlingB2B Collaboration Network supportsa RosettaNet/PIDX translation that accepts flat files and translatesthem into RosettaNet or PIDX standard documents. The service allowsRosettaNet/PIDX supply chain and solution partners to collaboratein executing RosettaNet/PIDX single-action Partner Interface Processes(PIPs). PIPs are XML-based dialogs that define business processesbetween trading partners.

The RosettaNet/PIDX service providesthe following features:
  • Transmission via HTTP/HTTPS.
  • Built- inin RosettaNet 0A1 PIP support.
  • Ability to accept flat files and translates into the RosettaNetor PIDX standard.
  • Ability to view data flow tracking and transaction status usingSterling InFlight Data Management.
  • Guaranteed delivery and automated retries.
  • Use of MIME multipart/related type for basic enveloping construction.
  • Support for optional use of SMIME encryption/decryption user certificates.
  • Support for SSL.
In the current implementation dual-action PIPs and inboundPIPs are not supported. Sterling B2B CollaborationNetwork supportis limited to the following PIDX version 1.3 PIPs:
  • P21 (Invoice)
  • P31 (Create Purchase Order)
Table 2. International EDI Standards
StandardIndustryRegionSince
TRADACOMSRetailUK1982
ODETTEAutomotiveEurope1985
UN/EDIFACTCommercial Export and TransportationGlobal1988
EANCOMRetailEurope1990
UK/EDIFACTRetailUK1992
VDAAutomotiveEuropeN/A

The VDA Standard

VDA has several featuresthat distinguish it from most other standards:

  • It does not use a common set of interchange envelopes forall messages.
  • It does not use functional groups.
  • It uses a positional non-delimited format.
  • It uses looping but not composite elements.
  • It uses a new control number (for the current transmission) andan old control number (for the previous transmission). As a resultcontrol numbers do not need to be sequential.
  • In some messages it processes date formats differently than otherstandards.
  • It uses a separate message to identify the communications protocol.A message is defined by a four-digit number which does not appearin the data.
  • The first record has eight fields: I just did tag version customersupplier old transmission number new transmission number transmissiondate and date reset input.
  • Each record begins with a three-byte record ID and a two-byteversion number.
Parent topic: EDI Standards
"

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SS73G6","label":"Sterling Total Payments for Financial Services"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 December 2018

UID

ibm10758773

Page Feedback