When you receive an EDI transaction from a trading partner, much of its data is in the form of codes or identification numbers. For example, the trading partner who submitted the transaction is given as a Trading Partner ID, and the type of transaction is identified by a Transaction ID. Your PeopleSoft database also stores much of its data in the form of codes or IDs. You have Business Unit IDs, Customer IDs, Employee IDs, Operator IDs, and so on. Some of these codes and IDs represent the same data as the codes and IDs in the EDI transaction, even though the codes themselves might be different.
When the EDI Agent processes a transaction, it copies the transaction data into the PeopleSoft database. As it does so, it can convert the external EDI codes into the internal PeopleSoft codes. Similarly, as it writes out the file for an outgoing EDI transaction, it can convert the PeopleSoft codes into codes that your trading partner will recognize. You specify how the EDI Agent converts the codes using the EDI Manager.
The EDI Manager can perform two kinds of conversions:
• It can translate between EDI event codes and PeopleSoft action codes, which specify what action a transaction requires. See Action Codes and Event Codes.
• It can convert data values from any field in the transaction. See Data Values.
Action Codes and Event Codes
EDI transactions use event codes to specify what action the transaction calls for. For example,
event codes specify whether the current transaction is a completely new transaction, a resubmitted transaction, or an update to a previous transaction.
Event codes come in two flavors, both of which can be specified for the same transaction: • Primary event codes, also called purpose codes, specify the status of the transaction: whether
it’s a new transaction, a cancellation, a duplicate, a status request, and so on. Every transaction has a primary event code assigned to it.
• Secondary event codes, also called transaction codes, specify the type of transaction in detail. For example, a transaction’s secondary event code could say that the transaction is a catalog order, a rush order, or a request for a sample. Not all transaction types include secondary event codes.
PeopleSoft applications, on the other hand, determine what action to take on a transaction using a
single action code. So, when the EDI Agent processes an EDI transaction, it needs to convert its
Using the EDI Manager, you specify which (pairs of) event codes get translated into which action codes. Since you may want to process transactions differently depending on which trading partner they come from, the EDI Manager enables you to define different event code-to-action code translations for each trading partner.
The following table lists the three major steps in defining how the EDI Agent translates event codes into action codes and where to find information.
Steps for defining how to translate codes Use this section…
Define the set of recognized primary event codes, secondary event codes, and action codes.
Link to next section
As part of a trading partner profile, specify which event codes or pairs of event codes correspond to which action codes.
Defining EDI Transactions
For each of your trading partners, specify which trading partner profile to use.
Setting Up Trading Partners
Defining Primary and Secondary Event and Action Codes
To access EDI Manager from your browser
1. Open your browser. Select PeopleTools, EDI Manager, Use.
EDI Manager Use Options
2. Select an option from the list.
The following sections describe the Use options.
1. Select Primary Event Code Defn.
For each of the options, you can search for an existing value or directly add a new value by clicking on the link at
Find an Existing Value – Primary Event Code
Add a New Value – Primary Event Code
2. Click Add a New Value then add the value.
Enter the primary event code as it will appear in the PeopleSoft Business Document
3. Enter a description of the event code and save the page.
This Description is for your information only. It doesn’t affect the processing of a PeopleSoft Business Document.
To define a secondary event code
1. Select Secondary Event Code Defn.
2. Enter the secondary event code as it will appear in the PeopleSoft Business Document.
Alternatively, you can search for an existing Secondary Event Code, by clicking Search.
3. Enter a description of the event code and save the page.
This Description is for your information only. It doesn’t affect the processing of a PeopleSoft Business Document.
We deliver the EDI Manager with a complete set of action codes for the actions standard PeopleSoft applications support. You need to add new action codes only if you create new programs that handle new actions.
1. Select Action Code Definition.
2. Enter the action code as you want the EDI Agent to write it in the electronic commerce
staging tables.
Alternatively, you can search for an existing Action Code, by clicking Search.
3. Enter a description of the action code and save the page.
This Description is for your information only. It doesn’t affect processing.