Search Results delete_supp_code_conversion

Overview

OZF_CODE_CONVERSION_PVT is a private PL/SQL package owned by APPS in the Oracle E-Business Suite trade management (formerly Oracle Trade Management / OZF) schema. Its declared purpose is to maintain the code conversion definitions that map customer-specific external codes to internal Oracle EBS values. Code conversions allow a trade promotion or claims transaction to carry an identifier as it is known to a customer, reseller, or supplier, while the application internally resolves that identifier to a standard value stored in a value set. The package is classified as a PVT (private) API, meaning it is intended to be called by other OZF packages, forms logic, and concurrent programs rather than directly by external integration code. The header comment indicates creation in October 2003, with the shipped version reflecting a December 2007 update. The package is declared with AUTHID CURRENT_USER.

Key Procedures and Functions

The package exposes fourteen documented procedures and functions. The core set operates on the code conversion entity itself:

• CREATE_CODE_CONVERSION — inserts a new code conversion record, populating the code conversion record type with organization, party, and customer account context along with the external and internal code values and their active date range.
• UPDATE_CODE_CONVERSION — modifies an existing code conversion record.
• UPDATE_CODE_CONVERSION_TBL — the table-based (bulk) counterpart of the update operation, processing multiple code conversion records in a single call.
• DELETE_CODE_CONVERSION — removes a single code conversion record.
• DELETE_CODE_CONVERSION_TBL — the bulk deletion counterpart.
• CHECK_UNIQ_CODE_CONVERSION — validates that a proposed code conversion does not duplicate an existing definition for the same context.
• VALIDATE_CODE_CONVERSION_REC — performs record-level validation against the code conversion record structure.
• VALIDATE_CODE_CONVERSION — performs entity-level validation of a code conversion before it is persisted.
• CONVERT_CODE — the functional lookup routine that resolves an external code to its corresponding internal code using the stored conversion definitions.

A parallel group handles supplier-specific conversions: CREATE_SUPP_CODE_CONVERSION, UPDATE_SUPP_CODE_CONVERSION, UPDATE_SUPP_CODE_CONV_TBL, DELETE_SUPP_CODE_CONVERSION, and DELETE_SUPP_CODE_CONV_TBL. These mirror the primary operations against the supplier code conversion entity. The record type code_conversion_rec_type carries the identifier, object version number, audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN), ORG_ID, PARTY_ID, CUST_ACCOUNT_ID, CODE_CONVERSION_TYPE, VALUE_SET_ID, EXTERNAL_CODE, INTERNAL_CODE, DESCRIPTION, START_DATE_ACTIVE, END_DATE_ACTIVE, ATTRIBUTE_CATEGORY, the fifteen descriptive flexfield attributes, and SECURITY_GROUP_ID. Note that VALUE_SET_ID and VALUE_SET_ID are referenced in the same record; the package also defines a default fetch size of thirty records.

Tables Accessed

The package reads and writes OZF_CODE_CONVERSIONS and its _ALL and _ALL_S variants, which hold the base and multi-organization/security-group views of customer code conversions. Supplier conversions are stored in OZF_SUPP_CODE_CONVERSIONS, OZF_SUPP_CODE_CONVERSIONS_ALL, and OZF_SUPP_CODE_CONV_ALL_S. The package consults OZF_SYS_PARAMETERS for system-level configuration, and joins DUAL for single-row computations. PLITBLM is used as the PL/SQL index-by table type for bulk processing. Additional trade management tables — OZF_CLAIMS, OZF_RESALE_ADJUSTMENTS, OZF_RESALE_BATCHES, OZF_RESALE_BATCH_LINE_MAPS, OZF_RESALE_LINES, and OZF_RESALE_LINES_INT — are referenced by the conversion and validation logic, reflecting the dependency of code conversion on claims and resale adjustment processing.

Usage Notes

Because this is a private package, it is not documented as a public integration API. It is typically invoked indirectly by other OZF packages (it is referenced by five other packages), by the code conversion maintenance forms in the Trade Management module, and by concurrent programs that import or reconcile resale and claims data. Custom code should prefer the public code conversion API where one exists, and should treat UPDATE_CODE_CONVERSION and its table-based variant as internal entry points. The bulk (_TBL) procedures exist to support set-based processing from concurrent programs, which fetch in blocks governed by the package default of thirty records. The AUTHID CURRENT_USER declaration means execution privileges are evaluated against the calling schema.