Results for “esimate_status”

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

Overview

APPS.CSD_RO_GROUP_ESTIMATE_V is a reporting view in the Oracle E-Business Suite Depot Repair (CSD) module. It consolidates repair line information with material, labor, expense, and total cost estimates, and it resolves internal lookup codes into user-facing meanings. The view is defined as a join between repair records, their associated estimate rows, and two FND_LOOKUPS lookups, and it derives estimate amounts through calls to the CSD_PROCESS_UTIL package.

The view is primarily designed for repository/ordering-style reporting and integration where a flattened, denormalized row per repair line is required. A characteristic search term associated with this object is csd_estimate_status, which corresponds to the lookup type used to translate the estimate status code into a readable description in the esimate_status column.

Underlying Base Objects

Per documented view metadata in ETRM 12.2.2, the view is owned by APPS and references the following base objects:

• CSD_REPAIRS (SYNONYM) — the repair line header/master source, aliased as cr; supplies rowid, repair_number, repair_line_id, repair_group_id, and approval_required_flag.
• CSD_REPAIR_ESTIMATE (SYNONYM) — the estimate detail source, aliased as cre; supplies the estimate_status code joined back to cr.repair_line_id.
• FND_LOOKUPS (VIEW) — a standard Oracle lookup view used twice, aliased as fl and fl1, to resolve estimate status (CSD_ESTIMATE_STATUS) and approval status (CSD_APPROVAL_STATUS) codes into their meanings.
• CSD_PROCESS_UTIL (PACKAGE) — the PL/SQL package invoked via GET_ESTIMATE to compute material, labor, expense, and total estimates for each repair line.
• FND_GLOBAL (PACKAGE) — a standard EBS package referenced in documented metadata (commonly used for organization/context resolution within the CSD code stack).

The join to CSD_REPAIR_ESTIMATE and both FND_LOOKUPS instances uses outer joins (the (+) notation), so repair lines without an estimate row or without a matching lookup still return a row with null estimate and status meaning columns.

Key Columns

• rowid — physical row identifier of the repair line, useful for updates or diagnostics.
• repair_number — the user-visible repair order/line number.
• repair_line_id — unique identifier of the repair line; the join key to estimate rows and the input to the estimate functions.
• repair_group_id — groups related repair lines for reporting aggregation.
• material, labor, expense, total_estimate — calculated amounts returned by CSD_PROCESS_UTIL.GET_ESTIMATE, using codes 'M', 'L', 'E', and 'T' respectively.
• approval_required_flag — indicates whether the repair line requires approval.
• esimate_status — the decoded meaning of the estimate status lookup (note the documented spelling in the view definition). Requires lookup type CSD_ESTIMATE_STATUS.
• approval_status — the decoded meaning of the approval status lookup. Requires lookup type CSD_APPROVAL_STATUS.

Common Use Cases and Queries

Typical scenarios include reviewing estimated vs. approved repair costs, filtering by estimate status, and grouping estimates by repair group. Because the estimate amounts come from a PL/SQL function, filters on those values are usually applied in an outer query for performance.

• List total estimates for a repair number:

SELECT repair_number, material, labor, expense, total_estimate
FROM   apps.csd_ro_group_estimate_v
WHERE  repair_number = :p_repair_number;

• Find repair lines by estimate status meaning (uses the CSD_ESTIMATE_STATUS lookup):

SELECT repair_number, repair_line_id, esimate_status, approval_status
FROM   apps.csd_ro_group_estimate_v
WHERE  esimate_status = :p_estimate_status;

• Aggregate estimates by repair group:

SELECT repair_group_id,
       SUM(total_estimate) total_estimate
FROM   apps.csd_ro_group_estimate_v
GROUP  BY repair_group_id;

The view is intended for read-only reporting and integration. Any application logic requiring updates should operate on the underlying base objects rather than this view.