Results for “secondary_unit_of_measure”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PO_VALIDATION_HELPER is a shared PL/SQL utility package within the Oracle E-Business Suite Purchasing module. Its principal business function is to centralize the low-level validation primitives used by the Purchasing validation framework. Rather than embedding repetitive conditional logic in each of the higher-level validation packages, Oracle implements the atomic checks—range comparisons, null checks, period verification, uniqueness tests, and quantity/deviation tolerance checks—once in PO_VALIDATION_HELPER and exposes them for reuse. The package is classified as an "OTHER" API, indicating it is an internal helper rather than a formally published public interface. It operates in both 12.1.1 and 12.2.2, with metadata documented under ETRM 12.2.2.

The package underpins the validation of purchase orders, releases, and their associated entities. It returns results into the PO_VALIDATION_RESULTS_TYPE structure and stores atomic validation messages in PO_VALIDATION_RESULTS_GT, allowing the calling validation packages to accumulate and later report errors against a document.

Key Procedures and Functions

The package exposes 26 documented procedures and functions. They fall into recognizable categories:

• Numeric and range checks: GREATER_THAN_ZERO, GREATER_OR_EQUAL_ZERO, ZERO, NUM1_LESS_OR_EQUAL_NUM2, WITHIN_PERCENTAGE_RANGE, and QTYS_WITHIN_DEVIATION evaluate quantities and amounts against thresholds, including tolerance-based quantity deviation checks used during receiving and matching.
• Null and string checks: NOT_NULL, ENSURE_NULL, and FLAG_VALUE_Y_N enforce required-value and yes/no flag rules.
• Date and period checks: OPEN_PERIOD validates that a transaction date falls within an open GL period; START_DATE_LE_END_DATE verifies chronological ordering of date ranges.
• Uniqueness checks: CHILD_NUM_UNIQUE and PRICE_DIFF_VALUE_UNIQUE confirm the uniqueness of child sequence numbers and price differential values.
• Reference and lookup checks: TERMS_ID validates payment terms, and SECONDARY_UNIT_OF_MEASURE and SECONDARY_QUANTITY validate dual-unit-of-measure data.
• Organizational and notification checks: GT_ZERO_ORDER_TYPE_FILTER, GT_ZERO_OPM_FILTER, and AMOUNT_NOTIF_CTRL_WARNING apply order-type, process-manufacturing, and notification-control constraints, while NO_TIMECARDS_EXIST checks for associated timecard activity.

Each routine is designed to be called independently by validation logic, and none requires the caller to manage its own comparison logic.

Tables Accessed

The package reads from several master and transactional tables through APPS synonyms. MTL_SYSTEM_ITEMS, MTL_PARAMETERS, MTL_UNITS_OF_MEASURE, and MTL_GRADES_B supply item, inventory organization, unit-of-measure, and grade validation data. GL_PERIOD_STATUSES supports open-period determination, while FINANCIALS_SYSTEM_PARAMS_ALL and AP_TERMS support financial and payment-terms validation. PO_HEADERS_ALL, PO_LINES_ALL, PO_DISTRIBUTIONS_DRAFT_ALL, and PO_NOTIFICATION_CONTROLS provide the purchasing document context. Working state is held in PO_SESSION_GT and PO_VALIDATION_RESULTS_GT, with results returned through PO_VALIDATION_RESULTS_TYPE. DBMS_SQL and DUAL support dynamic SQL execution and singleton queries.

Usage Notes

PO_VALIDATION_HELPER is referenced by twelve other packages, including PO_VALIDATIONS, PO_VAL_HEADERS, PO_VAL_HEADERS2, PO_VAL_LINES, PO_VAL_LINES2, PO_VAL_SHIPMENTS, PO_VAL_DISTRIBUTIONS, PO_VAL_PRICE_BREAKS, PO_VAL_PRICE_DIFFS, PO_VAL_NOTIFICATION_CONTROLS, PO_VAL_GA_ORG_ASSIGNMENTS, and PO_PRICE_HELPER. It depends in turn on PO_TBL_VARCHAR1, PO_TBL_VARCHAR30, PO_TBL_VARCHAR2000, PO_TBL_VARCHAR4000, PO_TBL_NUMBER, PO_TBL_DATE, and PO_VALIDATION_RESULTS_TYPE. Because it is an internal helper, it is typically invoked indirectly—through the Purchasing forms and the PO document validation concurrent processes—rather than called directly by end users. Customizations should generally consume the higher-level validation APIs rather than PO_VALIDATION_HELPER directly, since its interface may change between releases and is not published for external support.