Search Results justification_notes

Overview

CSD_REPAIR_ESTIMATE_LINES_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 view owned by the APPS schema within the CSD – Depot Repair product. It fetches all estimate lines associated with repair orders, providing a consolidated, denormalized presentation of estimate detail data joined to repair order header information, item master attributes, pricing, billing, and contract data. Because the view consolidates fields that would otherwise require multi-table joins across CSD, CS, OKC, QP, and MTL schemas, it is the standard access point for Depot Repair estimate reporting, Extensions, and integration extracts. The STATUS column in the documented metadata is VALID, confirming the object is compiled and available in the reference environment.

Underlying Base Objects

The view is defined over a documented set of base objects spanning several EBS modules. Core Depot Repair objects include CSD_REPAIRS, CSD_REPAIR_ESTIMATE, and CSD_REPAIR_ESTIMATE_LINES, which supply repair header, estimate header, and estimate line data respectively. CS_ESTIMATE_DETAILS provides the detailed estimate attributes such as inventory item, quantity required, selling price, and serial number. Supporting lookup and reference views include CS_LOOKUPS, FND_LOOKUPS, CS_TRANSACTION_TYPES_VL, CS_BILLING_TYPE_CATEGORIES, CS_TXN_BILLING_TYPES, CS_KB_SETS_VL, and CS_SERVICE_CODES_VL. Integration-related objects include OKC_K_HEADERS_B for contract numbers, QP_LIST_HEADERS_TL for price list names, and CS_INCIDENTS_B_SEC for incident data. Item and unit-of-measure attributes are resolved through MTL_SYSTEM_ITEMS_VL and MTL_UNITS_OF_MEASURE_VL, while BOM_RESOURCES_V, WIP_ENTITIES, and the CS_STD and FND_GLOBAL packages supply costing and session context. The joins are anchored on REPAIR_LINE_ID, REPAIR_ESTIMATE_ID, REPAIR_ESTIMATE_LINE_ID, and ESTIMATE_DETAIL_ID.

Key Columns

• REPAIR_LINE_ID, REPAIR_NUMBER, REPAIR_ESTIMATE_ID, REPAIR_ESTIMATE_LINE_ID – Primary identifiers linking estimate lines to their parent repair order and estimate.
• ESTIMATE_DETAIL_ID, INVENTORY_ITEM_ID, PRODUCT, DESCRIPTION – The estimate detail reference and item identity, with MSI.CONCATENATED_SEGMENTS exposed as PRODUCT.
• ESTIMATE_QUANTITY (QUANTITY_REQUIRED), REPAIR_QUANTITY, UNIT_OF_MEASURE_CODE – Quantities and UOM for the estimate line versus the repair order.
• AFTER_WARRANTY_COST (CHARGE), ITEM_COST, PROFIT_MARGIN, PROFIT_MARGIN_PERCENTAGE – Derived financial columns computed with DECODE/NVL expressions from AFTER_WARRANTY_COST, QUANTITY_REQUIRED, and ITEM_COST.
• SELLING_PRICE, NO_CHARGE_FLAG, PRICE_LIST, TRANSACTION_TYPE, BILLING_TYPE, BILLING_CATEGORY – Pricing and billing attributes resolved from QP_LIST_HEADERS_TL, CS_TRANSACTION_TYPES_VL, and CS billing objects.
• APPROVAL_REQUIRED_FLAG, APPROVAL_STATUS, STATUS, PROMISE_DATE – Repair order workflow and commitment attributes.
• CONTRACT_NUMBER, CONTRACT_ID, INVOICE_TO_ORG_ID, ORDER_HEADER_ID, ORDER_LINE_ID – Contract and order linkage.
• CONTEXT, ATTRIBUTE1 through ATTRIBUTE15 – Descriptive flexfield columns for customer-specific estimate line data. Note that the view does not expose a column literally named JUSTIFICATION_NOTES; that user search term is not present in the documented view text.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – Standard audit columns.

Common Use Cases and Queries

This view is typically queried for estimate line reporting, repair cost analysis, and integration extracts feeding order or billing processes. A basic estimate line listing for a given repair order:

• SELECT repair_number, product, description, estimate_quantity, selling_price, no_charge_flag, status FROM csd_repair_estimate_lines_v WHERE repair_number = :p_repair_number;
• Profitability analysis using the derived margin columns: SELECT repair_number, product, after_warranty_cost charge, item_cost, profit_margin, profit_margin_percentage FROM csd_repair_estimate_lines_v WHERE profit_margin_percentage IS NOT NULL;
• Pricing and billing lookup: SELECT repair_number, product, price_list, transaction_type, billing_type, billing_type_meaning FROM csd_repair_estimate_lines_v WHERE price_list IS NOT NULL;
• Contract-linked estimates: SELECT repair_number, contract_number, invoice_to_org_id, order_header_id, order_line_id FROM csd_repair_estimate_lines_v WHERE contract_number IS NOT NULL;

Developers should join back to the base objects only when columns not exposed by the view are required, and should account for the flexfield CONTEXT/ATTRIBUTE columns when building customer-specific reporting.