Search Results po_val_price_diffs




Overview
Explore in AI Chat

Overview

APPS.PO_VAL_PRICE_DIFFS is a PL/SQL validation package within the Oracle E-Business Suite Purchasing module. Its business function is to enforce validation rules governing price differentials defined on purchasing documents and their associated source documents. A price differential represents an adjustment applied to a base price, typically expressed as a markup, discount, or absolute amount, and it is attached to the price differentials entity that drives supplier pricing behaviour on purchase orders, quotations, and related sourcing documents.

In the EBS 12.1.1 and 12.2.2 code lines, this package operates in the validation layer alongside the broader PO_VALIDATIONS framework. It is a member of the same family as other object-specific validation packages and is invoked as part of the standard validation cycle applied to Purchasing documents. Rather than performing user interface logic, it returns structured validation results that the calling framework interprets and presents to the user or logs for diagnostic purposes. The package is classified as OTHER in the ETRM metadata, indicating it is an internal companion package rather than a published public API.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents ten procedures and functions within this package. Each addresses a discrete arithmetic or uniqueness rule applied to price differential values.

  • MAX_MUL_GE_ZERO — validates that a maximum multiplier value is greater than or equal to zero.
  • MAX_MUL_GE_MIN_MUL — validates that the maximum multiplier is greater than or equal to the minimum multiplier.
  • MIN_MUL_GE_ZERO — validates that a minimum multiplier value is greater than or equal to zero.
  • MUL_GE_ZERO — validates that a multiplier is greater than or equal to zero.
  • UNIQUE_PRICE_DIFF_NUM — enforces uniqueness of the price differential number within its document context.
  • PRICE_DIFF_NUM_GT_ZERO — validates that the price differential number is greater than zero.
  • UNIQUE_PRICE_TYPE — enforces uniqueness of the price type associated with a differential.
  • SPO_PRICE_TYPE_ON_SRC_DOC — validates the price type carried from the source document.
  • SPO_MUL_BTWN_MIN_MAX — validates that a source document multiplier falls between the defined minimum and maximum bounds.
  • SPO_MUL_GE_MIN — validates that a source document multiplier is greater than or equal to the minimum.

The recurring "SPO" prefix indicates source purchase order related checks, distinguishing them from the general multiplier and price type validations.

Tables Accessed

The package references a small, focused set of database objects through APPS synonyms.

  • PO_PRICE_DIFFERENTIALS — the primary operational table holding price differential definitions; validations such as uniqueness and numeric range checks operate against this data.
  • PO_VALIDATION_RESULTS_GT — the global temporary table used to accumulate validation outcomes returned to the calling validation engine.
  • DUAL — used for scalar evaluation and procedural control logic.
  • PLITBLM — the standard PL/SQL indexed table buffer mechanism supporting bulk operations and result accumulation.

The dependency list additionally shows use of PL/SQL collection types PO_TBL_NUMBER and PO_TBL_VARCHAR30, and the object type PO_VALIDATION_RESULTS_TYPE, which shape the parameter and result structures used throughout the package.

Usage Notes

PO_VAL_PRICE_DIFFS is referenced by APPS.PO_VALIDATIONS, confirming that it is driven from the central Purchasing validation dispatcher rather than called directly by application forms or concurrent programs. In practice, the validations fire when a user creates or updates price differentials in the Purchasing forms, when documents are validated prior to approval, and when source documents propagate pricing information to downstream purchasing documents.

Because the procedures are internal and the package is not a published API, customizations and extensions should invoke the standard PO_VALIDATIONS entry points rather than calling PO_VAL_PRICE_DIFFS directly. Direct invocation risks bypassing framework-level result handling and is not supported across upgrades. The documented dependencies confirm the package self-references and is referenced by exactly one other package, keeping its integration surface narrow and predictable.