Results for “rate_end_date”

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

Overview

GMP_SR_MFG_FCST_V is a database view owned by the APPS schema within Oracle E-Business Suite, registered under the GMP (Process Manufacturing Process Planning) product family. Its documented description is "Manufacturing Forecast for Demand Planner." The view is intended to expose manufacturing forecast data in a normalized form suitable for consumption by demand planning processes and related reporting. In ETRM 12.1.1 and 12.2.2 installations, the object carries a VALID status, indicating it compiles and is available for reference by dependent code, concurrent programs, and integration layers.

The view is significant because it presents a stable column contract—covering forecast designators, organization and item keys, customer and sales channel attributes, ship-to locations, time buckets, and quantities—while shielding consumers from the physical storage and derivation logic of the underlying forecast tables. This abstraction supports both Report Builder/BI Publisher reporting and programmatic integration with external demand planning tools.

Underlying Base Objects

The documented view text defines GMP_SR_MFG_FCST_V solely over SYS.DUAL, using a WHERE clause of 1 <> 1. Every projection in the SELECT list is a strongly typed NULL cast: NULL FORECAST_DESIGNATOR, TO_NUMBER(NULL) for the various primary keys and numeric attributes, TO_DATE(NULL) for date columns, and NULL for character columns. Consequently, the view returns zero rows in its delivered form.

This construct functions as a typed placeholder or stub. The explicit data type declarations establish the result set shape—column names, ordinal positions, and types—so that dependent metadata, synonyms, grants, and calling programs compile against a consistent interface. The documented base object list contains only DUAL, meaning no Oracle Process Manufacturing forecast or planning tables are referenced by the delivered definition. Customers or implementation teams routinely replace the body with the actual forecast query, preserving the column list so downstream consumers remain unaffected.

Key Columns

The projection list defines twenty-one columns:

• FORECAST_DESIGNATOR – character identifier for the forecast entity.
• SR_INV_ORG_PK / INV_ORG – inventory organization surrogate key and code.
• SR_ITEM_PK / ITEM – item surrogate key and item identifier.
• SR_CUSTOMER_PK / CUSTOMER – customer key and customer name/number.
• SR_SALES_CHANNEL_PK / SALES_CHANNEL – sales channel key and description.
• SR_SHIP_TO_LOC_PK / SHIP_TO_LOC – ship-to location key and location value.
• BUCKET_TYPE – numeric code identifying the time bucket granularity.
• FORECAST_DATE / RATE_END_DATE – bucket start and rate end dates.
• ORIGINAL_QUANTITY / CURRENT_QUANTITY – original and revised forecast quantities.
• SR_USER_DEFINED1_PK / USER_DEFINED1 and SR_USER_DEFINED2_PK / USER_DEFINED2 – surrogate keys and values for two configurable user-defined (descriptive flexfield) dimensions.
• PRD_LEVEL_ID – product level identifier for planning hierarchy.

The user search term "user_defined2" maps directly to the USER_DEFINED2 and SR_USER_DEFINED2_PK columns, which expose the second descriptive segment for segmentation, filtering, or grouping in demand planning reports.

Common Use Cases and Queries

Because the delivered view returns no rows, use cases center on its role as an interface contract and on implementations that populate it. Typical scenarios include reporting forecast demand by organization, item, and customer; filtering by the second user-defined attribute; and integrating forecast buckets with downstream planning systems.

Sample query structured against the documented columns:

SELECT forecast_designator, inv_org, item, customer,
       sales_channel, ship_to_loc, bucket_type,
       forecast_date, rate_end_date,
       original_quantity, current_quantity,
       user_defined1, user_defined2, prd_level_id
FROM   apps.gmp_sr_mfg_forecast_v
WHERE  user_defined2 = :segment_value
AND    forecast_date BETWEEN :start_date AND :end_date;

Integration users should verify whether the site has replaced the stub body, since the documented definition produces an empty result set. Where customized, standard APPS grants and synonyms permit read-only access under the APPS schema, and the fixed column contract protects dependent reports and interfaces from source-table changes.