Search Results variable_code




Overview
Explore in AI Chat

Overview

APPS.PON_CONTERMS_UTL_GRP is a Group (GRP) layer PL/SQL package body in the Oracle E-Business Suite Contracts and Sourcing module. Its architectural role is to expose a stable, public interface for contract-terms (conterms) processing while delegating the substantive business logic to its paired private implementation package, PON_CONTERMS_UTL_PVT. This GRP/PVT split is the standard Oracle Application Framework convention that isolates the callable API surface from the internal implementation, allowing Oracle to revise private logic without altering the public signatures relied upon by other products. The package header revision reference, PONCTDVB.pls 120.6, dated 2006, indicates the utility dates from the 11i era and has been carried forward essentially unchanged into Release 12.1.1 and 12.2.2, where it remains an APPS-owned, seeded object.

The package supports the Contract Terms library functionality surrounding sourcing negotiations, auctions, bids, and contract documents. It answers questions about document types, commit eligibility, article variable values, and item category derivation, and it is referenced by four other packages, making it a shared dependency within the sourcing and contracts stack.

Key Procedures and Functions

  • IS_CONTRACTS_INSTALLED — A function that reports whether the Oracle Contracts application is installed and available in the current environment. It is a thin wrapper that returns the result of the corresponding private function, allowing callers to guard contract-dependent logic without querying installation tables directly.
  • GET_CONTRACTS_DOCUMENT_TYPE — A function that returns the contract document type for a given document type identifier. It distinguishes response documents from negotiation documents by branching to the appropriate private function. This is the routine most closely associated with the user search term variable_code, because document type classification drives how article variables and their codes are resolved for a contract template.
  • OK_TO_COMMIT — A procedure that determines whether a document is eligible to be committed. It performs the standard API validation sequence: initializing the output status and message values, verifying API version compatibility through FND_API.Compatible_API_Call, optionally initializing the message list, then resolving the auction header and its status before returning an update-allowed flag, return status, message data, and message count. It also establishes an internal API version and API name for compatibility checking.
  • GET_ARTICLE_VARIABLE_VALUES — A function that retrieves the values of article variables associated with contract terms, returning the substituted values used when contract clauses are generated.
  • GET_CHANGED_VARIABLES — A function that returns the set of article variables that have changed, typically used to identify which terms require regeneration or re-evaluation.
  • GET_ITEM_CATEGORY — A function that derives the item category relevant to the contract terms context.

Tables Accessed

The package and its private implementation work against several documented tables via APPS synonyms. PON_AUCTION_HEADERS_ALL and PON_AUCTION_ITEM_PRICES_ALL hold auction and pricing data central to negotiation and commit checks. PON_AUC_DOCTYPES and PON_BID_HEADERS provide document type definitions and supplier bid information. FND_USER supplies the application user context. HZ_PARTIES, HZ_RELATIONSHIPS, and HZ_CODE_ASSIGNMENTS supply trading partner and classification data from the TCA model. HR_ALL_ORGANIZATION_UNITS provides organization context, and PLITBLM is the PL/SQL integer table type used for message list handling. Access is predominantly read-oriented, supporting validation and value resolution rather than transactional updates.

Usage Notes

PON_CONTERMS_UTL_GRP is invoked from Oracle Sourcing and Contracts forms, from concurrent programs that process negotiations and contract documents, and from custom extensions requiring document type or commit-eligibility information. Developers should call the GRP layer rather than the PVT package, since the GRP layer carries the supported API signatures. OK_TO_COMMIT follows the standard EBS API contract, so callers must check x_return_status against FND_API.G_RET_STS_SUCCESS and inspect x_msg_data and x_msg_count on failure. Because the package is referenced by four other packages, changes to its behavior can propagate widely across the sourcing and contracts modules.