Search Results copy_config

Overview

OKC_CFG_PUB is a public PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module that provides the integration layer between Oracle Contracts authoring and Oracle Configurator (CZ). Its principal responsibility is to interpret configuration data captured against a contract line — either from the Contract Authoring form (OKCAUDET.fmx) or from a Configurator session — and to instantiate, validate, and price the resulting configuration structure inside the Contracts data model. In Release 12.1.1 and 12.2.2 the package is owned by APPS and carries the PUB API classification, meaning its procedures are intended for external invocation by forms, concurrent programs, and other application modules.

The package defines two documented PL/SQL record and table types used internally and by callers. The au_rec_type record mirrors the configuration-related contract line attributes obtained from the Authoring form, including configuration header and revision identifiers, quantity, UOM, inventory item, line number, effective dates, currency, negotiated price, and header-level estimated amount and price list. The au_tbl_type collection, indexed by BINARY_INTEGER, is the corresponding array of these records. A second record structure, config_rec_type, carries detailed configuration information sourced from Oracle Configurator. These structures are populated with FND_API.G_MISS_* sentinel values, consistent with standard EBS API conventions for distinguishing supplied from unsupplied attributes.

Key Procedures and Functions

• COPY_CONFIG — Reproduces an existing configuration onto a target contract line or document, providing the copy semantics required when a configured item must be replicated. This is the entry point most commonly associated with the "copy_config" search term.
• CLE_CONFIG_CHECK — Performs validation of Contract Line Effectivity (CLE) configuration data, confirming that the configuration associated with a line satisfies the structural and effectivity rules required before the line is accepted.
• BUILD_CLE_FROM_CZ — Builds Contract Line Effectivity records from Oracle Configurator output, translating the Configurator result set into the Contracts configuration hierarchy.
• CONFIG_QA_CHECK — Executes quality-assurance validation over configuration data, verifying completeness and internal consistency prior to further processing.
• OKC_PRICING_CALLBACK — Serves as the pricing callback invoked during configuration processing, integrating the Contracts configuration with the pricing engine so that configured lines receive appropriate pricing.

Tables Accessed

The package operates against five documented tables through APPS synonyms. OKC_K_HEADERS_B stores the contract header definition and supplies header-level context such as currency, price list, and estimated amount. OKC_K_LINES_B holds the contract line definition into which configuration data is written. OKC_K_ITEMS stores the individual configured items belonging to a line and is the principal target for configuration instantiation. CZ_PRICING_STRUCTURES provides the Oracle Configurator pricing structure data consumed during pricing callbacks. PLITBLM is the standard EBS table used for storing and retrieving PL/SQL table data in a form context, supporting the passing of the au and config record structures between the form and the database package.

Usage Notes

OKC_CFG_PUB is invoked primarily from the Contract Authoring user interface, where the OKCAUDET form calls the package to validate and persist configuration detail for a contract line. It is also called programmatically during order-to-contract flows, where Configurator results must be converted into Contracts configuration structures via BUILD_CLE_FROM_CZ, and during pricing activities through OKC_PRICING_CALLBACK. The package is referenced by one other documented package, indicating that it functions as a shared service within the Contracts configuration stack rather than as a standalone utility. Because the procedures are classified as PUBLIC, custom extensions and integrations may call them directly; however, callers must observe the FND_API sentinel conventions for the record types and should not assume parameter signatures beyond those published in the ETRM documentation. In 12.1.1 and 12.2.2 the package is shipped as a standard, non-customized Contracts component, and the version header indicates a stable interface that has not required structural revision since its original delivery.