Results for “org_assignment_id”

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

Overview

PO_GA_ORG_ASSIGNMENTS_ARCHIVE is a Purchasing (PO) module table that stores archived organizational assignments for Global Agreements. A Global Agreement is a purchasing document that can be shared across multiple operating units within an Oracle E-Business Suite implementation. The org assignment records determine which organizations are permitted to reference, release against, or otherwise use a given global agreement. When an agreement is modified, superseded, or archived, its prior organizational assignment rows are preserved in this table so that a complete historical record remains available for audit, reconciliation, and reporting purposes.

In Oracle EBS 12.1.1 and 12.2.2, this table functions as a companion archive to the live global agreement org assignment data. It is maintained by Purchasing processes rather than by direct user entry, and it is not exposed through standard Purchasing forms. The heuristic Data Vault classification derived from the foreign-key structure is standalone. From a dimensional modeling perspective, this classification suggests the table could be modeled as a satellite-like history store keyed to the parent purchasing document and organization, capturing attribute states (such as ENABLED_FLAG and VENDOR_SITE_ID) that change across revisions.

Key Information Stored

The table contains 13 documented columns. The most significant are described below.

• PO_HEADER_ID — Identifier of the parent global agreement header. Part of the composite primary key and the principal link to the purchasing document.
• ORGANIZATION_ID — The operating unit or organization to which the global agreement was assigned. Part of the composite primary key.
• REVISION_NUM — Revision number of the assignment state. This column is central to the archive's purpose: it distinguishes successive revisions of an org assignment, making the table a revision history rather than a simple snapshot. It participates in all three documented key structures.
• ORG_ASSIGNMENT_ID — Surrogate identifier for the individual org assignment. It forms the single-column primary key PO_GA_ORG_ASSIGN_ARCHIVE_PK and is also the basis of the alternate unique key PO_GA_ORG_ASSIGN_ARCHIVE_UK.
• ENABLED_FLAG — Indicates whether the organization assignment was enabled or disabled at that revision.
• VENDOR_SITE_ID — Supplier site associated with the assignment where applicable.
• PURCHASING_ORG_ID — The purchasing organization context in which the assignment was effective.
• LATEST_EXTERNAL_FLAG — Flag identifying the most recent externally facing version of the assignment record.
• Audit columns CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — Standard EBS who-columns recording creation and last modification metadata.

Three key definitions are documented: the surrogate primary key PO_GA_ORG_ASSIGN_ARCHIVE_PK on ORG_ASSIGNMENT_ID; the unique key PO_GA_ORG_ASSIGN_ARCHIVE_UK on ORGANIZATION_ID, PO_HEADER_ID, REVISION_NUM; and PO_GA_ORG_ASSIGN_ARC_PK on PO_HEADER_ID, ORGANIZATION_ID, REVISION_NUM. The latter two represent the business-key candidates, collectively identifying a distinct revision of an organization's assignment to a given agreement.

Common Use Cases and Queries

Typical uses include auditing historical agreement access, reconstructing which organizations could use an agreement at a point in time, and reporting on revision history for compliance reviews.

• Retrieve all archived revisions for a specific agreement:

  SELECT po_header_id, organization_id, revision_num,
         enabled_flag, vendor_site_id, latest_external_flag
  FROM   po_ga_org_assignments_archive
  WHERE  po_header_id = :p_header_id
  ORDER  BY revision_num, organization_id;

• Identify the highest revision per agreement and organization:

  SELECT po_header_id, organization_id, MAX(revision_num)
  FROM   po_ga_org_assignments_archive
  GROUP  BY po_header_id, organization_id;

• Determine which operating units were enabled for a release at a specific revision:

  SELECT organization_id, vendor_site_id
  FROM   po_ga_org_assignments_archive
  WHERE  po_header_id = :p_header_id
  AND    revision_num = :p_revision
  AND    enabled_flag = 'Y';

Related Objects

The table's relationships center on the purchasing document and organization model. Significant related objects, joined through the documented key columns, include:

• PO_HEADERS_ALL — join on PO_HEADER_ID to retrieve agreement header details.
• PO_GA_ORG_ASSIGNMENTS — the live counterpart from which archived rows are derived; compare on PO_HEADER_ID, ORGANIZATION_ID, and REVISION_NUM.
• ORG_ORGANIZATION_DEFINITIONS / HR_ALL_ORGANIZATION_UNITS — join on ORGANIZATION_ID for organization names.
• PO_VENDOR_SITES_ALL — join on VENDOR_SITE_ID for supplier site context.
• PO_HEADERS_ARCHIVE_ALL — the archived header row corresponding to PO_HEADER_ID, preserving agreement history alongside its org assignments.

Because the metadata classifies this object as standalone, no formal foreign keys are documented; joins above are based on the documented key columns and the natural Purchasing data model.