Search Results po_doc_style_pvt




Overview
Explore in AI Chat

Overview

APPS.PO_DOC_STYLE_PVT is a private PL/SQL package body in the Oracle E-Business Suite Purchasing module. It implements the runtime logic behind the "Document Style" feature, which allows an organization to govern how purchasing documents behave and how their attributes are presented to users. Document Styles are configured in the Purchasing setup area and control characteristics such as which tabs and fields appear on the Enter Purchase Orders form, the numbering and approval behavior of documents, and whether specific capabilities — including progress payments — are available for a given document type.

The package belongs to the API classification PVT, denoting a private implementation layer. It is not intended as a public, externally supported interface; instead it is invoked by the public Purchasing APIs and by the Oracle Forms that drive requisition and purchase order entry. Its responsibilities center on validating that a requested style is applicable to a given document or requisition line, populating session-level temporary tables used during validation, and supplying display information for the style selected by the user. The package holds 8 documented procedures and functions and is referenced by 12 other packages, confirming its role as a shared internal utility within the Purchasing stack.

Key Procedures and Functions

  • POPULATE_GT_AND_VALIDATE — Populates the session global temporary table (PO_SESSION_GT) with the rows relevant to the current transaction and then performs validation against those rows. This is the central entry point for style checking during line processing.
  • STYLE_VALIDATE_REQ_LINES — Validates requisition lines against the governing document style, ensuring that the attributes entered on the line are consistent with the style configured for the requisition's document type.
  • STYLE_VALIDATE_REQ_ATTRS — Validates individual requisition attributes against the document style, enforcing the field-level and behavioral restrictions the style imposes.
  • IS_PROGRESS_PAYMENTS_ENABLED — Returns an indicator of whether progress payments are enabled for the applicable document style, allowing callers to conditionally expose progress payment functionality.
  • GET_DOC_STYLE_ID — Resolves and returns the document style identifier applicable to the current document type and context.
  • GET_STYLE_DISPLAY_NAME — Returns the translated display name of a document style, using the language-specific style definition for presentation on forms and reports.

Tables Accessed

The package reads and writes configuration and transactional data across the Purchasing schema. Style definitions are sourced from PO_DOC_STYLE_HEADERS, PO_DOC_STYLE_LINES_TL (translated style line descriptions), PO_DOC_STYLE_VALUES (style-to-value assignments), and PO_DOC_STYLE_GRP, with document type translation obtained from PO_DOCUMENT_TYPES_TL. Purchase order and requisition context is drawn from PO_HEADERS_ALL, PO_HEADERS_MERGE_V, PO_LINE_TYPES_B, and PO_REQUISITION_LINES_ALL. Working and validation data is staged in PO_SESSION_GT and PO_SESSION_GT_S, while lookups are resolved through PO_LOOKUP_CODES. Utility dependencies include PO_TBL_NUMBER, PO_LOG for logging, and the standard FND_API, FND_MESSAGE, and FND_MSG_PUB packages for error handling and message retrieval. The query relevant to the user's search — PO_DOCUMENT_TYPES_TL — is used to resolve the translated names of document types so that style validation and display operate against the correct language row.

Usage Notes

PO_DOC_STYLE_PVT is a private package and should not be called directly by customer extensions. It is invoked internally by the Purchasing forms during purchase order and requisition entry, by the public Purchasing APIs when creating or updating documents, and by concurrent programs that validate or process purchasing documents in batch. Because it stages data in a session-level global temporary table, it is safe for concurrent multi-user execution; each session sees only its own rows. The presence of PO_LOG and the FND message utilities indicates that failures are surfaced through the standard EBS message stack rather than raw exceptions. Custom code requiring document style behavior should call the supported public APIs, which in turn delegate to this package.