Search Results interface_line_attribute9

Overview

ECE_CDMO_LINE_V is a private APPS-owned database view within the Oracle E-Business Suite e-Commerce Gateway (EC) module. It is the Credit/Debit Memo Line View, registered under the AR product and the AR_CREDIT BUSINESS_ENTITY category, and is used to extract line-level information for the outbound Credit/Debit Memo outbound transaction, documented as 812/CREADV/DEBADV. In the ETRM 12.2.2 lifecycle it carries an active status, and it is preserved in 12.1.1 as well. Its purpose is to flatten Receivables credit and debit memo lines into a transaction-ready structure that the e-Commerce Gateway interface programs can consume when building outbound 812 EDI documents.

Underlying Base Objects

The view's documented base objects include RA_CUSTOMER_TRX and RA_CUSTOMER_TRX_LINES, which supply the transaction header and line context (CUSTOMER_TRX_ID, CUSTOMER_TRX_LINE_ID, LINE_NUMBER, quantities, prices, and amounts). WSH_NEW_DELIVERIES, WSH_DELIVERY_LEGS, and WSH_DOCUMENT_INSTANCES are referenced to relate shipping/delivery context. OE_ORDER_HEADERS, OE_ORDER_LINES, and OE_PRICE_ADJUSTMENTS provide sales order linkage, while MTL_CUSTOMER_ITEMS and MTL_PARAMETERS supply item and inventory context. HR_ALL_ORGANIZATION_UNITS, HR_ALL_ORGANIZATION_UNITS_TL, and HR_LOCATIONS_ALL provide organization and location attributes. The view text excerpt confirms direct joins on RCT (RA_CUSTOMER_TRX), RCTL1 and RCTL2 (aliases of RA_CUSTOMER_TRX_LINES), producing the line-plus-credited-line relationship. FND_PROFILE is referenced for profile-based value resolution.

Key Columns

• TRANSACTION_ID and TRANSACTION_LINE_ID — surrogate keys from the Receivables transaction header and line.
• LINE_NUMBER — the line sequence for the memo.
• SALES_ORDER_NUMBER, SALES_ORDER_REVISION_NUMBER, SALES_ORDER_LINE_NUMBER, SALES_ORDER_DATE — sales order references inherited from the transaction line.
• ITEM_ID, ITEM_DESCRIPTION, UOM_CODE — item identification fields.
• ORDERED_QUANTITY — the NVL of QUANTITY_ORDERED and QUANTITY_INVOICED; QUANTITY — the NVL of QUANTITY_INVOICED and QUANTITY_CREDITED. This is the shipping/invoiced quantity dimension users search for under "shipping_quantity".
• UNIT_STANDARD_PRICE, UNIT_SELLING_PRICE, LINE_AMOUNT — pricing and extended amount, with NVL(LINE_AMOUNT, 0).
• CREDIT_MEMO_REASON — the reason code for the credit or debit.
• CREDITED_LINE_NUMBER — the referenced line for credit memo association.
• INTERFACE_LINE_CATEGORY and INTERFACE_LINE_ATTRIBUTE1 through ATTRIBUTE11 — flexible interface descriptors carried into the outbound document.
• SHIP_ORDER_STATUS_INT and CUSTOMER_ITEM_NUMBER/CUSTOMER_ITEM_DESC are returned as NULL placeholders in the documented view text.

Common Use Cases and Queries

This view is primarily queried when troubleshooting or validating outbound 812 EDI credit/debit memo content, reconciling line amounts back to RA_CUSTOMER_TRX_LINES, and reviewing affected lines by credit reason code. A representative query:

SELECT transaction_id, transaction_line_id, line_number, item_id, ordered_quantity, quantity, unit_selling_price, line_amount, credit_memo_reason FROM apps.ece_cdmo_line_v WHERE transaction_id = :p_transaction_id ORDER BY line_number;

To review credits tied to a specific reason code: SELECT line_number, item_description, quantity, line_amount FROM apps.ece_cdmo_line_v WHERE credit_memo_reason = :p_reason AND transaction_id = :p_trx_id;

Because the view sources quantities from RA_CUSTOMER_TRX_LINES, the QUANTITY column reflects the invoiced or credited quantity rather than a warehouse shipment quantity in the strict shipping sense; where users expect a shipping_quantity value, they should map it to QUANTITY or ORDERED_QUANTITY as returned by the view, and cross-reference WSH delivery objects for physical shipment confirmation.