Results for “aps_collection_flag”

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

Overview

MRP_FORECAST_DESIGNATORS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined within the MRP (Master Scheduling/MRP) product family. It presents forecast designator definitions — the named configurations that govern how forecast demand is consumed, updated, and bucketed within Oracle Advanced Supply Chain Planning and the MRP/MPS planning engines. A forecast designator identifies a distinct forecast stream (for example, a customer-specific, ship-to-specific, or bill-to-specific forecast) and controls behaviors such as whether the forecast is consumed during planning, the direction and width of the update time fences, and the outlier update percentage.

The view's principal value in reporting and integration is that it resolves raw foreign-key identifiers into human-readable descriptive values. Rather than returning only numeric CUSTOMER_ID, SHIP_ID, and BILL_ID values, the view calls packaged functions in MRP_MANAGER_PK to derive CUSTOMER_NAME, SHIP_ADDRESS, and BILL_ADDRESS. This makes it directly consumable by BI Publisher reports, Oracle Discoverer workbooks, OBIEE repositories, and custom concurrent programs without requiring additional lookups against customer and address tables.

Underlying Base Objects

The view is defined with a single-table SELECT over MRP_FORECAST_DESIGNATORS, accessed through a synonym resolved in the APPS schema. The base table supplies all persistent designator attributes, including organization, forecast set, demand class, bucket type, and the full set of descriptive flexfield columns (DDF_CONTEXT plus ATTRIBUTE1 through ATTRIBUTE15). In addition to the ROWID alias exposed as ROW_ID, the view references the MRP_MANAGER_PK package on three occasions to invoke GET_CUSTOMER_NAME, GET_SHIP_ADDRESS, and GET_BILL_ADDRESS.

The presence of standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) confirms that the underlying table is an audited, developer-extensible entity. The inclusion of REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE reflects concurrent-program context captured when designators are created or updated through batch processes. Because the view is defined solely over MRP_FORECAST_DESIGNATORS, it inherits that table's row-level security and organization partitioning characteristics; callers should therefore filter by ORGANIZATION_ID where multi-org isolation is required.

Key Columns

• FORECAST_DESIGNATOR — The unique name identifying the forecast designator.
• ORGANIZATION_ID — The inventory organization to which the designator belongs.
• CONSUME_FORECAST — Flag indicating whether forecast entries are consumed by actual demand during planning.
• UPDATE_TYPE — Determines how the forecast is updated (for example, by percentage or by amount).
• FOREWARD_UPDATE_TIME_FENCE / BACKWARD_UPDATE_TIME_FENCE — The forward- and backward-looking windows within which forecast updates are permitted.
• OUTLIER_UPDATE_PERCENTAGE — The threshold percentage used to detect and exclude outlier updates when revising forecast quantities. This is the column most closely associated with the search term outlier_update_percentage.
• FORECAST_SET — The forecast set linked to the designator.
• CUSTOMER_NAME, SHIP_ADDRESS, BILL_ADDRESS — Derived descriptive values returned by MRP_MANAGER_PK functions.
• DEMAND_CLASS — The demand class used to segregate forecast consumption.
• BUCKET_TYPE — The time-bucket granularity applied to the forecast.
• ATTRIBUTE1–ATTRIBUTE15, DDF_CONTEXT — Descriptive flexfield segments for customer-specific extensions.

Common Use Cases and Queries

Typical uses include auditing designator configuration across organizations, validating outlier and time-fence settings before a planning run, and feeding downstream reports with resolved customer and address text.

SELECT forecast_designator,
       organization_id,
       consume_forecast,
       outlier_update_percentage,
       foreward_update_time_fence,
       backward_update_time_fence
FROM   apps.mrp_forecast_designators_v
WHERE  organization_id = :org_id;

A second common pattern retrieves designators with their resolved customer information for a given forecast set:

SELECT forecast_designator,
       customer_name,
       ship_address,
       bill_address,
       demand_class
FROM   apps.mrp_forecast_designators_v
WHERE  forecast_set = :forecast_set;

A third pattern validates outlier configuration prior to planning, filtering designators whose outlier percentage is outside an expected range:

SELECT forecast_designator, outlier_update_percentage
FROM   apps.mrp_forecast_designators_v
WHERE  update_type IS NOT NULL
AND    NVL(outlier_update_percentage, 0) NOT BETWEEN 1 AND 100;

Because MRP_FORECAST_DESIGNATORS_V is a view, all statements against it are read-only; maintenance of designators must be performed through the base table's owning form or concurrent program, never by direct DML against the view. Performance is generally acceptable for organization- or forecast-set-scoped queries, but the packaged function calls executed per row can add cost on large result sets, so predicates should be applied to restrict rows before those functions are evaluated.