Table of Contents

Search

  1. Preface
  2. Introducing B2B Gateway
  3. B2B Gateway administration
  4. Project and asset management
  5. EDI X12 and EDIFACT Messages
  6. Custom files with custom mappings
  7. Inbound Custom Files with Intelligent Structure Discovery
  8. File transfer tasks
  9. Partners
  10. Tracking and Monitoring Events
  11. B2B Gateway REST APIs
  12. Glossary

B2B Gateway

B2B Gateway

Structure of segment

Structure of segment

In the interface file, the segment element uses the segment ID as the name of the corresponding XML element. Data elements within the segment use the reference element ID with the prefix
R
as the name of the corresponding XML element.
The following XML shows the syntax of a segment element that contains data elements:
<segment ID> <data element reference ID>...</data element reference ID> <data element reference ID>...</data element reference ID> <data element reference ID>...</data element reference ID> ... </segment ID>

Example of an EDI X12 segment

As an example, in the 810 message, the segment ID for the Transaction Set Header segment is ST. The segment contains three data elements. The following table describes the data elements according to the EDI X12 standard:
Name of data element
Reference element ID
Transaction Set Identifier Code
01
Transaction Set Control Number
02
Implementation Convention Reference
03
The following XML represents the Transaction Set Header segment in the interface file:
<ST> <R01>810</R01> <R02>1131</R02> <R03>005030</R03> </ST>

Example of an EDIFACT segment

As an example, in the INVOIC message, the segment ID for the UNH Message Header segment is UNH. The segment contains seven data elements. The following table describes the data elements according to the EDIFACT standard:
Name of data element
Reference element ID
Message reference number
010
MESSAGE IDENTIFIER
020
Common access reference
030
STATUS OF THE TRANSFER
040
MESSAGE SUBJECT IDENTIFICATION
050
MESSAGE IMPLEMENTATION GUIDELINE IDENTIFICATION
060
SCENARIO IDENTIFICATION
070
The following XML represents the UNH Message Header segment in the interface file:
<UNH> <R01>1</R01> <R02> <R01>DELFOR</R01> <R02>D</R02> <R03>97A</R03> <R04>UN</R04> <R05>A09041</R05> </R02> <UNH>

0 COMMENTS

We’d like to hear from you!