Search Results convert_code

Overview

OZF_CODE_CONVERSION_PVT is a private (PVT) PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Trade Management (formerly Oracle Marketing) family of modules, as indicated by the OZF object prefix and the associated OZF_CODE_CONVERSIONS, OZF_RESALE_ADJUSTMENTS, and OZF_CLAIMS tables. The package encapsulates the business logic for maintaining and applying code conversions — mappings between external codes (for example, customer, product, or promotion identifiers supplied by external systems or channel partners) and internal EBS codes. Its header declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user, and exposes a PL/SQL record type, code_conversion_rec_type, that models a full code-conversion row including ORG_ID, PARTY_ID, CUST_ACCOUNT_ID, CODE_CONVERSION_TYPE, a VALUE_SET_ID, EXTERNAL_CODE, INTERNAL_CODE, description, effective dates, and the standard 15 attribute columns and audit columns. The package also defines the global constant G_DEFAULT_NUM_REC_FETCH (30), controlling the batch size for bulk record fetching.

Key Procedures and Functions

The documented API surface comprises fourteen procedures and functions, split between standard code-conversion maintenance and supplier-specific variants:

• CREATE_CODE_CONVERSION — inserts a new code-conversion mapping into the conversion tables.
• UPDATE_CODE_CONVERSION / UPDATE_CODE_CONVERSION_TBL — modify an existing conversion; the _TBL variant supports bulk, table-driven updates.
• DELETE_CODE_CONVERSION / DELETE_CODE_CONVERSION_TBL — remove a single conversion, or process deletions in bulk.
• CHECK_UNIQ_CODE_CONVERSION — validates uniqueness of a conversion, preventing duplicate external-to-internal mappings.
• VALIDATE_CODE_CONVERSION_REC / VALIDATE_CODE_CONVERSION — perform record-level and scalar-level validation of mandatory fields, dates, and referential integrity before persistence.
• CONVERT_CODE — the core lookup routine that translates an external code to its internal equivalent (or vice versa) using the stored mappings.
• CREATE_SUPP_CODE_CONVERSION — creates a supplier-scoped code conversion.
• UPDATE_SUPP_CODE_CONVERSION / UPDATE_SUPP_CODE_CONV_TBL — update supplier conversions singly or in bulk.
• DELETE_SUPP_CODE_CONVERSION / DELETE_SUPP_CODE_CONV_TBL — delete supplier conversions singly or in bulk.

Tables Accessed

All tables are referenced through APPS synonyms. Primary read/write targets are OZF_CODE_CONVERSIONS, OZF_CODE_CONVERSIONS_ALL, and OZF_CODE_CONVERSIONS_ALL_S, which store the conversion definitions and their security-group translation rows. Supplier-scoped conversions reside in OZF_SUPP_CODE_CONVERSIONS, OZF_SUPP_CODE_CONVERSIONS_ALL, and OZF_SUPP_CODE_CONV_ALL_S. The resale subsystem tables — OZF_RESALE_ADJUSTMENTS, OZF_RESALE_BATCHES, OZF_RESALE_BATCH_LINE_MAPS, OZF_RESALE_LINES, and OZF_RESALE_LINES_INT — are accessed because code conversions are applied when resale and adjustment data is processed. OZF_CLAIMS and OZF_SYS_PARAMETERS provide claim-related and system-parameter lookups, while DUAL and PLITBLM support scalar queries and PL/SQL table (index-by table) operations used by the bulk procedures.

Usage Notes

As a PVT (private) package, OZF_CODE_CONVERSION_PVT is not a supported public API; it is invoked internally by Oracle Trade Management forms, concurrent programs, and related PL/SQL such as the ETRM metadata note that it is referenced by five other packages. Functional flows that import channel or third-party data, reconcile claims and resale transactions, or resolve supplier identifiers rely on CONVERT_CODE to standardize codes before processing. Customizations should not call this package directly. Where code conversion maintenance is required, developers should use the supported public APIs or the standard Trade Management setup forms; direct invocation of _PVT procedures bypasses validation ordering and may violate security-group and multi-org (ORG_ID) expectations enforced by the _ALL and _ALL_S tables.