Search Results update_code_conversion_tbl

Overview

OZF_CODE_CONVERSION_PVT is a private PL/SQL package in the Oracle E-Business Suite APPS schema that implements the application logic behind code conversion within the Oracle Trade Management (OZF) module. Code conversion allows trading partners and internal users to map external reference codes supplied by customers or suppliers onto internal codes recognized by EBS, and vice versa. The package is classified as a PVT (private) API, meaning it is intended to be called by its public wrapper packages, business object APIs, or Oracle Forms rather than directly by external integrations. The header comment records a creation date of 09-OCT-2003 and identifies the artifact as ozfvsccs.pls, with the most recent revision noted at 120.2, dated 24-DEC-2007.

The package provides two parallel families of operations: one handling customer-facing code conversions stored in OZF_CODE_CONVERSIONS, and one handling supplier-facing code conversions stored in OZF_SUPP_CODE_CONVERSIONS, reflecting the need to translate codes in both order-to-cash and procure-to-pay trade flows.

Key Procedures and Functions

The ETRM metadata documents fourteen procedures and functions:

• CREATE_CODE_CONVERSION — inserts a new customer code conversion record, assigning an identifier and validating that the external/internal code pair is unique before persist.
• UPDATE_CODE_CONVERSION / UPDATE_CODE_CONVERSION_TBL — apply changes to an existing customer conversion row; the _TBL variant operates on a set or table of records, supporting bulk updates.
• DELETE_CODE_CONVERSION / DELETE_CODE_CONVERSION_TBL — remove one or many customer conversion records.
• CHECK_UNIQ_CODE_CONVERSION — verifies that no duplicate conversion exists for the same party, customer account, value set, and code pair.
• VALIDATE_CODE_CONVERSION_REC / VALIDATE_CODE_CONVERSION — perform mandatory-field, date-range, and referential validation on conversion data before insert or update.
• CONVERT_CODE — the runtime lookup routine that resolves an external code to its internal counterpart (or the reverse) using the active conversion rules defined for the relevant organization and value set.
• CREATE_SUPP_CODE_CONVERSION — the supplier-side equivalent of CREATE_CODE_CONVERSION, inserting records into OZF_SUPP_CODE_CONVERSIONS.
• UPDATE_SUPP_CODE_CONVERSION / UPDATE_SUPP_CODE_CONV_TBL — modify single or multiple supplier conversion rows.
• DELETE_SUPP_CODE_CONVERSION / DELETE_SUPP_CODE_CONV_TBL — remove single or multiple supplier conversion records.

The package also declares the record type code_conversion_rec_type, whose fields mirror the OZF_CODE_CONVERSIONS columns, and the constant G_DEFAULT_NUM_REC_FETCH set to 30, controlling the default bulk fetch size.

Tables Accessed

The package reads and writes OZF_CODE_CONVERSIONS, OZF_CODE_CONVERSIONS_ALL, and its sequence OZF_CODE_CONVERSIONS_ALL_S for customer conversion data, and OZF_SUPP_CODE_CONVERSIONS, OZF_SUPP_CODE_CONVERSIONS_ALL, and OZF_SUPP_CODE_CONV_ALL_S for supplier conversion data. It also references OZF_CLAIMS, OZF_RESALE_ADJUSTMENTS, OZF_RESALE_BATCHES, OZF_RESALE_BATCH_LINE_MAPS, OZF_RESALE_LINES, and OZF_RESALE_LINES_INT, which consume the resolved codes during claim and resale processing. OZF_SYS_PARAMETERS supplies configuration values such as defaulting and validation rules. DUAL and PLITBLM are used for standard PL/SQL and bulk-bind operations.

Usage Notes

Because OZF_CODE_CONVERSION_PVT is a private package, it is normally invoked indirectly through the corresponding public OZF APIs or through the Trade Management setup forms that maintain code conversions. Integrations that need to bulk-load supplier conversion data should call the public wrapper rather than referencing CREATE_SUPP_CODE_CONVERSION directly. The CONVERT_CODE routine is called at runtime by claim and resale processing to translate partner codes. Five other packages are documented as referencing this package, reinforcing its role as a shared service. Sites on 12.1.1 and 12.2.2 should treat the package signature as stable but non-public, and verify against the deployed version before embedding direct calls in custom code.