Search Results rbk_srl_num_ib_instance

Overview

OKL_ACTIVATE_IB_PVT is a private PL/SQL package in the APPS schema that forms part of the Oracle Lease and Finance Management (OKL) module within Oracle E-Business Suite 12.1.1 and 12.2.2. Its name reflects its role within the Installed Base (IB) activation process flow. The package serves as the private implementation layer that supports the public activation APIs, specifically manipulating Oracle Installed Base (CSI) instance records and associated contract data during the activation of lease contracts and the underlying assets. In the ETRM (Enterprise Transaction and Reference Model) classification, this package is designated as type "PVT," indicating it is an internal or private package not intended for direct invocation by external or custom code. Public wrappers such as OKL_ACTIVATE_IB_PUB expose its functionality to calling applications, while OKL_ACTIVATE_IB_PVT performs the granular processing logic. The package operates at the intersection of the OKL lease management schema and the CSI Installed Base schema, coordinating updates to contract instances, serial numbers, and party relationships when an asset is placed into service or released from a lease agreement.

Key Procedures and Functions

The package exposes six documented procedures and functions, all of which support the activation, release, and reversal of Installed Base instances tied to lease contracts:

• ACTIVATE_IB_INSTANCE — The core procedure that activates an Installed Base instance when an asset enters a leased state. It coordinates the creation or update of CSI instance records and links them to the associated contract.
• ACTIVATE_RBK_IB_INST — Handles activation of an Installed Base instance in the context of a rebooking (RBK) scenario, where a contract or asset is rebooked, requiring the IB records to be activated in alignment with the new contract terms.
• RELEASE_IB_INSTANCE — Manages the release of an Installed Base instance, typically when a lease terminates or an asset is returned, updating the CSI instance status accordingly.
• RBK_SRL_NUM_IB_INSTANCE — Processes serial number handling for Installed Base instances during rebooking operations, ensuring serial number tracking remains consistent across contract transitions.
• QC — A quality-control or validation helper procedure that performs consistency checks before or after the main activation steps, validating that contract and Installed Base data align.
• API_COPY — A utility procedure for copying API context or data structures, supporting the internal invocation pattern used by the private package to delegate to public APIs.

Tables Accessed

The package reads and writes to tables across the CSI (Installed Base) and OKC (Contracts Core) schemas, accessed via APPS synonyms. Key CSI tables include CSI_ITEM_INSTANCES (the master Installed Base instance records), CSI_INSTANCE_STATUSES (tracking current status values), CSI_I_PARTIES and CSI_TXN_TYPES (party relationships and transaction typing for instances). On the contract side, it touches OKC_K_HEADERS_B, OKC_K_LINES_B, OKC_K_ITEMS, OKC_K_PARTY_ROLES_B, OKC_LINE_STYLES_B, and OKC_STATUSES_B, which define contract headers, lines, items, party roles, line styles, and statuses. It also references HZ_PARTIES, HZ_PARTY_SITES, and HZ_PARTY_SITE_USES for trading community party data, and MTL_SYSTEM_ITEMS and MTL_PARAMETERS for inventory item and organization validation.

Usage Notes

Because OKL_ACTIVATE_IB_PVT is a private package, it is not intended for direct invocation by customers or customizations. It is invoked indirectly through public APIs including OKL_ACTIVATE_IB_PUB, OKL_ACTIVATE_ASSET_PVT, OKL_ACTIVATE_CONTRACT_PUB, and OKL_RELEASE_PVT, making it a transitive dependency for any process that activates assets or releases leases. In practice, these flows are triggered from Lease Management forms, concurrent programs that mass-process contract activation or termination, and integration points that synchronize lease data with Installed Base. Custom code should always call the public OKL_ACTIVATE_IB_PUB or OKL_RELEASE_PVT APIs rather than the private package, and Oracle may change the private package's internals between releases without notice. Dependency tracking shows OKL_ACTIVATE_IB_PVT also references OKC_API, OKL_API, OKL_ITI_PVT, OKL_OKC_MIGRATION_PVT, OKL_TXL_ITM_INSTS_PUB, and CSI_DATASTRUCTURES_PUB, confirming its role as an orchestration layer across contract, tax, and Installed Base services.