Ansicht
Dokumentation

BAPI_MOSRVAPS_CHANGEACTMULTI - Change Activities

ABAP Short Reference   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Functionality

This method can be used to:

• Reschedule an activity

• Change the mode of an activity

• Change the status of an activity

If you are using this function for the first time, you can find detailed documentation under the following important information.

Example

Notes

• The function first schedules the activities and changes the modes that have been transferred. Then, the transferred statuses are set. That is, the transferred status is only set after rescheduling has occurred.

• To reschedule an activity either the start date/time or the end date/time must be given, depending on the scheduling direction selected (in the strategy profile). If both backwards and forwards scheduling are entered in the strategy, both the start and end times must be entered.
  Using the times entered as a basis, the system attempts to reschedule the transferred activities and their associated orders. This means that the transferred times are not simply written in the corresponding activities, but that internal attempts are made on the basis of these times to create consistent orders. Due to this, the actual scheduling result can differ from the data that is transferred. The most important aspects with regards to this are:

• Depending on the scheduling settings made, attempts are made to find available capacities. That is, if the transferred times are not working times (for example, during a weekend) or there are no available capacities, the activities may not be scheduled.

• As standard, fixed activities are not rescheduled.

• The relationships between activities and orders must be taken into account. That is, if an activity is rescheduled that has relationships to other activities, the system also attempts to reschedule these other activities. If one of the activities within these relationships has a status that does not allow such changes (for example, confirmed or fixed), the other activities will not be rescheduled.
  For this reason, the status of all activities of an order should first be checked to determine whether it is allowed or possible to change one activity of an order.
  

• When making changes to the active mode of an activity a valid alternative mode must be entered. If a mode of an activity is changed, this can lead to an automatic change of mode for dependent activities (for example, with mode linkage).

• For status changes, it should be noted that only the following statuses can be changed using this method.

• 0,,:,,Default

• 1 ,,:,,Released

• 2 ,,:,,Fixed

• 3 ,,:,,Fixed, Released,,

Note:

• This method does not contain any consistency checks. It serves as an access for external optimization systems to activities. The consistency checks have to be run in the external system.

• Transaction behavior:
  The method can automatically post (COMMIT WORK) or discard (ROLLBACK WORK) data changes, depending on the COMMIT_CONTROL parameter.

Further information

Parameters

ACTIVITIES
COMMIT_CONTROL
EVENT_CONTROL
LOGICAL_SYSTEM
PLANNING_MODE_USAGE
PLANNING_VERSION
RETURN
SCHEDULE_MODE
STRATEGY_PROFILE

Exceptions

Function Group

10503

CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 4991 Date: 20240523 Time: 172929     sap01-206 ( 78 ms )