Search Results create_code_conversion

Overview

APPS.OZF_CODE_CONVERSION_PVT is a private PL/SQL package within the Oracle E-Business Suite Trade Management (formerly Oracle Trade Management / OZF) schema. Its primary business function is to manage the mapping between external customer-facing codes and internal Oracle EBS codes, a capability central to partner and reseller transactions, claims, and resale adjustments. In Oracle EBS 12.1.1 and 12.2.2, this package supports the Code Conversion feature that allows organizations to translate codes transmitted by external trading partners, such as resellers, distributors, or customers, into the internal codes recognized by Oracle applications. The package also provides a parallel code conversion mechanism specifically for supplier-side (supp) conversions, reflecting the bilateral nature of channel and resale data exchange in Trade Management. Because the package is classified as PVT (private), it is not intended as a public API; it is invoked by other Trade Management packages and forms rather than called directly by external integrators. The header comment dates the package to 2003, and the metadata indicates it is referenced by five other packages, underscoring its role as an internal utility layer for code translation logic within the OZF product family.

Key Procedures and Functions

The package exposes 14 documented procedures and functions. The core conversion lifecycle is handled by CREATE_CODE_CONVERSION and UPDATE_CODE_CONVERSION, which insert and modify code conversion definition records. UPDATE_CODE_CONVERSION_TBL and DELETE_CODE_CONVERSION_TBL provide table-level (bulk) update and delete handling, while DELETE_CODE_CONVERSION removes individual conversion records. CHECK_UNIQ_CODE_CONVERSION enforces uniqueness of a conversion definition, preventing conflicting mappings. VALIDATE_CODE_CONVERSION_REC and VALIDATE_CODE_CONVERSION perform validation of the record structure and its business rules before persistence. CONVERT_CODE is the functional workhorse that applies an existing conversion definition to translate an external code into its internal equivalent. A parallel set of supplier-oriented routines is provided: CREATE_SUPP_CODE_CONVERSION and UPDATE_SUPP_CODE_CONVERSION manage supplier code conversion definitions, with UPDATE_SUPP_CODE_CONV_TBL and DELETE_SUPP_CODE_CONV_TBL supplying bulk update and delete operations. Together these procedures implement a consistent validation, uniqueness, and lifecycle pattern across both customer and supplier conversion domains.

Tables Accessed

The package reads and writes the code conversion base and interface tables OZF_CODE_CONVERSIONS, OZF_CODE_CONVERSIONS_ALL, and its sequence OZF_CODE_CONVERSIONS_ALL_S. Supplier conversions are stored in OZF_SUPP_CODE_CONVERSIONS, OZF_SUPP_CODE_CONVERSIONS_ALL, and OZF_SUPP_CODE_CONV_ALL_S. It references OZF_CLAIMS, OZF_RESALE_ADJUSTMENTS, OZF_RESALE_BATCHES, OZF_RESALE_BATCH_LINE_MAPS, OZF_RESALE_LINES, and OZF_RESALE_LINES_INT because code conversions are consumed during claims processing and resale batch line mapping. OZF_SYS_PARAMETERS supplies system-level configuration, DUAL is used for trivial queries, and PLITBLM is the standard PL/SQL index-by table type used for bulk collection operations.

Usage Notes

Because OZF_CODE_CONVERSION_PVT is a private package, it is not invoked directly through concurrent programs. It is called internally by Trade Management forms and by the five documented dependent packages, typically during claim entry, resale batch import, and interface processing where external codes must be resolved. Custom code should not call this package directly; instead, integrators should use the corresponding public APIs or interface tables. The presence of UPDATE_*_TBL and DELETE_*_TBL procedures confirms that bulk DML is used during concurrent import and cleanup processes, where the G_DEFAULT_NUM_REC_FETCH constant of 30 governs fetch batching. Administrators modifying code conversion definitions should do so through the supported Trade Management UI or public APIs so that the validation and uniqueness checks in this package are consistently enforced in both 12.1.1 and 12.2.2.