ITX Pack for Supply Chain EDI

SPE Pack for Supply Chain overview
The IBM Standards Processing Engine Pack for Supply Chain EDI is an industry accelerator that provides Business-to-Business enabling functionality to users of the IBM Standards Processing Engine (SPE).
What is an EDI type tree?
An EDI type tree includes definitions of objects that are used in EDI.
Analysis of EDI trees
Before an EDI version tree is released, the tree is analyzed by using the Type Tree Analyzer.
Create industry subsets
An industry subset is a type tree that contains only those functional groups that are of interest to your specific industry or company.
Make a multi-version tree
To support different trading partners, it is often necessary to create a type tree that represents multiple EDI version releases.
Create a multi-partner tree
You might have to create a multi-partner type tree. You can use a multi-partner type tree to specify particular partners and/or group partners by business relationships, such as customer, distributor, or supplier. This documentation contains step-by-step instructions for creating a multi-partner type tree.
Making a multi-standard tree
To support requirements for different partners, it is often necessary to create a type tree that represents multiple standards. For instance, if some partners use ANSI X12 and others use EDIFACT. This documentation contains instructions for modifying one of the standards trees to create a multi-standard tree (for instance, a type tree that contains both ANSI X12 and EDIFACT).
Mapping inbound EDI data
To map inbound EDI data, you need type trees, specifications, and test data.
Mapping outbound EDI data
If you intend to map outbound EDI data, you need type trees, specifications, and test data.
Sending functional acknowledgments
This documentation explains the audit997.mms example map source file.
Mapping purchase orders to invoices
This documentation explains the example map that maps an ANSI X12 EDI transmission that contains purchase orders (#850 transaction sets) to an ANSI X12 EDI transmission that contains invoices (#810 transaction sets).
Mapping inbound invoices
This documentation explains the example map that maps an EDI data file of ANSI X12 3020 invoices (transaction #810) to a file that is read into your order application.
Mapping invalid EDI data
Tracking your EDI documents
This documentation explains the example maps that track the EDI documents you are sending and receiving.
Editobol.mms map
This documentation describes the editobol.mms map source file.
X12 type trees
The SPE Pack for Supply Chain EDI contains X12 type trees. The X12 type trees are used to validate and ultimately transform data that conforms to the ANSI's X12 standard, as described in the ANSI X12 specifications.
EDIFACT type trees
The SPE Pack for Supply Chain EDI contains EDIFACT standard type trees and example type trees.
Compliance check
The EDI Standard organizations publish formats for X12 and EDIFACT documents so that they can be correctly translated by computers. Strict compliance with these standards is essential if EDI files are to be processed properly. The WebSphere Transformation Extender EDI Compliance Check framework enforces these EDI standards by validating X12 and EDIFACT EDI documents before translation. Validation of newly created EDI documents ensures that the data you create conforms and does not create issues for your trading partners. As the trend in the industry is to consider fines for non-compliance, verifying that the data you create is compliant, and is of key importance.
SPE Pack for Supply Chain EDI samples
The SPE Pack for Supply Chain EDI includes sample deenvelope and envelope tests for EDIFACT, X12 and TRADACOMS.