Results for “component_number”

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

Overview

The APPS.OE_RETROBILLED_INFO_V view is a reporting and integration object in the Oracle Order Management (ONT) module. Its documented purpose is to show retrobilled activities, that is, the relationship between an original sales order line and the subsequent retrobill order line created to bill for that activity. Retrobilling in Oracle EBS typically arises in service, warranty, and subscription scenarios where charges are captured after the original order event, and the resulting charges are posted against a dedicated retrobill order type.

The view is defined in the APPS schema with a status of VALID and is exposed for query in both EBS 12.1.1 and 12.2.2. It carries no DML semantics; it is a read-only projection intended for operational reporting, reconciliation of billed versus unbilled activity, and downstream integration extracts. Because it joins the original and retrobill order lines within a single SELECT, it removes the need for consumers to reconstruct the linkage logic themselves.

Underlying Base Objects

ETRM 12.2.2 documents the following base objects referenced through synonyms: OE_ORDER_LINES_ALL, OE_ORDER_HEADERS, OE_TRANSACTION_TYPES_TL, and FND_LANGUAGES.

• OE_ORDER_LINES_ALL is aliased twice, once as ORIG_LIN (the original order line) and once as RETRO_LIN (the retrobill line). This self-join is the core of the view.
• OE_ORDER_HEADERS supplies the retrobill order number and the transaction type link for the retrobill.
• OE_TRANSACTION_TYPES_TL provides the translated transaction type name, joined on TRANSACTION_TYPE_ID.
• FND_LANGUAGES is used in a scalar subquery to restrict the transaction type name to the installed base language (INSTALLED_FLAG = 'B').

The join predicate constrains RETRO_LIN.ORDER_SOURCE_ID = 27, which identifies lines sourced from retrobilling, and matches the original line through ORIG_SYS_DOCUMENT_REF and ORIG_SYS_LINE_REF against the character representation of the original HEADER_ID and LINE_ID.

Key Columns

• LINE_NUMBER, HEADER_ID, LINE_ID — the original order line identifiers.
• ORIG_COMPONENT_NUMBER, ORIG_SHIPMENT_NUMBER, ORIG_OPTION_NUMBER, ORIG_SERVICE_NUMBER — the original line's component, shipment, option, and service references.
• ORDERED_ITEM — the item on the original line.
• COMPONENT_NUMBER, SHIPMENT_NUMBER, OPTION_NUMBER, SERVICE_NUMBER — the corresponding references on the retrobill line; COMPONENT_NUMBER is the most frequently queried of these in the user search context.
• PRICING_DATE, UNIT_SELLING_PRICE, ORDER_QUANTITY_UOM — pricing and unit of measure details for the retrobill.
• QTY and AMOUNT — derived values; both are negated with DECODE when LINE_CATEGORY_CODE = 'RETURN', giving signed quantities and extended amounts.
• RETROBILL_ORDER_NUMBER, RETROBILL_LINE_NUMBER, RETROBILL_HEADER_ID, RETROBILL_LINE_ID — identifiers of the retrobill order and line.
• INVOICED_QUANTITY, ITEM_IDENTIFIER_TYPE, NAME — invoiced quantity, identifier type, and the transaction type name from OE_TRANSACTION_TYPES_TL.

Common Use Cases and Queries

Typical usage includes reconciling retrobilled revenue against original shipments, tracing a component-level retrobill back to its source line, and feeding downstream invoicing or analytics extracts.

To find all retrobilled activities for a given original order:

SELECT LINE_NUMBER, ORDERED_ITEM, COMPONENT_NUMBER, QTY, AMOUNT, RETROBILL_ORDER_NUMBER FROM APPS.OE_RETROBILLED_INFO_V WHERE HEADER_ID = :p_header_id;

To trace a specific component across original and retrobill lines:

SELECT ORIG_COMPONENT_NUMBER, COMPONENT_NUMBER, RETROBILL_ORDER_NUMBER, RETROBILL_LINE_NUMBER FROM APPS.OE_RETROBILLED_INFO_V WHERE COMPONENT_NUMBER = :p_component_number;

Because the view already resolves the order-source and reference predicates, queries should filter on the exposed columns (order number, item, component, pricing date) rather than re-implementing the join against OE_ORDER_LINES_ALL.