Search Results ordered_quantity2

Overview

The view RCV_ENTER_RECEIPTS_RMA_V is an APPS-owned database view within the Oracle E-Business Suite Purchasing (PO) module. Its ETRM description, "10SC ONLY - Retrofitted," identifies it as a customer-specific or localized extension object rather than a standard Oracle-delivered artifact in the core receiving schema. Objects carrying this designation were typically introduced to satisfy a specific implementation requirement (in this case associated with a 10SC configuration) and subsequently retrofitted into the EBS 12.1.1 and 12.2.2 environments. The view is currently reported with a VALID status in the data dictionary.

Functionally, the view presents a flattened, receipts-entry-oriented result set for Return Merchandise Authorization (RMA) transactions. It surfaces the attributes needed to display and process receipt lines in the Receiving Transactions and Enter Receipts forms, including order identifiers, item details, quantity and UOM information, shipment routing, and descriptive flexfield columns. Because it is a view rather than a base table, it provides no persistent storage; it derives its rows at runtime from its underlying objects and serves as a reporting and form-integration layer.

Underlying Base Objects

According to the documented view metadata for 12.2.2, RCV_ENTER_RECEIPTS_RMA_V is defined over two referenced objects:

• OE_PO_ENTER_RECEIPTS_V (VIEW) — the primary source of receipt and purchase order line data.
• OE_SYS_PARAMETERS (PACKAGE) — referenced for system parameter resolution, typically supplying operating unit or profile-driven defaults used during receipt entry.

The view text itself is a single SELECT that projects a fixed column list without joins or filters visible in the excerpt, indicating that the join logic and RMA-specific filtering are encapsulated within OE_PO_ENTER_RECEIPTS_V. This layered design means the object inherits its row population rules from the Order Management enter-receipts view, then passes the result set through unchanged to consumers. The single TO_CHAR(NULL) expression in the select list acts as a placeholder column, a common pattern where a form block expects a bind or derived column that is not populated at this layer.

Key Columns

The projection covers receipt header, line, shipment, item, and supplier attributes. Significant columns include:

• Receipt identifiers: RCV_SHIPMENT_HEADER_ID, RCV_SHIPMENT_NUMBER, RCV_SHIPMENT_LINE_ID, RCV_LINE_NUMBER, and LINE_CHKBOX, which drive form selection.
• Order references: PO_HEADER_ID, PO_NUMBER, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_RELEASE_ID, and the requisition columns REQ_HEADER_ID, REQ_LINE_ID, and REQ_DISTRIBUTION_ID.
• Source and control codes: SOURCE_TYPE_CODE, RECEIPT_SOURCE_CODE, ORDER_TYPE_CODE, DESTINATION_TYPE_CODE, INSPECTION_REQUIRED_FLAG, and RECEIPT_REQUIRED_FLAG.
• Item and quantity data: ITEM_ID, ITEM_NUMBER, ITEM_REVISION, PRIMARY_UOM, ORDERED_QTY, ORDERED_UOM, plus lot, serial, and locator control flags.
• Financial and logistics columns: UNIT_PRICE, CURRENCY_CODE, the currency conversion fields, NEED_BY_DATE, EXPECTED_RECEIPT_DATE, and shipment routing attributes such as ROUTING_NAME and WAYBILL_AIRBILL_NUM.
• Flexfields: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

The view is most frequently queried to reconcile RMA receipt lines against purchase orders, to populate custom receipt-entry forms, and to feed downstream integrations or extracts. A representative query retrieves receipt lines for a given PO number:

• SELECT rcv_shipment_number, po_number, po_line_number, item_number, ordered_qty, order_ordered_uom, unit_price FROM apps.rcv_enter_receipts_rma_v WHERE po_number = :p_po_number;
• Filtering by item to inspect all pending receipts: WHERE item_number = :p_item AND receipt_required_flag = 'Y';
• Joining back to RCV_SHIPMENT_HEADERS on RCV_SHIPMENT_HEADER_ID to obtain receipt dates and statuses not exposed by the view.

Because the object is marked 10SC-only and retrofitted, it should be treated as non-standard. Use it with caution in custom code, validate its behavior against the current release, and avoid assuming parity with Oracle-delivered receiving views such as the standard enter-receipts views in the RCV schema.