Maintaining Forecast Items

This chapter provides an overview of forecast items, list common elements, and discusses how to:

Create forecast item captions and descriptions.
Create forecast items.
Maintain forecast items.
Define calculation codes for forecast items.
Refresh forecast items.
Make mass changes to forecast items.
Merge forecast item demand.

Understanding Forecast Items

Forecast items are entities with a unique set of descriptive, demand, and forecast data at a specific level within a view. You create forecast items for a wide range of uses, but they ultimately represent things that you buy, sell, or use in the organization and for which you require a predictable usage.

The system uses the template record at each level to determine the default data for the forecast item record. Although you can transfer forecast items at any level of a view, PeopleSoft recommends that you transfer them only at the lowest level in the view. This enables the system to create the higher levels automatically during summarization. A forecast item has a direct relationship with an inventory item code only if the item code is part of the forecast item key definition.

You can change most information that is associated with a forecast item at any time; however, you cannot change key fields. You can also delete a forecast item at any time. Use an existing forecast item as a model for a new forecast item by copying the existing forecast item to a new record and then changing it. To make mass changes to multiple forecast item records, use the Mass Change feature in the Process Forecast menu.

Common Elements Used in This Chapter

Description	Provides a method to enter more details about an item that others can use for planning purposes. The system uses this field for informational purposes only, and it is not required. You can enter up to 254 characters. The system also considers this to be the description of the item while the short description is considered the caption. You can create this description automatically from a combination of user-defined fields and the their descriptions and user-entered text.
Forecast View	Defines a multilevel forecast structure. Views include information that defines the view and structure type. Forecast items reside in a forecast view. The view determines many of the processing and usage parameters for the item. If you are creating an item, select the view to which you want the item to belong. Items can belong to more than one view. You must also be authorized to use a view before it appears in drop-down lists.
From Period	Enter a period during the forecast horizon when you want to begin processing. Use this field in conjunction with the From Year, To Year, and To Period fields to define a range of periods. These are the periods that the system processes when using calculation codes or for mass changes to items.
From Year	Enter a year during the planning horizon at which you want to start calculations.
Level	Defines a set of forecast items with a common key structure. Each level is related in a hierarchical definition with other levels in the view. Create items at specific levels in the view.
Model	Defines a set of attributes and parameters that make up a technique that you use to analyze item forecasts. You can use a variety of models in PeopleSoft Demand Planning to simulate what-if scenarios without compromising live forecast data.
Offset From Period	Defines when the system should calculate a start period, using the forecast start period as the base. The system uses this field on several selection criteria pages for defining forecast time periods. You can define periods either using the offset method or by indicating the year and period number. Use offsets to avoid changing period and year values as the forecast moves forward in time. An offset is always assumed to be n periods from the forecast start period. Using the Offset From Period and Offset To Period fields, enter the number of periods from the current period that you want to include in the processing. Enter values in both fields to define the range. If you use a single period, enter it in both fields. Zero is not a valid offset. The system assumes that 1 is the first forecast period, with -1 being the last historical period.
Offset To Period	Use this field with the Offset From Period field to define a range of periods to include in forecast item calculations.
Short Description	Enter a brief description of the forecast item (40 characters maximum). PeopleSoft Demand Planning uses this value to identify the forecast item. You can create the short description field automatically from a combination of user-defined fields and their descriptions and user-entered text by using the template caption. The system considers this the caption for the item.
To Period	Enter a period during the planning horizon at which you want to end calculations.
To Year	Enter a year during the planning horizon at which you want to end calculations.

Creating Forecast Item Captions and Descriptions

To set up forecast item captions, use the Forecast Item Descriptions component.

This section discusses how to:

Set up item captions and descriptions.
Rebuild captions and descriptions.

Pages Used to Create Forecast Item Captions and Descriptions

Page Name	Object Name	Navigation	Usage
Forecast Item Descriptions	DP_FCITMCAPTIONS	Demand Planning, Define Forecast Elements, Forecast Items, Forecast Item Descriptions	Set up captions and descriptions for templates used for forecast items.
Rebuild Caption/Description	DP_RUN_CAPDESC	Demand Planning, Define Forecast Elements, Forecast Items, Rebuild Caption/Description	Rebuild captions and descriptions for items in a specific forecast view.

Setting Up Item Captions and Descriptions

Access the Forecast Item Descriptions page.

Before you define data for a forecast item, you can set up templates for captions and descriptions that uniquely define the item. Captions and descriptions are the naming conventions that the system uses to track forecast items. The caption or description that you create is a string of values that you select and enter for the item. For example, you can select from existing user-defined fields, key fields, or enter information in text fields to arrive at the sting that defines the caption or description. The system builds the text for the caption or description in the order that you define the fields.

The differences between captions and descriptions are:

Captions populate the short description field.

The system limits the description fields to 40 characters.
Descriptions populate the long description field for an item.

You can use up to 254 characters to establish a description for an item.

You can use an item as a model for creating or assigning attributes to another item by selecting to set the item up as a template item.

Description Use	Displays the value that the system initially used to create the item description, either Caption or Description. Captions populate the short description fields while descriptions populate the long description fields for an item.
Rebuild	Click to compile the elements that you select for this item and rebuild the caption description. Use this option to rebuild single items. Use the Rebuild Caption/Description feature on the Forecast Items menu to rebuild multiple items for a view.
Description Type	Select the type of description that you want to use for this caption or description. Values include: Field: Select from the fields that are created as user-defined fields for this forecast view. Text: Provides a way for you to enter unique text that you want to use to describe the item.
Field Name	Select a user-defined field that you want to include in the caption or description for the forecast item.
Field Length	Displays the default length for the field. If you overwrite the value, then the number of characters that describe the field are reduced in the naming convention. For example, if a field length is 18 and you enter 10 for the field length, then the caption or description uses only the first 10 characters of the field to help create the description.
Description	Enter a description when you select Text as the caption type in the Description Type field.
Maximum Length	Displays the maximum length that you can use for the field. Values that you enter in the Field Length field must be equal to or less than this value.

Rebuilding Captions and Descriptions

Access the Rebuild Caption/Description page.

When captions and descriptions change, you can run this process to update either the caption, description, or both for a view.

Forecast View

Select the view for which you want to rebuild captions and descriptions.

Build Caption/Description

Select one of these item rebuild values to use with this run control ID:

Build Caption Only: Rebuilds only captions for items in the view.
Build Caption and Description: Rebuilds all captions and descriptions for items in the view.
Build Description Only: Rebuilds only descriptions for items in the view.

Creating Forecast Items

To create forecast items, use the Forecast Items Maintenance component.

This section provides an overview of item creation and discusses how to:

Create forecast items.
Create templates for items.

Understanding Item Creation

Using PeopleSoft Demand Planning, you can create and maintain forecast items and their corresponding data. The key definition for each level determines the unique key for each forecast item. You can also define templates to group together the default field values that are used to create new forecast items.

You can create forecast items by using these methods:

Manually create and maintain items by using pages that are described in this chapter.
Automatically create items when you transfer internal demand history from PeopleSoft Billing, PeopleSoft Order Management, and PeopleSoft Inventory records to PeopleSoft Demand Planning.

During the transfer, the system creates a new forecast item if one is not found, or it updates the static information for the item if it already exists. You can also refresh existing item data by using the Refresh Specifications option. This feature accesses records where the items reside and extracts field data that has changed.
Automatically create items when you load external data from third-party systems.

Pages Used to Create Forecast Items

Page Name	Object Name	Navigation	Usage
Create Forecast Items	DP_FCITEMS_CREATE	Demand Planning, Define Forecast Elements, Forecast Items, Create Forecast Items	Create forecast items.
Create Forecast Items	DP_FCITEMS_CREATE	Select the Template Item check box on the Create Forecast Items page.	Define a template on which the system bases the creation of an item.
Copy Forecast Items	DP_FCITEMS_COPY	Demand Planning, Define Forecast Elements, Forecast Items, Maintain Forecast Items Click the Copy button on the Forecast Items page.	Create a forecast item by copying the attributes from a similar item. See Setting Up General Data for Forecast Items.

Creating Forecast Items

Access the Create Forecast Items page.

Template Item	Select this check box if you want to use this forecast item as a model for other items. If you do not want to use the item as a template item, clear the check box. See Creating Templates for Items.
User Data Value	Enter a value you want to associate with this forecast item. If a field is defined as a key field, a value is required for the User Data Value field, because it creates part of the forecast item key.
Key Field	Indicates whether the field is a key field for the item. If the check box is selected, then you must enter a value in the User Data Value field.
Length	Displays the number of characters that you can enter in the field.
Invisible	Indicates whether the user data field is visible when it is used as part of the key. If the check box is selected, the system does not display the field as part of the item key. However, the user data field is effectively used as part of the forecast item key and must be a part of the unique key combination.

Creating Templates for Items

Access the Create Forecast Items page.

Manually select the Template Item check box when you access the page. This indicates that you want to use the default values that are established for this forecast item as the basis for adding new forecast items, either manually or when importing data. If you clear the check box, the system displays the initial Create Forecast Items page, where you can continue to define fields that make up the item.

A template item is a type of forecast item that acts as a model or pattern by supplying default field values for other forecast items that are associated with the same view level that you create. You can create templates for each level of the view, but the system automatically creates one template for each level of the view when you create the view. You can use only one template at a time. Use the Level field to indicate the template item's level.

Note. The field changes when you select the Template Item check box.

You can enter any text for the template. When new items are added manually, the system displays a new record with all fields set up from the template. You define the template item to use with a view by using the Define Levels page for a view.

Maintaining Forecast Items

You can add and maintain data for individual items depending on how you want to use them in specific views.

You can also use the Forecast Items option in the Process Forecast menu to perform item maintenance for items within specific views. Using the option, you can perform these item maintenance operations:

Make mass changes to items.
Merge item quantities.
Make changes resulting from item simulations.
Use the Adjustment Workbench to change item values and parameters.

Other sections in the chapter describe these routines along with other chapters in this PeopleBook.

See Simulating Item Forecasts.

See Viewing Item Forecast Statistics.

This section discusses how to:

Set up general data for forecast items.
Define item unit of measurement (UOM) attributes.
Create and maintain UOMs for specific, individual items.
Enter forecast item control parameters.
Set up forecast item model controls.
Display forecast item model tracking.
Display forecast item seasonality profiles.
Maintain forecast item price and costs.
Display other data for forecast items.
Maintain user period data for forecast items.
Maintain user data fields for forecast items.
View item forecast statistics.
Delete forecast items.

Pages Used to Maintain Forecast Items

Page Name	Object Name	Navigation	Usage
Maintain Forecast Items	DP_FCITEMS	Demand Planning, Define Forecast Elements, Forecast Items, Maintain Forecast Items, Maintain Forecast Items	Set up general data for forecast items.
Units	DP_FCITEMS2	Demand Planning, Define Forecast Elements, Forecast Items, Maintain Forecast Items, Units	Define UOM attributes for forecast items.
Forecast Items UOMs	DP_FCITEMUOMS	Click the Forecast Items UOMs link on the Units page.	Create and maintain UOMs specific to individual items. Define to units, conversion factors, and UOM groups for forecast items.
Control	DP_FCITEMS3	Demand Planning, Define Forecast Elements, Forecast Items, Maintain Forecast Items, Control	Enter forecast item control parameters. Associate the forecast item with a control group and a seasonality group.
Model Control	DP_FCITEMS4	Click the Model Control link on the Control page.	Set up forecast item model controls and define their associated controls.
Model Tracking	DP_FCITEMS5	Click the Model Tracking link on the Control page.	Display forecast item model tracking. Displays information that is summarized. You cannot change this data.
Seas Profile (seasonality profile)	DP_FCITEMS6	Demand Planning, Define Forecast Elements, Forecast Items, Maintain Forecast Items, Seasonality Profile	Display forecast item seasonality profiles. If the item derives its seasonality factors from a seasonality group, it also appears.
Other Data	DP_FCITEMS7	Demand Planning, Define Forecast Elements, Forecast Items, Maintain Forecast Items, Other Data	Display other data for forecast items, such as current demand and review period details.
User Period Data	DP_FCITEMS9	Click the User Period Data link on the Other Data page.	Maintain user period data for forecast items.
User Data Fields	DP_FCITEMS10	Click the User Data Fields link on the Other Data page.	Maintain user data fields for forecast items.
Prices/Costs	DP_FCITEMS8	Demand Planning, Define Forecast Elements, Forecast Items, Maintain Forecast Items, Prices/Costs	Set up period price and costs for forecast items.
Statistics	DP_FCITEMS11	Demand Planning, Define Forecast Elements, Forecast Items, Maintain Forecast Items, Statistics	View item forecast statistical information that includes accuracy statistics, model-specific forecast parameters, and descriptive statistics.
Copy Forecast Item	DP_FCITEMS_COPY	Click the Copy button on the Maintain Forecast Items page.	Create a new item by copying the attributes of an existing item.
Delete Forecast Item	DP_FCITEMS_DELETE	Demand Planning, Process Deletions, Forecast Items	Delete forecast items from the forecast view.

Setting Up General Data for Forecast Items

Access the Maintain Forecast Items page.

Template Item	Displays if the current item is a template item. A template item is a type of forecast item that acts as a model or pattern by supplying default field values for other forecast items that are associated with the same view level that you create. You must create templates for each level of the view.
Update to IPP (update to PeopleSoft Inventory Policy Planning)	Select to indicate that this forecast item should be updated when you publish a forecast. Then, when you generate an inventory policy by using this forecast view, the system uses the publish records to determine which items to include in the policy generation. If you do not select to update the item values, the item is not included in the new inventory policy.
Next Level Item	Displays the forecast item key at the next level up in the forecast view hierarchy. The system summarizes the demand for the current level into this forecast item. The field is display-only.
Weight Profile	Select a profile to use for this forecast item. You define weight profiles within a calendar to indicate the relative importance of demand for an item. The system uses the weights to distribute data into different period buckets.
Rounding Decimals	Enter the number of rounding decimals for numeric values, such as forecast or demand quantities, that this forecast item uses. For example, you can round to tenths (.01- two decimal places) or to hundreds (.001- three decimal places). You can round up to four decimal places. Note. Rounding decimals for PeopleSoft Demand Planning can differ from those that other PeopleSoft applications use.
Forecast Analyst	Enter the user who is responsible for developing and adjusting the statistical forecast. You can enter up to 20 characters. The default value for this field comes from the template record.
Copy	Click to create a new item based on the attributes of this item.

Defining Item UOM Attributes

Access the Units page.

The initial default data is derived from the item template. If you are defining the conversion factor for a UOM group, you must first define the UOM group. If you are creating a new item, you must first define the user data by creating user-defined fields.

Values that you define for the forecast items are applicable to the item at the level defined in the Level field.

Click the Forecast Item UOMs link to set up UOM conversions and assign the item to a UOM group.

Units/Conversion Factors

Base Unit	Select a UOM. All demand and forecast quantities are stored in this unit. This unit is also the UOM that is associated with all prices and costs. The system obtains the default value for the field from the template record. This is a required field.
Weight	Enter the weight of the forecast item. The system obtains the default value for the field from the template record. Select a UOM from the corresponding drop-down list. The system requires a UOM if you enter a weight value.
Volume	Enter the amount of space that the forecast item occupies, such as cubic yards or square inches. The system obtains the default value from the template record. Select a UOM from the corresponding drop-down list. The system requires a UOM if you enter a volume value.
Next Level Conversion Factor	Enter a value that converts the base UOM for the forecast item to its parent item UOM at the next-highest level in the view structure. The system obtains the default value from the template record. The UOM for the next level appears next to the conversion factor. This is the UOM for the item that appears in the Next Level Item field on the Forecast Items page.

Standard Price/Cost

Use this group box to enter monetary values for the forecast item. Enter the static price in the Standard Price field and the static cost in the Standard Cost field. You can use this value for displaying or publishing forecast items. This information also serves as the default value for any period where there is no time-phased price or cost available. The system obtains default values from the template record.

The Average Price field is display-only. It is generally the price of an item over a period of time. The system calculates the value during period-end processing and extracts the number of periods used to calculate average price from the price/cost periods on the forecast view.

Utilization Type

Utilization Group	Enter a group to which you want this item group associated. Utilization groups indicate how items are maintained.
Utilization Type	Enter a code in which you want to place this item. Also known as a utilization code, you generally use this as an inventory indicator to determine the contribution of the item to the overall inventory value.

Creating and Maintaining UOMs for Specific, Individual Items

Access the Forecast Item UOMs page.

Values that you define for forecast items are applicable to the item at the level that is defined in the Level field.

Click the Unit link to define UOM attributes that are associated with an item.

To Unit

Enter a UOM for which you want to define item-specific UOM conversions. During UOM conversion processing, the system first checks for item-specific UOMs before using weight, volume, or generic UOMs.

Conversion Factor

Enter a value for converting from the base unit to the to unit.

See Defining UOM Conversions.

UOM Group (unit of measure group)

You can categorize units of measure into groupings for different kinds of measurements. Use UOM groups to associate units of measure with certain types of quantities. You can also publish forecast for items based on the UOM group to which they belong. Use the UOM Groups page to create groups.

Entering Forecast Item Control Parameters

Access the Control page.

Control Group	Select a group to associate with the forecast item. The group controls several major forecast processing options, including forecast development, projection, and tracking. This is a required field.
Seasonality Group	Select a group that provides the seasonality profile for when you generate a forecast for this forecast item. When you select a group, other seasonality fields become available for use. Seasonality is a repetitive pattern of demand for an item during certain periods of a forecast. You can use a group for items where there is not enough demand for forecast items. This field is optional.
Uses Seasonality Profile	Select to indicate that the forecast item derives its seasonality profile factors from the selected seasonality group.
Contributes to Seasonality Profile	Select to indicate that the forecast item is a contributor in the creation of the seasonality profile. This means that the demand for the forecast item is accumulated with all other contributors to determine the profile for the seasonality group.
Life Profile	Displays the life profile for the item in this forecast view.

See Also

Setting Up Seasonality Profile Groups

Setting Up Forecast Item Model Controls

Access the Model Control page.

The system automatically calculates model control data. You do not typically change the data unless you create a new item or you want to manually control or reset how an item is forecasted.

Forecast Model

Forecast Model	Models are forecasting techniques that you use to analyze item forecasts. Values include: Adaptive Exponential Smoothing: A derivative of exponential smoothing. The difference with this model is that the alpha value systematically changes from period to period to allow for pattern changes in the historical data. Box Jenkins: A way of decomposing a time series. It is a multistep model-building strategy for analyzing and forecasting time series data by looking for an adequate model in the group of models that are known as auto regression moving average and auto regression integrated moving average processes. Census X11: A refinement of the seasonal-decomposition model. It seasonally adjusts and decomposes forecast data through a series of predefined steps: seasonal, trend, cycle, and random or irregular. Croston: Processes sporadic data. Double Exponential Smoothing-Brown: Attempts to create a linear equation. The model performs two simple exponential smoothing forecasts and then adjusts for the linear trend in the data. It is similar to double exponential smoothing in that the goal is to create a linear trend, but it does so without adding additional parameters to the equation. Double Exponential Smoothing-Holt: A model that is similar in principle to simple exponential smoothing. It calculates alpha (the level component) to measure the level that is in the forecast. It also adds the parameter gamma (the trend component) to create a linear trend in the forecast. Exponential Smoothing: Uses historical and fitted data to generate the next forecast. The forecasting technique creates the fitted line that the system uses as a base for the forecast. Holt-Winters (Additive/Multiplicative): An exponential smoothing technique that incorporates growth and seasonality into the forecast by producing seasonal lift factors for each seasonal period. This model's components include: Alpha, a smoothing constant to update the level. Gamma for the slope or trend. Beta for the seasonal components. Linear Regression: Uses an equation to analyze the relationship between two or more quantitative variables in order to predict one from the others. The model measures the relationship between two variables: X and Y. Moving Average: The average of a time series over a specific number of preceding periods. When the system adds a new value, it drops the last value from the calculation, so that the specific number of preceding periods remains a constant. No Model: A forecast model is not selected. Triple Exponential Smoothing-Brown: Implemented on data by showing a quadratic trend over time, this model is beneficial for data that has steep growth or decline. Weighted Moving Average: Moves averages of moving averages. Rather than replace the oldest observations within the data, the model replaces the oldest moving average with the most recent moving average.
Calculation Type	Select a type that controls when the system calculates new values for a forecast item. Calculation types include: No Calculation: Does not include this item during mid-period processing. During period-end processing, the system reoptimizes the forecast item. Best Fit: Optimizes the item against all models specified on the forecast model. Model components and smoothing constants are also recalculated. Reoptimize: Calculates the forecast by using the current model and its components.
Moving Average Periods	Displays the number of periods that the system uses during forecast calculations when you select Moving Average as the model type for the forecast item. The system updates this field with the number of periods that provides the minimum error moving average. Values are between 0 and 12. The Item Simulation process tries a set of moving average period values. While the minimum error moving average model is determined, the system stores this set on the control group.
Suspended Item	Appears if the system considers this item to be suspended. Suspended items are those that have zero demand for the number of periods that are specified on their control groups. The system defines these items automatically by selecting the check box.
Prorate	Select to indicate that the system should prorate the item's forecast to its children. This provides item-by-item control over proration.
Inhibited Item	Select to set the forecasts for the item to 0. You can inhibit the forecast of an item if it has erratic demand and you do not want a forecast for the item. You can also inhibit an item because it is a special order item or discontinued. If demand is subsequently posted to an inhibited item, the system creates a message for the review. If the system detects an inhibited item during period-end processing, it: Resets the adjusted demand that is filtered (demand process action code 3) for the period to the actual demand. This removes any prior filtering from the item's adjusted demand. Sets the statistical, prorated, and adjusted forecast to zero for all periods, past and future. Sets the Forecast Adjustment field and the process action code to zero for all periods. Sets the statistical, prorated, and adjusted forecast deviation values to zero. Sets all model parameters and accuracy statistics to zero, removes the forecast model, and sets the calculation type to No Calculation. Sets the suspended item setting to false.

Effective Period

Historical Periods	Displays the number of periods of historical demand that exist for the forecast item. The system updates the field automatically when you transfer in demand values or make manual adjustments.
Effective Demand Periods	Enter the number of historical demand periods that you want to use for the model reset option when you simulate or calculate item forecasts. Use this field to exclude older, possibly unrepresentative historical demand data from model optimization. The number must be less than or equal to the number of historical demand periods available for this item.
Forecast Effective Year/Period	Enter the period and year from which the system generates the forecast. This makes it possible for you to inhibit forecast generation until a future period for new items.

Zero Demand Defaults

Enter the values that you want to use for items with zero demand to assist in generating an initial forecast. These models are available for supporting zero demand:

Holt-Winters.
Linear Regression.
Exponential Smoothing.

Note. For items with demand, the values of the smoothing weights do not affect the forecasted values.

Alpha (Smoothing)	Enter a value that represents the level smoothing constant for the exponential smoothing method family.
Beta (Seasonal)	Enter a value that represents the seasonal smoothing constant for the exponential smoothing method family.
Gamma (Trend)	Enter a value that represents the trend smoothing constant for the exponential smoothing method family. This is a distribution that is used for continuous random variables, which are constrained to be greater than or equal to zero. It is characterized by two parameters: shape and scale. The gamma distribution is often used to model data that is positively skewed.
Slope	Enter a value that represents the change in the dependent variable (Y) per unit change in the independent variable (X).
Intercept	Enter a value that represents the constant in the regression equation. This is the point where a regression line intercepts the vertical axis if the horizontal axis has a true zero origin.
Final Level	Enter a value that represents the exponential smoothing value.
Final Trend	Enter a value that represents the final trend value in the double-Holt and Holt-Winters exponential smoothing models.

Note. When calculating the forecast for items with zero demand in Holt-Winters models, the system uses the Final Level and Final Trend values from the forecast item. If these values are not defined, then the system checks for these values for the template item at the same level in the forecast view. If these values are not defined, then the system checks for these values for the control group. If the system finds no values defined for these fields, then it uses the first historical period’s adjusted demand as the Final Level and 0 for the Final Trend.

Displaying Forecast Item Model Tracking

Access the Model Tracking page.

All fields on this page are display-only.

Tracking Signals

The use of tracking signals is a forecasting technique that detects biases in the forecast and provides an early warning of an unstable forecast. Use the signals to evaluate structural errors that exist within a forecast by identifying situations where a forecasting model is over or under forecasting.

Note. A positive value indicates that the system is under forecasting and a negative value indicates that it is over forecasting. As a general rule, the only time that a forecast should be adjusted is when the tracking signal is at + or −.5 or greater.

Current

Displays the tracking signal value for the current time period.

1 Period Back - 5 Periods Back

Six tracking signals are associated with each forecast item. These signals correspond to the six most recent historical periods. At the period end, the system updates the errors and calculates a tracking value for the period.

The tracking value is always a number in a range from zero to one. The closer it is to one, the more likely it is that the forecast is biased.

When the tracking value exceeds the bias test that is stored on the control group, the system activates the tracking signal for the current period. When the number of consecutive signals exceeds the bias signal limit, the system indicates the problem on the error log and automatically resets the model.

Forecast Deviation

Forecast deviation is a statistical method that measures the dispersion of a data series and displays the average deviation between historical forecast data and actual demand. The more dispersed the data is, the larger the standard deviation that appears for each forecast type in this group box. Generally, the lower the value is, the more accurate the forecast.

PeopleSoft statistical forecast deviation is not computed in the same manner as the industry standard forecast deviation. Standard deviation uses a single series of demand values to arrive at a fixed average demand value. This computation then measures the deviation between the actual demand and the average value. With statistical deviation, the system uses two series of data: one for actual demand values, and the other for forecasted values.

To calculate the value, the system averages two sets of data. It looks at each period and computes the difference between the historical value and the actual demand value for that period. Then, it averages those values to arrive at the statistical deviation. This provides you a measurement of how well you forecast for items.

Statistical	Displays the forecast deviation value of the statistical forecast. A statistical forecast is one that the system develops at each level of the view structure for each forecast item that is independent of any forecast adjustments or proration.
Prorated	Displays the forecast deviation value for the prorated forecast. Proration allocates the item (group) forecasts for each future period. It makes the allocation by period to the forecasts of the related items (children) at the next lower. The allocation is prorated, based on the future forecasts of the children, and the effect is to make the aggregate forecast of children equal to the group forecast.
Adjusted	Displays the forecast deviation value for the adjusted forecast.

Best Fit Accuracy Statistic

Best-fit analysis is an automated system function that searches through various forecasting techniques, methods, and models to find a model that best fits a particular data set. The Best Fit Accuracy Statistic field displays the accuracy statistic that the system uses to calculate the best forecast and displays this value in the Accuracy Statistic field. This value indicates how well the model performs in the planning horizon.

Each accuracy measurement is based on different statistical criteria. Understanding how and why the system applies an accuracy measurement helps you to determine which forecast model best meets the business needs. Use accuracy statistics and forecast models during item simulation. You maintain accuracy statistics using the control group.

See Forecast Model Accuracy Measurements.

Mean Error

The Mean Error field displays the average error value. The mean error is less reliable in some cases than other accuracy statistics, because there is the risk that large outliers can cancel each other out, producing a mean error near zero, indicating a perfect fit. For example, positive and negative error values could produce an average of zero, which may not be an accurate description of the overall fit of the forecast.

Mean Absolute Error

The Mean Absolute Error field displays the absolute value of the errors in a forecast. The error rate is calculated separately for each statistical, prorated, and adjusted forecast, and for each of their evaluated equivalents. The Mean Absolute Error (MAE) is similar to the mean error, except that the MAE considers the absolute values of the errors. It takes negative values and replaces them with their absolute (positive) values. This model de-emphasizes large outliers, because negative and positive results cannot cancel each other out. A zero MAE represents a perfect fit.

Displaying Forecast Item Seasonality Profiles

Access the Seasonality page.

Profile factors identify the weight index assigned to each forecast period to take into account seasonal fluctuations in demand. The factor or index typically measures the percentage difference between the base demand and expected actual demand in the period. The system generates profiles only for items that use the Holt-Winters and Census X11 seasonal models.

The Seasonality Type field displays the seasonality type. The values are Additive and Multiplicative.

To differentiate between the two types, suppose that sales for product X repeatedly peaks every year in the months of November and December. Each year during December, the sales of X increase by 200,000 pesos. Each year, you add 200,000 pesos more to the annual average of product X sales in December. This seasonality is additive. However, suppose that sales of X increase by 20 percent during December, or some other factor. Then the seasonality is multiplicative.

Maintaining Forecast Item Price and Costs

Access the Prices/Costs page.

Use these time-phased items prices and costs in inquiries, reports, and in publishing to display or output the forecast and demand data as a value rather than a quantity. The forecast item's price and cost appear according to year and period. If a forecast period does not have a specific price or cost value, the standard price and cost that is established on the Units page is the default. You can change the price or cost for the forecast item.

Note. Before you enter a new price or cost for the forecast item, you must establish the number of periods for which this price or cost is effective in the Periods to Copy Forward field. For example, if you require a new cost to apply to the current and next four periods, enter 4. You can only roll period price and cost values forward to periods that do not exceed the current year. For example, if you only have six periods remaining in the year, you cannot roll price and cost values forward seven periods.

Displaying Other Data for Forecast Items

Access the Other Data page.

The system updates values in this page automatically. You cannot change those values.

Actual	Displays the actual demand for the item in the current period. The system measures this number in the forecast item's base UOM. The system defines the current period as the forecast start period plus one. This information is typically imported from another system at the end of each period. Any negative or positive number is a valid value.
Adjusted	Displays the adjusted demand. This represents the result after adjustments are made to the actual demand for the current forecast period. These can be adjustments made by the system, using filtering, for example, or by management overrides. The system uses the adjusted demand (not actual demand) in resetting models on the Simulation Options page and in the recalculation of model components during period end.
Value	Displays the value for the adjusted demand. The system uses the adjusted demand value to calculate the item's average price for the current period.
Demand Process Action	Displays the code that the system uses to explain why the current demand adjustment is made. Values include: Direct: A manual adjustment to either adjusted or actual current demand. Not Adjusted: Applies to actual demand only; changing this value indicates that you are correcting it, as opposed to adjusting it.
Last Reset Year	Displays the last year for which the forecast for the item was calculated.
Last Reset Period	Displays the last period for which the forecast for the item was calculated.
Current Model Year	Displays the year when the forecast model was last changed.
Current Model Period	Displays the period when the forecast model was last changed.

Maintaining User Period Data for Forecast Items

Access the User Period Data page.

Use this page to view, add, or override forecast data contained in user period fields for an item. You define period data fields using the forecast view. The system adds these fields to the forecast item record enabling you to store additional data that is not supplied by the standard set of fields.

Forecast data for the item appears for each period and year of the current forecast view model.

Maintaining User Data Fields for Forecast Items

Access the User Data Fields page.

User fields contain data that is specific to the forecast item. Each set of user-defined fields is identified by a user data code. Each forecast view is associated with a user data code. This means that all forecast items within a single view share the same set of user-defined fields.

You use user data fields to construct the key for the forecast item at each level within the forecast view, as well as provide location-specific information. Multiple views can use the same user data code. You cannot change key fields.

Field Name	Displays the field name that is defined by the user data code that is associated with the forecast view on the Maintain User Field Codes page. These field names cannot be changed or added to on this panel.
User Field	Enter a code or value, or select a code or value from the list of values.
Key Field	Displays the key field if the system considers this field as a required field. Key fields provide descriptive and control data at each level of a forecast view.
Field Type	Displays whether the field is a character field or a numeric field.
Field Length	Displays the length of the field. This is the number of characters (numeric or alphanumeric) that you can enter in the field.
Invisible	Displays whether the field is invisible. When fields are invisible, the system maintains the key's integrity for the field without using the invisible field as part of the key. You define a field as invisible when you define the levels in a forecast view. Use the Define Forecast Views Level page on the Define Forecast View menu to define the level to which the field is not visible. The system uses an invisible field for a greater granularity in performing processes, such as cross-view reconciliation.

Viewing Item Forecast Statistics

Access the Statistics page.

This page displays the current forecast model that controls statistical processing for the item. The model provides standard forecast accuracy measures. These are measurements of how accurate a forecast model predicts the forecast. These measurements appear in the Accuracy Measure field.

The system bases each accuracy measure on different statistical criteria. Depending on the forecasting requirements, these measurements provide you with a meaningful measure of model accuracy.

The Value field displays each accuracy measure's level of accuracy.

See Also

Forecast Model Accuracy Measurements

Deleting Forecast Items

Access the Delete Forecast Items page.

Use this page to define criteria for deleting forecast items and to submit the run control for deleting the items. After you have selected the deletion criteria, use these buttons to review and run the delete process:

Preview

Click to view items that match the criteria you entered in the Selection Criteria grid box. When you click the button, the system displays the Preview grid box with the forecast item and its level.

Run

Click to use the batch process defined in the Run Control ID field to run the deletion process. Use this button to delete large numbers of forecast items.

Delete Now

Click to delete a small group of forecast items immediately.

Warning! You should only use this button to remove small numbers of forecast items. When processing large volumes, the system might issue an error message when you delete them immediately. Use the Run Control ID to submit a batch process to delete large volumes of forecast items.

See Also

Deleting Views

Defining Calculation Codes for Forecast Items

This section provides an overview of calculation codes, code elements and operators, and discusses how to create calculation codes.

Understanding Calculation Codes

Calculation codes represent mathematical operations. The codes are part of the run specification that the system uses to process forecast data from specific periods. For example, by using the codes you can increase or decrease values that appear in target fields, such as standard cost, error ratios, or forecast effective periods.

The system uses the codes when:

Calculating forecasts.
Processing period-end calculations.
Making mass changes to forecast items.

Use the Control Data page on the Define Forecast Views feature to assign calculation codes for forecast calculations and period-end processing. Use the Update Operations page in the Mass Change Specification menu to assign calculation codes for item maintenance. You can assign any calculation code to any of the three processes.

The system applies calculation code parameters to all items in the process that you run, with the exception of Item Mass Maintenance, where you can apply selection criteria, restricting the items available for update.

Elements of Calculation Codes

When you set up a calculation code, you define these code elements:

Operators that determine the type of mathematical computations that the system uses when running specifications.
Targets that determine where the result of the calculation is stored.

Targets can be any field available in the drop-down list or a variable that the system uses in another operation in the same calculation code. Target variables appear as Variable1, Variable2, and so forth. This enables you to store the results of a specific variable in one row of the calculation code for use in calculating a subsequent row.

Note. When you include target variables in the calculation code, the system uses the full range of historic and future periods that are defined on the view to perform the calculation.
Sources that determine where source data is extracted from.

This data is the data against which the system performs calculations and then places the results into the Target field. Depending on the operator that you select, the system validates the source data-entry requirements. These source types are available:
- Any field that is stored on the DP_FCITEMS or DP_FCITEMDATA records and that is not considered a system field.
- A variable that you create in another line of the same calculation code.
- A fixed value or constant.
- Another calculation code.
Values that determine the extent of the breadth of the calculation.

The system prompts you to enter these values.
Periods that determine the periods and years to process in the calculation.

Calculation Code Operators

This table describes calculation operators that are available for calculation codes, their actions, and the operations that they perform:

Calculation Operator	System Action	Operation	Requirements
Absolute.	Returns the absolute value of the source row.	Target = ABS(Source1).	The system requires Source1 and defines it as a field name or variable.
Add Constant.	Adds a constant to the source row.	Target = Source1+ Source2.	The system requires Source1 and defines it as a field name or variable. It also requires Source2 and defines it as a value.
Add Rows.	Adds the values in two rows.	Target = Source1+ Source2.	The system requires Source1 and Source2 and defines them as field names or variables.
Compare.	Compares two rows and returns a new row with True or False.	If Source1 operator = Source2, then Target = True. Else. Target = FalseEnd If.	The system requires Source1 and Source2 and defines them as field names or variables. It also requires Source3 and defines it as a fixed set of operators (=,<, >, <=, >= or <>).
Constant Fill.	Fills each cell in a new row with a constant.	Target = Source.	The system requires Source1 and defines it as a value.
Days - Calendar.	Returns the number of calendar days in each period.	If you do not enter from or to periods, the system processes from the first historical period through the last future period. Target = Number of days in period.	A source is not required.
Divide by Constant.	Divides the source row by a constant.	Target = Source1÷ Source2.	The system requires Source1 and defines it as a field name or variable. It also requires Source2 defined as a value.
Divide Rows.	Divides the source row by a second divisor row.	Target = Source1÷ Source2.	The system requires Source1 and Source2 and defines them as field names or variables.
Exponent.	Computes a (natural log base) exponentiated by the values in the source row.	Target=Exp(Log(Source1)).	The system requires Source1 and defines it as a field name or variable.
Include Calculation.	Performs another calculation.	Perform calculations that are defined in another calculation code.	The system requires Source1 and defines it as a calculation code name.
If Then Else.	If values of the source row are nonzero, it uses the Then row values. Otherwise, use the Else row values.	This operation is performed for each record element. If Source1 <> zero, Target = Source2. Else. Target = Source3 End If.	The system requires Source1, 2, and 3 and defines them as field names or variables.
Linear Trend.	Finds the best straight line fit for the source row.	Call LSQFit with source data and plot best straight line target results from this.	The system requires Source1 and defines it as a field name or variable.
Log Values.	Returns the natural log of the values in the source row.	Target = Log(Source1).	The system requires Source1 and defines it as a field name or variable. The base for the log is always the natural log.
Maximum against Constant.	Returns the maximum of either the source row or a constant.	Target = Greater of Source1 and Source2.	The system requires Source1 and defines it as a field name or variable. It requires Source2 defined as a value.
Maximum between Rows.	Returns the maximum of two source rows.	Target = Greater of Source1 and Source2.	The system requires Source1 and Source2 and defines them as field names or variables.
Minimum against Constant.	Returns the minimum of either the source row or a constant.	Target = Lesser of Source1 and Source2.	The system requires Source1and defines it as a field name or variable. It requires Source2 defined as a value.
Minimum between Rows.	Returns the minimum of two source rows.	Target = Lesser of Source1 and Source2.	The system requires Source1 and Source2 and defines them as field names or variables.
Multiply and Add Rows.	Returns the source row 1 multiplied by a constant, plus source row 2 multiplied by a constant.	Target = (Source1 × Source3) + (Source2 × Source3).	The system requires Source1 and Source2 and defines them as field names or variables. It also requires Source3 defined as a fixed value.
Multiply by Constant.	Multiplies the source row by a constant.	Target = Source × Source2.	The system requires Source1 and defines it as a field name or variable. It also requires Source2 defined as a value.
Multiply Rows.	Multiplies two rows.	Target = Source1 × Source2.	The system requires Source1 and Source2 and defines them as field names.
Offset.	Shifts the source row data ahead or behind by a fixed number of periods.	If Source1(n) not blank, then Target(n + Source2) = Source1(n). Else. Target(n + Source2) = Source3.	The system requires Source1 and defines it as a field name or variable. It also requires Source2 and Source3 to be defined as values.
Percent.	Divides the source row by the contents of a second divisor row.	Target = (Source1÷ Source2) × 100.	The system requires Source1 and Source2 and defines them as field names or variables.
Round.	Rounds the source row using standard rounding rules (up if greater than .5 and down if less than .5).	Target = Round (Source1, Source2).	The system requires Source1and defines it as a field name or variable. It also requires Source2 and defines it as a value. This represents the decimal precision (number of places) for rounding. For example, suppose that Source1 equals 1.333, the rounding result is 1.33. If Source1 equals 1.666, the rounding result is 1.67.
Round Down.	Rounds down the source row.	This is the same as the round function, but the results are always rounded down to the decimal precision that Source2 specifies.	The system requires Source1 and defines it as a field name or variable. It also requires Source2 and defines it as value. This represents the number of places for rounding. For example, suppose that Source1 equals 1.333, then Result equals 1.33. If Source1 equals 1.666 Result equals 1.66.
Round Up.	Rounds up the source row.	This is the same as the round function, but the results are always rounded up to the decimal precision that Source2 specifies.	The system requires Source1 and defines it as a field name or variable. It also requires Source2 and defines it as a value. This represents the number of places for rounding. For example, if Source1 equals 1.333, the rounding result equals 1.34. If Source1 equals 1.666, the rounding result equals 1.67.
Subtract Constant.	Subtracts the constant from source row.	Target = Source1 − Source2.	The system requires Source1 and defines it as a field name or variable. It also requires Source2 and defines it as a value.
Subtract Rows.	Subtracts one row from another.	Target = Source1 − Source2.	The system requires Source1 and Source2 and defines them as field names or variables.
Truncate.	Truncates the source row.	Truncate Source1 to the decimal precision that Source2 specifies.	The system requires Source1 and defines it as a field name or variable. It also requires Source2 to be defined as a value.
Unit of Measure.	Returns a UOM conversion rate.	Source1 is a UOM. The Target is the conversion rate between the forecast item's base UOM and Source1.	The system requires Source1 and defines it as a valid UOM.

Pages Used to Define Calculation Codes for Forecast Items

Page Name	Object Name	Navigation	Usage
Define Calculation Codes	DP_CALCCODES	Demand Planning, Define Forecast Elements, Forecast Items, Define Calculation Codes	Create calculation codes for use in forecast calculations, period-end processing, and item mass maintenance.
Define Selection Criteria	DP_CALCCODES_SEC	Select a value in the Calculation Operator field on any Define Calculation Codes page tab and click the Add button.	Define selection criteria, including target and source fields, offset periods, and period data, for the calculation operator.
Delete Calculation Codes	DP_DELETE_CALCODES	Demand Planning, Process Deletions, Calculation Codes	Remove calculation codes from the PeopleSoft Demand Planning system.

Creating Calculation Codes

Access the Define Calculation Codes page.

A forecast calculation code contains one or more calculation operators. After you define the calculation operators, you can resequence the operators by entering new sequence numbers and then click the Sequence column heading.

Defining Calculation Operators

To add a new calculation operator, use the Calculation Operator field to select an operator and then click the Add button. To edit an existing calculation operator, click the Edit Calculator Operator button. The system displays the Define Selection Criteria page, where you define calculation parameters for the operator.

To define a calculation operator:

Use the Target field to select where you want to place the calculation results.
Use the Source 1 and Source 2 fields, if necessary, to define the components for calculations.

Depending on the calculation operator that you select, the system might require more than one source value. The system prompts you for additional values when they are needed and displays messages for values that are not valid.
Use the Source 3 field to designate values for use in calculating Source 1 and Source 2 fields.

These values determine the factor by which the calculation operator is calculated. The system prompts you when it requires values for this field.
Define any offset periods that you want to include in the calculation process.

You can use offset periods or enter a period and year to define the horizon for the calculations. To use an offset range, enter +1 to +12 or −5 to +5 in the From and Through fields. Zero is not a valid offset. The system assumes +1 to be the first forecast period, with −1 the previous historical period.
Use the Period/Year field to define a range of periods to use in calculations.

Period fields are not required, unless this is stated previously in the calculation operator definitions. The system uses the full range of historic and future periods that is defined on the view record if periods are not defined

See Also

Calculation Code Operators

Elements of Calculation Codes

Refreshing Forecast Items

This section provides an overview of item refresh and discusses how to:

Define refresh specifications.
Refresh items.

Understanding Item Refresh

Use the Forecast Item Refresh process (DP_FCREFRESH) to refresh items. When the system refreshes forecast items, it extracts information from PeopleSoft Inventory, Billing, and Order Management records and updates the item data in PeopleSoft Demand Planning, keeping the item updated with the most current data.

To refresh forecast items, define a specification, then create a run control ID to process the specification. Specifications determine which fields of data to refresh, and define the selection criteria for specific items to process.

This table lists fields that the system refreshes and the records from which the refresh information originates:

Field to Refresh	Description
SETID	Refreshed from either PS_PROD_ITEM or PS_MASTER_ITEM_TBL (depends on the key on the forecast item).
DP_DESCRIPTION DP_FCITEMCAPTION	The system processes these fields at the end of refresh processing and after all user-defined fields are updated.
CATEGORY_ID INV_ITEM_GROUP INV_PROD_FAM_CD	Refreshed from PS_MASTER_ITEM_TBL.
DP_VOLUME DP_VOLUMEUOM DP_WEIGHT DP_WEIGHTUOM INV_ITEM_COLOR INV_ITEM_TYPE UPD_ID	Refreshed from PS_INV_ITEMS.
CONVERSION_RATE	Refreshed from PS_INV_ITEM_UOM.
DP_FORECASTANALYST ITEM_FIELD_C30_A-D ITEM_FIELD_C1_A-D ITEM_FIELD_C10_A-D ITEM_FIELD_C2 ITEM_FIELD_C4 ITEM_FIELD_C6 ITEM_FIELD_C8 ITEM_FIELD_N12_A-D ITEM_FIELD_N15_A-D SOURCE_CODE	Refreshed from PS_BU_ITEMS_INV.
UTILIZ_CD UTILIZ_GROUP	Refreshed from PS_BU_ITEM_UTIL_CD.
DP_STANDARDCOST CM_UNIT_COST	The system determines cost methodologies by SELECT CM_METHOD FROM PS_CM_ITEM_LED_VW.
DP_STANDARDPRICE	Refreshed from PS_PROD_PRICE.
DP_PERIODPRICE	The system updates the current period with the standard price. The Roll Forward Price/Cost field updates price data for the number of future periods that you enter in the field. For example, suppose that a cost is supplied for period 03/2000 and the number of periods to roll forward is set to 3, periods 03, 04, 05, and 06 are set to the given cost.
DP_PERIODCOST	The system updates the current period with the standard cost. The Roll Forward Price/Cost field updates price data for the number of future periods that you enter in the field.
LOCATION	Refreshed from PS_BUS_UNIT_TBL_OM.
CURRENCY_CD CORPORATE_CUST_ID SUBCUST_QUAL1 SUBCUST_QUAL1 CUST_FIELD_C1_A-D CUST_FIELD_C2 CUST_FIELD_C4 CUST_FIELD_C6 CUST_FIELD_C8 CUST_FIELD_C10_A-D CUST_FIELD_C30_A-D CUST_FIELD_N12_A-D CUST_FIELD_N15_A-D	Refreshed from PS_CUSTOMERS record.
PM_REGION PM_DIVISION PM_TERRITORY CLASSIFICATION	Refreshed from PS_CUST_HIERARCHY record.
CUST_CHANNEL	Refreshed from PS_CUST_PM_CHANNEL.
CUSTOMER_GROUP	Refreshed from PS_CUST_CGRP_LNK.
ITEM PROD_BRAND PROD_CATEGORY PROD_FIELD_C1_A-D PROD_FIELD_C10_A-D PROD_FIELD_C30_A-D PROD_FIELD_C2 PROD_FIELD_C4 PROD_FIELD_C6 PROD_FIELD_C8 PROD_FIELD_N12_A-D PROD_FIELD_N15_A-D	Refreshed from PS_PROD_ITEM.
PRODUCT_GROUP	Refreshed from PS_PROD_PGRP_LNK.
UD01 - UD50	During processing of the levels, the system reads the valid to level for each user-defined field to determine the refresh level. The system refreshes user-defined fields from the planning fields to which they are mapped. The system does not refresh fields that are not mapped to a planning field.

Pages Used to Refresh Forecast Items

Page Name	Object Name	Navigation	Usage
Refresh Specifications	DP_REFRESH_SPEC	Demand Planning, Define Forecast Elements, Forecast Items, Refresh Specifications	Define refresh specifications for items and fields of data from PeopleSoft Supply Chain Management applications.
Execute Refresh	DP_FCREFRESH	Demand Planning, Define Forecast Elements, Forecast Items, Execute Refresh	Refresh items.

Defining Refresh Specifications

Access the Refresh Specifications page.

Specification ID	Displays the specification that the system uses to retrieve this set of refresh data. You can use specifications over and over to refresh items on a regular basis.
Roll Price/Cost Periods	Enter the number of periods for which this price or cost is effective. For example, if you require a new cost to apply to the current and next four periods, enter 4. You can only roll period price and cost values forward to periods that do not exceed the current year. For example, if you have only six periods remaining in the year, you cannot roll price and cost values forward seven periods.
Refresh Custom Fields From	Select the PeopleSoft Supply Chain Management records from which you want to refresh custom fields. These fields reside on both records, but the data may be different from record to record. Record values for the field include Master Item Table and Business Unit Items Inventory.
Refresh Parents	Select to update the parent items of each forecast item when the system refreshes the item. If you do not refresh parent items, then the system only refreshes items at and below the level that you define in the Refresh Level field.
Refresh Level	Enter the level of the view that you want to refresh. The system refreshes this level and all lower levels in the view. For example, if you select a level in the a Level field and then enter 3 in the Criteria, field, the system refreshes item fields at level three and below. If you select the Refresh Parents check box, the system refreshes all levels of the view.
Items to Select	Use this grid to define selection criteria. This criteria limits the items that the system refreshes. You can target a specific range of items or all items. See Defining Selection Criteria.
Key Field	Indicates whether a field is a key field for a forecast view hierarchy level. Each view and level combination contains a definition of the fields that make up the components of the forecast item key for that level. Key fields are defined for forecast view when you define levels. This is a display-only field. Note. The system does not refresh key fields.
Field Name	Displays fields that the system refreshes when you use this specification to refresh items. These are the fields that are defined as in use. Use the Refresh Non-Value and Refresh check boxes to define how to refresh the field. After the system processes all the user-defined fields, it updates the DP_DESCRIPTION and DP_FCITEMCAPTION fields, if you select them for refreshing.
Planning Field ID	Identifies the PeopleSoft Demand Planning field to which you map data.
Refresh Non-Value	Select to update the field's value, even though the new value is an empty field or a zero. Use this option when you know that the new value is wrong or that you want to maintain a value in the field.
Refresh	Select to refresh the current PeopleSoft Demand Planning field with values from other PeopleSoft SCM application records.

Refreshing Items

Access the Execute Refresh page.

When the system refreshes a view, it locks it for the update and unlocks it after the process successfully completes. The system uses the IFIR function code when locking the view for refreshing and for writing a beginning and ending function audit record for the refresh. The system refreshes only non-key fields for the forecast item.

Making Mass Changes to Forecast Items

This section provides an overview of mass change and discusses how to:

Select items for mass change specifications.
Define mass change specification items and periods.
Process mass changes.

Understanding Mass Change

Use mass changes to apply item changes to multiple items at the same time. For example, you can add five percent to the price values for all items that are in the view, or you can update the average cost for a certain group of items that is in the view. The system stores specifications that you define for mass maintenance in the DP_MMSPEC_HDR record.

To make mass changes:

Create a specification for the items to which you want to make changes.
Select the records to include by using the Record Selection page.
Define the changes that you want to make to the items by using the Update Operations page.
Process mass changes by using the Mass Change page.

Pages Used to Make Mass Changes to Forecast Items

Page Name	Object Name	Navigation	Usage
Mass Change Specification	DP_MMSPEC_FILTER	Demand Planning, Process Forecast, Forecast Items, Mass Change Specification	Select items for mass change specifications.
Selection Criteria	DP_MMSPECSEL_SEC	Demand Planning, Process Forecast, Forecast Items, Mass Change Specification	Select specific criteria for making mass item changes. The system bases the available values on the value that you enter on the Record Selection page.
Update Operations	DP_MMSPEC_OPER	Demand Planning, Process Forecast, Forecast Items, Mass Change Specification, Update Operations	Define mass change specification items and periods.
Define Update Operation	DP_MMSPEC_SEC	Select a mass maintenance operator and click the Add button on the Update Operations page.	Define update operations for mass changes.
Mass Change	DP_MASSCALC	Demand Planning, Process Forecast, Forecast Items, Mass Change	Process mass changes. Run the Item Mass Maintenance process.

Selecting Items for Mass Change Specifications

Access the Record Selection page.

Specifications control how the system makes mass changes. Within the specification, you create data subsets that are made up of records that are contained in individual fields. Create the subset by establishing selection criteria for the field. For example, suppose that you want to limit the number of items or create forecasting data for a specific location, you can select a range of records to limit the Item Code or Location fields. Record selection enables you to control and filter ranges of data or types of data that are placed in the file that you want to publish.

See Defining Selection Criteria.

Defining Mass Change Specification Items and Periods

Access the Update Operations page.

Use the Update Operations page to view which operations belong to this specification. To enter new values, or change values, select a value in the Mass Maintenance Operator field and click the Add button. To edit a row of data, click the Edit Operation button.

The Sequence field indicates the order in which the system performs operations for mass change. You change the sequence by typing the new sequence number in the field and then click the Sequence column.

Select Mass Maintenance Operator value. The operator determines the action that the system performs during mass maintenance processing. You select the value using this page and complete operator parameters using the Define Update Operation page.

Value include:

Add
Blank
Calculation Code
Divide
Move
Multiply
Replace
Subtract

Periods Tab

Select the Periods tab.

After defining periods for each line of the mass change operation, you can add more changes by selecting another operator. When you run the mass change control ID for this specification, the system makes updates to the items for the periods that appear on this page.

Defining Update Operations

Access the Define Update Operation page.

Use the Define Update Operation page to create new operations for the mass change specification. Available fields on this page depend on the value you select on the Mass Change Specification page.

Operator

Select a value that determines the type of action that the system performs on the source and target fields. This table describes each value:

Operator	System Action	Requirements
Add, Subtract, Multiply, Divide	Using the operator, the system applies the operand to the target and stores the result. If you select a source, the system applies the operand to Source field value and stores the result in the Target field.	The Target, Source, and Operand fields are required.
Replace	The system replaces the Target field value with the operand and stores the result.	The Target and Operand fields are required.
Move	The system copies data from the Source field to the Target field.	The Target and Source fields are required and must be different fields. The system does not allow incompatible matches between fields, such as text to numeric, numeric to Boolean, and so forth.
Calculation Code	The Source field is a calculation code for the from period and to period.	The Target and Operand fields are unavailable for entry. Select a calculation code from the drop-down list for the Source field. The From Period and To Period fields are optional. If you leave the fields empty, the period range appears by default from the calculation code definition.

Target Field	Select a field in which to store the results of the update. The target values that appear can be any non-key fields that are on the DP_FCITEMS record, and are dependent on the operand that you select. For example, if you select a numeric operation, such as Add or Subtract, then the Target Field only includes numeric field types.
Operands	Enter a valid operand or click the Look up Operand button to select an operand. The system validates the data in this field against the data type of the Target Field.
Source Field	Select a field where data that you want to maintain resides. Like the Target Field, the source can be any non-key field on the DP_FCITEMS record and is dependent on the operand that you select. The system validates the field type against the operator.

When you select Calculation Code as the update operator, the From Period and To Period fields are available for entry. To determine which periods to process in the update, enter a valid period and year (PP/YYYY), or an offset range, such as +1 to +12 or −5 to +5 in the From Period and To Period fields. Zero is not t a valid offset.

The system assumes that 1 is the first forecast period, with −1 as the last historical period. To use the periods that are defined for the calculation code, leave the From Period and To Period fields empty. If periods are not defined for the calculation code, the update includes all periods for the forecast item based on the number of historical periods and future periods.

Note. You can change specific lines after you save the values on the Define Update Operations page.

Process Mass Changes

Access the Mass Change page.

Use this page to run the Mass Calculation process (DP_MASSCALC ) based on parameter settings in the mass change specification. After defining the specification, select an Adjustment Reason Code that identifies the reason for the adjustment to the forecast item. Define these codes by using the Adjustment Reasons option in the Define Forecast Elements component. You can also enter an Adjustment Comment to explain the adjustment.

Merging Forecast Item Demand

This section discusses how to merge forecast item demand.

Page Used to Merge Forecast Item Demand

Page Name	Object Name	Navigation	Usage
Forecast Items Merge	DP_FCITEMMERGE	Demand Planning, Process Forecast, Forecast Items, Merge	Merge forecast items by merging the demand from one forecast item into that of another forecast item.

Merging Forecast Items

Access the Forecast Items Merge page.

When you merge demand, you transfer the demand from one forecast item into that of another forecast item. You merge demand to accommodate organizational changes, such as a change in the number of warehouse locations or distribution centers, or changes to the boundaries of sales regions. You can also use it to enter new products or change product codes. Demand must exist for an item before you can merge item data.

Note. You can only merge demand for level one forecast items.

Forecast View	Select the view for which you want to perform the merge.
Source Item	Select the item from which you want to transfer demand quantities. You can select a forecast item by using its full description or its short description.
Target Item	Select the forecast item to which you want to transfer demand.
Source to Target Multiplier	Enter a multiplier value to multiply the source base UOM value when you populate the target. Using a multiplier, you can account for differences between the two fields. For example, if the source and target base units of measure are different, use this value to convert them appropriately.
Percent Demand to Transfer	Enter a percentage of demand that you want to transfer from the source item to the target item. The system reduces the demand for the source item by the same value that is transferred to the target item.
Delete Source Item	Select to delete the source item from the view when the transfer is complete. You might want to delete the source item, for example, if the products are basically the same, but the source item code has changed, or if one product supersedes another.