Setting Up Inbound EDI Transactions Using Flat Files

To set up an inbound EDI transaction using flat files:

1. If trading partner is not delivering data in PeopleSoft's business document file format, set up mapping software to transform the trading partner's format to the PeopleSoft format.

   For a definition of PeopleSoft's business document file format, obtain the file layout for the EDI transaction. For information about obtaining the file layouts, see Obtaining File Layouts, which appears later in this document.

   For the appropriate file layout definition for each transaction, refer to the table in the Reviewing PeopleSoft Supported EDI Transactions section.

2. Perform application specific setup.

   Refer to the table in the Reviewing PeopleSoft Supported EDI Transactions section for information on locating documentation explaining application-specific setup instructions for each EDI transaction.

3. Perform Integration Broker setup.

   You must set up and activate nodes, service operations, handlers and routings before you can begin processing inbound transactions.

   1. Set up nodes.

      PeopleSoft delivers a sample external inbound node (PSFT_XINBND) used to deliver sample routing definitions for each service operation. For inbound transactions using flat files you need the default local node only. The default local node (PSFT_EP) is packaged with initial delivery of the system. Unless you are changing the local node, no additional node setup is required. If for auditing purposes you wish to differentiate the node from which transactions are received, you may do so by creating a node definition and inbound file rule for each external trading partner or VAN you plan to integrate with, and specifying the sender node name on each inbound file rule.

   2. Activate Service Operations.

      PeopleSoft provides Service Operation definitions for each EDI transaction that you must activate before use.

   3. Activate Service Operation Handlers.

      OnNotify Service Operation Handlers are subscription processes that are automatically executed by Integration Broker when an inbound asynchronous transaction is received. PeopleSoft provides OnNotify Handlers on each asynchronous service operation that supports inbound integration. You must activate the appropriate OnNotify Handler on each Service Operation before use.

   4. Activate Service Operation Routings.

      Service Operation Routings define the sending and receiving nodes for an integration, the external name of the integration, and optionally specify inbound and outbound transformations to be invoked on each transaction. The sender node on inbound routings can be specified as "ANY" node allowing transactions to be received from any valid node. For each trading partner or VAN sending data into PeopleSoft, a routing must be activated either from a specific sender node, or from "ANY" node.

4. Set up Inbound File Rule.

   For integrations using the PeopleSoft flat-file format, the Enterprise Components Inbound File Publish process uses an inbound file rule to identify information about the source file. Most EDI transactions are already set up on the SCM Inbound EDI file rule. If you are processing one of these transactions, then enter the file name on the file rule and activate the file rule.

   For integrations using the X.12 EDI flat-file format, the PeopleTools Integration Broker Inbound File Process uses an inbound file loader rule to identify information about the source file. Each sample inbound EDI transaction has been delivered with a sample inbound file loader rule. If you are processing one of these transactions, then enter the file name on the file rule and activate the file rule.

5. When you are ready to process a trading partner's file, run the Inbound File Publish process.

   After you run the Inbound File Publish process, run the appropriate application process to validate and load the transactions.