EDI Accelerator Guide

EDI Accelerator Guide

Transaction Set (ST) Processing

Transaction Set (ST) Processing

Parsing is done for each file with one ISA and one GS and one ST segment.
The file is processed in the following steps.
  1. Split the file into separate files for each transaction set (single ST).
  2. Create a DX event for every file and attach the file to the DX event.
  3. Parse the files to Informatica canonical xml format and add that output to the event.
  4. Event attributes are also extracted and can be reviewed from the event attributes tab of the event.
  5. Transactions in XML format and in EDI text format are uploaded to a Queue to be consumed later by a Customer Specific mapping. A mapping is provided that reads the queue. If needed, customer specific mapping can be added there.
The EDI-X12 library includes parsing to EDI-X12 Informatica canonical XML format. To map the Informatica canonical XML format to customer-specific formats, you can create and configure a DT Mapper and/or DT Serializer. For more information about how to create a DT Mapper or a DT Serializer, see the
Data Transformation User Guide.
Note that converting from Canonical XML, to load the data into the backend systems, needs to be developed as part of the project implementation, and is beyond the scope of the EDI Accelerator.

Event statuses

DX Event Status
Description
Transaction initiated
Start processing of EDI document type
Transaction processed
EDI document has been parsed

Event types

The event type format is '<edi document identifier> (ST)'. For example, the event type will be '
810 (ST)
' for EDI Document 810.

Event attributes

DX Event Attribute
Description
GS_control_number
Functional Group control number as appears in GS\R06
ISA_control_number
Interchange control number as appears in ISA\R13
ST_control_number
EDI Document Control Number as appears in ST\R02
ST_transaction_type
EDI Document type as appears in ST\R01
The following table describes the specific event attributes extracted per EDI document:
DX Event Attribute Name
Transaction Name
Loop ID
Segment ID
Element ID
EDI Name
Invoice_Number
810
BIG
02
Invoice Number
Purchase_Order_Number
810
BIG
04
Purchase Order Number
Monetary_Amount
810
TDS
01
Monetary Amount
Number_of_Line_Items
810
CTT
01
Number of Line Items
Monetary_Amount
820
BPR
02
Monetary Amount
Purchase_Order_Number
850
BEG
03
Purchase Order Number
Number_of_Line_Items
850
CTT
CTT
01
Number of Line Items
Monetary_Amount
850
CTT
AMT
02
Monetary Amount
Purchase_Order_Number
855
BAK
03
Purchase Order Number
Number_of_Line_Items
855
CTT
CTT
01
Number of Line Items
Monetary_Amount
855
CTT
AMT
02
Monetary Amount
Shipment_Identification
856
BSN
02
Shipment Identification
Number_of_Line_Items
856
CTT
01
Number of Line Items

Documents attached

The following documents are attached:
Log Name
Description
ST Data
Transaction Set wrapped by ISA and GS
Converted XML
Output in Informatica canonical XML format

0 COMMENTS

We’d like to hear from you!