Search Results configure_from_html_ui

Overview

APPS.CSI_CZ_INT is a PL/SQL integration package body belonging to the Oracle EBS Configure-to-Order (Cto) and Installed Base application family, bridging the CSI (Customer Service/Installed Base) schema with the CZ (Configurator) schema. Its header revision ($Header: csigczib.pls 120.5, dated 2006) marks it as a legacy integration unit that has been maintained across the 11i, 12.1.1, and 12.2.2 code lines. The package's central business function is to resolve and manage configuration revisions and item-instance locking for configured items — that is, items whose structure is driven by a Configurator model rather than a static bill of material.

The package exposes ten documented procedures that span configuration retrieval (GET_CONFIGURATION_REVISION, GET_CONNECTED_CONFIGURATIONS), UI-driven configuration creation (CONFIGURE_FROM_HTML_UI), tree generation (GENERATE_CONFIG_TREES), configurability checks (IS_CONFIGURABLE, CSI_CONFIG_LAUNCH_PRMS), and instance-level concurrency control (CHECK_ITEM_INSTANCE_LOCK, LOCK_ITEM_INSTANCES, UNLOCK_CURRENT_NODE, UNLOCK_ITEM_INSTANCES). It is referenced by eleven other packages, indicating it is a shared utility layer rather than an end-user-facing entry point.

Key Procedures and Functions

• GET_CONFIGURATION_REVISION — Resolves the applicable configuration revision number for a configuration header, given a target commitment date. It distinguishes installed revisions (from csi_item_instances) from proposed revisions (from the transaction-line tables), which is critical for as-of-date configuration queries.
• GET_CONNECTED_CONFIGURATIONS — Returns configurations connected to a given instance via the CSI item-instance relationship graph.
• CONFIGURE_FROM_HTML_UI — Supports configuration creation initiated from an HTML/self-service UI rather than the professional Forms interface.
• CSI_CONFIG_LAUNCH_PRMS — Derives the launch parameters needed to invoke the Configurator for a given item, used when determining whether a "Configure" action should be enabled.
• IS_CONFIGURABLE — Predicate that determines whether an inventory item is configurable, gating downstream configuration logic.
• GENERATE_CONFIG_TREES — Builds the hierarchical configuration tree structure for display or processing.
• CHECK_ITEM_INSTANCE_LOCK — Tests whether an item instance is currently locked, typically before attempting a modify or delete.
• LOCK_ITEM_INSTANCES — Acquires locks on one or more item instances to serialize concurrent configuration edits.
• UNLOCK_CURRENT_NODE — Releases the lock held on the currently active configuration node. This is the procedure most commonly searched for; it is invoked when the user navigates away from or completes work on a node in the Configurator UI.
• UNLOCK_ITEM_INSTANCES — Bulk counterpart to UNLOCK_CURRENT_NODE, clearing locks on a set of instances.

Tables Accessed

• CSI_ITEM_INSTANCES — Read to obtain installed configuration revision numbers and instance attributes.
• CSI_ITEM_INSTANCE_LOCKS — Read/written by CHECK, LOCK, and UNLOCK procedures to enforce instance-level locking.
• CSI_II_RELATIONSHIPS / CSI_T_II_RELATIONSHIPS — Traversed to resolve connected configurations and parent/child instance links.
• CSI_T_TRANSACTION_LINES / CSI_T_TXN_LINE_DETAILS — Read to derive proposed (uncommitted) configuration revisions.
• CZ_CONFIG_ITEMS — Read to map configurator components to CSI instances, distinguishing root ('I') from other component types.
• PLITBLM — The standard PL/SQL table used for message handling.

Usage Notes

CSI_CZ_INT is not a user-invoked package; it is called from Oracle's Configure-to-Order Forms (e.g., the item instance and configuration workbenches), from the HTML Configurator flow, and from other CSI/CZ integration packages. On 12.1.1 and 12.2.2, customizations that manipulate configured item instances should call the LOCK/UNLOCK family rather than updating CSI_ITEM_INSTANCE_LOCKS directly, to preserve concurrency semantics. Debug and API-log procedures route output through CSI_T_GEN_UTILITY_PVT. Comments in the body reference bug fixes 3502896, 3901123, and 4147624, reflecting cumulative performance and locking refinements; any modifications should be evaluated against those behaviors.