Search Results csd_ro_group_estimate_v




Overview
Explore in AI Chat

Overview

CSD_RO_GROUP_ESTIMATE_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 reporting view owned by the APPS schema in the CSD (Depot Repair) product family. Its documented purpose is to summarize all estimates for a given repair order line, grouped by MLE (multi-lingual entity) categories. In practice, the view consolidates material, labor, expense, and total estimate amounts alongside their associated status lookups into a single, denormalized result set that can be queried directly by reports, OAF pages, concurrent programs, and integration interfaces without requiring callers to invoke packaging logic themselves.

The view is especially relevant to users searching on the term estimate_status, because it exposes an ESTIMATE_STATUS column that resolves the coded value stored on the estimate record to its translated meaning via FND_LOOKUPS. This makes the view a convenient data source when a repair order must be displayed or extracted together with human-readable estimate and approval statuses.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects:

  • CSD_PROCESS_UTIL (PACKAGE) — supplies the GET_ESTIMATE function used inline in the view text to derive MATERIAL, LABOR, EXPENSE, and TOTAL_ESTIMATE values for a repair line.
  • CSD_REPAIRS (SYNONYM) — the repair order line source; contributes repair number, line/group identifiers, and approval attributes.
  • CSD_REPAIR_ESTIMATE (SYNONYM) — the estimate record source; contributes the estimate status code.
  • FND_LOOKUPS (VIEW) — joined twice with outer joins to translate the estimate status and approval status codes into their meanings.
  • FND_GLOBAL (PACKAGE) — supplied for session/context resolution within the underlying logic.

The view joins CSD_REPAIRS to CSD_REPAIR_ESTIMATE on REPAIR_LINE_ID using an outer join, so repair lines without an estimate record are still returned. The lookup joins are likewise outer joins, which prevents rows from being dropped when a status code is null or has no matching lookup entry. The lookups are constrained to the lookup types CSD_ESTIMATE_STATUS and CSD_APPROVAL_STATUS.

Key Columns

  • ROW_ID — the ROWID of the underlying CSD_REPAIRS row, useful for direct row access.
  • REPAIR_NUMBER — the user-visible depot repair order number.
  • REPAIR_LINE_ID — the primary key of the repair line; also passed to GET_ESTIMATE.
  • REPAIR_GROUP_ID — the repair group identifier, supporting the "group estimate" aggregation implied by the view name.
  • MATERIAL, LABOR, EXPENSE, TOTAL_ESTIMATE — amounts computed by CSD_PROCESS_UTIL.GET_ESTIMATE using category codes 'M', 'L', 'E', and 'T' respectively.
  • APPROVAL_REQUIRED_FLAG — indicates whether the estimate requires approval.
  • ESTIMATE_STATUS — the translated meaning of the estimate status lookup (documented column name; the view text aliases it as ESIMATE_STATUS). This is the column of primary interest to users searching on estimate_status.
  • APPROVAL_STATUS — the translated meaning of the approval status lookup.

Common Use Cases and Queries

The view is typically used to report estimate composition and status by repair line or group, to drive approval workflows, and to feed downstream cost or billing processes. A straightforward query listing estimate status per repair is:

SELECT repair_number, repair_line_id, material, labor, expense, total_estimate, estimate_status, approval_status FROM csd_ro_group_estimate_v;

Filtering by status is equally direct — for example, retrieving all lines awaiting approval by estimate status or by approval requirement:

SELECT repair_number, total_estimate, estimate_status FROM csd_ro_group_estimate_v WHERE estimate_status = 'Pending Approval';

SELECT repair_number, repair_group_id, total_estimate FROM csd_ro_group_estimate_v WHERE approval_required_flag = 'Y';

Because the view already resolves lookup meanings, it removes the need for application code to join FND_LOOKUPS manually, making it well suited to concurrent report data sources, OAF VO definitions, and outbound integration extracts.