Results for “ra_interface_lines_all”

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

Overview

RA_INTERFACE_LINES_ALL is the AutoInvoice line-level interface table in the Oracle Receivables (AR) module. It stores the information for each invoice line imported using AutoInvoice, serving as the staging area where external source systems, legacy feeds, order management extracts, and third-party applications deposit transactional line data before the Receivables AutoInvoice concurrent program validates, derives, and transfers that data into the production transaction tables (RA_CUSTOMER_TRX_ALL, RA_CUSTOMER_TRX_LINES_ALL, and related distribution tables). Every row in the table carries a completeness and validation status through the INTERFACE_STATUS column, allowing the AutoInvoice process to identify which lines are eligible for transfer, which must be rejected, and which must be corrected and retried.

The table is owned by the AR schema and, as of ETRM 12.2.2 documentation, contains 342 columns. This makes it one of the broadest staging tables in the E-Business Suite, reflecting the enormous range of attributes required to fully describe an invoice line: customer, address, item, pricing, tax, revenue recognition, sales credit, and contract references.

From a dimensional modeling perspective, the heuristic Data Vault classification derived from the foreign key structure is satellite-leaning. This suggests the table behaves primarily as an attribute-bearing structure clustered around a transactional hub keyed on INTERFACE_LINE_ID, with numerous descriptive and contextual columns, rather than as a pure association (link) table. The heavy concentration of descriptive attributes, flexfield context columns, and GDF/attribute columns reinforces the satellite characterization.

Key Information Stored

The surrogate primary key is INTERFACE_LINE_ID, enforced by the RA_INTERFACE_LINES_PK constraint and further supported by the unique index RA_INTERFACE_LINES_U1 (also on INTERFACE_LINE_ID). Because the only documented unique index is on this surrogate column, there is no exposed natural business key at the table level; the "business key" for AutoInvoice import is effectively the combination of BATCH_SOURCE_NAME, ORIG_SYSTEM_BATCH_NAME, and the customer/original system reference columns, but these are captured as foreign references and descriptive data rather than as a documented unique constraint.

The most operationally significant columns include:

• INTERFACE_LINE_ID – surrogate primary key and the join point to ZX_LINES.INTERFACE_TAX_LINE_ID and ZX_LINES_DET_FACTORS.INTERFACE_LINE_ID.
• INTERFACE_LINE_CONTEXT / INTERFACE_LINE_ATTRIBUTE1–15 – descriptive flexfield context and attribute values used to carry source-specific extensions into the line.
• BATCH_SOURCE_NAME – identifies the AutoInvoice batch source that governs validation and derivation rules at import time.
• SET_OF_BOOKS_ID – foreign key to GL_SETS_OF_BOOKS_11I, tying the line to a specific ledger.
• LINE_TYPE – distinguishes LINE, TAX, FREIGHT, and similar line classes.
• CUSTOMER_TRX_ID / TRX_NUMBER / TRX_DATE / GL_DATE – transaction identity and date information used on transfer.
• CUST_TRX_TYPE_ID / TERM_ID / RECEIPT_METHOD_ID – foreign keys to the transaction setup tables that drive accounting and receivables behavior.
• ORIG_SYSTEM_BILL_CUSTOMER_ID, ORIG_SYSTEM_SHIP_CUSTOMER_ID, ORIG_SYSTEM_SOLD_CUSTOMER_ID – customer references resolved against HZ_CUST_ACCOUNTS.
• INVENTORY_ITEM_ID plus MTL_SYSTEM_ITEMS_SEG1–20 – item identity and its concatenated key flexfield segments.
• QUANTITY / UNIT_SELLING_PRICE / AMOUNT / ACCTD_AMOUNT – core pricing and amount measures.
• TAX_CODE / TAX_RATE / TAXABLE_AMOUNT / TAX_REGIME_CODE – tax-determining attributes consumed by E-Business Tax.
• INTERFACE_STATUS – line-level processing status controlling whether AutoInvoice transfers, rejects, or corrects the row.
• REQUEST_ID – links the interface row to the concurrent request that created or processed it.

Common Use Cases and Queries

RA_INTERFACE_LINES_ALL is queried most frequently for pre-transfer troubleshooting, post-import reconciliation, and purge management. A typical diagnostic query isolates lines that AutoInvoice has rejected:

• Rejection triage: SELECT interface_line_id, trx_number, line_number, interface_status, request_id FROM ra_interface_lines_all WHERE interface_status = 'REJECTED';
• Batch-level reconciliation: count and sum line amounts grouped by batch and interface status to confirm the source system's totals match what the interface holds before and after transfer.
• Request correlation: join REQUEST_ID to FND_CONCURRENT_REQUESTS to correlate imported lines with the specific AutoInvoice run that processed them.
• Tax cross-check: join INTERFACE_LINE_ID to ZX_LINES.INTERFACE_TAX_LINE_ID to inspect calculated tax lines for a given staged line.
• Purge / cleanup: identify rows whose corresponding CUSTOMER_TRX_ID is non-null (successfully transferred) versus null (still pending) to decide what may be safely purged.
• Source integrity audit: group by BATCH_SOURCE_NAME and ORIG_SYSTEM_BATCH_NAME to detect duplicate or orphaned feeds from upstream systems.

Reporting typically centers on exception handling: items that failed validation, missing customer or address references, tax mismatches, and lines held in correction status.

Related Objects

The most significant related objects, based on documented foreign key relationships, are:

• ZX_LINES – references RA_INTERFACE_LINES_ALL.INTERFACE_LINE_ID via INTERFACE_TAX_LINE_ID; carries calculated tax detail.
• ZX_LINES_DET_FACTORS – references INTERFACE_LINE_ID and stores tax-determining factor detail.
• HZ_CUST_ACCOUNTS – parent for ORIG_SYSTEM_BILL_CUSTOMER_ID, ORIG_SYSTEM_SHIP_CUSTOMER_ID, ORIG_SYSTEM_SOLD_CUSTOMER_ID, and PAYING_CUSTOMER_ID.
• HZ_CUST_ACCT_SITES_ALL / HZ_CUST_ACCOUNT_ROLES – resolve bill-to and ship-to addresses and contacts.
• RA_CUST_TRX_TYPES_ALL – referenced by CUST_TRX_TYPE_ID; drives invoice classification and accounting.
• GL_SETS_OF_BOOKS_11I – referenced by SET_OF_BOOKS_ID; establishes the ledger association.
• FND_APPLICATION – referenced by APPLICATION_ID; identifies the source application.
• OKC_K_HEADERS_B / OKC_K_LINES_B – parent contract header and line structures linked through CONTRACT_ID and CONTRACT_LINE_ID.
• AR_RECEIPT_METHODS – referenced by RECEIPT_METHOD_ID.
• FV_LEGAL_ENTITIES – referenced by LEGAL_ENTITY_ID; supplies tax registration context.

In practical terms, the AutoInvoice execution path moves data from RA_INTERFACE_LINES_ALL into RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL, so those production tables are the primary downstream consumers, while the HZ and ZX families provide the reference and tax detail surrounding each staged line.