Search Results ar_line_conts_all




Overview
Explore in AI Chat

Overview

AR_LINE_CONTS_ALL is an Oracle Receivables (AR) transactional table that stores contingency information associated with individual billing lines. In Oracle EBS 12.1.1 and 12.2.2, a contingency represents a condition or deferral reason attached to a receivable line — for example, a disputed amount, a retention, or an amount whose recognition is deferred until a future event occurs. Each row links a specific transaction line (identified by CUSTOMER_TRX_LINE_ID) to a contingency definition (identified by CONTINGENCY_ID and CONTINGENCY_CODE), and carries the dates, flags, and audit columns that govern when the contingency expires or is removed. In the ETRM 12.2.2 physical schema the table is owned by the AR schema and exposes 17 documented columns. The mined relationship analysis classifies AR_LINE_CONTS_ALL as a standalone object from a Data Vault modeling perspective; this is a heuristic suggestion only. Because its primary key combines a foreign reference to a transaction line with a contingency code, it functions in practice as an association (link-style) record between receivable lines and deferral reasons, with a small satellite of descriptive attributes (expiration, completion, dates).

Key Information Stored

The primary key is AR_LINE_CONTS_PK, defined on the composite of (CUSTOMER_TRX_LINE_ID, CONTINGENCY_CODE). A unique index, AR_LINE_CONTS_U1, exists on the same two columns, making this pair the natural business-key candidate that guarantees a given contingency code appears only once per transaction line. Note that CUSTOMER_TRX_LINE_ID carries a dual role: it identifies the owning line and simultaneously anchors the primary key. The most significant documented columns are:

Common Use Cases and Queries

Typical usage centers on receivables reporting and reconciliation of deferred or contingent amounts. A common query joins the table to transaction lines to list open contingencies for a transaction:

  • Listing contingencies per line: SELECT customer_trx_line_id, contingency_code, expiration_date, completed_flag FROM ar_line_conts_all WHERE customer_trx_line_id = :line_id;
  • Finding expired-but-uncompleted contingencies for follow-up: filter on EXPIRATION_DATE < SYSDATE and COMPLETED_FLAG = 'N'.
  • Operating-unit scoped reporting: always constrain on ORG_ID under MOAC to return only the active operating unit's rows.
  • Resolving the deferral reason: join CONTINGENCY_ID = AR_DEFERRAL_REASONS.CONTINGENCY_ID for descriptive text.
  • Audit trails: use REQUEST_ID and the who-columns to trace which concurrent program touched a row.

Related Objects

The most significant objects related to AR_LINE_CONTS_ALL, per the documented FK/PK metadata, are:

  • AR_DEFERRAL_REASONS — referenced through CONTINGENCY_ID; holds the deferral reason definitions.
  • RA_CUSTOMER_TRX_LINES_ALL — the transaction line identified by CUSTOMER_TRX_LINE_ID, the parent of each contingency.
  • RA_CUSTOMER_TRX_ALL — the transaction header reached via the line, used for customer and transaction context.
  • RA_CUSTOMER_TRX_LINES — the reporting view over transaction lines used with this table.
  • AR transaction and AutoInvoice APIs that populate contingencies when lines are imported or adjusted.