Search Results validate_code_conversion




Overview
Explore in AI Chat

Overview

OZF_CODE_CONVERSION_PVT_W is a private PL/SQL package in the Oracle EBS APPS schema that supports the Trade Management (formerly Oracle Trade Management, product code OZF) code conversion infrastructure. The package exposes the programmatic interface used to maintain, validate, and detect duplicate entries in the code conversion tables that map legacy or external codes to Oracle EBS internal identifiers. It is a wrapper ("_W") package, meaning its procedures are generated as friendly, NLS-agnostic wrappers over the corresponding private (PVT) implementation package, OZF_CODE_CONVERSION_PVT. The wrapper exposes strongly typed JTF collection parameters that allow bulk transfer of code conversion records between the database and calling Java, Forms, or OAF layers via the Rosetta table-copy mechanism. In the 12.1.1 and 12.2.2 releases, the package is part of the standard APPS code set and is compiled with AUTHID CURRENT_USER, so it executes under the privileges of the invoking user and relies on APPS synonyms for cross-schema access.

Key Procedures and Functions

  • ROSETTA_TABLE_COPY_IN_P3 — Copies an inbound set of JTF typed arrays into a code_conversion_tbl_type PL/SQL collection. Used to marshal bulk rows from a client (typically a Java or Forms layer) into the private package for processing.
  • ROSETTA_TABLE_COPY_OUT_P3 — The inverse operation: copies a populated code_conversion_tbl_type collection back into the out JTF typed arrays for return to the caller.
  • ROSETTA_TABLE_COPY_IN_P15 / ROSETTA_TABLE_COPY_OUT_P15 — Alternative Rosetta marshalling variants used for the supplementary code conversion table, distinguished by the number and types of typed array parameters required for that record structure.
  • UPDATE_CODE_CONVERSION_TBL — Applies updates to existing code conversion rows, typically invoked by the code conversion maintenance UI.
  • DELETE_CODE_CONVERSION_TBL — Removes code conversion rows identified by the caller.
  • CHECK_UNIQ_CODE_CONVERSION — Verifies uniqueness of a proposed conversion mapping, preventing duplicate source or target code combinations from being inserted.
  • VALIDATE_CODE_CONVERSION — Validates a code conversion record against the business rules of the code conversion setup before it is saved. This is the procedure most commonly searched for as "validate_code_conversion" and is invoked to confirm that the supplied mapping is complete, correctly typed, and consistent with existing configuration.
  • UPDATE_SUPP_CODE_CONV_TBL / DELETE_SUPP_CODE_CONV_TBL — Corresponding update and delete operations for the supplementary code conversion table, which stores ancillary mappings associated with the primary conversion records.

Tables Accessed

The documented table reference for this package is PLITBLM, an APPS synonym that is part of the PL/SQL table access infrastructure used by the Rosetta and generic collection handling routines. PLITBLM supports the temporary storage and retrieval of bulk typed array data during the copy-in and copy-out operations, allowing large sets of conversion rows to cross the client/server boundary efficiently. The private implementation (OZF_CODE_CONVERSION_PVT) performs the actual DML against the OZF code conversion base tables; the wrapper package surfaces this functionality without exposing the underlying table structures directly to callers.

Usage Notes

OZF_CODE_CONVERSION_PVT_W is not intended to be called directly by end users or by ad-hoc SQL. It is normally invoked by Trade Management code conversion setup forms, OAF pages, or Java-based integration services that need to create, validate, or delete code mappings. Custom code that must manipulate code conversion records should call the _W procedures rather than issuing direct DML against the base tables, because the wrapper enforces the validation and uniqueness rules implemented in VALIDATE_CODE_CONVERSION and CHECK_UNIQ_CODE_CONVERSION. The package is referenced by zero other APPS packages according to the ETRM metadata, confirming its role as an API entry point rather than a shared internal utility. Because it is compiled AUTHID CURRENT_USER, callers must ensure the invoking schema has the necessary privileges on the APPS synonyms and underlying objects.