EDI Accelerator Guide

EDI Accelerator Guide

Extending EDI Accelerator with Backend Systems Integration

Extending EDI Accelerator with Backend Systems Integration

EDI-X12 messages should be mapped to customer-specific formats and then loaded into back-end systems. The mapping and the loading process
are not part
of the Accelerator as they are customer specific. Accelerator users can add specific B2B Data Exchange and PowerCenter implementations for mapping and loading, and define endpoint connectivity for B2B Data Exchange communication.
The EDI Accelerator package includes a workflow wf_EDI_GW_ST_Details. Inputs for that workflow are transaction sets in EDI text format, and also in Informatica canonical XML format for inbound messages. Customers can modify the workflow to conform to the organization's needs.
EDI Accelerator Outbound messages start from Informatica canonical format since the back-end format is customer specific. Those back-end files need to be mapped to Informatica canonical format. Accelerator users can add specific B2B Data Exchange and PowerCenter implementations for mapping from customer specific format to the Informatica canonical XML format. The Accelerator includes a sample PowerCenter mapping (can be found in the c:\temp\Examples\PwC_Workflows) that can be used as a guideline for development of customer specific mappings to Informatica canonical format.

0 COMMENTS

We’d like to hear from you!