Oracle A75089-02 - Manual (Page 49)

Code Conversion
Code Conversion 4-7
If no match is found, default Internal Value into the External Value 1 field.
Processing Keys (1-5)
In Oracle e-Commerce Gateway, keys are used to construct a logical hierarchy of
key attributes. Code conversion processing derives key values based on data
entered in the Assign Code Conversion Category form.
Once key values are derived from the interface file (inbound) or transaction record
(outbound), a composite key is constructed with values for all key levels that apply
for the code conversion category.
Code conversion processing will use this composite key to locate records in the
Code Conversion Values table with exactly the same composite key plus matching
attributes for the other critical data elements in code conversion processing.
Failure to located a matching record will cause code conversion processing to
construct a new composite key by using values for all key levels except the highest
key level. This is effectively the same as stepping up one level in the 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 = ”UOM”.
Trading Partner (Key 1) = ”Company ABC”.
Trading Partner Location (Key 2) = ”CA”
The initial composite key will contain values ”Company ABC” and ”CA”. Any
records in the Code Conversion Values table that have matching Key 1 and Key 2
values, plus meet all other matching criteria, will be used to convert internal or
external values.
If a matching record is not found, the new composite key will contain the value
”Company ABC” (”CA” has been removed from the composite key). Now, code
conversion processing is looking for a match on Trading Partner (Key 1) only.
This cycle of stepping up the hierarchy of key attributes to construct new composite
keys is repeated until the composite key contains no values. At this point, code
conversion processing attempts to locate a match based on Code Conversion
Category only.
Processing External Values (1-5)
External Values (1-5) are processed as one, composite external value. Code
conversion processing does not view External Values (1-5) as a hierarchy or
multiple composite values.