Search Results get_changed_variables
Overview
OKC_PON_INT_GRP is a PL/SQL package body in the APPS schema belonging to the Oracle Contracts (OKC) module family, specifically the "PON" integration group area that bridges Oracle Contracts with Oracle Purchasing (PON). The package is classified as a Group (GRP) API, meaning it exposes a collection of related public procedures that share common error-handling conventions, message tokens, and logging behavior rather than a single entity-level API. Internally it adopts the standard Oracle EBS API infrastructure: it declares G_FND_APP, G_PKG_NAME, G_APP_NAME, and the standard FND_API return-status constants (G_RET_STS_SUCCESS, G_RET_STS_ERROR, G_RET_STS_UNEXP_ERROR), along with message tokens such as G_UNEXPECTED_ERROR, G_SQLERRM_TOKEN, and G_SQLCODE_TOKEN. Debug tracing is governed by FND_LOG runtime levels, with G_DBG_LEVEL, G_PROC_LEVEL, and G_EXCP_LEVEL controlling procedure and exception logging. The package's business purpose is to resolve contract and article variables — text substitutions used in contract documents and terms — and to support expert-driven item and variable retrieval used when contract terms reference purchasing data. The "$Header" version string (OKCGISOB.pls 120.1, dated 2005) indicates the file has been stable since the early 11i/12.x code line and remains shipped in 12.1.1 and 12.2.2.
Key Procedures and Functions
ETRM documents four public routines on this package:
- GET_ARTICLE_VARIABLE_VALUES — Returns the resolved values of variables associated with a contract article. It accepts an API version, an initialization flag, a document type and document identifier, and populates an IN OUT NOCOPY variable-value table (sys_var_value_tbl_type) alongside standard return status, message data, and message count outputs. This is the primary entry point for substituting live data into contract article text.
- GET_CHANGED_VARIABLES — Identifies variables whose values have changed for a given contract or document, enabling downstream processing to refresh only the affected substitutions. This is the routine most often targeted by the search term "get_changed_variables."
- GET_ITEM_DTL_FOR_EXPERT — Retrieves item detail information for use by the expert (rules) engine when evaluating contract terms that depend on purchasing item attributes.
- OK_TO_COMMIT — A validation helper that signals whether a transaction or variable-resolution operation is in a state safe to commit, supporting transactional integrity in calling code.
Tables Accessed
The provided ETRM metadata does not enumerate specific base tables accessed through APPS synonyms. Based on the documented procedures, the package operates against contract article/variable definition and value data in the OKC schema (such as article variable and document tables) and reads item master information in support of GET_ITEM_DTL_FOR_EXPERT. Implementers should confirm the exact table list by querying DBA_DEPENDENCIES for OKC_PON_INT_GRP in their instance.
Usage Notes
As a GRP-class API, OKC_PON_INT_GRP is typically invoked from Oracle Forms, concurrent programs, or custom PL/SQL that renders contract documents and terms. Callers must supply a valid API version, honor the p_init_msg_list convention, and inspect x_return_status before proceeding. The message count and message data outputs should be consumed through FND_MSG_PUB. The package is referenced by three other packages, indicating it functions as a shared utility layer. Because the source header predates Release 12, behavior is consistent across 12.1.1 and 12.2.2; customizations should avoid modifying the shipped body and instead wrap the public procedures.
-
PACKAGE BODY: APPS.OKC_PON_INT_GRP
12.2.2
-
PACKAGE BODY: APPS.OKC_PON_INT_GRP
12.1.1
-
PACKAGE BODY: APPS.OKC_PO_INT_GRP
12.1.1
-
PACKAGE BODY: APPS.OKC_PO_INT_GRP
12.2.2
-
PACKAGE: APPS.OKC_PON_INT_GRP
12.2.2
-
PACKAGE: APPS.OKC_PO_INT_GRP
12.1.1
-
PACKAGE: APPS.PON_CONTERMS_UTL_GRP
12.2.2
-
PACKAGE: APPS.PON_CONTERMS_UTL_GRP
12.1.1
-
PACKAGE: APPS.OKC_PON_INT_GRP
12.1.1
-
PACKAGE: APPS.OKC_PO_INT_GRP
12.2.2
-
PACKAGE BODY: APPS.PON_CONTERMS_UTL_GRP
12.2.2
-
PACKAGE BODY: APPS.PON_CONTERMS_UTL_GRP
12.1.1
-
APPS.OKC_PON_INT_GRP dependencies on OKC_API
12.2.2
-
APPS.OKC_PON_INT_GRP dependencies on OKC_API
12.1.1
-
APPS.OKC_PON_INT_GRP dependencies on FND_LOG
12.2.2
-
APPS.OKC_PON_INT_GRP dependencies on FND_MSG_PUB
12.1.1
-
APPS.OKC_PON_INT_GRP dependencies on FND_MSG_PUB
12.2.2
-
APPS.OKC_PO_INT_GRP dependencies on FND_LOG
12.1.1
-
APPS.OKC_PON_INT_GRP dependencies on FND_LOG
12.1.1
-
APPS.OKC_PO_INT_GRP dependencies on OKC_API
12.1.1
-
APPS.OKC_PO_INT_GRP dependencies on OKC_API
12.2.2
-
APPS.OKC_PO_INT_GRP dependencies on FND_LOG
12.2.2
-
APPS.OKC_PO_INT_GRP dependencies on FND_MSG_PUB
12.1.1
-
APPS.PON_CONTERMS_UTL_GRP dependencies on PON_AUCTION_HEADERS_ALL
12.2.2
-
APPS.PON_CONTERMS_UTL_GRP dependencies on PON_AUCTION_HEADERS_ALL
12.1.1
-
APPS.OKC_PO_INT_GRP dependencies on FND_MSG_PUB
12.2.2
-
APPS.OKC_PO_INT_GRP dependencies on FND_API
12.1.1
-
APPS.OKC_PO_INT_GRP dependencies on FND_API
12.2.2
-
APPS.PON_CONTERMS_UTL_GRP dependencies on FND_API
12.1.1
-
APPS.PON_CONTERMS_UTL_GRP dependencies on FND_API
12.2.2
-
APPS.OKC_PON_INT_GRP dependencies on FND_API
12.2.2
-
APPS.OKC_PON_INT_GRP dependencies on FND_API
12.1.1
-
APPS.OKC_PON_INT_GRP dependencies on FND_API
12.1.1
-
APPS.OKC_PON_INT_GRP dependencies on FND_API
12.2.2
-
APPS.PON_CONTERMS_UTL_GRP dependencies on FND_API
12.2.2
-
APPS.PON_CONTERMS_UTL_GRP dependencies on FND_API
12.1.1
-
APPS.OKC_PO_INT_GRP dependencies on FND_API
12.1.1
-
APPS.OKC_PO_INT_GRP dependencies on FND_API
12.2.2