Results for “ap_le_group”

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

Overview

AP_LE_GROUP is an Oracle Payables (AP) transaction table that stores the association between legal entities and either a Payment Process Request Template or an individual Payment Process Request. In Oracle E-Business Suite 12.1.1 and 12.2.2, the Payment Process Request (PPR) framework allows a payables user to select, group, and pay invoices across one or more legal entities. The AP_LE_GROUP table captures the set of legal entities that a given template or a given payment run is permitted to include, effectively acting as the legal entity selection filter for the payment process.

From a Data Vault modeling perspective, the metadata heuristically classifies AP_LE_GROUP as a link table. This is a modeling suggestion rather than a physical designation: the table resolves the many-to-many relationship between legal entities and the two parent contexts (templates and payment requests) through its foreign keys, without carrying descriptive attributes of its own beyond standard audit columns.

Key Information Stored

The table is defined in the AP schema with nine documented columns. Its primary key is AP_LE_GROUP_PK, defined on LE_GROUP_ID, which is also enforced by the unique index AP_LE_GROUP_U1. LE_GROUP_ID is the surrogate primary key; the business significance of a row is determined by the combination of the legal entity and the parent template or payment request it references, not by the surrogate alone.

• LE_GROUP_ID — Surrogate primary key (AP_LE_GROUP_PK / AP_LE_GROUP_U1) uniquely identifying each legal entity grouping row.
• LEGAL_ENTITY_ID — Foreign key to FV_LEGAL_ENTITIES identifying the legal entity included in the group.
• TEMPLATE_ID — Foreign key to AP_PAYMENT_TEMPLATES, populated when the row defines the legal entity scope of a Payment Process Request Template.
• CHECKRUN_ID — Foreign key to AP_INV_SELECTION_CRITERIA_ALL, populated when the row defines the legal entity scope of a specific Payment Process Request.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the most recent modification.

In practice TEMPLATE_ID and CHECKRUN_ID are mutually exclusive: a row is anchored either to a template or to a live payment request, and the corresponding opposite column is left null.

Common Use Cases and Queries

The most frequent use of AP_LE_GROUP is diagnostic and reporting work around Payment Process Requests. Payables administrators query it to determine which legal entities a template or a submitted request will draw invoices from, particularly when a payment run unexpectedly returns no transactions or excludes an entity.

A typical query lists the legal entities attached to a payment request:

• SELECT g.le_group_id, g.legal_entity_id, g.checkrun_id FROM ap.ap_le_group g WHERE g.checkrun_id = :p_checkrun_id;
• SELECT g.le_group_id, g.legal_entity_id, g.template_id FROM ap.ap_le_group g WHERE g.template_id = :p_template_id;

Joining to FV_LEGAL_ENTITIES resolves the entity name for reporting, and joining on CHECKRUN_ID to AP_INV_SELECTION_CRITERIA_ALL links the grouping back to the payment request header and its selection criteria. Reconciliation reports that compare the legal entities configured on a template against those actually used at run time rely on both join paths. Because the table is small and indexed on its primary key, these queries are inexpensive and suitable for ad hoc troubleshooting as well as embedded diagnostics.

Related Objects

AP_LE_GROUP sits at the intersection of the Payables payment setup and payment execution objects. The principal related objects, with their join columns, are:

• AP_PAYMENT_TEMPLATES — joined via AP_LE_GROUP.TEMPLATE_ID; defines reusable Payment Process Request Templates whose legal entity scope is stored here.
• AP_INV_SELECTION_CRITERIA_ALL — joined via AP_LE_GROUP.CHECKRUN_ID; holds the selection criteria and header information for a specific Payment Process Request.
• FV_LEGAL_ENTITIES — joined via AP_LE_GROUP.LEGAL_ENTITY_ID; the legal entity master providing the entity name and identifier.
• AP_LE_GROUP_PK / AP_LE_GROUP_U1 — the primary key constraint and unique index enforcing uniqueness of LE_GROUP_ID.

Together these objects support the legal entity dimension of the Oracle Payables Payment Process Request framework in both 12.1.1 and 12.2.2.