Search Results pa_number




Overview
Explore in AI Chat

Overview

ASO_CONTRACT_TERMS_INT is a public PL/SQL package body owned by APPS within the Oracle E-Business Suite Order-to-Cash (ASO) application family. Its documented purpose is to resolve contract-term (variable) values referenced by sales quote and order documents at runtime, translating internal entity codes into human-readable text that can be printed or displayed on contracts, order confirmations, and quote output. The package is classified under ETRM as OTHER, reflecting that it is neither a pure validation API nor a workflow API, but a server-side utility layer invoked by output and integration logic.

The body is versioned from asoiktcb.pls (header revision 120.1, dated 2005/06/29), with the original creation attributed to 2002. The majority of the body is composed of constants rather than complex logic: each constant maps a contract-term variable code (for example OKC$S_ITEMS, OKC$S_CUSTOMER_NAME, or OKC$S_PAYMENT_TERM) to the internal identifier used by Oracle Contracts (OKC) to recognize that variable within a contract template. These tokens act as the lookup keys the procedures use when populating merged contract text.

Key Procedures and Functions

  • GET_ARTICLE_VARIABLE_VALUES — Resolves contract-term variables that are scoped at the article (document header or body) level. It accepts an API version and initialization flag, and returns status plus message information through its OUT parameters, populating the article-level variable tokens defined by the package constants.
  • GET_LINE_VARIABLE_VALUES — Resolves the equivalent set of contract-term variables at the document line level. This is the procedure that supplies line-scoped substitutions such as item, item category, and line-specific identifiers to contract text.
  • OK_TO_COMMIT — The procedure associated with the user's search term. It is the package's commit-control entry point: callers use it to determine whether outstanding changes accumulated during variable resolution may be committed by the current caller, preserving the standard EBS API contract in which the calling program — not the API — owns transaction control. The documented metadata does not expose its parameter list, but its naming convention follows the established FND/ASO pattern of separating business logic from commit decisions.

Tables Accessed

The package reads reference and transactional data needed to translate the variable codes into printable values. Documented tables include ASO_QUOTE_HEADERS_ALL and ASO_QUOTE_LINES_ALL for quote header and line context; ASO_QUOTE_STATUSES_B for status determination; ASO_SHIPMENTS and ASO_PAYMENTS for fulfillment and payment-related terms such as shipping method, freight terms, and payment terms; MTL_SYSTEM_ITEMS_B, MTL_ITEM_CATEGORIES, and MTL_DEFAULT_CATEGORY_SETS for item number and category resolution behind OKC$S_ITEMS and OKC$S_ITEM_CATEGORIES; and PLITBLM, the PL/SQL table-to-message buffer used for error and message reporting.

Usage Notes

ASO_CONTRACT_TERMS_INT is typically invoked indirectly rather than from end-user forms. It is called during contract and quote document generation — the output or reporting path where contract terms must be rendered with actual data — and is referenced by one other package in the ETRM dependency graph, indicating it is a shared utility rather than a top-level entry point. Custom code that extends quote or contract output should call the article-level and line-level procedures first and only commit after confirming the OK_TO_COMMIT result, honoring the standard EBS convention that the caller controls transaction boundaries. Because the package carries an ETRM classification of OTHER and a limited documented procedure count, developers extending it should treat the constant list as the authoritative mapping of contract-term codes and avoid duplicating those literals elsewhere.