Show TOC

 Mass Processing of Process and Production Orders

Use

You can use mass processing to execute functions for multiple process or production orders.

Some of the following mass processing functions cannot be used for process orders.

The following documentation about mass processing refers 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 ).

Features

Functions

The following functions are available for process and production orders:

Order headers

Material availability check (manufacturing orders and planned orders)

Release

Printing of Shop Floor Papers

Costing

Scheduling

Generate Capacity Requirements

WM Material Staging

Picking

Set/delete user status

Confirmation

Technically Complete

Close

Log Display

Operations

Release

Printing of Shop Floor Papers

Picking

Set/delete user status

Confirmation

Log Display

Components

Printing of Shop Floor Papers

Picking

Log Display

Production resources/tools(PP only)

Printing of Shop Floor Papers

Log Display

The following functions are available for planned orders:

Conversion of Planned Order

Material Availability Check

The material availability check can be carried out simultaneously for planned orders and production or process orders.

Starting Mass Processing

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 transaction

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 request(see Processing Requests s)

First, requests are created without any further checks. The requests are created very quickly. Mass processing is actually executed with the program COWORKDISPATCH. As a result, it is 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 requests and system administration takes care of their execution.

Execute function in the background

First, requests are created without any further checks. Then a background process is started, which processes these requests immediately. Scheduling a background job does not create any administrative work and reduces the workload for the dialog.

Parallel Processing

For parallel processing, you define server groups for mass processing (COWORK-DIALOG, COWORK-BATCH). This enables you to speed up the execution of processing.

Mass processing online sapurl_link_0001_00or in the background .

You can either execute mass processing online or you can schedule it in a background job (no online steps are possible).

Application Toolbar with Mass Processing Functions

You can define that an application toolbar, with selected mass processing functions, is displayed in the list of the selected objects. You can use this application toolbar to execute the functions in the dialog.

For more information, see Display Application Toolbar with Mass Processing Functions .

Test Run

You can decide whether changes caused by a mass processing function are executed in the form of a test run only. Error messages that may occur are collected. No changes are updated to the database.

You can use the test run for these functions:

Close

Set/delete user status

Release

Costing

Generate capacity requirements

Technically Complete

Scheduling

WM Material Staging

To test a function, select the option Test function without changes to data on the Mass processing tab page.

Log

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 executed without any problems. The log records are assigned to the order or the collective order.

For more information, see Logs

Activities

In the menu for Logistics, choose ProductionShop Floor ControlControlMass Processing for the production order and Production – ProcessProcess OrderToolsMass Processing for the process order.

See also:

Scheduling Mass Processing in the Background

Executing Mass Processing Online