Results for “po_ga_org_assignments”

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

Overview

PO_GA_ORG_ASSIGNMENTS is a Purchasing module table owned by the PO schema that stores Global Agreements Org Assignments. A global agreement is a purchasing document — typically a global blanket purchase agreement or global contract — that is authored in one operating unit and shared across multiple operating units. This table captures that sharing relationship: it records, for each global agreement header, the specific inventory organizations to which the agreement has been assigned, and whether each assignment is currently enabled.

The object therefore functions as a cross-reference between a purchasing document header and the organizations entitled to consume it. Its documented physical schema in ETRM 12.2.2 contains eleven columns. The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning it holds no documented outbound foreign keys and would be modeled as an independent structure rather than as a hub, link, or satellite. Where integration with parent purchasing documents is required, that linkage is best derived directly from the PO_HEADER_ID column.

Key Information Stored

The table's substantive content is concentrated in a small number of columns. Two business identifiers anchor every row:

• PO_HEADER_ID — references the global agreement header in PO_HEADERS_ALL. This is the parent document being distributed.
• ORGANIZATION_ID — the inventory organization receiving the assignment.
• PURCHASING_ORG_ID — the purchasing (operating unit) organization associated with the assignment.
• ORG_ASSIGNMENT_ID — a surrogate identifier for the assignment record itself, isolated by unique index PO_GA_ORG_ASSIGN_U2.
• ENABLED_FLAG — indicates whether the assignment is active. Disabled assignments remain in the table but are excluded from effective agreement scope.
• VENDOR_SITE_ID — the supplier site associated with the assignment, where the agreement is restricted to a particular vendor site.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns providing audit lineage for each row.

Two unique indexes are documented. PO_GA_ORG_ASSIGN_PK is the primary key on (PO_HEADER_ID, ORGANIZATION_ID), and the same column pair forms business-key candidate PO_GA_ORG_ASSIGN_U1. Consequently, a given organization may appear only once per global agreement header. ORG_ASSIGNMENT_ID is a secondary unique key (PO_GA_ORG_ASSIGN_U2) rather than the primary key, so it should be treated as an alternate identifier, not the definitive row identity.

Common Use Cases and Queries

Reporting on global agreement distribution is the principal use case. Buyers and sourcing analysts need to know which organizations can transact against a given global agreement, and whether any assignments have been disabled. A typical query joining to the agreement header is:

• SELECT ga.PO_HEADER_ID, ga.ORGANIZATION_ID, ga.ENABLED_FLAG, ga.PURCHASING_ORG_ID FROM PO.PO_GA_ORG_ASSIGNMENTS ga WHERE ga.PO_HEADER_ID = :p_header_id;
• Filtering active scope only: add AND ga.ENABLED_FLAG = 'Y'.
• Auditing recently changed assignments: order by LAST_UPDATE_DATE descending and return LAST_UPDATED_BY.
• Identifying all agreements available to one organization: SELECT PO_HEADER_ID FROM PO.PO_GA_ORG_ASSIGNMENTS WHERE ORGANIZATION_ID = :p_org_id AND ENABLED_FLAG = 'Y';

These patterns support procurement dashboards, agreement-scope validation reports, and troubleshooting when requisitioners report that a global agreement is unavailable to their organization. Because the table is standalone with no documented outbound foreign keys, joins to PO_HEADERS_ALL, HR_ALL_ORGANIZATION_UNITS, and vendor-site tables must be written explicitly against PO_HEADER_ID, ORGANIZATION_ID, and VENDOR_SITE_ID respectively.

Related Objects

• PO_HEADERS_ALL — joined on PO_HEADERS_ALL.PO_HEADER_ID = PO_GA_ORG_ASSIGNMENTS.PO_HEADER_ID; supplies agreement number, type, and status.
• PO_GA_ORG_ASSIGNMENTS child records — the table itself is the authoritative source for scope; no separate child table is documented.
• HR_ALL_ORGANIZATION_UNITS / ORG_ORGANIZATION_DEFINITIONS — resolve ORGANIZATION_ID and PURCHASING_ORG_ID to organization names.
• PO_VENDOR_SITES_ALL — resolves VENDOR_SITE_ID to the supplier site.
• PO_LINES_ALL / PO_LINE_LOCATIONS_ALL — agreement lines available for release within the assigned organizations.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to application users for audit reporting.

No PL/SQL APIs are documented in the supplied metadata; the table is maintained through the Global Agreements setup and Purchasing document flows in the E-Business Suite forms interface.