Results for “ar_interface_conts_all”

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

Overview

AR_INTERFACE_CONTS_ALL is the Receivables interface staging table that stores contingency information for transactions imported through the AutoInvoice process. In Oracle EBS 12.1.1 and 12.2.2, contingency terms typically accompany deferred payment arrangements, allowing a receivable to carry a specified expiration date, expiration window, or expiration event that governs when a contingent amount becomes due. The table is owned by the AR schema and holds 49 documented columns.

The table exists purely as an inbound staging structure. Data is populated from external feeder systems or from complementary AutoInvoice interface tables, validated and transformed by the AutoInvoice concurrent programs, then transferred into the permanent contingency tables in Receivables before being purged from the interface. Records in this table are keyed by ORG_ID and REQUEST_ID, so a single run of AutoInvoice can be identified and reconciled against a specific concurrent request.

From a heuristic Data Vault modeling perspective, the FK structure suggests a link classification: the table connects a transaction line context (INTERFACE_LINE_ID with INTERFACE_LINE_CONTEXT) to a contingency definition held in AR_DEFERRAL_REASONS through CONTINGENCY_ID, and to the completing user through COMPLETED_BY referencing FND_USER. This indicates a relationship or association entity rather than a standalone hub of descriptive attributes.

Key Information Stored

• INTERFACE_CONTINGENCY_ID — the surrogate primary key and the column backed by the unique index AR_INTERFACE_CONTS_U1.
• CONTINGENCY_CODE and CONTINGENCY_ID — the business identifier and the foreign key to AR_DEFERRAL_REASONS defining which contingency or deferral reason applies.
• INTERFACE_LINE_ID and INTERFACE_LINE_CONTEXT — link each contingency record to the specific transaction line being imported.
• EXPIRATION_DATE, EXPIRATION_DAYS, and EXPIRATION_EVENT_DATE — define when the contingency lapses, either by fixed date, relative day count, or event-driven date.
• INTERFACE_STATUS — tracks the processing state of each row during import (for example, pending, processed, or rejected).
• REQUEST_ID and ORG_ID — identify the AutoInvoice concurrent request and the operating unit that owns the record.
• COMPLETED_FLAG and COMPLETED_BY — indicate whether the contingency has been satisfied and which user completed it, with COMPLETED_BY referencing FND_USER.
• INTERFACE_LINE_ATTRIBUTE1 through 15 and ATTRIBUTE1 through 15 with ATTRIBUTE_CATEGORY — descriptive flexfield and extensibility columns for customer-specific data carried through the interface.
• Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) provide row-level lineage.

Common Use Cases and Queries

Typical usage centers on diagnosing AutoInvoice rejections and reconciling contingency data before or after import. The following query lists unprocessed interface rows for a specific concurrent request:

• SELECT interface_contingency_id, contingency_code, interface_line_id, interface_status, expiration_date FROM ar_interface_conts_all WHERE request_id = :req_id AND interface_status = 'PENDING' ORDER BY interface_line_id;
• Joining to the deferral reason definition for readability: SELECT c.interface_contingency_id, c.contingency_code, d.name FROM ar_interface_conts_all c, ar_deferral_reasons d WHERE c.contingency_id = d.deferral_reason_id AND c.request_id = :req_id;
• Identifying the user who completed a contingency: SELECT c.interface_contingency_id, c.completed_flag, u.user_name FROM ar_interface_conts_all c, fnd_user u WHERE c.completed_by = u.user_id;

Reporting scenarios include auditing contingencies awaiting expiry, verifying that all lines of a deferred transaction carried the correct expiration attributes, and validating that no staging rows remain after a successful AutoInvoice run. Because the table is a transient interface object, purge and cleanup scripts are frequently written against REQUEST_ID and CREATION_DATE.

Related Objects

• AR_DEFERRAL_REASONS — referenced through CONTINGENCY_ID; defines the contingency and deferral reason codes applied to the line.
• FND_USER — referenced through COMPLETED_BY; resolves the user who marked the contingency complete.
• RA_INTERFACE_LINES_ALL — the primary AutoInvoice line interface table; joined via INTERFACE_LINE_ID and INTERFACE_LINE_CONTEXT.
• RA_INTERFACE_DISTRIBUTIONS_ALL — distribution-level staging records created alongside the same transaction lines.
• RA_INTERFACE_SALESCREDITS_ALL — sales credit staging rows for the same imported lines.
• AR_AUTOINVOICE / the AutoInvoice execution programs — consume and validate records from these interface tables, moving valid data into the permanent Receivables contingency structures.
• RA_BATCH_SOURCES_ALL and RA_CUSTOMER_TRX_ALL — the batch source and final transaction tables that receive processed contingency information.

Collectively these objects form the AutoInvoice import pipeline in which AR_INTERFACE_CONTS_ALL carries contingency detail for each transaction line.