Search Results ozf_code_conversion_pkg




Overview
Explore in AI Chat

Overview

OZF_CODE_CONVERSION_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the Trade Management (formerly Oracle Sales and Marketing / Oracle Incentive Compensation) product family, as indicated by the OZF prefix. Its core business function is to manage the code conversion definitions used within Oracle Trade Management to translate or map external codes—such as distributor, customer, or supplier codes—into the internal codes recognized by the EBS application. This mapping capability is essential when integrating Trade Management with external systems, third-party data feeds, or legacy applications where the incoming identification codes differ from the standardized values stored in the EBS tables.

The package provides the standard programmatic interface for creating, maintaining, and removing code conversion records, both for general conversions and for supplementary conversions. It underpins the data integrity of the conversion tables and serves as the supported API layer that other EBS components—most notably OZF_CODE_CONVERSION_PVT—depend on for their processing logic.

Key Procedures and Functions

The ETRM metadata documents six procedures, organized into two functional pairs:

  • INSERT_ROW — Creates a new code conversion record in the primary conversions table, establishing the mapping between an external code and its internal counterpart.
  • UPDATE_ROW — Modifies the attributes of an existing primary code conversion record.
  • DELETE_ROW — Removes an existing primary code conversion record.
  • INSERT_SUPP_CODE_CONV_ROW — Creates a new supplementary code conversion record, typically used for secondary or additional conversion mappings associated with a primary conversion.
  • UPDATE_SUPP_CODE_CONV_ROW — Modifies an existing supplementary code conversion record.
  • DELETE_SUPP_CODE_CONV_ROW — Removes an existing supplementary code conversion record.

These procedures represent the complete lifecycle (insert, update, delete) for both the primary and supplementary conversion entities. No parameter lists are documented in the ETRM metadata; callers should reference the live package specification in the APPS schema for exact signatures.

Tables Accessed

The package operates against two documented base tables, referenced through APPS synonyms:

  • OZF_CODE_CONVERSIONS_ALL — Stores the primary code conversion definitions. The "_ALL" suffix indicates an organization- or operating-unit-aware table, meaning conversion records may be partitioned by organization context. INSERT_ROW, UPDATE_ROW, and DELETE_ROW write to and maintain this table.
  • OZF_SUPP_CODE_CONVERSIONS_ALL — Stores supplementary code conversion definitions that extend or qualify the primary conversions. INSERT_SUPP_CODE_CONV_ROW, UPDATE_SUPP_CODE_CONV_ROW, and DELETE_SUPP_CODE_CONV_ROW maintain this table.

These tables form the persistence layer for the code-mapping functionality and are the direct targets of the package's data manipulation logic.

Usage Notes

OZF_CODE_CONVERSION_PKG is the private implementation package within a two-tier design pattern. The ETRM dependency metadata confirms that it is referenced by OZF_CODE_CONVERSION_PVT, the public API package. Standard EBS development practice dictates that external callers invoke the PVT (private) package, which in turn delegates DML operations to this PKG package. Direct invocation of OZF_CODE_CONVERSION_PKG by custom code is therefore discouraged in favor of the PVT layer, unless the PVT does not expose a required operation.

The package is typically exercised from Trade Management setup forms (code conversion maintenance windows) and from integration or conversion programs that load external code mappings during implementation. Because the package is validated (Status: VALID) in both EBS 12.1.1 and 12.2.2, its interface is stable across these releases. As with all EBS APIs, callers should observe standard transaction control conventions—committing or rolling back their work explicitly—and audit any data seeded through seeding programs.