Search Results calculated_failure_rate




Overview
Explore in AI Chat

Overview

APPS.CSP_FAILURE_RATES_V is a reporting view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments, owned by the APPS schema. It exposes failure rate information maintained within the Service (CSP) product family, which supports field service, depot repair, and service planning operations. The view presents a read-oriented projection of failure rate data, allowing integrators, report developers, and personalization authors to query failure rate values without interacting directly with the underlying base table.

The view's principal function is to normalize the precision of the failure rate values. Both the CALCULATED_FAILURE_RATE and MANUAL_FAILURE_RATE columns are wrapped in a ROUND(..., 5) function, meaning the view consistently returns each rate truncated to five decimal places of precision. This is significant for users searching on "calculated_failure_rate," since the exact column name they are targeting appears in the view's SELECT list rather than only in the base table. The deterministic rounding provides consistent numeric output for downstream calculations and reporting.

Underlying Base Objects

The view is defined over a single base object: the synonym CSP_FAILURE_RATES. All columns in the view are projected directly from that source with no joins, unions, or aggregations. Because the definition is a straight column projection with a rounding transformation, the view behaves as a thin, low-overhead wrapper over CSP_FAILURE_RATES. The view does not alter the cardinality of the result set; each row in CSP_FAILURE_RATES corresponds to exactly one row in the view.

The synonym resolves within the APPS schema to the underlying Service failure rates table. Filters, order-by clauses, and predicate pushdown performed against the view are transparently applied to the base object, which allows the optimizer to use indexes defined on the base table.

Key Columns

  • FAILURE_RATE_ID — Primary identifier for a failure rate record; the unique key linking to related service planning and item configuration data.
  • PRODUCT_ID — Reference to the product to which the failure rate applies.
  • INVENTORY_ITEM_ID — Reference to the specific inventory item associated with the failure rate.
  • CALCULATED_FAILURE_RATE — System-derived failure rate, rounded to five decimal places. This is the column most commonly referenced when searching for "calculated failure rate."
  • MANUAL_FAILURE_RATE — User-entered or overridden failure rate, also rounded to five decimal places.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified each record.
  • SECURITY_GROUP_ID — Multi-org/security group discriminator used in older multi-org configurations.
  • PLANNING_PARAMETERS_ID — Reference to the associated planning parameter set governing how the failure rate is consumed in service planning and forecasting.

Common Use Cases and Queries

Typical usage centers on analytics and integration scenarios: exporting failure rates for reliability analysis, verifying that manual overrides exist alongside calculated values, or feeding failure rate data into external forecasting models. The following sample retrieves rounded calculated and manual rates for a specific item:

  • SELECT inventory_item_id, calculated_failure_rate, manual_failure_rate FROM apps.csp_failure_rates_v WHERE inventory_item_id = :item_id;

To identify records where a manual override diverges from the calculated value:

  • SELECT failure_rate_id, product_id, calculated_failure_rate, manual_failure_rate FROM apps.csp_failure_rates_v WHERE calculated_failure_rate != manual_failure_rate;

Audit-oriented queries frequently report the last update timestamp and user:

  • SELECT failure_rate_id, calculated_failure_rate, last_update_date, last_updated_by FROM apps.csp_failure_rates_v ORDER BY last_update_date DESC;

Because the view applies rounding, values retrieved differ from base table storage only in precision. Any comparison or reconciliation against directly queried base data should account for this five-decimal rounding. The view is read-only from a functional standpoint and should not be targeted by DML; updates belong against the underlying Service maintenance forms or the base table through supported APIs.