Results for “ar_idep_actions_not_taken”

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

Overview

AR_IDEP_ACTIONS_NOT_TAKEN is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the Receivables (AR) product family and is designed to surface order-line commitments originating in Oracle Order Management that have not had a corresponding invoicing or interface action completed. In practice the view answers a reconciliation question: which confirmed order lines, tied to a commitment (customer transaction), still lack a completed action such as a fully processed invoice interface record.

Because the view joins order management, inventory, and receivables data, it functions as a cross-module diagnostic and reporting object. It is commonly consumed by period-end reconciliation reports, integration monitoring, and custom extracts where the business needs to identify line-level commitments that have not yet flowed through to receivables processing. The presence of COMMITMENT_ID as the leading column reflects that the object is keyed on the commitment concept, and this is the term most users search when locating it.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms:

• OE_ORDER_HEADERS_ALL — order header attributes such as order number and organization.
• OE_ORDER_LINES_ALL — order line details including quantity, price, commitment, and status flags.
• OE_TRANSACTION_TYPES_TL — translated transaction type names used for the TRX_TYPE column.
• OE_PAYMENTS — commitment applied amounts tied to the order line.
• RA_CUSTOMER_TRX_ALL — the customer transaction (invoice) joined on the order line commitment.
• RA_CUSTOMER_TRX_LINES_ALL and RA_INTERFACE_LINES_ALL — used in the subquery that checks whether an interface line has already been processed.
• MTL_SYSTEM_ITEMS — item description, outer-joined on inventory item and organization.
• AR_IDEP_UTILS — a package whose GET_COURSE_DESCRIPTION function supplies the DESCRIPTION column.

The order header and line tables are joined on HEADER_ID and ORG_ID; the transaction type join uses ORDER_TYPE_ID; and the commitment relationship is established by matching TRX.CUSTOMER_TRX_ID to OL.COMMITMENT_ID.

Key Columns

• COMMITMENT_ID — the customer transaction identifier associated with the order line.
• TRX_NUMBER — the receivables transaction number.
• SALES_ORDER — the order number from the order header.
• TRX_DATE — the pricing date of the order line.
• CHILD_TYPE — the translated transaction type name.
• QTY — ordered quantity.
• PRICE — unit selling price.
• LINE_AMT / EXT_AMT — ordered quantity multiplied by unit selling price.
• APPLIED_AMOUNT — commitment applied amount, defaulted to zero when null.
• DESCRIPTION — item or course description, resolved through AR_IDEP_UTILS or the item master.

The filter conditions exclude cancelled lines and closed lines, and only include lines whose invoice interface status is not complete, or which have an unprocessed interface line record.

Common Use Cases and Queries

A typical use is identifying open commitments that have not been invoiced:

• Reconciling order lines against receivable transactions at period close.
• Monitoring interface records that remain unprocessed.
• Auditing applied commitment amounts against expected line amounts.

SELECT commitment_id, trx_number, sales_order,
       trx_date, qty, price, line_amt, applied_amount
FROM   apps.ar_idep_actions_not_taken
WHERE  sales_order = :order_number;

Because the view already restricts results to lines where actions have not been taken, standard queries require little additional filtering. Reports often aggregate by SALES_ORDER or COMMITMENT_ID to quantify exposure. All access is read-only and governed by APPS schema privileges.