Prerequisites

Function requests for process or production orders must have been generated in mass processing. (In other words, you have selected a function in mass processing and selected Create Function Request for function execution.)

Procedure

Processing is carried out by the report COWORKDISPATCHNEW, either via the menu in the dialog or in Customizing in the background ( Production → Shop Floor Control → Operations → Schedule Background Jobs → Process Requests for Mass Processing or transaction OPJ4).

In the menu, choose System ® Services ® Reporting

In the Program field, enterCOWORKDISPATCHNEW

Choose ( ) ( Execute ).

The object type is already enteredOR(= order).

For operations, use the object type OV

The object number is made up of a two figure abbreviation for the object type (OR for orders, OV for operations) and the internal key for the object (AUFNR for orders, AUFPL + APLZL for operations).

For a collective availability check, leave the Object Type and Object Number fields empty. The object number is assigned by the system and displayed in the results list. In the collective availability check, this number is made up of MATAVAIL ( material availability check) and a sequential number, for example, MATAVAIL0000000805.

The object number of the orders is made up of the object type OR and the number of the order, for example, OR000060000763.

Enter the following selection criteria ( user name, plant, date of entry, time of entry ).

Choose the function you want to execute.

If you choose more than one, the mass change functions are carried out in the order in which you entered them.

Choose whether you want to execute, delete or output requests in a list. (It is not possible to process a list in the background.)

If you choose Edit List , you see a list in which you can execute mass processing or delete the requests.

You can also define whether:

A log is created and saved in the spool system when background processing is executed

Background processing logs are sent to the same spool request as the list of requests to be processed. (You must have chosen Edit List under Requests .)

For background processing you can define that you want to receive a list of requests in addition to a log:

To display the log, choose System → Jobs → Job Overview and select your job

Choose ( ) Spool List .

On the subsequent screen, select the spool number and choose ( ) Display Contents

If parallel processing is active, the number of processes defined here is used. If this number of processes is not available, the maximum possible number of processes is used. (See Setting Up Parallel Processing )

Delete any temporary requests.

Temporary requests are generated during direct execution of functions in mass processing. After processing, these requests are immediately deleted. If functions are tested without data changes in mass processing, test requests are generated, which are then also deleted after testing. However, under certain circumstances (for example, due to a program termination) temporary or test requests are sometimes not deleted.

Therefore, either the report deletes all requests that are older as seven days, or you can specify when these requests should be deleted. If you enter -1 , then temporary and test requests from today are also deleted. However, in this case, you must ensure that mass processing is not running (in the foreground or as a batch job) at the same time, because otherwise you will also delete temporary requests that are currently being processed.

You can also save your entries as a variant. In the menu, choose Goto → Variants → Save As Variant

Choose ( ) ( Execute ), to process the requests.

If you have chosen Edit List , then you can execute ( ( ) ) or delete ( ( ) ) requests in the list:

Deleted requests are displayed in orange, executed requests in green.

If errors have occurred during execution, a red light is displayed in the first column. A yellow light is displayed for warning messages and a green light for info messages.

To display the logs for the executed requests, choose Log . Executed and deleted requests are displayed until the next time that the list is refreshed.

The last two columns in the output list are indicators for tests and temporary requests.