Search Results po_val_constants




Overview
Explore in AI Chat

Overview

PO_VAL_PRICE_DIFFS2 is an APPS-owned PL/SQL package body classified under the ORACLE EBS validation framework as an "OTHER" API. Its role is to support the Purchasing module's validation of price differentials — the pricing adjustments attached to document styles and purchase order lines that modify a base price according to quantity breaks, supplier-specific terms, or item attributes. In Oracle EBS 12.1.1 and 12.2.2, price differentials are maintained on PO_DOC_STYLE_HEADERS and PO_PRICE_DIFFERENTIALS, and the package enforces consistency of those definitions before they are committed or applied to ordering documents.

The status of the object is VALID, and it is not referenced by any other database object, meaning it is an entry point rather than a shared utility invoked through the dependency chain. It does, however, depend on several core Purchasing objects, most notably PO_VAL_CONSTANTS, PO_VALIDATIONS, PO_CORE_S, PO_LOG, and PO_DOC_STYLE_HEADERS. The presence of PO_LOG and PO_VALIDATIONS indicates the package participates in the Purchasing validation engine, recording results through PO_VALIDATION_RESULTS_GT and PO_VALIDATION_RESULTS_TYPE. Because it is not referenced externally, customizations that call it directly should be treated as unsupported extensions.

Key Procedures and Functions

The documented API surface contains seven program units. Their names are self-describing but the ETRM metadata does not publish parameter lists, so only their purposes are described here.

  • PRICE_TYPE — Resolves or validates the price differential type, distinguishing among the differential categories supported by Purchasing (for example percentage, amount, or formula-based adjustments) before downstream validation.
  • MULTIPLE_PRICE_DIFF — Handles the case where more than one price differential applies to the same pricing context, ensuring the combination is legal and unambiguous.
  • ENTITY_TYPE — Determines the entity type to which a differential applies, such as a document style header or a line-level construct, guiding which validation rules are executed.
  • MULTIPLIER — Validates the multiplier value used in the differential calculation, confirming it is defined and in range.
  • MIN_MULTIPLIER — Applies the lower bound check for the multiplier.
  • MAX_MULTIPLIER — Applies the upper bound check for the multiplier.
  • STYLE_RELATED_INFO — Extracts and validates style-related attributes for the differential, tying the differential back to PO_DOC_STYLE_HEADERS.

Tables Accessed

  • PO_DOC_STYLE_HEADERS — Source of style definitions to which price differentials are attached; read to establish the validation context.
  • PO_PRICE_DIFFERENTIALS — The primary table holding differential definitions; read to validate the differential being processed.
  • PO_PRICE_DIFF_DRAFT — Staging/draft records for price differentials, used while changes are pending validation.
  • PO_VALIDATION_RESULTS_GT — Global temporary result set where validation outcomes are accumulated.
  • PO_SESSION_GT — Session-scoped working storage used by the validation engine.
  • DUAL and PLITBLM — Utility objects used for single-row selection and PL/SQL table manipulation.

Usage Notes

PO_VAL_PRICE_DIFFS2 is invoked within the Purchasing validation sequence, typically triggered from the Price Differential definition window or from validation concurrent programs that process pending draft records. It is not a public API and is not referenced by other packages. Because PO_VAL_CONSTANTS is a direct dependency, constants such as entity-type codes and multiplier bounds are centralized there rather than hard-coded. In 12.2.2 the same behavior applies; the package remains a validation-layer object rather than a business API. Any direct call from custom code should be avoided, as signatures are not published and Oracle does not guarantee backward compatibility at this layer.