Results for “shipment_type”

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

Overview

PO_VAL_SHIPMENTS2 is a validation package in the Oracle E-Business Suite APPS schema that evaluates the shipment-level attributes of a purchase order line location before the record is committed to the database. Within the Oracle Purchasing module, a shipment corresponds to a row in PO_LINE_LOCATIONS_ALL, and PO_VAL_SHIPMENTS2 is the component responsible for applying the field-level validation rules that govern those rows. It forms part of the layered validation framework invoked by PO_VALIDATIONS, and its results are written into the standard validation results structure so that the calling form or interface can report errors and warnings back to the user.

The package does not perform the insert or update itself. Instead, it inspects candidate values, compares them against reference data such as item master attributes, organisation definitions, freight terms, and document style configuration, and returns a structured result set. This separation allows the same validation logic to be reused by the Purchasing forms, by the replenishment and sourcing flows, and by custom inbound interfaces.

Key Procedures and Functions

The package exposes twenty-eight documented procedures and functions, each targeting a discrete shipment attribute:

• NEED_BY_DATE, PROMISED_DATE, EFFECTIVE_DATES — validate the date fields on the shipment, including ordering of the need-by and promised dates.
• SHIPMENT_TYPE, PAYMENT_TYPE, SHIPMENT_NUM — validate enumerated and identifying shipment attributes.
• QUANTITY, AMOUNT — check numeric values against tolerance and sign rules.
• PRICE_OVERRIDE, PRICE_DISCOUNT, PRICE_BREAK_ATTRIBUTES — validate pricing-related shipment attributes and their consistency with the line.
• SHIP_TO_ORGANIZATION_ID, ENFORCE_SHIP_TO_LOC_CODE — confirm that the ship-to organisation and location are valid and permitted for the transaction.
• ALLOW_SUB_RECEIPTS_FLAG, DAYS_EARLY_RECEIPT_ALLOWED, RECEIPT_DAYS_EXCEPTION_CODE, ACCRUE_ON_RECEIPT_FLAG — validate receiving and accrual controls at shipment level.
• INVOICE_CLOSE_TOLERANCE, RECEIVE_CLOSE_TOLERANCE — validate the close tolerance percentages used for automatic closure.
• RECEIVING_ROUTING_ID — confirm the routing reference is valid for the shipment.

Tables Accessed

Validation depends on reference data drawn through APPS synonyms. MTL_SYSTEM_ITEMS and MTL_ITEM_REVISIONS supply item-level attributes that constrain acceptable shipment values. PO_LINE_LOCATIONS_ALL and PO_LINE_LOCATIONS_DRAFT_ALL provide the current and draft shipment rows under evaluation. PO_DOC_STYLE_HEADERS supplies document style configuration that determines which validations apply, ORG_FREIGHT supplies freight terms, and ZX_ID_TCC_MAPPING supports tax classification. PO_VALIDATION_RESULTS_GT is the global temporary table into which validation messages are written, while DUAL and the PL/SQL table types PO_TBL_DATE, PO_TBL_NUMBER, PO_TBL_VARCHAR1, PO_TBL_VARCHAR5, PO_TBL_VARCHAR30, and PO_VALIDATION_RESULTS_TYPE carry the in-memory collections used to pass attribute values and results between procedures. The PO_TBL_VARCHAR5 collection is significant because it is the type commonly used to hold short coded values, including the descriptive flexfield column po_tbl_varchar5 referenced by users searching on that term; the flexfield columns on the shipment record are passed into this package through such PL/SQL table types.

Usage Notes

PO_VAL_SHIPMENTS2 is invoked indirectly rather than called directly by end users. The Purchasing shipment and line-location forms call PO_VALIDATIONS, which in turn invokes the individual validation routines in this package at the point of save. Interfaces and custom PL/SQL that insert or update PO_LINE_LOCATIONS_ALL should follow the same pattern, populating the relevant PL/SQL table types and PO_VALIDATION_RESULTS_TYPE before checking the returned messages. Because the package writes to a global temporary table, callers must read results within the same session. The package is referenced by PO_VALIDATIONS and is itself dependent on the PO_TBL collection types, so changes to those type definitions can invalidate it and require recompilation.