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

Example of an inbound interface file for EDI X12 messages

Example of an inbound interface file for EDI X12 messages

The inbound interface file for EDI X12 messages contains a root element, message type element, delimiters, loop elements, segment elements, and data elements.
The following XML represents an interface file for an inbound message of type 850:
<x12:interchanges xmlns:x12="http://www.informatica.com/B2B/X12/4010"> <interchange> <delimiters> <field_separator>*</field_separator> <segment_separator>~</segment_separator> <composite_separator>^</composite_separator> <segment_separator_suffix> </segment_separator_suffix> </delimiters> <ISA> <R01>03</R01> <R02>Brett </R02> <R03>01</R03> <R04>JoZaza </R04> <R05>ZZ</R05> <R06>6666 </R06> <R07>14</R07> <R08>148055531ECPI </R08> <R09>071031</R09> <R10>0619</R10> <R11>U</R11> <R12>00503</R12> <R13>111111176</R13> <R14>0</R14> <R15>P</R15> <R16>^</R16> </ISA> <GS> <R01>PO</R01> <R02>4405197800</R02> <R03>999999999</R03> <R04>20101127</R04> <R05>1719</R05> <R06>1421</R06> <R07>X</R07> <R08>004010</R08> </GS> <x12:TS_850> <ST> <R01>850</R01> <R02>000000010</R02> </ST> <BEG> <R01>00</R01> <R02>SA</R02> <R03>08292233294</R03> <R05>20101127</R05> <R06>610385385</R06> </BEG> <LOOP_PO1> <PO1> <R01>1</R01> <R02>120</R02> <R03>EA</R03> <R04>9.25</R04> <R05>TE</R05> <R06>CB</R06> <R07>065322-117</R07> <R08>PR</R08> <R09>RO</R09> <R10>VN</R10> <R11>AB3542</R11> </PO1> <LOOP_PID> <PID> <R01>F</R01> <R05>SMALL WIDGET</R05> </PID> </LOOP_PID> <PO4> <R01>4</R01> <R02>4</R02> <R03>EA</R03> <R04>PLT94</R04> <R06>3</R06> <R07>LR</R07> <R08>15</R08> <R09>CT</R09> </PO4> </LOOP_PO1> <LOOP_PO1> <PO1> <R01>2</R01> <R02>220</R02> <R03>EA</R03> <R04>13.79</R04> <R05>TE</R05> <R06>CB</R06> <R07>066850-116</R07> <R08>PR</R08> <R09>RO</R09> <R10>VN</R10> <R11>RD5322</R11> </PO1> </LOOP_PO1> <LOOP_CTT> <CTT> <R01>6</R01> </CTT> <AMT> <R01>1</R01> <R02>13045.94</R02> </AMT> </LOOP_CTT> <SE> <R01>14</R01> <R02>000000010</R02> </SE> </x12:TS_850> <GE> <R01>1</R01> <R02>1421</R02> </GE> <IEA> <R01>1</R01> <R02>000003438</R02> </IEA> </interchange> </x12:interchanges>
If you trace through the hierarchy of the interface file, you can see that there are multiple interchanges. The hierarchy reflects the structure of the relevant message type, the schema, and the type of information that the customer sent.
You can pass the data from this interface file to a backend system for further processing.

0 COMMENTS

We’d like to hear from you!