Results for “ra_interface_lines_u1”

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

Overview

AR.RA_INTERFACE_LINES_ALL is the AutoInvoice line-level interface table in Oracle E-Business Suite Receivables. It serves as the staging area into which external feeder systems, legacy applications, order management, and third-party billing engines load invoice and credit memo line data before the AutoInvoice concurrent program validates and transfers those records into the production transaction tables (RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL). Each row in this table represents a single invoice or credit memo line destined for import, together with its associated header-level attributes, tax attributes, referencing data, and descriptive flexfield context.

The object is documented in ETRM as VALID and owned by the AR schema, storing data in the APPS_TS_INTERFACE tablespace with 342 columns. In 12.1.1 and 12.2.2 the table is filtered through a multi-org secured view (RA_INTERFACE_LINES_ALL view) so that queries return only records belonging to the current operating unit; the ORG_ID column carries the operating unit identifier. From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification: the table is dominated by descriptive and contextual attributes hanging off a small number of business hubs and links (customer, legal entity, transaction type, contract, memo line), rather than acting as a pure hub or link itself.

Key Information Stored

The surrogate primary key is INTERFACE_LINE_ID, a NUMBER(15) column that uniquely identifies each staging record and is enforced by the unique index RA_INTERFACE_LINES_U1 (RA_INTERFACE_LINES_PK). This is the primary business-key candidate and the target of the user's search term ra_interface_lines_u1. Other documented columns of operational importance include:

• INTERFACE_LINE_CONTEXT and INTERFACE_LINE_ATTRIBUTE1–8 — descriptive flexfield context and attribute values for the line.
• BATCH_SOURCE_NAME — identifies the AutoInvoice batch source that governs grouping, validation rules, and accounting defaults.
• LINE_TYPE, DESCRIPTION, AMOUNT, CURRENCY_CODE — line classification, free-text description, monetary value, and transaction currency.
• CUST_TRX_TYPE_NAME / CUST_TRX_TYPE_ID and TERM_NAME / TERM_ID — the transaction type and payment terms applied to the line.
• ORIG_SYSTEM_BILL_CUSTOMER_ID, ORIG_SYSTEM_SHIP_CUSTOMER_ID, ORIG_SYSTEM_SOLD_CUSTOMER_ID and their _REF counterparts — bill-to, ship-to, and sold-to customer identifiers.
• SET_OF_BOOKS_ID, TRX_DATE, GL_DATE, DOCUMENT_NUMBER, TRX_NUMBER, LINE_NUMBER — ledger, accounting dates, and document/transaction numbering.
• INTERFACE_STATUS and REQUEST_ID — processing state and the AutoInvoice run that last touched the row.
• CUSTOMER_TRX_ID — populated on successful import to point at the resulting RA_CUSTOMER_TRX_ALL record.
• ORG_ID — operating unit, enabling the multi-org secured view.

Common Use Cases and Queries

Typical uses include monitoring AutoInvoice batch loads, diagnosing rejected lines, purging stale interface rows, and reconciling source systems against imported transactions. A frequent pattern is to filter outstanding errors for a given run:

• Inspect pending rows: SELECT INTERFACE_LINE_ID, BATCH_SOURCE_NAME, TRX_NUMBER, LINE_NUMBER, AMOUNT, INTERFACE_STATUS FROM RA_INTERFACE_LINES_ALL WHERE REQUEST_ID = :run_id AND INTERFACE_STATUS IN ('P','N');
• Join to the completed transaction: SELECT i.TRX_NUMBER, i.LINE_NUMBER, i.AMOUNT, c.TRX_NUMBER trx FROM RA_INTERFACE_LINES_ALL i JOIN RA_CUSTOMER_TRX_ALL c ON i.CUSTOMER_TRX_ID = c.CUSTOMER_TRX_ID;
• Group by batch source for volume reporting: SELECT BATCH_SOURCE_NAME, COUNT(*) FROM RA_INTERFACE_LINES_ALL GROUP BY BATCH_SOURCE_NAME;

Because the table is multi-org secured, queries must run under the correct operating unit or explicitly include ORG_ID.

Related Objects

The table participates in many documented relationships. The most significant are:

• RA_CUSTOMER_TRX_TYPES_ALL — via CUST_TRX_TYPE_ID, the transaction type applied to the line.
• GL_SETS_OF_BOOKS_11I — via SET_OF_BOOKS_ID, the ledger for the transaction.
• HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_SITE_USES_ALL — via the ORIG_SYSTEM_* and PAYING_* columns for customer, site, and contact references.
• RA_RECEIPT_METHODS and AR_MEMO_LINES_ALL_B — via RECEIPT_METHOD_ID and MEMO_LINE_ID.
• OKC_K_HEADERS_B / OKC_K_LINES_B — via CONTRACT_ID and CONTRACT_LINE_ID for contract-linked lines.
• ZX_LINES and ZX_LINES_DET_FACTORS — E-Business Tax tables that reference INTERFACE_LINE_ID and INTERFACE_TAX_LINE_ID back into this interface table during tax determination.