Ansicht
Dokumentation

Capacity requirements planning: Changed functions ( RELNPP_CRP_KAPAPL_30CÄ )

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

Short text

Capacity requirements planning: Changed functions

Description

This release note describes functions that have been changed in the area of capacity requirements planning for Release 3.0C.

Changing the strategy profile during capacity leveling

Up to now, the current strategy profile could be displayed and changed on both types of planning table during capacity leveling. As of Release 3.0C, it is possible not only to change the strategy profile but also to alter the settings in the current strategy profile.

Choosing the menu options Settings -> Strategy calls up the dialog box Strategy.

Changes to the settings of the current strategy profile for the current capacity leveling can be transferred here using the function key Transfer. The changes are not saved when you exit the planning tables.

By pressing the function key Reset in the dialog box Strategy, settings that have been changed in the strategy profile during planning can be reset to their original status.

Change to the display of the strategy profile during planning

It was possible to display the current strategy profile on both types of planning table in Release 3.0A. This display has been enhanced for Release 3.0C:

• In the dialog box Strategy, an overview of the strategy profile available for dispatching is displayed in the area Overview.

• When you select a strategy profile in the overview and press the function key Refresh, the settings of this profile are displayed in the detail area.

• If you select a strategy profile in the overview and press the function key Transfer, the selected strategy profile is transferred.

• If you have compiled an individual help for the strategy profile, only the strategy profiles are displayed from the individual help.

Changed entry for indicator "Date entry when dispatching."

Up until now, if you set the indicator Date entry when dispatching in the strategy profile, both the start date and the start time together with the finish date and the finish time were called up by the system during dispatching on the two types of planning table. This has been changed for Release 3.0C.

If the indicator Date entry when dispatching is set in the strategy profile, the dispatch date is called up by the system depending on the planning direction set in the strategy profile. If the indicator Planning direction forwards is set, you are required to enter the start date and the start time. If the indicator Planning direction forwards is not set, the system asks for the finish date and the finish time.

Change to dispatching a capacity requirement to an individual capacity or person

You can use "drag and drop" in the planning table (individual capacity view) to "shift" a capacity requirement onto an individual capacity or a person. In this case, up to now, the entire operation was dispatched to the work center to which the individual capacity or the person belongs.

The allocation of a non-split capacity requirement to an individual capacity or a person is possible. If a capacity requirement that should be dispatched is not yet split, an individual split is created and allocated to the individual capacity or person. The split has the status dispatched. The original capacity requirement is displayed at its former position.

Change to processing remaining split records

Up to now, a remaining split record which only contained the capacity requirement and the dates of the capacity requirement was created for the incomplete splitting of capacity requirements. This remaining split record was displayed on the graphic and tabular planning table (individual capacity view), but could not be dispatched nor allocated.

As of Release 3.0C, a remaining split record is always created if either a remaining quantity (with quantity-related operations) or remaining work (with internally processed operations) is left over when splitting a capacity requirement. The remaining split record contains the remaining quantity or the remaining work as well as the dates of the respective capacity requirement or the operation. For operations with operation segments, the standard values are taken over from the operation. Duration is calculated automatically for internally processed operations.

On the planning table and in the dialog box Split and Allocate, the remaining split record is displayed just like every other split.

A remaining split record can be processed in the same way as other splits (e.g. dispatched), however, it cannot be deleted. The remaining split record is deleted by the system when there is no more remaining quantity or remaining work.

The remaining split record loses its status at the first manual change made by the user (Allocate, Change date). If remaining quantities or remaining work still exist after the manual change, the system creates a new remaining split record.

If there is no more remaining quantity or remaining work then remaining split records that still exist after updating from Release 3.0B to 3.0C are converted into the new "version" or deleted in the first action (for example, on the dialog box Define splits when allocating, dispatching or deleting splits).

Change to scheduling in Project System

In the Project System as of Release 3.0C, the operations are no longer rescheduled when a requirement is deallocated.

BAL Application Log Documentation   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 6265 Date: 20240523 Time: 041214     sap01-206 ( 156 ms )