Search Results batch_source_name




Overview
Explore in AI Chat

Overview

The APPS.AR_TRX_BATCH_SOURCE_S_V view is a Receivables (AR) reporting and integration object defined in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "transaction batch source shared extract," which identifies its role as a denormalized read interface that joins transaction batch source configuration data from the Receivables module to the Subledger Accounting (XLA) extract lines used by the accounting and transfer processes.

The view is owned by the APPS schema and is reported as VALID in the ETRM metadata. It is not a base table; it exists to expose batch source attributes alongside the XLA event and line identifiers that are needed to attribute accounting events back to the batch source that originated them. As a "shared extract" object, it is intended for consumption by downstream extraction and reporting routines rather than for transactional data entry.

Underlying Base Objects

The view is defined over two base objects, documented in the ETRM metadata as synonyms: AR_XLA_LINES_EXTRACT and RA_BATCH_SOURCES_ALL.

  • RA_BATCH_SOURCES_ALL — the Receivables batch source definition table, providing the batch source name, description, and descriptive flexfield (global attributes) values.
  • AR_XLA_LINES_EXTRACT — the Subledger Accounting extract lines table, providing the accounting event identifier, extract line number, ledger identifier, event class code, level flag, and from/to flag needed to correlate each line to its source transaction.

The join is performed on BATCH_SOURCE_ID and ORG_ID, ensuring the batch source row is resolved within the correct operating unit context. The view text includes the optimizer hint /*+ INDEX(L AR_XLA_LINES_EXTRACT_N1) */, directing the cost-based optimizer to drive the AR_XLA_LINES_EXTRACT access through its BATCH_SOURCE_ID index, which confirms that batch source is the primary filter path.

Key Columns

  • BATCH_SOURCE_ID — primary identifier of the transaction batch source; the join key to RA_BATCH_SOURCES_ALL.
  • BATCH_SOURCE_NAME — the batch source name. This is the column most frequently referenced when users search for "batch_source_name," since it is the human-readable label for the source such as Manual, Order Entry, or Recurring Invoice.
  • BATCH_SOURCE_DESCRIPTION — the descriptive text associated with the batch source.
  • BATCH_SOURCE_GLOBAL_ATTR_CAT / BATCH_SOURCE_GLOBAL_ATTR1..6 — the global descriptive flexfield context and segment values carried from the batch source definition, allowing attribute-based reporting and extraction.
  • EVENT_ID — the Subledger Accounting event identifier from the extract lines, linking the batch source to the accounting event.
  • LINE_NUMBER — the extract line number within the event.
  • LEDGER_ID — the ledger to which the accounting event belongs.

Notably, the WHERE clause restricts rows by event class and level. INVOICE, DEBIT_MEMO, DEPOSIT, GUARANTEE, CHARGEBACK, ADJUSTMENT, and BILL rows are included only when LEVEL_FLAG = 'H'; CREDIT_MEMO and RECEIPT rows are included only when LEVEL_FLAG = 'L' and FROM_TO_FLAG = 'T'. This makes the view selective rather than a full extract of all events.

Common Use Cases and Queries

The view supports reconciliation and reporting that must attribute XLA extract lines to their originating batch source, for example confirming which batch source generated a given accounting event, or listing all events for a specific source such as Manual or Order Entry.

  • Retrieving events by batch source name:
    SELECT batch_source_name, event_id, line_number, ledger_id FROM apps.ar_trx_batch_source_s_v WHERE batch_source_name = 'Manual';
  • Listing distinct batch sources present in the extract:
    SELECT DISTINCT batch_source_id, batch_source_name FROM apps.ar_trx_batch_source_s_v ORDER BY batch_source_name;
  • Joining to event or journal data using EVENT_ID to trace extract lines back to their batch source attributes, or reporting by the global attribute segments for custom categorization.

Because the view is metadata-designated for shared extract use, it should be treated as a read-only interface. Oracle Proprietary, Confidential Information and Legal Notices apply to its definition and use.