Results for “jai_rcv_tp_batches”

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

Overview

JA.JAI_RCV_TP_BATCHES is a table within the Oracle E-Business Suite Asia/Pacific Localizations product (JA). It holds details of receipts processed against a run of a third party invoices batch. In the Oracle EBS 12.1.1 and 12.2.2 data models, this table acts as the batch header container that groups the individual third party invoice receipt records created during a given concurrent program run, binding each batch to a specific shipment header and to the concurrent request that generated it.

Under the heuristic Data Vault classification mined from its foreign key structure, this table is described as satellite-leaning. This classification suggests a modeling perspective in which JAI_RCV_TP_BATCHES functions primarily as a descriptive satellite attached to a batch or shipment business key, carrying processing status and audit metadata rather than serving as a pure hub or link. The single documented unique index, JAI_RCV_TP_BATCHES_PK on (BATCH_ID, SHIPMENT_HEADER_ID), reinforces the composite-key nature of the entity and is the appropriate basis for treating those two columns as the business key candidate.

Key Information Stored

The table contains 15 documented columns. The most significant are:

• BATCH_ID and SHIPMENT_HEADER_ID — the composite columns forming the primary key (JAI_RCV_TP_BATCHES_PK) and the business-key candidate for the entity.
• PROCESS_FLAG — indicates the processing state of the batch, typically used to signal completion, error, or pending status.
• PROCESS_MESSAGE — stores the outcome or error text produced when receipts are processed against the batch.
• DUMMY_FLAG — a control flag used by the localization logic to distinguish placeholder entries.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• REQUEST_ID — the concurrent request that created or processed the batch.
• PROGRAM_ID and PROGRAM_APPLICATION_ID — identify the concurrent program and its owning application.
• PROGRAM_LOGIN_ID — the login session under which the program executed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking record provenance and change history.

Common Use Cases and Queries

Typical reporting scenarios include reconciling third party invoice receipt batches to their concurrent requests, diagnosing failed or incomplete processing runs, and tracing which shipment header received third party invoices. A representative join to the concurrent request metadata is:

• SELECT b.BATCH_ID, b.SHIPMENT_HEADER_ID, b.PROCESS_FLAG, b.PROCESS_MESSAGE, r.REQUEST_ID, r.STATUS_CODE FROM JA.JAI_RCV_TP_BATCHES b JOIN FND_CONCURRENT_REQUESTS r ON b.REQUEST_ID = r.REQUEST_ID WHERE b.PROCESS_FLAG = 'E';
• Batch-to-invoice drill-down: join to JAI_RCV_TP_INVOICES on BATCH_ID and SHIPMENT_HEADER_ID.
• Audit queries leveraging CREATION_DATE, LAST_UPDATE_DATE, and PROGRAM_LOGIN_ID to identify the operator and session responsible for a batch.

Related Objects

• JA.JAI_RCV_TP_INVOICES — child table referencing JAI_RCV_TP_BATCHES via (BATCH_ID, SHIPMENT_HEADER_ID); holds the detailed invoice lines processed in each batch.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID; identifies the concurrent request execution.
• FND_CONCURRENT_PROGRAMS — joined on PROGRAM_APPLICATION_ID and PROGRAM_ID; identifies the executing program.
• FND_LOGINS — joined on PROGRAM_LOGIN_ID; resolves the login session.

These relationships establish JAI_RCV_TP_BATCHES as the pivotal batch-level entity linking third party invoice receipt processing to the Oracle concurrent manager framework.