Search Results get_standard_doc_style

Overview

PO_DOC_STYLE_GRP is an Oracle EBS PL/SQL package owned by APPS and classified as a GRP (group) package within the Purchasing (PO) module. It provides the central validation and retrieval services for Purchasing document styles. A document style in Oracle Purchasing defines the set of capabilities and behaviors permitted on a purchasing document — such as whether advances, retainage, price breaks, price differentials, progress payments, and contract financing are enabled, and which line types are permitted. PO_DOC_STYLE_GRP exposes the logic that determines whether a proposed style name or alias conflicts with an existing style, identifies and resolves the seeded standard document style, retrieves the full set of style-level settings, and validates that the required attributes for a style on a specific document are satisfied. Because document style drives downstream behavior on requisitions, purchase orders, and related documents, this package is a foundational dependency for the Purchasing application and for any custom code that manipulates document styles. In the documented ETRM metadata for 12.2.2 it exposes six public program units and references PO_DOC_STYLE_HEADERS and DUAL; it is referenced by 13 other packages, confirming its role as a shared utility rather than a standalone entry point.

Key Procedures and Functions

• IS_STYLE_ALIAS_CONFLICT — Determines whether a supplied style alias conflicts with an existing document style alias. This is the object targeted by the search term "is_style_alias_conflict." It accepts a name and an optional style identifier (used to exclude the style currently being edited from the conflict check) and returns a VARCHAR2 result.
• IS_STYLE_NAME_CONFLICT — The name-level counterpart to the alias check. It determines whether a proposed document style name collides with an existing style name, again allowing the current style to be excluded via the optional style ID parameter.
• IS_STANDARD_DOC_STYLE — Tests whether a given style ID corresponds to the seeded standard document style, returning a VARCHAR2 indicator.
• GET_STANDARD_DOC_STYLE — Returns the style ID of the standard document style as a NUMBER, providing the canonical reference used when a default or fallback style is required.
• GET_DOCUMENT_STYLE_SETTINGS — Retrieves the complete configuration of a document style. It accepts an API version and style ID and returns, as output parameters, the style name, description, and type, the status, and the individual feature flags (advances, retainage, price breaks, price differentials, progress payment, and contract financing) plus the permitted line types.
• STYLE_VALIDATE_REQ_ATTRS — Validates the required attributes of a document style against the context of a specific document and line. It takes the API version and initialization message-list flag, and returns the standard API return status, message count, and message data, evaluating the document style ID, document ID, line type, purchasing basis, destination type, and source.

Tables Accessed

The package reads PO_DOC_STYLE_HEADERS, the table that stores document style definitions, including style names, aliases, types, feature flags, and status. This table supports the conflict checks, the standard-style lookups, and the settings retrieval. DUAL is referenced for single-row evaluations and constant or scalar derivations used inside the conflict and identification functions. No insert or update of application tables is documented; the package functions principally as a read-and-validate layer over the style header definition.

Usage Notes

PO_DOC_STYLE_GRP is typically invoked from Purchasing setup forms during document style definition and maintenance, where the conflict-check functions prevent duplicate names and aliases, and from internal validation routines on requisition and purchase order entry where style attributes must be verified against the document context. Because it is referenced by 13 other packages, it is generally consumed indirectly by higher-level Purchasing APIs and concurrent programs rather than called directly by end users. Custom code that creates or validates document styles should call IS_STYLE_NAME_CONFLICT and IS_STYLE_ALIAS_CONFLICT before committing definitions, use GET_DOCUMENT_STYLE_SETTINGS to read the configured flags, and observe the standard FND_API return status, message count, and message data conventions when invoking STYLE_VALIDATE_REQ_ATTRS so that errors are surfaced consistently with other EBS APIs.