You can use mass processing to execute functions for several process or production orders.
Note
Some of the mass processing functions described in the following cannot be used for process orders.
The following documentation on mass processing relates to the transactions COHV ( Mass Processing Production Orders ) and COHVPI ( Mass Processing Process Orders ), which replace the transactions CO28 ( Individual Object Lists ), COID ( Individual Object Lists PI ) and CO44 ( Mass Processing for Orders ).
The following functions are available for process and production orders :
Order headers
Material availability check (manufacturing orders and planned orders)
Release
Print shop floor papers
Costing
Scheduling
Set up capacity requirements
WM materials staging
Picking
Set/delete user status
Confirmation
Technically complete
Complete
Log display
Operations
Release
Print shop floor papers
Picking
Set/delete user status
Confirmation
Log display
Components
Print shop floor papers
Picking
Log display
Production resources/tools (PP only)
Print shop floor papers
Log display
There are also mass-processing functions for planned orders . See also: Mass-Processing Functions for Planned Orders
Mass processing can be started in the following ways:
Triggering the execution of a function
The execution of a function can be triggered as follows:
Execute function immediately
The functions are executed directly after mass processing has been triggered. This can take a long time for functions that require a lot of system resources. However, you can immediately check whether the function was successfully executed.
Execute function with dialog
Further processing is controlled by a dialog that is specific to the function. This option is available for the following functions: Confirmation, Picking, Log display.
Create a function preselection (see Processing Requests )
First, preselections are created without any further checks. The preselections are created very quickly. Actual execution takes place with the program COWORKDISPATCH. It is thus delayed until the next time the program starts. You can decouple the function in terms of time, so that the main work takes place at night, for example. The end users create preselections and system administration takes care of their execution.
Execute function in background
First, preselections are created without any further checks. Then a background process is started, which processes these preselections immediately. Scheduling a background job does not create any administrative work and reduces the burden on dialog.
For parallelization, you define server groups for mass processing (COWORK-DIALOG, COWORK-BATCH). This enables you to speed up the execution of processing.
Mass processing in dialog / in the background .
You can either execute mass processing in dialog or you can schedule it in a background job (no dialog steps possible).
You can specify that an application toolbar with selected mass processing functions is to be displayed in the list of the selected objects. You can use this application toolbar to execute the functions in dialog.
For more information, see Display Application Toolbar with Mass-Processing Functions .
You can specify whether the changes are to be made by a mass-processing function or test-wise. Any error messages that may occur are collected. No changes are written to the database.
The test run is available for the following functions:
Complete
Set/delete user status
Release
Costing
Set up capacity requirements
Technically complete
Scheduling
WM materials staging
To test a function, choose the Test Function Without Changes to Data option on the Mass Processing tab page.
Log records are written and saved when the function is executed. They provide information about the execution of the mass processing functions. If no log record exists, the function was carried out without restriction. The log records are assigned to the order or the order network.
For more information, see Logs .
From the menu for Logistics, choose
for the production order and for the process order .See also: