If this check box is selected, if errors occur during regeneration, an error report is generated.
Regenerate Schedules (tdpur3211m000)Use this session to regenerate non-referenced schedules. Note LN only regenerates the schedule lines that have the Approved status. For push schedules, the process of schedule line regeneration serves the following purposes:
For pull-forecast schedules, regeneration is only performed to retrieve the correct segment set, pattern code, and buyer for the purchase schedule. To shift segments due to regeneration Regeneration is performed based on a schedule's applicable segment set and issue pattern, as stored in the Purchase Contract Line Logistic Data (tdpur3102m000) session and/or the Items - Purchase Business Partner (tdipu0110m000) session. Every time the regeneration process is repeated, the next schedule issue date is determined based on the schedule's linked issue pattern. After this, LN determines in which segment the schedule lines fall. If the segments are shifted, the changed requirement types are stored on the schedule lines. For the following release types, the following segment set and issue pattern are used for regeneration:
Note As a general rule, you can assume that in the regeneration process, only the Firm requirement types are calculated. All schedule lines that fall outside the period of the Firm requirement type, receive the Planned requirement type. Whether or not the lines with the Planned requirement type are sent in a purchase release depends on the purchase schedule's release type. However, if a period is undefined between two segments, the schedule lines that fall in this time gap automatically receive the requirement type of the segment with the highest sequence number. Example
If the next schedule issue date, according to the issue pattern for material release, is Monday, 23 April 2001, the following applies:
If you take the same example, but the next schedule issue date is Tuesday, 24 April 2001, requirement types are calculated from 30 April 2001 on. The reason for this is that the weekly segment time unit always takes Monday as a starting point. As a result, the schedule lines that fall between 24 April 2001 and 29 April 2001 are excluded from the regeneration process. Note If schedule lines are moved in time through regeneration, transactions are logged for the schedule line based on the value of the Transaction Time Fence field of the Purchase Contract Line Logistic Data (tdpur3102m000) session and/or the Items - Purchase Business Partner (tdipu0110m000) session.
Error Report If this check box is selected, if errors occur during regeneration, an error report is generated.
Regenerate Regenerates the purchase schedule.
| |||||||||||||||||||||||