Code Conversion
Code Conversion
4-3
predefined categories are included in Oracle e-Commerce Gateway. You may
choose to implement these predefined categories or define your own. See Defining
Code Conversion Categories section for additional details.
Define Code Conversion Values is where simple, or advanced code conversion rules
along with their corresponding internal/external values are defined. Internal
values are defined as code values stored in Oracle Applications. External values are
code values in your trading partner’s application or industry standard. In this form
you can define advanced rules such as direction-specific,
industry-standard-specific, one-to-many, and multi-level hierarchy code conversion
rules. Every code conversion rule is associated with a code conversion category.
See Defining Code Conversion Values section for additional details.
Assign Code Conversion Category associates a category (including all rules
associated with that category) with a specific data element in a transaction. This
assignment will enable code conversion for the transaction/data element. See
Assigning Categories section for additional details.
If you use the code conversion by trading partner standard feature, an additional
setup step to enter document standard in the Trading Partner Details form is
required. See Trading Partner Details section for additional details.
Code Conversion Based on Direction
Direction-specific code conversion is used in situations where a trading partner or
group of trading partners have code conversion requirements that apply to only
inbound or outbound code conversions. This feature is used in conjunction with
the multiple key feature of Code Conversion to provide maximum flexibility and
configuration of your unique code conversion requirements.
An example of how this feature can be applied is:
An Oracle Applications trading partner both receives purchase orders and sends
invoices electronically. They have separate Order Entry and Accounts Receivable
applications, each with its own unique set of UOM codes. Separate code conversion
rules must be defined for the same trading partner based on transaction direction.
Direction-specific code conversion rules are defined in the Define Code Conversion
Values form of Oracle e-Commerce Gateway. For each code conversion rule, you
can also specify if the rule applies to inbound transactions, outbound transactions,
or both.
In most situations, you will accept the default value of ”Both”. However, if you
have complex code conversion requirements that require direction-specific code
conversion rules, you will specify direction on this form.
Summary of Contents for e-Commerce Gateway 11i.2
Page 1: ...Oracle e Commerce Gateway User s Guide Release 11i 2 August 2000 Part No A75089 02...
Page 6: ...vi Oracle e Commerce Gateway User s Guide...
Page 18: ...xviii...
Page 42: ...Defining Trading Partner Data 3 8 Oracle e Commerce Gateway User s Guide...
Page 68: ...Assigning Column Rules 5 10 Oracle e Commerce Gateway User s Guide...
Page 78: ...Viewing Column Violations 6 10 Oracle e Commerce Gateway User s Guide...
Page 128: ...Viewing the Status of Concurrent Programs 9 8 Oracle e Commerce Gateway User s Guide...