Integrating PeopleSoft XML and Standard EDI Formats Such as X.12 EDI or EDIFACT

In this scenario, PeopleSoft exchanges EDI data utilizing PeopleSoft XML and transformations to or from industry standard EDI formats. Most EDI suppliers now support XML formats and can receive XML, translate the fields to standard EDI field formats, such as X.12 EDI or EDIFACT, and write the data to a flat file (They can also deposit the EDI transactions onto the VAN of your choice). Conversely, they can also receive inbound transactions from the VAN, map the fields to PeopleSoft XML format, and publish to the PeopleSoft Integration Broker Gateway.

Note:

This is the best approach for maintaining your investment in translation software while using PeopleSoft Integration Broker architecture. It is not a strong option if your current translation software does not support XML.

Consider the following advantages when using this upgrade path:

  • Batch windows reduction: data can be transmitted between PeopleSoft and the translation software with zero latency, then pooled into appropriate batches for transmission to the VAN.

  • Preserves investment in EDI standards support, minimizing impact to trading partners.

  • Provides a stepping stone to pure XML business-to-business architecture.

  • Uses delivered PeopleSoft EDI XML transactions.

Consider the following disadvantages to using this upgrade path:

  • Requires major EDI maps rewrite for the translation application or the VAN.

  • Still incurs VAN charges.

Converting Existing Outbound Translation Maps to Use XML

To convert existing outbound translation maps to use XML:

  1. Customize new EDI maps to convert the XML data into the customer's required format, such as X.12 or EDIFACT.

  2. Define a node within PeopleSoft to represent the trading partner, and setup the PeopleSoft Integration Broker.

    The specified URL points to the trading partner's web server.

  3. If the translator uses one of the industry-standard connectors packaged with PeopleSoft Integration Broker, configure the node to use this connector.

  4. If the trading partner does not support any industry-standard connectors, build a connector to transport XML data, and register the connector on the PeopleSoft Gateway.

  5. Initiate your publish functions within the PeopleSoft applications.

Converting Existing Inbound Translation Maps to Use XML

To convert existing inbound translation maps to use XML:

  1. Customize new EDI maps to convert the customer format to XML data.

  2. Define a node within PeopleSoft to receive this data, set up the PeopleSoft Integration Broker.

  3. If the translator uses one of the industry-standard connectors packaged with PeopleSoft Integration Broker, configure the node to use this connector.

  4. If the trading partner does not support any industry-standard connectors, build a connector to transport XML data, and register the connector on the PeopleSoft Gateway.

  5. Configure the trading partner's system so that it posts to the proper connector on the PeopleSoft Gateway.

  6. Begin receiving data from your trading partner.