Search Results activate_agreement

Overview

The APPS.OKL_SEC_CONCURRENT_PVT package is a private (PVT classification) PL/SQL package within the Oracle E-Business Suite Lease Management (OKL) module. It provides the underlying program logic that supports secure concurrent processing of lease agreement lifecycle operations in Oracle EBS 12.1.1 and 12.2.2. Specifically, the package is designed to handle the programmatic activation of lease agreements and buyback agreements in a controlled, concurrent-safe manner — typically from a concurrent program or background job that must operate independently of an interactive form session.

The package acts as a private implementation layer, exposed to callers only indirectly through the public wrapper package OKL_SEC_CONCURRENT_PVT_W. This naming convention (a "_PVT" package paired with a "_PVT_W" wrapper) is standard in ETRM and other Oracle application families, where the private package contains the substantive business logic and the wrapper provides the public API signature and validation entry points. Internal dependency metadata confirms that OKL_SEC_CONCURRENT_PVT depends on FND_API and OKL_API, indicating that it conforms to the Oracle Application Object Library API standards, including standard return-status conventions (success, warning, error) and message-stack handling.

Key Procedures and Functions

The package exposes three documented procedures:

• ACTIVATE_AGREEMENT — Performs the core activation logic for a lease agreement. This is the primary business operation, marking an agreement as active and executing the associated lifecycle side effects such as status transition, accounting option resolution, and downstream record generation.
• ACTIVATE_AGREEMENT_UI — A variant of the activation routine intended to be invoked in the context of the user interface, providing the behavior expected when activation is triggered from a form or UI-driven flow.
• BUYBACK_AGREEMENT — Handles activation or processing specific to buyback agreements, which are lease arrangements containing an end-of-term buyback clause requiring separate treatment from standard lease activation.

All three procedures follow the OAF/ETRM API convention of returning a status code and populating the FND message stack. No parameter lists are documented in the reference metadata, so specific argument signatures are not asserted here.

Tables Accessed

The package reads and writes through APPS synonyms referenced in the ETRM documentation:

• OKC_K_HEADERS_ALL_B, OKC_K_HEADERS_B — Core contract/lease header records, including the base and translation-independent header rows whose status is updated during activation.
• OKC_K_LINES_B, OKC_K_LINES_TL — Contract line records and their translatable description columns, supporting line-level validation during activation.
• OKC_K_PARTY_ROLES_B — Party-role assignments on the contract, used to confirm the parties required for a valid activation.
• OKL_POOLS, OKL_POOL_CONTENTS — Lease pool definitions and pool contents, relevant to buyback and pooled-asset agreements.
• OKL_STRM_TYPE_B — Stream type definitions used to resolve the pricing/streaming structure of the agreement.
• OKL_SYS_ACCT_OPTS — System accounting options, consulted to determine the accounting treatment applied at activation.
• PLITBLM — A PL/SQL index-by table type used internally for bulk message handling.

Usage Notes

Because OKL_SEC_CONCURRENT_PVT is a private package, it should not be called directly from custom code. Standard practice is to invoke the public wrapper OKL_SEC_CONCURRENT_PVT_W, which is the object referenced by one other package according to the documented metadata. The package is typically driven by a concurrent program or a background submission that activates lease agreements without occupying an interactive session. Customizations requiring agreement activation should call the _W wrapper to preserve API compatibility and message-stack behavior. Direct calls to the _PVT package risk bypassing validation and are not supported across upgrades.