Search Results get_style_display_name

Overview

PO_DOC_STYLE_PVT is a private PL/SQL package within the Oracle E-Business Suite Purchasing (PO) module, owned by the APPS schema and classified as a PVT (private) API. Its principal business function is the validation and resolution of document styles for purchasing documents — purchase orders and requisitions — prior to commitments being created or documents being finalized. In EBS, a "document style" governs the behavior and presentation of a purchasing document, controlling attributes such as the document type, line type, purchase basis, and destination type. The package validates that requisition lines selected for a given purchasing document conform to an applicable style, resolves the correct style identifier for a document, and exposes supporting utilities for style display and progress payments detection. The package header carries a relatively early source control stamp (120.2, 2005), indicating it is a foundational, long-lived component of the Purchasing codebase that remains present in both 12.1.1 and 12.2.2. Approximately twelve other packages reference it, confirming that it is a shared internal utility rather than a standalone entry point.

Key Procedures and Functions

• POPULATE_GT_AND_VALIDATE — Populates the session global temporary structures with requisition line data supplied through PL/SQL index-by tables and then invokes the validation logic. It accepts collections describing requisition line identifiers, source document identifiers, line type identifiers, destination types, and purchase bases, together with a PO header identifier and an optional style identifier. It returns the resolved style identifier to the caller.
• STYLE_VALIDATE_REQ_LINES — The procedure targeted by the user's search term. This routine validates requisition lines against a document style. It operates on data previously staged in the session global temporary table, identified by a session GT key, and takes a PO header identifier plus an optional style identifier. It returns the resolved style identifier along with the standard FND_API return status, message count, and message data parameters. It is the core entry point for line-level style validation.
• STYLE_VALIDATE_REQ_ATTRS — Validates individual style-relevant attributes of a requisition or document line: the document style identifier, document identifier, line type, purchase basis, destination type, and source. This provides attribute-level checking independent of the bulk line validation path.
• IS_PROGRESS_PAYMENTS_ENABLED — A Boolean function that determines whether progress payments are enabled for a given style identifier.
• GET_DOC_STYLE_ID — Returns the document style identifier associated with a supplied document identifier.
• GET_STYLE_DISPLAY_NAME — Returns the display name of a document style for a document identifier, with an optional language parameter for translated presentation.

Tables Accessed

The package reads and writes configuration and transactional data through APPS synonyms. Style definitions are sourced from PO_DOC_STYLE_HEADERS, PO_DOC_STYLE_LINES_TL, and PO_DOC_STYLE_VALUES, with translated document type descriptions from PO_DOCUMENT_TYPES_TL. Transactional and validation context is drawn from PO_HEADERS_ALL, PO_LINE_TYPES_B, and PO_REQUISITION_LINES_ALL. Staging data is held in the session global temporary table PO_SESSION_GT and its sequence PO_SESSION_GT_S. DUAL and the PLITBLM index-by table type are used for utility and collection handling.

Usage Notes

As a PVT API, PO_DOC_STYLE_PVT is not intended for direct customer invocation; it is called internally by Purchasing forms, requisition-to-PO autocreate processing, and higher-level public APIs during document style validation. Custom code should generally reach it only through supported public interfaces. The session-GT staging pattern means callers must populate PO_SESSION_GT before invoking STYLE_VALIDATE_REQ_LINES and must manage the associated session key correctly.