Search Results actual_accepted_date

Overview

APPS.SO_LINES_RMA_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as OE.SO_LINES_RMA_V. It exposes return material authorization (RMA) line information drawn from the Order Management (OE) and Receivables (AR/RA) table families, presenting a consolidated, report-ready projection of RMA activity at the line level. The object carries a status of VALID and, in the documented 12.1.1 / 12.2.2 environment, is defined over both views and synonyms spanning order entry, inventory, pricing, and receivables.

The view is primarily consumed by reporting, integration, and reconciliation programs that need to correlate returned quantities, receipt and acceptance dates, pricing attributes, and credit invoicing details without navigating the underlying normalized order and transaction tables directly. Because it surfaces both operational return data (ordered, received, accepted quantities and dates) and financial context (credit invoice line, tax setup, selling price), it serves as a single reference point for RMA analytics.

Underlying Base Objects

The documented dependency list for this view comprises the following objects:

• Views and synonyms: SO_HEADERS, SO_LINES, SO_LOOKUPS, SO_PRICE_LISTS, MTL_SYSTEM_ITEMS_VL, AR_LOOKUPS, AR_VAT_TAX, MTL_PARAMETERS, and RA_CUSTOMER_TRX / RA_CUSTOMER_TRX_LINES.
• PL/SQL components invoked during evaluation: OE_QUERY, QP_PRICE_LIST_PVT, FND_GLOBAL, and FND_PROFILE.

SO_LINES and SO_HEADERS supply the base RMA line and header attributes. MTL_SYSTEM_ITEMS_VL resolves descriptive item information, while MTL_PARAMETERS supplies inventory organization context. SO_LOOKUPS, AR_LOOKUPS, and AR_VAT_TAX translate coded values (line types, return reasons, tax codes, tax exemption reasons) into displayable forms. RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES provide the credit/invoice linkage exposed through CREDIT_INVOICE_LINE_ID and CREDIT_TO_INVOICE. FND_GLOBAL and FND_PROFILE resolve session and site-level security and functional context at query time, and QP_PRICE_LIST_PVT participates in the pricing projections.

Key Columns

Identification and hierarchical columns include LINE_ID, HEADER_ID, PARENT_LINE_ID, LINK_TO_LINE_ID, LINE_NUMBER, and CYCLE_ID. Return quantity and date tracking is handled by ORDERED_QUANTITY, CANCELLED_QUANTITY, RECEIVED_QUANTITY, ACCEPTED_QUANTITY, ACTUAL_RECEIPT_DATE, and ACTUAL_ACCEPTED_DATE — the last being the column most commonly sought for acceptance-date reporting.

Pricing and item context is provided by INVENTORY_ITEM_ID, ITEM_DESCRIPTION, ITEM_TYPE_CODE, ATO_FLAG, LIST_PRICE, SELLING_PRICE, PRICE_ADJUSTMENTS_TOTAL, and PRICING_METHOD_CODE. Return-handling attributes include RETURN_REASON_NAME, RETURN_REFERENCE_TYPE_CODE, INSPECTION_REQUIRED_FLAG, and TRANSACTION_REASON_CODE. Tax and credit columns include TAX_CODE, TAX_EXEMPT_FLAG, TAX_EXEMPT_REASON_DISPLAY, CREDIT_TO_INVOICE, and CREDIT_INVOICE_LINE_ID. The standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE) are also exposed.

Common Use Cases and Queries

Typical scenarios include RMA aging and acceptance-date analysis, return reason trending, reconciliation of accepted quantities against credit invoice lines, and integration feeds into external reporting marts.

• Return acceptance date lookup, the primary reason for querying this view:

SELECT line_id, header_id, inventory_item_id, ordered_quantity,
       received_quantity, accepted_quantity,
       actual_receipt_date, actual_accepted_date
  FROM apps.so_lines_rma_v
 WHERE actual_accepted_date >= :p_from_date
   AND actual_accepted_date <  :p_to_date;

• Return reason and credit invoice reconciliation:

SELECT return_reason_name, credit_to_invoice, credit_invoice_line_id,
       SUM(accepted_quantity) accepted_qty
  FROM apps.so_lines_rma_v
 WHERE credit_invoice_line_id IS NOT NULL
 GROUP BY return_reason_name, credit_to_invoice, credit_invoice_line_id;

Because the view incorporates profile and global session context via FND_PROFILE and FND_GLOBAL, results may vary with the effective operating unit and responsibility; queries should be run from the appropriate Order Management or Receivables context.