Results for “default_currency_code”

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

Overview

The GL_IEA_RECUR_BATCHES_V view is a General Ledger (GL) reporting and integration object within Oracle E-Business Suite, specifically associated with the Intercompany and Enterprise Accounting (IEA) functionality. It presents recurring intercompany batch definitions in a denormalized, query-friendly form, joining the recurring batch header to its originating sending subsidiary and to the application user identity of the last executor. In the Oracle EBS 12.1.1 and 12.2.2 releases, this view sits in the GL schema and serves as a read interface for both internal concurrent programs and external reporting layers, allowing developers and analysts to retrieve recurring batch configurations without navigating the multiple normalized base tables that store intercompany subsidiary and batch data.

Underlying Base Objects

The ETRM documentation lists no separately documented referenced base objects; however, the view text explicitly identifies the source tables used in the SQL definition:

• GL_IEA_RECUR_BATCHES B — the primary table holding recurring batch definitions, aliased as B. The view selects the batch row, name, subsidiary reference, flags, audit columns, execution history, and the descriptive flexfield (DFF) context and attribute columns from this table.
• GL_IEA_SUBSIDIARIES S — the intercompany subsidiary definition table, aliased as S, joined on B.SENDING_SUBSIDIARY_ID = S.SUBSIDIARY_ID. It supplies the subsidiary name, company value, currency code, subsidiary type, and auto-approve flag.
• FND_USER U — the application user table, joined with an outer join (U.USER_ID (+) = B.LAST_EXECUTED_BY) so batches that were never executed, or whose executor no longer exists, are still returned. It contributes the LAST_EXECUTED_BY_NAME column.

The inner join to GL_IEA_SUBSIDIARIES means a recurring batch is not returned unless its sending subsidiary exists; the outer join to FND_USER preserves batch rows regardless of executor history.

Key Columns

• ROW_ID — the ROWID of the underlying GL_IEA_RECUR_BATCHES row, useful for direct row addressing.
• RECURRING_BATCH_ID — the primary identifier of the recurring intercompany batch.
• CHART_OF_ACCOUNTS_ID — chart of accounts associated with the sending subsidiary.
• NAME — the user-defined batch name; DESCRIPTION — free-text description.
• SENDING_SUBSIDIARY_ID / SENDING_SUBSIDIARY / SENDER_COMPANY_VALUE — the sending subsidiary identifier, its name, and the company value used in accounting flexfield derivation.
• DEFAULT_CURRENCY_CODE — this is the aliased S.CURRENCY_CODE from GL_IEA_SUBSIDIARIES. It represents the default currency of the sending subsidiary and therefore governs the currency applied to recurring batch transactions when no override is supplied. Users searching for default_currency_code will find that this view does not store the value on the batch itself; the currency is inherited from the subsidiary record, making the alias a derived attribute rather than a batch-level column.
• SUBSIDIARY_TYPE_CODE, AUTO_APPROVE_FLAG, AUTOSELECT_FLAG — control flags governing subsidiary behavior, automatic approval, and automatic selection during batch processing.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the recurring batch.
• LAST_EXECUTED_BY / LAST_EXECUTED_BY_NAME / LAST_EXECUTED_GL_DATE — the executor user identifier, resolved username, and the GL date of the most recent execution.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield context and segment values for extensibility.

Common Use Cases and Queries

Typical use cases include recurring intercompany batch auditing, currency determination reporting, and configuration extraction for integration or migration efforts.

• Identify active recurring batches and the default currency inherited from the sending subsidiary:

  SELECT recurring_batch_id, name, sending_subsidiary,
         default_currency_code, start_date_active, end_date_active
  FROM   gl_iea_recur_batches_v
  WHERE  SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                     AND NVL(end_date_active, SYSDATE);

• Report batches that have never been executed:

  SELECT recurring_batch_id, name, sending_subsidiary
  FROM   gl_iea_recur_batches_v
  WHERE  last_executed_gl_date IS NULL
     OR  last_executed_by_name IS NULL;

• Extract execution history for operational monitoring:

  SELECT recurring_batch_id, last_executed_by_name, last_executed_gl_date
  FROM   gl_iea_recur_batches_v
  ORDER  BY last_executed_gl_date DESC;

Because the view joins three base tables and resolves the executor username, it is preferable to direct queries against the base tables when only batch-level columns are required, but the view remains the most convenient single source for reporting on recurring intercompany batch configuration and its subsidiary-derived currency.