Search Results po_price_diff_val_type




Overview
Explore in AI Chat

Overview

APPS.PO_VALIDATIONS is a core PL/SQL validation package within the Oracle E-Business Suite Purchasing module. It provides the centralized business-rule verification layer used across purchasing-related flows — Purchase Order entry, the PO Online entry forms, Purchasing Documents Open Interface (PDOI), and price/discount processing. The package consolidates validation logic for headers, lines, shipments, distributions, price breaks, price differentials, notification controls, and General Ledger organization assignments, returning structured results rather than raising discrete per-record exceptions.

The package operates on strongly-typed collection definitions rather than scalar arguments, including PO_HEADERS_VAL_TYPE, PO_LINES_VAL_TYPE, PO_LINE_LOCATIONS_VAL_TYPE, PO_DISTRIBUTIONS_VAL_TYPE, PO_PRICE_DIFF_VAL_TYPE, PO_NOTIFICATION_CTRL_VAL_TYPE, and PO_GA_ORG_ASSIGN_VAL_TYPE. Results are returned through PO_VALIDATION_RESULTS_TYPE and stored in the PO_VALIDATION_RESULTS_GT global temporary table, which allows the calling process to collect and report all validation messages in a single pass. The object is classified as OTHER in the ETRM API registry and is owned by the APPS schema with VALID status.

Key Procedures and Functions

The documented entry points cover result-set management, form-specific validation, and interface-driven validation:

  • NEXT_RESULT_SET_ID — retrieves the next sequence value for a validation result set, sourced from PO_VALIDATION_RESULT_SET_ID_S, so that concurrent or nested validation runs can be uniquely identified.
  • RESULT_TYPE_RANK — returns a numeric ranking for a given result type, enabling callers to order or prioritize validation messages (for example, error versus warning).
  • DELETE_RESULT_SET_AUTO — purges validation results associated with an automatically-generated result set from PO_VALIDATION_RESULTS_GT.
  • VALIDATE_UNIT_PRICE_CHANGE — checks whether a change to unit price on a purchasing document is permitted given current validation state.
  • VALIDATE_HTML_ORDER — performs validation for orders submitted through HTML (web) entry paths.
  • VALIDATE_HTML_AGREEMENT — performs validation for agreements (blanket/contract) submitted through HTML entry paths.
  • VALIDATE_PDOI — the primary entry point for the Purchasing Documents Open Interface, validating header, line, shipment, and distribution data before import.
  • VALIDATE_MODIFICATION_SYNC — validates modification changes for synchronized document processing.
  • LOG_VALIDATION_RESULTS_GT — writes accumulated validation results into the PO_VALIDATION_RESULTS_GT global temporary table.
  • CHECK_ENCUMBERED_AMOUNT — verifies that an encumbered amount is valid with respect to the purchasing document, supporting budgetary control integration.

Tables Accessed

Validation logic reads from and writes to the following objects through APPS synonyms:

  • PO_HEADERS_ALL — header-level attributes used when validating document type, supplier, and status.
  • PO_LINES_ALL — line item data used for line-level validation rules.
  • PO_LINE_LOCATIONS_ALL — shipment and schedule data used to validate quantities, dates, and receipt attributes.
  • PO_SYSTEM_PARAMETERS — purchasing system options that drive validation behavior.
  • PO_VALIDATION_RESULTS_GT — the global temporary table that holds validation output for the current session/result set.
  • PO_VALIDATION_RESULT_SET_ID_S — sequence used by NEXT_RESULT_SET_ID to allocate result set identifiers.
  • DUAL — used for scalar lookups and sequence retrieval.
  • PLITBLM — the PL/SQL integer table type used for internal list handling.

Usage Notes

PO_VALIDATIONS is invoked indirectly rather than as a standalone concurrent program. The PDOI processing packages (PO_PDOI_*_PROCESS_PVT and PO_PDOI_ERR_UTL) call it during open interface import, while the PO_VAL_* validation packages call it for interactive form validation, price break and price differential checks, and shipment/distribution validation. PO_PRICE_HELPER and PO_VALIDATION_HELPER also depend on it. In total, at least 26 packages in the PO schema reference PO_VALIDATIONS.

Custom code should not call the package directly unless it also supplies the appropriate validation type collections. The recommended pattern is to populate the relevant PO_*_VAL_TYPE records, invoke the appropriate VALIDATE_* procedure, and then extract results from PO_VALIDATION_RESULTS_GT using the result set ID returned by NEXT_RESULT_SET_ID. Result sets should be purged with DELETE_RESULT_SET_AUTO after processing to avoid accumulation of stale rows. Because the package sits beneath both PDOI and the online purchasing forms, changes to validation rules here affect all downstream entry paths.