| Regenerate Schedules (tdpur3211m000) |  |
| Use this session to regenerate non-referenced schedules. Note ERP LN only regenerates the schedule lines that have the Approved status. For push schedules, the process of schedule line regeneration serves the following purposes: To determine the applicable segment set and pattern code as retrieved from the Purchase Contract Line Logistic Data (tdpur3102m000) session and/or the Items - Purchase Business Partner (tdipu0110m000) session, and to update the buyer. To calculate the schedule line's new requirement type based on the applicable segment set and issue pattern. As a result, the schedule line is moved in time. 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, ERP LN determines in which segment the schedule lines fall. If the segments are shifted, the changed requirement types are stored on the schedule lines. Which segment set and issue pattern are used for regeneration, in turn, depends on the value of the Schedule Release Detail field in the Purchase Contract Line Logistic Data (tdpur3102m000) session and/or the Items - Purchase Business Partner (tdipu0110m000) session. For the following release types, the following segment set and issue pattern are used for regeneration: Material Release: only a material release is sent to the supplier. The issue pattern and segment set for material release are taken as starting point for the regeneration. All requirements that fall after the horizon of the material release's segment set, receive the Planned requirement type. Shipping Schedule Only: only a shipping schedule is sent to the supplier. The issue pattern and segment set for shipping schedule are taken as a starting point for the regeneration. All requirements that fall after the horizon of the shipping schedule's segment set, receive the Planned requirement type. Shipping Schedule: a material release and a shipping schedule are sent to the supplier. The issue pattern and segment set for shipping schedule are taken as a starting point for the regeneration. All requirements that fall after the horizon of the shipping schedule's segment set, receive the Planned requirement type. 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 Release type: Material Release. The Segment Set for Material Release SS1 contains the following segments:
Segment Code | Requirement Type | Time Unit | Segment Length
001 | Immediate | hours | 0
003 | Firm | weeks | 2 (weeks)
004 | Planned | weeks | 2 (weeks)
005 | Planned | four weeks | 2 (four weeks)
If the next schedule issue date, according to the issue pattern for material release, is Monday, 23 April 2001, the following applies: All schedule lines whose planned delivery dates/planned shipment dates fall within two weeks from the schedule issue date on (segment 003), receive the status Firm. These requirements are the schedule requirements that fall between 23 April 2001 and 6 May 2001. All schedule lines whose planned delivery dates/planned shipment dates fall within the next two weeks (segment 004), receive the status Planned. These are the schedule requirements that fall between 7 May 2001 and 20 May 2001. All schedule lines whose planned delivery dates/planned shipment dates fall within the next eight weeks (segment 005) also receive the status Planned. These are the schedule requirements that fall between 21 May 2001 and 15 July 2001. However, if schedule requirements fall after the horizon of the segment set, after 15 July 2001, these schedule lines also receive the status Planned. 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. Related topics Purchase schedule release types To use segment sets Overview of purchase schedule handling Push schedules Purchase contracts
Fields | Description
Error Report | If this check box is selected, if errors occur during regeneration, an error report is generated.
Commands | Description
Regenerate | Regenerates the purchase schedule.