Results for “batch_source_id”

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

Overview

JAI_AR_TRX_COPY_HDR_T is a table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations product family. Its documented purpose is to record header-level information whenever an invoice (customer transaction) is copied from a source transaction. This supports localization requirements common in the Asia/Pacific region, where documents such as credit memos, debit memos, and recurring invoices are frequently generated by copying an existing transaction rather than being entered from scratch. The table preserves the linkage between the newly created transaction and the original transaction from which it was derived, providing an audit and traceability trail across the copy operation.

From a heuristic Data Vault modeling perspective, this object is classified as a link. The classification derives from its foreign key structure: the table does not function as a standalone hub of a single business concept, but rather associates multiple entities—the copied customer transaction, the source transaction it recurred from, and the batch source under which it was created. This makes JAI_AR_TRX_COPY_HDR_T a natural candidate for a link table in a Data Vault model, bridging those relationships while carrying descriptive context.

Key Information Stored

The documented physical schema for release 12.2.2 contains eleven columns. The most significant are described below.

• CUSTOMER_TRX_ID — Foreign key to RA_CUSTOMER_TRX_ALL. Identifies the transaction that was created as a result of the copy operation. This is the primary business linkage and the principal join key to the receivables transaction tables.
• TRX_NUMBER — The transaction number of the copied invoice, providing a human-readable identifier that parallels the value in RA_CUSTOMER_TRX_ALL.
• RECURRED_FROM_TRX_NUMBER — The transaction number of the source invoice from which the copy originated. This is the core traceability attribute for recurring or duplicated transactions.
• BATCH_SOURCE_ID — Foreign key to RA_BATCH_SOURCES_ALL. Identifies the batch source used when the copied transaction was created, which determines transaction type behavior, numbering, and defaulting rules.
• CREATED_FROM — Indicates the origin or mechanism by which the copy record was generated, useful for distinguishing automated versus manual copy paths.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified the record and when.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework to detect concurrent updates.

No surrogate primary key column is documented separately in the provided metadata; the table is defined by its foreign key relationships, and CUSTOMER_TRX_ID serves as the principal identifying attribute in practice.

Common Use Cases and Queries

Typical usage centers on tracing the lineage of copied transactions. A common reporting pattern joins this table to RA_CUSTOMER_TRX_ALL to retrieve details of both the source and the copied invoice.

• Identifying all transactions copied from a given source transaction number, for audit or dispute resolution.
• Reporting on transactions grouped by BATCH_SOURCE_ID to analyze copy activity by batch source.
• Reconciling recurring invoice generation against the originating documents.

A representative query pattern is:

SELECT c.trx_number, c.batch_source_id, t.trx_number AS source_trx
FROM ja.jai_ar_trx_copy_hdr_t c, ra_customer_trx_all t
WHERE c.customer_trx_id = t.customer_trx_id
AND c.recurred_from_trx_number = :source_number;

Related Objects

The most significant related objects are those joined through the documented foreign keys and the standard receivables transaction model.

• RA_CUSTOMER_TRX_ALL — joined on CUSTOMER_TRX_ID; holds the copied transaction header.
• RA_BATCH_SOURCES_ALL — joined on BATCH_SOURCE_ID; defines the batch source used.
• RA_CUSTOMER_TRX_LINES_ALL — line-level detail for the copied transaction.
• RA_CUSTOMER_TRX_LINES_GT and related transaction APIs — used during copy processing.
• AR_INVOICE_API_PUB — the public API often invoked when creating copied transactions.
• Other JA localization tables in the JA schema that share the CUSTOMER_TRX_ID reference.

These relationships make JAI_AR_TRX_COPY_HDR_T a supporting audit table within the Asia/Pacific receivables localization, tightly coupled to the core AR transaction schema.