Search Results csi_config_launch_prms

Overview

APPS.CSI_CZ_INT is a PL/SQL integration package within the Oracle E-Business Suite (EBS) Configure-to-Order (CTO) and Oracle Configurator framework. It resides in the Application Object Library (APPS) schema and is classified under ETRM with an API classification of OTHER, indicating that it functions as an internal integration layer rather than a formally published public API. The package provides the runtime bridge between Oracle Configurator model structures and the installed base records maintained by the CSI (Customer Support & Installed Base) module.

In practice, CSI_CZ_INT enables Oracle Configurator and Oracle Order Management to resolve configuration definitions, link configured assemblies to item instances in the installed base, and serialize concurrent access to those instances during configuration generation. Its header records a version timestamp of 2005 and references bug fixes for root keys (bug 3892929) and multi-application configuration dependency (MACD) locking (bug 4147624), confirming its role in managing locked and connected configuration nodes across the installed base.

Key Procedures and Functions

The package exposes ten documented procedures and functions:

• GET_CONFIGURATION_REVISION — Retrieves configuration revision information for a given configuration record, returning revision numbers keyed to a configuration header.
• GET_CONNECTED_CONFIGURATIONS — Returns the set of configurations connected to a subject configuration through relationship records, supporting hierarchical and peer configuration queries.
• CONFIGURE_FROM_HTML_UI — Services configuration requests originating from the HTML-based Configurator user interface, translating UI selections into configuration records.
• CSI_CONFIG_LAUNCH_PRMS — Populates launch parameters used to initialize a configuration session, including context identifiers passed between Configurator and the installed base.
• IS_CONFIGURABLE — Determines whether a given item is eligible for configuration, returning a boolean-style indicator used by validation logic.
• GENERATE_CONFIG_TREES — Builds the configuration tree structure for a model, using the config_model_rec_type record to output item, organization, and configuration identifiers.
• CHECK_ITEM_INSTANCE_LOCK — Verifies whether a specific item instance is currently locked before permitting modification.
• LOCK_ITEM_INSTANCES — Acquires locks on item instances to prevent concurrent modification during configuration operations.
• UNLOCK_CURRENT_NODE — Releases the lock held on the current configuration node.
• UNLOCK_ITEM_INSTANCES — Releases locks on item instances upon completion of configuration processing.

Tables Accessed

The package reads and writes several installed base and Configurator tables via APPS synonyms:

• CSI_ITEM_INSTANCES — Core installed base instance records; read during lock checks and updated with configuration associations.
• CSI_II_RELATIONSHIPS and CSI_T_II_RELATIONSHIPS — Item instance relationship definitions linking configured parents to children.
• CSI_ITEM_INSTANCE_LOCKS — Stores lock records managed by the lock and unlock procedures.
• CSI_T_TRANSACTION_LINES and CSI_T_TXN_LINE_DETAILS — Transaction line and detail staging tables used to associate configuration output with transactional context.
• CZ_CONFIG_ITEMS — Oracle Configurator configuration item definitions, read during configuration tree generation.
• PLITBLM — PL/SQL index-by table infrastructure used for bulk data handling.

Usage Notes

CSI_CZ_INT is typically invoked indirectly rather than through direct user calls. It is referenced by eleven other packages, positioning it as a dependency in the Configurator and installed base call stack. It is most commonly executed during configuration generation from Oracle Configurator, when creating or modifying configured items through Order Management, and when the HTML-based Configurator UI submits configuration payloads. Because the package manages instance locking, it is critical in multi-user environments where concurrent configuration edits must be serialized. Custom extensions should generally call higher-level public APIs rather than CSI_CZ_INT directly, as its classification as OTHER signals an internal interface subject to change between releases.