Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-TS (Application Component) Technical Application Support⤷
BMG (Package) Material Master: Componentization Interfaces
Basic Data
| Data Element | UMTHZ |
| Short Description | Rescheduling horizon |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM03 | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | RESCHED_HORIZON | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | ReschHorzn |
| Medium | 15 | Resched.horizon |
| Long | 30 | Rescheduling horizon |
| Heading | 5 | Resch |
Documentation
Definition
Part of the planning area, starting from the end of the replenishment lead time (the system calculates the end of the replenishment lead time by the planning date + number of days for the replenishment lead time), in which the system checks in the net requirements calculation whether firmed or fixed receipt elements (purchase orders, production orders, firmed planned orders, and so on) should be rescheduled in. The rescheduling horizon is calculated in workdays.
Use
In this period, rescheduling proposals are created by the system for firmed or fixed receipt elements if this receipt element can cover the requirement and if the tolerance values for rescheduling in have been exceeded.
In this case, no new order proposal is created - instead the system includes this fixed receipt in the net requirements calculation with the rescheduled date.
Dependencies
Exception messages are also created for these firmed receipt elements as well as the rescheduling proposal:
- Bring operation forward if the receipt element lies after the requirement date (that is reschedule in).
The rescheduling horizon only applies to bringing fixed receipt elements forward. If there is a requirement before the receipt element that can be covered by the receipt element, the exception message Bring operation forward is issued. The MRP controller is thus requested to bring the receipt element forward to the date proposed by the system.
- Postpone operation, if the receipt element lies before the requirement date (that is, reschedule out).
The rescheduling horizon does not apply in this case. The system creates the rescheduling proposals to bring the elements forward according to the requirements date.
For rescheduling proposals in (that is bringing forward the operation), you can define exactly which receipt elements are to be included in the check.
For rescheduling proposals out (that is postponing the operation), all receipt elements are included in the check.
History
| Last changed by/on | SAP | 19990629 |
| SAP Release Created in |
