Results for “autoselect_flag”

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

Overview

GL_IEA_RECUR_BATCHES is a General Ledger table owned by the GL schema that stores the definition and control attributes of recurring intercompany batches. Within the Oracle E-Business Suite, it functions as the master definition object for intercompany allocations that are executed repeatedly on a defined schedule rather than entered manually each period. Each row represents a single recurring batch template, carrying the sending subsidiary, activation window, selection behavior, and the audit trail of the most recent execution.

The table sits at the center of the intercompany recurring processing model. It is referenced by GL_IEA_RECUR_HISTORY, which records the results of individual executions, and by GL_IEA_RECUR_TRANSACTIONS, which holds the transaction lines associated with a batch. Because the table primarily stores descriptive batch attributes and execution metadata rather than the transactional detail itself, the heuristic Data Vault classification of satellite-leaning is appropriate as a modeling suggestion: the object behaves as a descriptive satellite anchored to a recurring batch business key, with dependent history and transaction tables functioning as related detail stores.

Key Information Stored

The surrogate primary key is RECURRING_BATCH_ID, enforced through the index GL_IEA_RECUR_BATCHES_PK. Two unique indexes define the business keys: GL_IEA_RECUR_BATCHES_U1 on RECURRING_BATCH_ID and GL_IEA_RECUR_BATCHES_U2 on the combination of NAME and SENDING_SUBSIDIARY_ID, meaning a recurring batch name must be unique within a given sending subsidiary. The most significant columns include:

• RECURRING_BATCH_ID — surrogate primary key identifying the batch.
• NAME — the user-defined batch name, unique within the sending subsidiary.
• SENDING_SUBSIDIARY_ID — foreign key to GL_IEA_SUBSIDIARIES, identifying the originating intercompany entity.
• AUTOSELECT_FLAG — indicates whether transactions are selected automatically during execution.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the batch may run.
• DESCRIPTION — free-form purpose or notes for the batch.
• LAST_EXECUTED_BY — foreign key to FND_USER identifying the user who last ran the batch.
• LAST_EXECUTED_GL_DATE — the GL date of the most recent execution.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program request and audit context for the last run.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS auditing columns.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield and extensibility columns.

Common Use Cases and Queries

Typical reporting focuses on identifying active batches, their subsidiary, and execution recency. A representative query lists batches that are currently active for a subsidiary:

• SELECT b.recurring_batch_id, b.name, s.name subsidiary, b.start_date_active, b.end_date_active, b.last_executed_gl_date FROM gl_iea_recur_batches b, gl_iea_subsidiaries s WHERE b.sending_subsidiary_id = s.subsidiary_id AND SYSDATE BETWEEN b.start_date_active AND NVL(b.end_date_active, SYSDATE + 1);
• Join to GL_IEA_RECUR_HISTORY on RECURRING_BATCH_ID to review execution history and success rates for a given batch.
• Join to GL_IEA_RECUR_TRANSACTIONS on RECURRING_BATCH_ID to inspect the intercompany lines generated by a batch.
• Join LAST_EXECUTED_BY to FND_USER to attribute the most recent execution to a specific user.
• Filter on AUTOSELECT_FLAG to distinguish automated selection batches from manual ones for operational reporting.

Related Objects

The following objects are the most significant dependencies and references for this table:

• GL_IEA_SUBSIDIARIES — referenced via SENDING_SUBSIDIARY_ID; supplies the originating intercompany entity.
• FND_USER — referenced via LAST_EXECUTED_BY; identifies the user responsible for the most recent execution.
• GL_IEA_RECUR_HISTORY — references this table via RECURRING_BATCH_ID and stores per-execution results.
• GL_IEA_RECUR_TRANSACTIONS — references this table via RECURRING_BATCH_ID and stores the batch transaction lines.
• GL_IEA_RECUR_BATCHES_PK / U1 / U2 — the primary and unique indexes enforcing identity and the NAME plus SENDING_SUBSIDIARY_ID business key.

These relationships confirm that GL_IEA_RECUR_BATCHES acts as the parent definition object for the recurring intercompany process, with history and transaction tables capturing the outcomes of each execution.