Answers to Study Questions
Setup Forecast Simulation
1 False. In QAD Enterprise Applications, Forecast Simulation can only use data from sales history information
2 To post sales history to the cph_hist field, set:
Menu Name: Sales Order Control
Field and Setting; Integrate with SA = Yes
3 Forecasts are calculated for monthly buckets or periods. However, Master Scheduling quantities are in weekly buckets. Note this difference between Master Scheduling and Forecast Simulation.
4 Forecast consume forward and consume backward help smooth production. When sales order demand exceeds forecast demand for a week, you produce enough to meet the greater sales demand. When forecast demand exceeds sales orders, you overproduce to meet the forecasted demand, but product remains in excess after the sales orders are shipped. Consume forward and backward takes the excess sales order demand of one week and applies it to the unused portion of the forecasted demand of either the periods before or after. It continues to search backward and forward until the specified number of previous and future periods have been examined, or the entire sales order quantity has been applied.
Menu Name: Sales Order Control
Field and Setting; Consume Fwd = number of periods to search for future demand
Consume Back = number of periods to search for previous demand
5 False. Only confirmed sales orders consume the forecast.
6 True. The template can only be modified until it has been used for a calculation.
7 Ending Year is the same as the Forecast Year = Rolling Forecast
Ending Year is before the Forecast Year = Yearly Forecast
8 The system can use up to five years of sales history.
9 Trend: A steady growth of demand. Typically a new product.
Seasonal: A cycle of greater and lesser demand, usually within a single year. Typically products like soft drinks and frozen desserts, which have increased demand during hotter months.
Horizontal: A steady demand for a product, with little variation. Typically a stable, well-established product.
Cyclical: Similar to seasonal demand, with greater and lesser demand, but follows a business cycle over several years. Difficult to predict. Typically real estate.
Process Forecast Simulation
1 Simulated Forecast Calculation.
2 At least one sales record is required to produce nonzero forecast quantity. When insufficient history exists to create a valid forecast, the detailed forecast record is created with quantities of zero and the item is printed out as insufficient.
3 False. Memo items and drop shipments are excluded from any forecast calculations.
4 True. You cannot produce a rolling forecast manually, only yearly forecasts. The rolling forecast requires forecasting for the next 12 monthly periods. Manual forecasts can only be created for January through December.
5 Run a forecast calculation for the first item, then use one of the two copy features to copy the results to the second forecast template.
a Menu Name: Single Item Simulation Copy
b Menu Name: Simulation to Simulation Copy
6 To obtain the original forecast quantities, run the original calculation again. After the calculation is run, the template and detail records are updated. Previous templates and records are deleted. This result makes it important to archive the original forecast or copy to another forecast ID before modifying forecast detail records.
7 When performing a Simulation to Simulation copy, if the item ranges of target and source are different, the target range is expanded. Targets are changed/overwritten, source remains unchanged.
8 Forecast simulation records are in monthly buckets. MRP calculations use weekly buckets. Simulation to Summarized Forecast can load the detail records into the MRP summarized records by:
a Autospread (default)—calculating daily averages, rolling these averages into weekly buckets, distributing weekly averaged totals throughout the month
b Load first week
c Load last week