PreviousNext
TRAC v8 Reference > Understanding How Forecast Overrides are Allocated > Examples Where Overrides Cannot be Allocated
Examples Where Overrides Cannot be Allocated

If you make forecast overrides to more than one level of the hierarchy, you can generate situations where the overrides cannot be allocated. In these instances, you will get an error message and the override is not be applied.

Figure 7 below depicts a forecast hierarchy where ItemA1 and ItemA2 have both been overridden to equal 75 and ItemB1 has been overridden to equal 150.

 

Total

S = 5

F = 302

 

 

 

 

 

 

 

 

GroupA

S = 2

F = 150

GroupB

S = 3

F = 152

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

ItemA1

S = 1

O = 75

F = 75

ItemA2

S = 1

O = 75

F = 75

ItemB1

S = 1

O = 150

F = 150

ItemB2

S = 2

F = 2

Figure 7.

Suppose you try to override the forecast for GroupA to equal 100. The override could not be applied because both ItemA1 and ItemA2 are “locked”. Forecast Pro will display an error message and reject the override.

 Let’s now modify the above hierarchy by overriding the forecast for GroupB to equal 50. This results in the hierarchy shown in Figure 8 below.

 

 

Total

S = 5

F = 200

 

 

 

 

 

 

 

 

GroupA

S = 2

F = 150

GroupB

S = 3

O = 50

F = 50

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

ItemA1

S = 1

O = 75

F = 75

ItemA2

S = 1

O = 75

F = 75

ItemB1

S = 1

O = 150

F = 150

ItemB2

S = 2

F = -100

Figure 8.

Notice that the override for GroupB resulted in a negative committed Forecast for ItemB2. This result assumes that the “Allow Negative Forecasts” setting in the Forecast Pro Options dialog box was selected. If this setting was not selected, the override could not be made and Forecast Pro would display an error message and reject the override.

PreviousNext