Results for “orig_system_line_reference”

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

Overview

CS_ESTIMATE_DETAILS is a transaction table in the Oracle E-Business Suite Service (CS) module, owned by the CS schema. It stores the details of charge lines generated within Oracle Service, functioning as the operational backbone for estimate, billing, and quotation activity tied to service transactions, repairs, and returns. Each row represents a single charge line, capturing pricing, coverage, billing, and transactional attributes that drive downstream invoicing and order creation.

Under the Data Vault classification heuristic derived from its foreign key structure, this object is satellite-leaning. It carries a dense set of descriptive, mutable attributes (pricing context, billing flags, coverage references, and return details) keyed by a surrogate identifier, which is characteristic of a satellite surrounding a hub or link. Modelers should treat ESTIMATE_DETAIL_ID as the anchor while recognizing that the surrounding context (customer, incident, repair, coverage) is referenced rather than owned. The table is documented as VALID and contains 229 physical columns in the 12.2.2 schema, reflecting its role as a wide, attribute-rich detail store.

Key Information Stored

The surrogate primary key is ESTIMATE_DETAIL_ID, enforced by the unique index CS_ESTIMATE_DETAILS_U1 and the constraint CS_ESTIMATE_DETAILS_PK. It uniquely identifies each charge line. Although the unique index formalizes only the primary key, ESTIMATE_ID and LINE_NUMBER together function as the natural business key linking a detail line to its parent estimate.

The most significant columns include:

• ESTIMATE_DETAIL_ID – Surrogate primary key for the charge line.
• ESTIMATE_ID – Parent estimate header identifier; the primary grouping key for charge lines.
• LINE_NUMBER – Sequential line position within the estimate.
• INVENTORY_ITEM_ID and SERIAL_NUMBER – Identify the item and serial being serviced or billed.
• QUANTITY_REQUIRED and UNIT_OF_MEASURE_CODE – Quantity and UOM for the charge.
• SELLING_PRICE, LIST_PRICE, and COST – Pricing and cost basis for the line.
• SOURCE_ID and SOURCE_CODE – Reference to the originating repair (CSD_REPAIRS) or other source transaction.
• INCIDENT_ID – Links the charge line to the service incident.
• CUSTOMER_PRODUCT_ID – The installed customer product being serviced.
• SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, BILL_TO_PARTY_ID, and SHIP_TO_PARTY_ID – Party and site references used for billing and shipment.
• TXN_BILLING_TYPE_ID and LINE_TYPE_ID – Classify the billing and line type for pricing and accounting.
• COVERAGE_ID and EXCEPTION_COVERAGE_USED – Indicate service coverage applied to the line.
• CURRENCY_CODE, CONVERSION_RATE, and CONVERSION_TYPE_CODE – Currency and exchange-rate context for the charge.
• ADD_TO_ORDER_FLAG and INTERFACE_TO_OE_FLAG – Control whether the line is rolled into an order.

Common Use Cases and Queries

The table is central to service billing reconciliation, estimate-to-order conversion, and charge-line reporting. A common pattern joins detail lines to their parent estimate and source repair:

• Charge lines for an estimate: SELECT ESTIMATE_DETAIL_ID, LINE_NUMBER, INVENTORY_ITEM_ID, SELLING_PRICE FROM CS.CS_ESTIMATE_DETAILS WHERE ESTIMATE_ID = :estimate_id ORDER BY LINE_NUMBER;
• Lines pending order creation: filter on ADD_TO_ORDER_FLAG = 'Y' and INTERFACE_TO_OE_FLAG = 'N' to identify lines not yet interfaced to Order Management.
• Lines by source repair: join to CSD_REPAIRS using SOURCE_ID to trace charges back to a specific repair.
• Pricing and currency review: aggregate SELLING_PRICE by CURRENCY_CODE and PRICE_LIST_HEADER_ID for revenue reporting.
• Coverage analysis: group by COVERAGE_ID or TXN_BILLING_TYPE_ID to determine how much service work was covered versus billed.

Because the table carries extended PRICING_ATTRIBUTE1 through PRICING_ATTRIBUTE100 columns, reporting queries can leverage these to surface pricing-segment or contract-specific data captured at line level.

Related Objects

The following objects are the most significant relationship points, based on the documented foreign key metadata:

• CSD_PRODUCT_TRANSACTIONS – References CS_ESTIMATE_DETAILS via ESTIMATE_DETAIL_ID.
• CSD_REPAIR_ESTIMATE_LINES – References ESTIMATE_DETAIL_ID; links estimate lines to repair estimates.
• CSD_REPAIR_ACTUAL_LINES – References ESTIMATE_DETAIL_ID; links actual repair activity to estimates.
• CSD_REPAIRS – The repair source referenced by CS_ESTIMATE_DETAILS.SOURCE_ID.
• CS_INCIDENTS_ALL_B – Parent incident referenced by INCIDENT_ID.
• CS_CUSTOMER_PRODUCTS_ALL – Installed base product referenced by CUSTOMER_PRODUCT_ID.
• HZ_PARTIES – Party master referenced by BILL_TO_PARTY_ID, SHIP_TO_PARTY_ID, BILL_TO_CONTACT_ID, and SHIP_TO_CONTACT_ID.
• HZ_CUST_ACCOUNTS – Customer accounts referenced by INVOICE_TO_ACCOUNT_ID and SHIP_TO_ACCOUNT_ID.
• QP_LIST_HEADERS_B – Price list referenced by PRICE_LIST_HEADER_ID.
• CS_TXN_BILLING_TYPES – Billing type referenced by TXN_BILLING_TYPE_ID.

Together, these relationships position CS_ESTIMATE_DETAILS as the intersection between service execution (incidents, repairs, installed products) and commercial processing (pricing, billing, coverage, and order interface).