Search Results aflog_enabled

Overview

OKC_PO_INT_RTK_PVT is a private PL/SQL package body in the APPS schema that belongs to the Oracle Contracts (OKC) module family. Its naming convention — the OKC_PO_INT_RTK prefix combined with the _PVT suffix — indicates that it forms part of the internal runtime support layer for the purchase order interface (PO_INT) within the Oracle Contracts/Procurement integration, specifically the "RTK" (runtime toolkit) component. The $Header comment dates the package body to May 2005 (version 120.0), and the source is marked "noship", indicating that it is an internally deployed, non-shipped utility rather than a published integration API.

The package is classified as a private (PVT) API in ETRM 12.2.2, meaning it is not intended for direct invocation by customer or third-party code. It exists to support the contract-to-purchase-order integration flow, where contract terms, pricing, and deliverables are propagated to Oracle Purchasing documents. Version 12.1.1 and 12.2.2 both retain this private toolkit in the same role; the object is not replaced or obsoleted across the 12.x release line.

Key Procedures and Functions

The documented metadata for this package body lists zero public procedures or functions. This is consistent with its _PVT designation: the package body contains only private declarations and helper logic consumed by other members of the OKC PO integration runtime toolkit, and it exposes no callable API surface of its own.

The extract shows a single package-level variable declaration followed immediately by the package end statement. The variable, l_debug VARCHAR2(1), is initialized from the profile option AFLOG_ENABLED via FND_PROFILE.VALUE, defaulting to 'N' when the profile is not set. This variable acts as the package-wide diagnostic switch used to gate debug messaging (typically through FND_LOG / FND_MSG_PUB) throughout the toolkit. Because no functions or procedures are documented, any procedural content in the deployed body is either empty, minimal, or was stripped in this particular extraction; the object should be treated as a diagnostic/runtime scaffold rather than a functional business API.

Tables Accessed

The ETRM metadata documents no tables referenced through APPS synonyms for this package body, and it is not referenced by any other documented package. The only external dependency visible in the source is the FND_PROFILE view, accessed at package initialization time to read the AFLOG_ENABLED profile option value. No contract tables (OKC_*), purchasing tables (PO_*), or interface tables are listed as accessed by this object. Consequently, no data manipulation of contract or purchasing records is performed here.

Usage Notes

Because OKC_PO_INT_RTK_PVT is a private package with no documented public procedures, it is not invoked directly from Oracle Forms, concurrent programs, or workflow activities. It is loaded implicitly as part of the APPS schema when a parent object — most likely a public OKC PO integration runtime package — references the private elements defined here, and it is initialized when that parent package is first called in a session. The only observable behavior at this level is the read of AFLOG_ENABLED at initialization.

The relevance of the user search term "aflog_enabled" is explained by line 4 of the source: the package captures the AFLOG_ENABLED profile setting into l_debug so that runtime logging decisions can be made without repeated profile lookups. When diagnosing OKC PO integration behavior in 12.1.1 or 12.2.2, enabling AFLOG_ENABLED at the user, responsibility, or site level will cause this flag to be set to 'Y' and any dependent debug statements in the wider toolkit to emit output. Because the package is "noship" and private, it should not be modified or called from custom code; all investigation should target the public parent API that consumes it.