Results for “line_amt”

50+ results




Overview
Explore in AI Chat

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

Overview

AR_IDEP_ACTIONS_TAKEN is a reporting view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). It presents a consolidated, line-level picture of invoices and the credit memos raised against them, with particular emphasis on commitment-based billing. The name reflects its principal design intent: to expose the billing "actions taken" for a commitment — that is, the invoice lines generated against an initial transaction and any subsequent credit memo activity referencing that transaction. The view carries a status of VALID in the ETRM 12.2.2 metadata and is available in the 12.1.1 and 12.2.2 code lines.

Because the view is defined with a UNION between an invoice branch and a credit memo branch, it is typically consumed by downstream reporting, extracts, and integration interfaces that must reconcile what was billed against what was later credited. It is not an operational entry point; it is a read-only projection over standard Receivables transaction tables.

Underlying Base Objects

The documented referenced base objects are:

  • RA_CUSTOMER_TRX_ALL (synonym) — the transaction header table, supplying transaction identifiers, transaction number, transaction date, organisation, and type.
  • RA_CUSTOMER_TRX_LINES_ALL (synonym) — the transaction line table, joined twice: once as LINE for the revenue lines and once as TAXLINE for the linked tax lines.
  • RA_CUST_TRX_TYPES_ALL (synonym) — the transaction type definition table, filtered to TYPE = 'INV' in the invoice branch.
  • AR_IDEP_UTILS (package) — a Receivables utility package whose GET_COURSE_DESCRIPTION function resolves a human-readable course description from the interface line attribute, falling back to the line description.

The joins enforce complete transactions (COMPLETE_FLAG = 'Y'), consistent organisation identifiers across header, type, and line, and an outer join to tax lines via LINK_TO_CUST_TRX_LINE_ID. The credit memo branch keys off PREVIOUS_CUSTOMER_TRX_ID to associate the memo with its originating invoice.

Key Columns

  • COMMITMENT_ID — derived from TRX.INITIAL_CUSTOMER_TRX_ID in the invoice branch, identifying the originating commitment transaction.
  • TRX_ID / TRX_NUMBER — the invoice transaction identifier and its user-facing number.
  • CM_INV — the transaction type classification (INV for invoices), with CHILD_TYPE carrying the type name.
  • SALES_ORDER — the sales order reference captured on the line.
  • TRX_DATE — the transaction date used for period and aging analysis.
  • DESCRIPTION, QTY, PRICE — line description, quantity (ordered or invoiced), and unit price.
  • LINE_AMT, EXT_AMT, TAX_FREIGHT_AMT, TOTAL_LINE_AMT — extended line amount, tax/freight amount, and the computed total.
  • LINE_NUMBER — the line sequence on the transaction.

Common Use Cases and Queries

Typical scenarios include commitment-to-invoice reconciliation, credit memo tracking against original invoices, and revenue or billing extracts for downstream analytics. A representative query follows.

  • Locate all billing actions for a specific initial transaction:
SELECT commitment_id, trx_number, cm_inv, trx_date,
       description, qty, total_line_amt
  FROM apps.ar_idep_actions_taken
 WHERE commitment_id = :initial_customer_trx_id
 ORDER BY trx_date, line_number;
  • Summarise amounts billed and credited per commitment:
SELECT commitment_id, cm_inv, SUM(total_line_amt) amt
  FROM apps.ar_idep_actions_taken
 GROUP BY commitment_id, cm_inv;

Because the view's first branch keys on INITIAL_CUSTOMER_TRX_ID, searches phrased around initial_customer_trx_id map directly to the COMMITMENT_ID column, making the view the natural target for queries that begin from an original transaction identifier.