Search Results ap_le_group




Overview
Explore in AI Chat

Overview

The AP_LE_GROUP table is a core data structure within the Oracle E-Business Suite Payables (AP) module, specifically for the Payment Process Request framework. It serves as a junction table that defines the relationship between a payment process template or a specific payment process request (check run) and the legal entities for which payments can be processed. Its primary role is to enforce and manage the legal entity context for payment operations, ensuring that payment instructions and disbursements are correctly scoped to the appropriate organizational units within a multi-entity setup. This is critical for maintaining financial compliance and accurate accounting in global deployments.

Key Information Stored

The table's structure is designed to link a payment process definition to one or more legal entities. While the full column list is not detailed in the provided metadata, the foreign key relationships explicitly identify the most critical columns. The LE_GROUP_ID is the table's primary key. The TEMPLATE_ID column links a group of legal entities to a specific Payment Process Request Template (AP_PAYMENT_TEMPLATES). The CHECKRUN_ID column links a group of legal entities to a specific, executed Payment Process Request or check run (AP_INV_SELECTION_CRITERIA_ALL). Each record in this table typically associates a single legal entity identifier (such as ORG_ID) with one of these parent identifiers, allowing a single template or request to be valid for multiple legal entities.

Common Use Cases and Queries

This table is central to queries that determine which legal entities are authorized for a given payment process. A common reporting use case is to list all legal entities assigned to a specific payment template to verify setup before submission. For troubleshooting, one might query to identify which payment process request a particular legal entity was processed under. Sample SQL patterns include joining to AP_PAYMENT_TEMPLATES to analyze template scope or joining to AP_INV_SELECTION_CRITERIA_ALL to audit historical payment runs. For example:

  • Identifying legal entities for a template: SELECT leg.legal_entity_id, apt.template_name FROM ap_le_group leg, ap_payment_templates apt WHERE leg.template_id = apt.template_id AND apt.template_name = 'MY_TEMPLATE';
  • Validating legal entity inclusion in a payment batch: SELECT count(*) FROM ap_le_group WHERE checkrun_id = :p_checkrun_id AND legal_entity_id = :p_org_id;

Related Objects

The AP_LE_GROUP table has direct foreign key relationships with two primary payment processing tables, as confirmed by the metadata. It is a child table of AP_PAYMENT_TEMPLATES, which stores the definition of reusable payment process templates. It is also a child table of AP_INV_SELECTION_CRITERIA_ALL, which stores the parameters and control data for individual payment process requests (check runs). The table is referenced by the primary key constraint AP_LE_GROUP_PK on LE_GROUP_ID. While not listed, it is logically related to the underlying legal entity definition tables (such as XLE_ENTITY_PROFILES) via the legal entity identifier stored within its records.