Results for “ap_ou_group”

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

Overview

AP.AP_OU_GROUP is a Payables module table that stores the set of operating units associated with a Payment Process Request Template or an individual Payment Process Request. In Oracle EBS Release 12.1.1 and 12.2.2, the Payment Process Request (PPR) framework allows a payables user to select payments across multiple operating units in a single run. This table records that operating-unit scope explicitly, one row per operating unit included in a template or request, enabling the selection criteria to be reused and audited.

The ETRM metadata documents the table as owning 9 columns under the AP schema, with the unique index AP_OU_GROUP_U1 on OU_GROUP_ID and the primary key constraint AP_OU_GROUP_PK also on OU_GROUP_ID. The data vault classification mined from the foreign-key structure is link. From a modeling perspective, this is appropriate: the table resolves the relationship between operating units and their owning PPR template or checkrun context, rather than describing an operating unit itself. It should therefore be treated as an associative or intersection entity, not as a hub or satellite.

Key Information Stored

The documented columns permit the following functional interpretation:

• OU_GROUP_ID — Surrogate primary key. Uniquely identifies each row and is the column backed by both AP_OU_GROUP_PK and the unique index AP_OU_GROUP_U1. It is the primary access path for lookups, though it carries no business meaning beyond row identity.
• ORG_ID — The operating unit identifier. This is the principal business-key candidate in practice, since it determines which organization's transactions are included in the group.
• TEMPLATE_ID — Foreign key to AP_PAYMENT_TEMPLATES. Populated when the operating-unit group belongs to a reusable Payment Process Request Template.
• CHECKRUN_ID — Foreign key to AP_INV_SELECTION_CRITERIA_ALL. Populated when the group is tied to a specific Payment Process Request run rather than a template.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login session that performed it.

In a typical row, exactly one of TEMPLATE_ID or CHECKRUN_ID establishes the parent context, with ORG_ID supplying the business-value payload. The absence of descriptive columns (such as an operating-unit name) confirms the table's narrow, associative role.

Common Use Cases and Queries

Reporting and troubleshooting around multi-organization payment runs are the dominant use cases. A common query retrieves the operating units included in a specific Payment Process Request:

• List operating units for a checkrun: SELECT ORG_ID FROM AP.AP_OU_GROUP WHERE CHECKRUN_ID = :checkrun_id;
• List operating units for a template: SELECT ORG_ID FROM AP.AP_OU_GROUP WHERE TEMPLATE_ID = :template_id;
• Identify all PPR requests spanning a given operating unit: SELECT CHECKRUN_ID FROM AP.AP_OU_GROUP WHERE ORG_ID = :org_id AND CHECKRUN_ID IS NOT NULL;
• Join to selection criteria to obtain run status and dates: SELECT g.ORG_ID, s.CHECKRUN_NAME, s.STATUS FROM AP.AP_OU_GROUP g, AP.AP_INV_SELECTION_CRITERIA_ALL s WHERE g.CHECKRUN_ID = s.CHECKRUN_ID;

These patterns support audit of payment scope, reconciliation of which organizations were processed in a given run, and validation that a template's configured operating units match operational expectations. Because OU_GROUP_ID is the only unique index, always filter on the foreign-key columns or ORG_ID rather than relying on the surrogate key in ad hoc reporting.

Related Objects

• AP.AP_PAYMENT_TEMPLATES — Referenced by AP_OU_GROUP.TEMPLATE_ID; defines reusable Payment Process Request configurations whose operating-unit scope is stored in this table.
• AP.AP_INV_SELECTION_CRITERIA_ALL — Referenced by AP_OU_GROUP.CHECKRUN_ID; holds the selection criteria for each Payment Process Request and is the primary parent for request-specific operating-unit groups.
• AP.AP_INVOICE_SELECTION_CRITERIA and related PPR criteria tables — sibling selection objects that participate in the same payment-run framework.
• AP.AP_PAYMENT_SCHEDULES_ALL and AP.AP_CHECKS_ALL — downstream objects where payments generated under the covered operating units are recorded.
• Payables PPR concurrent programs and the Payments workbench — application-layer consumers that read this table to determine which operating units participate in a run.

The table's two foreign keys to AP_PAYMENT_TEMPLATES and AP_INV_SELECTION_CRITERIA_ALL confirm it is a dependent, link-style object with no independent business identity.