| | Resetting high FAB and high RAW sales schedule
authorizationsHow the high FAB authorizations and high RAW authorizations
are reset, is based on the setting of the Authorizations to be parameter in the Items - Sales Business Partner (tdisa0510m000) and Sales Contract Line Logistic Data (tdsls3102m000) sessions: Carried Forward The high FAB authorizations and high RAW authorizations are
reduced by the reset quantity. Reset The high FAB authorizations and high RAW authorizations are
equalized to the FAB authorization and RAW authorization values.
Carried Forward If already FAB/RAW authorization records exist with release
dates that are later than the CUM Reset Date, LN copies these records with the following adjustments: - The FAB Authorization, RAW Authorization, High FAB Authorization, and High RAW Authorization are decreased with the reset quantity.
- The old Reset Date is replaced with the new Reset Date.
Reset If already FAB/RAW authorization records exist with release
dates that are later than the CUM Reset Date, LN: - Decreases the FAB Authorization and High FAB Authorization of these records with the FAB reset quantity.
- Decreases the RAW Authorization and High RAW Authorization of these records with the RAW reset quantity.
- Replaces the old Reset Date with the new Reset Date.
Example - FAB period = 4 weeks
- Cumulative model = Order Based
- Authorizations to be Carried Forward
- Reset date = start week 3
- The schedule lines are generated before the reset takes place
- Schedule line 2 is received in week 3
- Schedule line 3 is received in week 5
| Week | Line 1 | - | Line 2 | - | Line 3 | - | CUMs after
reset |
|---|
| - | Qty. | CUM | Qty. | CUM | Qty. | CUM | - |
|---|
| 1 | 20 | 20 | - | 20 | - | 20 | 20 | | 2 | 20 | 40 | - | 40 | - | 40 | 40 | | 3 | 20 | 60 | 5 | 45 | - | 45 | 5 | | 4 | 20 | 80 | 5 | 50 | - | 50 | 10 | | 5 | 20 | 100 | 5 | 55 | 20 | 70 | 30 | | 6 | 20 | 120 | 55 | 110 | 5 | 75 | 35 | | 7 | - | - | 5 | 115 | 5 | 80 | 40 | | 8 | - | - | 5 | 120 | 5 | 85 | 45 | | 9 | - | - | - | - | 5 | 90 | 50 | | 10 | - | - | - | - | 5 | 95 | 55 |
| TOTALS | CUM Line 1 | CUM line
2 | CUM line 3 | CUMs after
reset |
|---|
| Start CUM | 0 | 40 | 50 | 10 | | FAB | 80 | 110 | 85 | 45 | | High
FAB | 80 | 110 | 110 | 70 |
The reset date starts in week 3. Because of the Order Based CUM model, resetting is performed based on the prior required
CUM. At the end of week 2, the reset quantity is 40. Because authorizations
must be Carried Forward, the authorization cumulatives are updated by -40 from the
reset date on (week 3). If you take the same example, however, with the authorizations
reset rather than carried forward, the high FAB is not updated but equalized to
the FAB quantity. The calculation then arrives at: | TOTALS | CUM Line 1 | CUM line 2 | CUM
line 3 | CUMs after reset |
|---|
| Start
CUM | 0 | 40 | 50 | 10 | | FAB | 80 | 110 | 85 | 45 | | High FAB | 80 | 110 | 110 | 45 |
| |