Results for “get_article_application”

8 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKE_CONTRACT_PRINTING_PKG is a PL/SQL package owned by APPS within the Oracle E-Business Suite, defined with AUTHID CURRENT_USER and classified under the ETRM API classification of OTHER. Its business purpose is to support the generation and printing of Oracle Contracts (OKE/OKC) documents by supplying the descriptive metadata that appears on printed contract output. Specifically, the package retrieves human-readable values — organization names, party or contact names, article subjects, release comments, and formatted dates — that the contract printing engine requires in order to render a complete and presentable document.

The package header carries the version identifier $Header: OKEKCPPS.pls 115.1 2003/10/14, indicating that the interface has remained stable across the 12.1.1 and 12.2.2 release lines. Because it is a printing support package rather than a transactional API, it is oriented toward read-only resolution of display values rather than creation or modification of contract data.

Key Procedures and Functions

The package exposes six documented procedures:

  • GET_ITEM_MASTER_ORG — Resolves and returns the item master organization name associated with a given contract header, providing the organizational context for printed contract content.
  • GET_PARTYORCONTACT_NAME — Accepts a JTOT object code and object identifiers and returns the resolved name of the corresponding party or contact, enabling the printed contract to display the correct trading partner or contact person.
  • GET_ARTICLE_INFO — The procedure targeted by the user's search. It accepts a category type, a savings/standard article identifier, an article short name code, and an article name, and returns the resolved short name code, article name, and subject name. This procedure resolves contract article (clause/term) identifiers into the descriptive text that appears in the printed contract body.
  • GET_ARTICLE_APPLICATION — Retrieves the application details of a contract article for a given identifier, version, category type, and release, returning comments, applied lines, and the article text as a CLOB. This supports rendering of the substantive article content.
  • CONVERT_DATE — Converts a DATE value into a formatted character string suitable for display on printed contract output.
  • GET_LINE_NUMBER — Returns the display line number for a contract line identified by its identifier, version, and line identifier, used to sequence line items in printed documents.

Tables Accessed

The package references two documented tables through APPS synonyms:

  • HR_ALL_ORGANIZATION_UNITS — Read to resolve organization names, principally in support of GET_ITEM_MASTER_ORG and related name resolution logic.
  • OKC_K_HEADERS_B — The core contract headers base table, read to obtain header-level context such as the contract identifier, version, and associated organizational data used across the resolution procedures.

All access is consistent with the package's read-only printing orientation; no inserts, updates, or deletes are documented against these objects.

Usage Notes

OKE_CONTRACT_PRINTING_PKG is typically invoked from the Oracle Contracts printing infrastructure rather than called directly by end users. It is most commonly referenced by the contract print concurrent programs and by the Oracle Forms and OAF pages that render contract previews and printed output, where display values must be resolved at runtime.

Custom extensions that reproduce or supplement standard contract printing output may call these procedures directly to obtain consistent display values. Because the package is declared AUTHID CURRENT_USER, invokers require appropriate privileges on the underlying APPS synonyms. The ETRM metadata records zero dependent packages, confirming that this is a leaf-level utility package with no downstream API consumers. Developers integrating with it should note that parameter lists are fixed as documented and that the procedures return values exclusively through OUT parameters, returning no function results.