Search Results original_source_code

Overview

CS_CHARGE_DETAILS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CS (Service) product family. It exposes charge lines associated with service requests, depot repair orders, and field service reports, consolidating estimate-level pricing and billing information into a single queryable structure. The view is documented as VALID in both ETRM 12.1.1 and 12.2.2, which confirms a consistent definition across releases. Its primary role is to provide a denormalized, read-only projection of charge detail data for use in custom reports, service billing reconciliations, and downstream integrations that need service charge context without joining the many underlying service, order, and contract tables directly.

Underlying Base Objects

The view is defined over a broad set of service, order management, contract, and pricing objects. The core service objects include CS_ESTIMATE_DETAILS (which supplies ESTIMATE_DETAIL_ID and the pricing attributes), CS_INCIDENTS_ALL_B (for the incident and party context), CS_LOOKUPS (used as LK1 for meaning lookups), CS_TRANSACTION_TYPES_B and CS_TRANSACTION_TYPES_TL, CS_TXN_BILLING_OETXN_ALL, CS_TXN_BILLING_TYPES, and CS_BUSINESS_PROCESSES. Order management context is drawn from OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, and OE_TRANSACTION_TYPES_TL. Contract and entitlement data comes through OKC_K_HEADERS_ALL_B, OKC_K_LINES_TL, and the OKS_ENT_BILL_RATES_V and OKS_ENT_UTIL_PVT objects. Party and location data is resolved via HZ_PARTY_SITES and HZ_LOCATIONS, while pricing list context is supplied by QP_LIST_HEADERS_TL. FND_GLOBAL is referenced as a package, typically for session and user context.

Key Columns

• ESTIMATE_DETAIL_ID — Primary identifier for the charge/estimate line.
• INCIDENT_ID — The service request (incident) to which the charge belongs.
• PARTY_ID and ACCOUNT_ID — Customer identifiers sourced from the incident context.
• LINE_NUMBER — Sequence of the charge line within the estimate.
• INVENTORY_ITEM_ID and SERIAL_NUMBER — The item and serial number associated with the charge.
• QUANTITY_REQUIRED and UNIT_OF_MEASURE_CODE — Charge quantity and its UOM.
• SELLING_PRICE — The price quoted or charged for the line.
• AFTER_WARRANTY_COST and FUNC_CURR_AFT_WARR_COST — Cost figures applicable after warranty coverage, in transaction and functional currency.
• PRICING_ATTRIBUTE1 through PRICING_ATTRIBUTE41 — Flexible pricing context attributes used by Oracle Advanced Pricing.
• SOURCE_CODE, SOURCE_ID, ORIGINAL_SOURCE_CODE, ORIGINAL_SOURCE_ID — Identify the originating document and its type.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include service charge reporting, warranty versus non-warranty cost analysis, and reconciliation of billing against service requests. A representative query retrieves charge lines for a given incident:

• SELECT ESTIMATE_DETAIL_ID, INCIDENT_ID, PARTY_ID, LINE_NUMBER, INVENTORY_ITEM_ID, QUANTITY_REQUIRED, SELLING_PRICE, AFTER_WARRANTY_COST FROM APPS.CS_CHARGE_DETAILS_V WHERE INCIDENT_ID = :p_incident_id ORDER BY LINE_NUMBER;

For billing reconciliation, filtering by SOURCE_CODE and SOURCE_ID isolates charges originating from a specific document, while grouping by ACCOUNT_ID supports customer-level cost summaries. Because the view references FND_GLOBAL and entitlement packages, queries should be executed with the appropriate APPS session context. Direct DML against the view is not supported; it is intended strictly for read access in reporting and integration layers.