Oracle A75089-02 - Manual (Page 46)

Code Conversion
4-4 Oracle e-Commerce Gateway User’s Guide
Use of Keys in Code Conversion
In many situations, one set of code conversion rules will not apply to all of your
trading partners. Code conversion rules may apply to specific trading partners,
specific industry standards, or any number of key attributes defined in Oracle
Applications.
These rules may be complex and involve a hierarchy of key attributes.
For example, trading partner and trading partner location may be defined as two
key attributes. The logical hierarchy structure will look like this:
Code Conversion Category
Trading Partner (Key 1)
Trading Partner Location (Key 2)
During code conversion processing, if a code conversion rule is defined for the
specific trading partner, trading partner location combination, that code conversion
rule will be applied. Otherwise, processing will default to the trading partner level
and apply any code conversion rules for that trading partner. If a rule still cannot
be found, processing will default to the category level and apply any code
conversion rules that apply to the entire category.
Keys and key hierarchies are user defined and apply to a specific code conversion
category. Any data element that appears on the Interface File Definition form can
be defined as a key attribute. In addition, Document Standard, defined in the
Trading Partner Details form, can also be defined as a key attribute.
Multiple keys are used to construct a logical hierarchy used by code conversion
processing to determine which code conversion rules to apply. Up to five levels of
keys can be defined for a single code conversion category. See Processing Keys (1-5)
section for additional details on how multiple keys are processed.
If keys are used for code conversion, setup is required in each of the three code
conversion forms.
■
In the Define Code Conversion Category form, indicate the number of keys to
enable for the selected category.
■
In the Assign Code Conversion Category form, define the key(s) by indicating
the data element associated with each key (e.g. Key 1 = Trading Partner for
Category UOM).
■
In the Define Code Conversion Values form, enter specific values for each key
combination requiring a unique set of code conversion rules (e.g. Key 1 = ABC
Company).