Search Results mrp_update_type

Overview

EDW_MRP_FCDM_SET_LCV is an Oracle E-Business Suite view owned by the APPS schema and resides in the EDW (Enterprise Data Warehouse / Oracle Business Intelligence Applications) reporting layer. Its name follows the EDW staging convention: the "LCV" suffix denotes a "lookup code value" wrapper view, indicating that the view resolves a coded column into a human-readable meaning rather than exposing the raw code. Specifically, the view presents forecast-designator information from the material planning (MRP) domain, enriched with the decoded update type and organization identifiers, so that downstream extracts can report forecast data without performing lookup joins themselves.

The view carries no documented business object of its own; it is a denormalized presentation object intended for extract, reporting, and integration consumption. In the 12.1.1 and 12.2.2 releases the underlying tables are unchanged, so the view behaves identically in both environments.

Underlying Base Objects

The view is defined as an inner join across four base objects:

• MRP_FORECAST_DESIGNATORS (aliased fd) — the primary driving table, supplying forecast_designator, organization_id, creation_date, description, disable_date, last_update_date, and update_type.
• MFG_LOOKUPS (aliased ml) — joined on ml.lookup_code = fd.update_type with the restriction ml.lookup_type = 'MRP_UPDATE_TYPE', providing the decoded meaning for the update type. This join is the reason the object is styled an LCV view.
• MTL_PARAMETERS (aliased mp) — joined on fd.organization_id = mp.organization_id, supplying organization_code.
• EDW_LOCAL_INSTANCE (aliased inst) — supplying the instance_code used to qualify each row by source instance in multi-instance warehouse loads.

Because MFG_LOOKUPS is an inner join, any forecast designator whose update_type has no corresponding MRP_UPDATE_TYPE lookup row is silently excluded. The predicate fd.forecast_set IS NULL further restricts the result to designators that are not part of a forecast set, isolating stand-alone designators.

Key Columns

• Concatenated designator keys — the view synthesizes at least three composite identifiers: forecast_designator||'-'||organization_id||'-'||instance_code, forecast_designator||'-'||organization_code||'-'||instance_code, and the display form forecast_designator||'('||organization_code||')'. These serve as natural keys for warehouse dimension loading.
• meaning — the decoded value of the MRP_UPDATE_TYPE lookup. This is the column users typically want when searching for "mrp_update_type," since the raw code lives on the base table and only the decoded meaning is exposed here.
• creation_date, description, disable_date, last_update_date — audit and lifecycle attributes of the forecast designator.
• instance_code — the EDW local instance identifier, enabling cross-instance aggregation.
• Trailing NULL columns — five unnamed NULL placeholders exist to satisfy the column contract expected by the consuming EDW extract or interface; they carry no data.

Common Use Cases and Queries

Typical uses include validating MRP_UPDATE_TYPE lookup coverage, extracting forecast designator reference data for a data warehouse dimension, and auditing which designators are disabled. A representative query:

• SELECT DISTINCT meaning FROM apps.edw_mrp_fcdm_set_lcv; — lists every update type actually in use.
• SELECT * FROM apps.edw_mrp_fcdm_set_lcv WHERE disable_date IS NULL ORDER BY creation_date; — returns active designators for load.
• SELECT forecast_designator, organization_code, meaning FROM apps.edw_mrp_fcdm_set_lcv; — produces a human-readable reference listing.

Because MFG_LOOKUPS restricts to MRP_UPDATE_TYPE, a query returning fewer rows than SELECT COUNT(*) FROM mrp_forecast_designators WHERE forecast_set IS NULL signals orphaned or missing lookup codes, a frequent root cause when users report that "mrp_update_type" values are absent from reports.