Search Results okc_inst_cnd_pub




Overview
Explore in AI Chat

Overview

OKC_INST_CND_PUB is the public API package body for managing installment conditions within Oracle Service Contracts (OKC) in Oracle E-Business Suite. It belongs to the Contracts Intelligence / Service Contracts module family and operates under the APPS schema, exposed to callers as the standard interface for installment-related condition processing. The package forms part of the layered OKC architecture, where public packages (suffix _PUB) act as the supported entry point for external callers, delegating business logic to private packages (suffix _PVT) and shared utilities (OKC_API, FND_API).

The "INST" prefix denotes installment, while "CND" denotes condition, reflecting the practice of associating payment or billing conditions with installment schedules on a contract. The body is documented as VALID in both EBS 12.1.1 and 12.2.2, and it is not referenced by any other database object, confirming that it exists purely to be invoked by external callers such as forms, concurrent programs, or custom code rather than by internal database dependencies.

Key Procedures and Functions

The documented interface exposes a single procedure:

  • INST_CONDITION — The primary routine for processing installment conditions. It encapsulates the creation or maintenance of installment condition data on behalf of the caller, invoking the underlying private implementation in OKC_INST_CND_PUB's partner package OKC_INST_CND_PVT and relying on OKC_API for shared contract-level validation and concurrency handling. The procedure follows the standard EBS API conventions: it is designed to be called inside a caller-controlled transaction, with error signalling surfaced through the FND_API message stack rather than raised exceptions alone.

The body depends on FND_API, FND_PROFILE, OKC_API, OKC_INST_CND_PUB (recursive self-reference for the package specification), OKC_INST_CND_PVT, and the SYS STANDARD package. No parameter lists are documented in the ETRM metadata, and none should be assumed; callers should obtain the exact signature from the package specification in the target release.

Tables Accessed

The ETRM metadata does not enumerate the tables accessed directly through APPS synonyms for this package. Based on the package name and its dependency on OKC_INST_CND_PVT, the body works with the installment condition structures maintained by the private layer — the OKC installment and condition base tables reached through APPS synonyms. All such access is performed indirectly: the public body validates input and calls the private package, which performs the actual DML. Because the metadata does not list concrete table names, readers should trace the private package dependencies in the target instance for a definitive table list.

Usage Notes

OKC_INST_CND_PUB is invoked whenever a business process must establish, modify, or validate an installment condition against a contract. Typical call sites include Service Contracts forms that manage installment billing schedules, concurrent programs that generate or regenerate installment conditions in batch, and custom PL/SQL extensions that need to create installment conditions as part of an integration or data-conversion routine.

Because the package is documented as referenced by six other packages, it is a genuine integration point within the OKC stack, and the recommended calling convention is to use OKC_INST_CND_PUB rather than the private OKC_INST_CND_PVT. Callers should initialize the FND_API global variables, invoke INST_CONDITION within an explicitly managed transaction, check the FND_API return status, and commit only after a successful result. As with all EBS public APIs, passing invalid or stale identifiers can produce partial results, so callers should validate the contract and installment context before invocation.