Results for “po_val_ga_org_assignments”

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

Overview

PO_VAL_GA_ORG_ASSIGNMENTS is a validation package body in the Oracle E-Business Suite Purchasing module (APPS schema). It belongs to the family of PO_VAL_* packages that implement attribute-level validation for the Purchasing document entry and maintenance flows. Its specific responsibility is to validate records representing the association between a Purchasing Organization and a Supplier Site — the "GA Org Assignment" entity (Global Agreement Organization Assignment). In Oracle Purchasing, a Global Agreement is an agreement negotiated at a global (non-operating-unit-specific) level and then assigned to one or more purchasing organizations, each pointing at a supplier site from which the agreement is fulfilled. Before such an assignment row can be written through the Public API or the associated forms, the mandatory columns on the assignment record must be verified. This package performs that verification using the shared PO_VALIDATION_HELPER infrastructure and the PO_MESSAGE_S message dictionary.

The package follows the standard PO validation framework contract: each validation subprogram receives PL/SQL tables of primary keys and the attribute values being checked, appends its findings to a shared PO_VALIDATION_RESULTS_TYPE collection, and returns an overall result type. This design lets the caller validate an entire batch of assignment rows in one pass rather than row-by-row, and it keeps all messages, logging, and result aggregation consistent with the rest of the Purchasing validation stack.

Key Procedures and Functions

• PURCHASING_ORG_ID_NOT_NULL — Verifies that the Purchasing Organization identifier on each GA Org Assignment record is populated. It delegates the actual check to PO_VALIDATION_HELPER.not_null, passing the assignment primary keys as the entity identifiers, the entity type constant PO_VALIDATIONS.C_ENTITY_TYPE_GA_ORG_ASSIGN, the column name 'PURCHASING_ORG_ID', and the shared message PO_MESSAGE_S.PO_ALL_NOT_NULL. A missing purchasing organization is reported through the standard "value must not be null" message rather than a bespoke error text.
• VENDOR_SITE_ID_NOT_NULL — Verifies that the Supplier (Vendor) Site identifier on each GA Org Assignment record is populated. It mirrors the structure of the purchasing organization check, using the same entity type, the column name 'VENDOR_SITE_ID', and the same not-null message. This is the subprogram referenced when users search on "vendor_site_id_not_null".

Both procedures are instrumented for PO_LOG via PO_LOG.get_subprogram_base using a package base derived from PO_LOG.get_package_base('PO_VAL_GA_ORG_ASSIGNMENTS'), so diagnostics are emitted under stable module names. Each is declared with an IN OUT NOCOPY results collection to avoid copying the accumulated validation findings.

Tables Accessed

The package body is purely a validation routine and does not itself open cursors against application tables. It operates on the in-memory PL/SQL tables supplied by the caller, converting numeric identifier and value collections with PO_TYPE_CONVERTER.to_po_tbl_varchar4000 before handing them to the validation helper. Consequently, no base tables are recorded as directly referenced through APPS synonyms. The persisted data it ultimately guards resides in the GA organization assignment storage maintained by the broader PO Global Agreements API, while messages are sourced from PO_MESSAGE_S. Any database reads needed to confirm that the referenced purchasing organization or vendor site actually exists are performed by other validation packages in the PO_VAL_* group, not here.

Usage Notes

This package is invoked indirectly. It is referenced by one other package in the ETRM inventory, indicating it is called from a higher-level validation or Global Agreements API driver rather than exposed as a standalone entry point. Typical call paths include the Global Agreements / PO Public API validation phases and the Purchasing forms that maintain agreement organization assignments, where a batch of assignment rows is validated before insert or update. Customizations should not call these procedures directly; instead, custom code writing GA Org Assignment data should go through the supported Public API so that this validation — and the remainder of the PO_VAL_* chain — executes automatically and raises the standardized PO_ALL_NOT_NULL errors when PURCHASING_ORG_ID or VENDOR_SITE_ID is left blank. Because the package is a compiled body owned by APPS with no documented public signature beyond the two internal procedures, it should be treated as framework-internal and left unmodified during upgrades from 12.1.1 to 12.2.2.