Defining Trading Partner Data
To define a trading partner group:
1. Navigate to the Trading Partner Groups window.
2. Enter a unique trading partner group identifier.
A trading partner group is a collection of individual address entities for a given trading partner.
3. Optionally, enter a description for the trading partner group.
4. Do one of the following:
- To add a new trading partner to a trading partner group, enter the trading partner code and description. Then choose the New button.
This trading partner entity is linked to a physical address in the Oracle application using the Assignments alternative region of the Define Trading Partner window.
- To update an existing trading partner in a trading partner group, enter the trading partner location code and description. Then choose the Open button.
To define a trading partner within a trading partner group:
1. Enter a unique trading partner identifier. This defines a trading partner identifier for the EDI Gateway. This code is not written to the data files.
2. Optionally, enter the trading partner description.
3. Enter references 1 and 2. This is for any additional information needed by the trading partner.
This data is written to the control record of every outbound transaction as the primary location for the specific transaction. You can use this information to return codes to the trading partner per their requirement.
For example, assume the bill-to customer wants code 'AB-XY' added to all invoices, but you do not want to define an application flexfield for this customer-specific code. Once the code is in the data file, you can map it to the desired data element in the standard transaction.
4. Access trading partner flexfields (also known as attributes) set up using system administration.
To define trading partner assignment:
1. In the Assignment alternative region, associate this trading partner definition with the corresponding Oracle Applications physical address entity. This is usually address- or site-level data.
2. Do one of the following:
- If you are defining the trading partner as a customer, select a customer and customer site. These values are defined in Oracle Order Entry and / or Oracle Receivables.
- If you are defining the trading partner as a supplier, select a supplier and supplier site. These values are defined in Oracle Purchasing and / or Oracle Payables.
- If you are defining the trading partner as a bank, select a bank branch address. This value is defined in Payables.
- If you are defining other trading partner relationships, select the Human Resources location code. These values are defined in Oracle Human Resources.
To define trading partner details:
1. Open the Details alternative region to enable EDI transactions and processing rules for the trading partner location.
2. Select the EDI document and the document type. Doing so enables the transaction for the trading partner.
You must enter each document and each type explicitly to enable the transaction. If you do not enter both, no data is extracted.
3. Enter the translator code (as defined in the EDI translator software) to associate with the transaction and location which is being enabled. The translator code links the EDI Gateway trading partner definition to that in the EDI translator.
4. Indicate whether to send documents via EDI to this trading partner. This permits outbound transactions to be extracted and sent via EDI for this trading partner.
5. Indicate whether to print a paper copy for this partner. (This functionality is not presently supported.)
6. Indicate whether you are sending / receiving test EDI transactions for this partner.
This allows transactions to be marked as a test transaction even if it is extracted from a production application. This code should agree with the test / production flag defined in the EDI translator software.
To define trading partner contact data:
- Optionally, open the Contact alternative region and enter the EDI contact name, title, basic address information, electronic mail address, phone, fax number, and so on. This information is useful for EDI coordinators in case issues arise regarding transmission of EDI files. This data is not written to the data files. The data is independent of all contact information in the Oracle Applications.
