Ansicht
Dokumentation

/SAPAPO/OM_ACT_SCHEDULE - Reschedule Activities in liveCache

/SAPAPO/OM_ACT_SCHEDULE - Reschedule Activities in liveCache

ABAP Short Reference   General Material Data  
This documentation is copyright by SAP AG.
SAP E-Book

Further information

@0P@liveCache Scheduler

Functionality

This function module reschedules activities in liveCache using the scheduler.

Planning Instructions for Activities

The table IT_ACTIVITIES contains the required times and properties of the activities:

Field Name Meaning
ACTID Key of the activity
RESID Required primary resource
MODE_NO Required mode number
NEW_START_TIME Instruction for the start time
NEW_END_TIME Instruction for the end time
PLANNED_STATUS Required planning status (descheduled or scheduled)

If a mode number (>0) is specified, the scheduler chooses the appropriate mode for the activity. If a (non-initial) primary resource is specified, the scheduler chooses a mode on this primary resource. If both fields are filled, the stronger argument wins, the mode number instruction.

In certain circumstances, (for example, if there are mode priority conflicts), the mode or primary resource instructions may be ignored.

Time Instructions for I/O Nodes

You can specify time instructions for I/O nodes in the table IT_IONODES. This requires the key fields ORDERID, POSITION_NO, LINE_NO, and IS_INPUT_NODE of the I/O node structure and the field PEGID to be filled, and the required times to be entered in the field IO_TIME (and IO_END_TIME if required).

The scheduler attempts to plan the activities of the I/O nodes so that the I/O nodes receive the correct times.

The activities of the I/O nodes do not need to be in the table IT_ACTIVITIES.

Scheduling

You can use the following import parameters to influence scheduling actions:

Parameter Name Meaning
IS_CONTROLPARAMETERS Control Parameters (Scheduler Control)
IT_SCHED_PARAMS Scheduling Profile (Scheduling Parameters)
IT_RES_PLAN_INTERVALLS Planning Intervals

An activity that cannot be scheduled creates a data record with return code 59 = om_scheduling_error in the return code table ET_RC. The export table ET_SCHED_FAILURES (scheduling results) contains further information.

The objects changed by the scheduling action are entered in the lists of changed objects if required. The activities of I/O nodes in the table IT_IONODES are considered to be modified.

Notes

Error Handling and Troubleshooting

OM_ACT_SCHEDULE always operates in "all-or-nothing" mode. If any error occurs when processing one activity, all changes are rolled back and a follow-on error 184 is created for all other activities listed in IT_ACTIVITIES.

Possible return code:

  • 43 = om_invalid_segment




Parameters

ET_CHANGED_CAP_REQS
ET_CHANGED_IO_NODES
ET_CHANGED_IO_PP_NODES
ET_CHANGED_ORDERS
ET_CHANGED_PEGIDS
ET_OVERFLOWS
ET_RC
ET_SCHED_FAILURES
ET_SCHED_LOG
IS_ATP_INFO
IS_CONTROLPARAMETERS
IS_EXCLUDE_FIELDS
IS_GEN_PARAMS
IS_GET_CHANGED_OPTIONS
IT_ACTIVITIES
IT_IONODES
IT_RES_PLAN_INTERVALS
IT_SCHED_PARAMS
IV_GET_ALL_OBJECTS
IV_SIMSESSION

Exceptions

LC_APPL_ERROR
LC_COM_ERROR
LC_CONNECT_FAILED

Function Group

APO/SAPLOM_PLANNINGTABLE

ROGBILLS - Synchronize billing plans   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 6527 Date: 20240328 Time: 213703     sap01-206 ( 61 ms )