Multilevel Worklist: Process Flow
Prerequisites
You have created a flow definition . In the flow definition, you define the sequence of processing steps that you want to perform. A processing step corresponds to a single function. Examples of individual processing steps are WIP calculation, variance calculation, and settlement. A processing step sequence is defined by linking these single functions to each other in a flow definition.
You have established the flow definition in the scheduler .
Process Flow
The system starts the sequence of processing steps in accordance with the planning specified in the scheduler. The objects to be processed are selected on the basis of the following logic:
Objects that were processed successfully in the previous flow step but have not yet been processed successfully in the current flow step are transferred from the selection to be processed. These objects are called
primary objects
.The system also reads the dependent objects for the current flow step for all selected objects. These dependent objects are called
secondary objects
. If a primary object has one or more secondary objects that were not successfully processed in the previous flow step, neither the primary object nor its associated secondary objects can be processed in the current flow step.
The system executes the processing steps.
When the system has executed all processing steps, you receive a mail to inform you that the planned sequence of processing steps has been completed. This mail is generated using the workflow link.
You can reprocess the faulty objects directly from the mail.
The user can view the processed objects with their processing status in the monitor of the Schedule Manager.
The user processes the objects with errors.
The user retriggers the processing step sequence from the mail in his office inbox.
The system now processes the objects in the selection that were processed with errors in the first run of the processing sequence, or whose processing was forced manually.
For each object, processing starts with the step that was not processed correctly.
The subsequent processing steps are then started automatically in the defined sequence.
Note
If an object that was processed without errors in the first run of the processing step sequence is changed before the second run of the processing step sequence, these changes do not result in an automatic reprocessing of the object. If you want the object to be reprocessed, manually set the corresponding processing status.
The production order 1000000 is included with all other production orders of plant 1000 in period-end closing of
Product Cost by Order
. Work in process for the order is calculated as EUR 1,000 and settled to
Financial Accounting
(FI). All processing steps (for example,
WIP calculation
and
settlement
) of the processing step sequence were also performed without out errors.
However, not all production orders were processed without errors. In this way, for example, the production order 1000005 receives the processing status
error
for the processing step
WIP calculation a
nd the production order 1000010 receives the processsing status
error
for the processing step
Settlement
.
After work in process has been settled for all production orders, including production order 1000000, additional costs amounting to EUR 200 are posted to production order 1000000.
Remove the errors for the production orders 1000005 and 1000010 and reinitiate the processing step sequence. The production orders 1000005 and 1000010 are reprocessed. Production order 1000000 is not processed as it was processed without errors in the first run.
If you want to force a reprocessing of production order 1000000, you can manually set the corresponding processing status.
See also:
Schedule Manager: Monitor - Working with the Object List