Understanding Custom EDI Integrations

Each trading partner using integrations conforming to an EDI specification usually has unique integration requirements. These unique requirements are commonly due to codes or data fields unique to a trading partner, or field lengths that do not map well into the EDI specification. Trading partners often vary the format of a transaction set to meet their specific needs. PeopleSoft Integration Broker provides the flexibility required to implement these trading partner specific integrations without requiring a middleware product to transform data.

Customers should expect to perform the following tasks for each trading partner with unique implementation requirements:

  1. Identify the integrations to implement for the trading partner.

  2. Create a copy of the delivered attribute mapping worksheets and customize the attribute mappings for each integration to match the trading partner's EDI implementation.

  3. If the trading partner's implementation requires adding, deleting, or modifying any fields or segments for an integration, create copies of the delivered file layouts and messages for the integration, customize them to match the attribute mappings, and create a message schema.

  4. Create a service operation for any new copies of the inbound integrations.

  5. For all integrations requiring transformations unique to the trading partner's implementation, create copies of the delivered transforms, and use the graphical mapper or any XSLT editor to customize them to match changes to the delivered attribute mappings.

  6. Create a message node for the trading partner.

  7. Using the delivered sample routings as a guide, create routing to or from the trading partner's node for each integration, and indicate the transforms to use for each routing.

  8. Create and activate a batch publish rule for each outbound integration.

  9. Create inbound file rules for each inbound EDI integration.

  10. Create run controls (schedules) for inbound and outbound processing.

To better understand how to take advantage of the transformation features available in the PeopleSoft Integration Broker, six of the more common EDI supportive integrations have been delivered with sample transforms to or form native X.12 EDI flat files:

  • 810 out: Billing Invoice

  • 840 in: Sales Quote Load

  • 845 out: Sales Quote Notice

  • 850 in: Sales Order Load

  • 855 out: Sales Order Acknowledgement

  • 856 out: Advanced Shipping Notice