Oracle A75089-02 - Manual (Page 30)

Oracle e-Commerce Gateway Profile Options
2-6 Oracle e-Commerce Gateway User’s Guide
When inbound EDI transactions are imported into Oracle Applications, the unique
business site address must be established before the transaction can be processed.
Each trading partner must have a unique address.
A trading partner is a site, such as a plant, a warehouse, a bank branch, or some
other business unit. A trading partner is not necessarily a company; one company
can have several sites.
The correct address can be obtained from one to three sources, each of which has a
precedence code:
When you set this profile option using the Transaction Profiles window, you must
select from the following values:
■
LTC, PHA, LON (default).
■
LTC, LON, PHA.
■
PHA, LTC, LON.
■
PHA, LON, LTC.
■
LON, LTC, PHA.
■
LON, PHA, LTC.
You must set up each inbound transaction to derive the correct address based on the
precedence of the three precedence codes, LON, LTC, and PHA. For example, one
transaction may be set up to derive the address based first on location / translator
code (LTC), then the physical address (PHA), and finally, the location name (LOC).
This means that the first attempt to derive the trading partner uses the combination
of the EDI location code and the translator code. If a unique address ID is not found,
a second attempt uses the physical site address. Finally, if the second attempt fails,
the location name is used.
The following profile options apply only to the Purchase Order Outbound (POO)
and Purchase Order Change Request Outbound (POCO) transactions:
Precedence Code Meaning
LON Unique ID number for location name.
LTC Location / translator code combination.
PHA Physical address or site detail.