Results for “freight_terms_lookup_code”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.PO_VAL_HEADERS2 is a PL/SQL validation package within Oracle E-Business Suite that supports the validation of Purchasing document headers. It operates as part of the broader PO_VALIDATIONS framework, which enforces data integrity rules on purchasing documents before they are saved, approved, or processed. The package is classified as an "OTHER" API in the ETRM metadata, indicating it is a supporting validation component rather than a public, supported interface for external integration. In Oracle EBS 12.1.1 and 12.2.2, PO_VAL_HEADERS2 is invoked by PO_VALIDATIONS to evaluate individual header-level attributes and record the outcome of each check. Its scope includes currency and rate validation, supplier and agent verification, ship-to and bill-to location checks, freight and shipping terms, encumbrance amounts, and document style validation. Results are stored in PO_VALIDATION_RESULTS_GT, enabling the calling framework to aggregate errors and warnings and present them to the user. The package depends on APPS.PO_VALIDATION_RESULTS_TYPE and a set of PL/SQL table types (PO_TBL_DATE, PO_TBL_NUMBER, PO_TBL_VARCHAR1, PO_TBL_VARCHAR30), which are used to pass collections of values and messages between validation routines and the calling process.

Key Procedures and Functions

The ETRM metadata documents 22 procedures and functions within PO_VAL_HEADERS2. These routines correspond to discrete header-level validation points. Representative members include PO_HEADER_ID and DOCUMENT_NUM, which identify and validate the purchasing document; CURRENCY_CODE and RATE_INFO, which verify that a valid currency is supplied and that rate information is consistent; AGENT_ID and VENDOR_INFO, which confirm the buyer and supplier references; SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID, and SHIP_VIA_LOOKUP_CODE, which validate location and shipping method values; FOB_LOOKUP_CODE, FREIGHT_TERMS_LOOKUP_CODE, and SHIPPING_CONTROL, which check trade and transportation terms; ACCEPTANCE_DUE_DATE, which confirms the acceptance date is valid; CANCEL_FLAG and CLOSED_CODE, which validate document status indicators; PRINT_COUNT and APPROVAL_STATUS, which check document state attributes; AMOUNT_TO_ENCUMBER, which validates encumbrance amounts; STYLE_ID, which validates the document style reference; and TYPE_LOOKUP_CODE, which confirms the document type. Each routine records success or failure through the validation results structure. Parameter lists are intentionally not documented here, as they are not exposed in the ETRM metadata.

Tables Accessed

PO_VAL_HEADERS2 reads and writes against several documented tables via APPS synonyms. PO_HEADERS and PO_HEADERS_ALL are the primary source of header data, used to confirm the existence and state of the purchasing document. PO_HEADERS_INTERFACE is referenced for validation performed during interface import processing. FND_CURRENCIES and PLITBLM supply currency definitions and multi-currency conversion information for rate validation. PO_AGENTS verifies the buyer reference, while PO_DOC_STYLE_HEADERS validates the style identifier. ORG_FREIGHT supports freight term and shipping validation. PO_VALIDATION_RESULTS_GT receives validation outcomes, and DUAL supports simple lookup and default checks.

Usage Notes

PO_VAL_HEADERS2 is not intended to be called directly by custom code. It is invoked indirectly when purchasing documents are created or modified through the Purchasing forms, when validation is triggered during approval workflows, and when PO_VALIDATIONS executes its header validation cycle. The package also references itself in the dependency listing, indicating internal routine calls, and is referenced by PO_VALIDATIONS, its principal caller. Customers extending validation logic should generally work through the supported PO_VALIDATIONS interface rather than invoking PO_VAL_HEADERS2 directly, since its procedures are tightly coupled to the validation results framework and PL/SQL table types.