Results for “interface_to_oe_flag”

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

Overview

CSD_REPAIR_ACTUAL_LINES_V is an APPS-owned reporting view in the Oracle E-Business Suite Depot Repair (CSD) module. It presents a consolidated, denormalized picture of actual repair lines, joining repair order headers, repair actuals, estimate details, inventory item master attributes, pricing, billing, contract, and service incident data into a single queryable structure. The view is commonly used in Depot Repair operational reporting, billing reconciliation, and cost/profit margin analysis, and it frequently serves as a source for custom concurrent programs, OBIEE/XML Publisher reports, and downstream integration extracts.

Materials planning and service billing staff query the view to reconcile estimated versus actual repair activity, determine chargeability, and review profit margins on repair lines. Because it exposes attributes from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL, it is also frequently used when investigating which repair estimates have been converted to sales orders — the context in which the search term interface_to_oe_flag typically arises. Note that the documented column list for this view does not include an INTERFACE_TO_OE_FLAG column; the order linkage is instead represented through ORDER_HEADER_ID and ORDER_LINE_ID, and the equivalent flag semantics are generally associated with the CS_ESTIMATE_DETAILS base record or the service/order interfaces rather than this view specifically.

Underlying Base Objects

The view is defined over several documented objects, including CSD_REPAIR_ACTUAL_LINES, CSD_REPAIR_ACTUALS, CSD_REPAIRS (the repair header), and CS_ESTIMATE_DETAILS (the estimate line detail). Supporting lookups and reference data come from CS_LOOKUPS, CS_TRANSACTION_TYPES_VL, CS_TXN_BILLING_TYPES, CS_BILLING_TYPE_CATEGORIES, FND_LOOKUPS, and MTL_UNITS_OF_MEASURE_VL.

Item and inventory attributes are sourced from MTL_SYSTEM_ITEMS_VL (concatenated segments, description, serial control code), while pricing and contract context is drawn from QP_LIST_HEADERS_TL, OKC_K_HEADERS_B, OE_ORDER_HEADERS_ALL, and OE_ORDER_LINES_ALL. Additional related objects documented in ETRM 12.2.2 include BOM_RESOURCES_V, CS_INCIDENTS_ALL_B, HZ_CUST_ACCOUNTS, HZ_LOCATIONS, HZ_PARTIES, HZ_PARTY_SITES, CS_STD, and FND_GLOBAL. The joins rely on the repair actual line as the driving record, linking back to the repair header, estimate detail, and associated transactional references.

Key Columns

• REPAIR_ACTUAL_LINE_ID / REPAIR_ACTUAL_ID / REPAIR_LINE_ID — primary and foreign keys linking the line to its actual and repair header.
• REPAIR_NUMBER, INCIDENT_ID, INCIDENT_NUMBER — repair and service incident identifiers.
• INVENTORY_ITEM_ID, PRODUCT, DESCRIPTION, SERIAL_NUMBER, SERIAL_NUMBER_CONTROL_CODE — item and serialization context.
• ESTIMATE_QUANTITY, REPAIR_QUANTITY — estimated versus actual repair quantities.
• ORDER_HEADER_ID, ORDER_LINE_ID — the sales order linkage corresponding to the estimate.
• SELLING_PRICE, AFTER_WARRANTY_COST (CHARGE), NO_CHARGE_FLAG, OVERRIDE_CHARGE_FLAG — pricing and charge determination.
• ITEM_COST, PROFIT_MARGIN, PROFIT_MARGIN_PERCENTAGE — derived margin calculations.
• BILLING_TYPE, BILLING_TYPE_MEANING, TXN_BILLING_TYPE_ID, TRANSACTION_TYPE — billing classification.
• CONTRACT_ID, CONTRACT_NUMBER, CURRENCY_CODE, PRICE_LIST, PURCHASE_ORDER_NUM — commercial context.

Common Use Cases and Queries

A representative query mirrors the view's intended reporting purpose, for example selecting repair_number, product, estimate_quantity, repair_quantity, actual_source_code, billing_type_meaning, and profit_margin_percentage from CSD_REPAIR_ACTUAL_LINES_V where repair_number equals a given value. Analysts often filter by actual_source_code or by order_header_id to isolate lines tied to specific repair sources or converted sales orders.

Because the view does not expose an INTERFACE_TO_OE_FLAG, users seeking order interface status should query the underlying CS_ESTIMATE_DETAILS or the relevant OE interface tables (such as OE_ORDER_HEADERS_ALL and its interface staging tables) directly, joining back to the estimate detail via ESTIMATE_DETAIL_ID. This view remains the most convenient consolidated source for repair line reporting, but order interface status must be resolved from the base service and order objects rather than from this view alone.