Ansicht
Dokumentation

SIMG_CFMENUOLMDSML - Maintain Planning Calendar

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

You use the planning calendar to define flexible period lengths for planning and procurement in demand management and in MRP. For this purpose, you can maintain period splits of your choice (for example, Wednesday to Tuesday). If you work with the planning calendar, you can also display the period totals display in the MRP list or in the stock/requirements list according to your planning calendar periods.

If, for example, a vendor always delivers his goods every second Wednesday, you can use the planning calendar to define a period length of two weeks starting on the Wednesday and ending on the Tuesday, two weeks later. The period lot size can also be set accordingly so that, on the one hand, the requirements are always grouped together within the defined period length, and on the other, the order proposals are planned in such a way that the delivery date lies at the end of the period.

If you want to determine flexible procurement dates, the planning calendar is assigned to the material with the appropriate lot size in the material master record.

1. Create the planning calendar.
2. Enter a key of up to three characters and a short description for the calendar.
3. Enter a minimum period in workdays for the calendar.

You use the minimum period to define a period that you require to reprocess the planning calendar. Calendars that are valid for a fewer number of days than is specified in the minimum period are proposed for maintenance when you select the function Cal. no longer valid

1. Determine whether the SAP system is to choose either the previous or the following workday is a procurement date falls on a day that is not defined in the factory calendar.
2. Select a calculation rule.
   The calculation rule determines the period split used to calculate the procurement date (for example, whether the period lengths are to be calculated per week, month, or year).
3. Enter your date specifications in the period split.
4. Select, "Calculate periods".
5. Enter a start date and a finish date to define the validity period of the planning calendar.

The finish date must be greater than the minimum period.

1. If necessary, change the periods displayed.

If you want to determine the procurement dates for a material using the planning calendar, you must note that the receipts created in the planning run must lie within the validity period of the planning calendar. Otherwise the planning run will be terminated.
Therefore, you must always make sure that sufficient calendar periods are available.

In this workstep, you can also change the calculation rule or the individual periods of the planning canendar as you require.

You can also calculate new periods for a planning calendar that is no longer valid. For this purpose, the function Maintain calendars that are no longer valid in workstep, Change PPS planning calendar.

1. Select the planning calendar that you want to change by entering the name of the planning calendar or you can select the "Calendar overview" button and in the following dialog box select the calendar you want to change.
2. Change the planning calendar accordingly.
3. Renew the calendar by selecting the function Cal.no longer valid.
4. If necessary, create new periods.

To display a planning calendar, proceed as follows:

Select the planning calendar that you want to display by entering the name of the planning calendar or you can select the "Calendar overview" button and in the following dialog box select the calendar you want to display.

1. Then select the appropriate function for displaying the planning calendar you are interested in.

Vendor Master (General Section)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 4440 Date: 20240524 Time: 000554     sap01-206 ( 74 ms )