Search Results ar_line_conts_u1

Overview

AR.AR_LINE_CONTS_ALL is a transactional table in the Oracle E-Business Suite Receivables (AR) module that stores, for each invoice line, the contingencies that impact revenue recognition. A contingency represents a condition or event that must be satisfied before revenue associated with a line can be recognized; until the contingency is resolved, the affected amount is deferred. Each row therefore links an invoice line to a contingency code and carries the expiration logic, completion status, and audit context required by Oracle's revenue recognition engine.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10 and is owned by the AR schema. Its FND Design Data reference is AR.AR_LINE_CONTS_ALL, it holds 17 documented columns in the 12.2.2 physical schema, and it currently carries a VALID status. From a heuristic Data Vault perspective, the mined FK structure classifies this object as standalone; a modeling exercise might instead treat it as a link table joining invoice lines to contingency or deferral reason definitions, with the codes, dates, and flags held as descriptive satellite attributes. That classification is a suggestion only, not a physical property of the object.

Key Information Stored

The primary key is AR_LINE_CONTS_PK, composed of CUSTOMER_TRX_LINE_ID and CONTINGENCY_CODE. The unique index AR_LINE_CONTS_U1 covers the same two columns (CUSTOMER_TRX_LINE_ID, CONTINGENCY_CODE) and is the principal business-key candidate, guaranteeing that a given contingency code appears at most once per invoice line.

• CUSTOMER_TRX_LINE_ID — invoice line identifier; the leading component of the primary key and unique index, joining to the transaction line.
• CONTINGENCY_CODE — lookup code for lookup type AR_REVENUE_CONTINGENCIES; the second component of the primary key and unique index.
• CONTINGENCY_ID — contingency identifier; the documented foreign key target is AR.AR_DEFERRAL_REASONS.
• EXPIRATION_DATE and EXPIRATION_DAYS — the date on which the contingency expires and the day-based equivalent used by the recognition engine.
• EXPIRATION_EVENT_DATE — the date of the event that drives expiration.
• REASON_REMOVAL_DATE — the date the contingency reason was removed.
• COMPLETED_FLAG and COMPLETED_BY — indication of completion and the user who completed the contingency.
• DEFAULTED_IN_AR_FLAG — indicates contingencies defaulted in Receivables.
• ORG_ID — organization identifier supporting multi-org access control.
• Standard WHO columns — REQUEST_ID, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record the concurrent request and user audit trail for each row.

Common Use Cases and Queries

The most frequent scenario is identifying which invoice lines carry unresolved revenue contingencies, typically to reconcile deferred revenue balances or to support period-end revenue recognition reporting. The following pattern joins the table to its unique key columns and filters on completion status:

• SELECT customer_trx_line_id, contingency_code, expiration_date, completed_flag FROM ar.ar_line_conts_all WHERE org_id = :p_org_id AND NVL(completed_flag, 'N') = 'N';
• Join to AR_DEFERRAL_REASONS on CONTINGENCY_ID to obtain the contingency description for reporting.
• Group by contingency_code to measure the volume and monetary impact of each contingency across a period.
• Filter on EXPIRATION_DATE or EXPIRATION_EVENT_DATE to list contingencies approaching expiration for follow-up.
• Trace DEFAULTED_IN_AR_FLAG to separate system-defaulted contingencies from those entered manually.
• Audit queries using REQUEST_ID, CREATED_BY, and LAST_UPDATED_BY to attribute changes to a concurrent program or user.

Related Objects

The following objects are the most significant counterparts, based on the documented foreign key and key structure:

• AR.AR_DEFERRAL_REASONS — referenced by AR_LINE_CONTS_ALL.CONTINGENCY_ID; supplies the deferral reason definition behind a contingency.
• RA_CUSTOMER_TRX_LINES_ALL — the invoice line master joined on CUSTOMER_TRX_LINE_ID, the primary key's leading column.
• RA_CUSTOMER_TRX_ALL — the transaction header reached through the line for invoice-level revenue reporting.
• AR_REVENUE_CONTINGENCIES lookup (FND_LOOKUP_VALUES) — the source of valid CONTINGENCY_CODE values.
• FND_CONCURRENT_REQUESTS — target of REQUEST_ID for concurrent program traceability.
• FND_USERS — target of CREATED_BY, LAST_UPDATED_BY, and COMPLETED_BY.
• FND_LOGINS — target of LAST_UPDATE_LOGIN for operating system login attribution.
• Revenue recognition and deferred revenue processes in the AR module, which read and update this table during contingency processing.