Defining and Executing Mass Processing Jobs 

Define Mass Processing Job (System Administrators, Development System)

...

       1.      Choose transaction WTYMP_A.

A list of the existing mass processing jobs is displayed.

       2.      Choose  Create.

The first screen of the Job Wizard appears.

       3.      Define the global job parameters (job ID, description etc.)

¡        If required, define an authorization group (see: Mass Processing: Security Measures).

¡        Specify that the mass processing job may only be executed with a variant (see: Mass Processing: Security Measures).

¡        Enter a customer-specific class (customer exit) if you want to work with customer-specific job parameters.

¡        If required, define that the message log is checked automatically every time the field values are changed when the mass processing job is executed. The standard check is defined in such a way that a claim is skipped as soon as an error message occurs (message of type E).

This standard check cannot have an effect in retrospect on operations already created. It only applies to new operations.

The standard check is activated in the default settings.

¡        If required, specify that when the job is executed the individual steps or operations in the job are not displayed one under the other but on individual tab pages. This is especially useful if a job contains several operations.

¡        Specify which additional parameters you want to load to the memory before the claim is processed. Set the appropriate indicator for copying the criteria (Copy) next to the desired parameters.

Choose  Continue.

The next screen of the Job Wizard appears.

       4.      Specify according to which selection criteria you want to search for warranty claims. Set the appropriate indicator for copying the criteria (Copy) next to the desired fields. All the fields from the claim header, version and item are at your disposal. If the field is to be a required field when the mass processing job is executed, set the appropriate indicator for defining it as such (Required).

Choose  Continue.

The next screen of the Job Wizard appears.

       5.      If required, define customer-specific job parameters by entering a customer-specific DDIC structure and choosing fields from it. These fields are then made available to the warranty claim processor later for entering data when the mass processing job is executed. The entries are then returned to the customer-specific class (customer exit) that you have entered in the first screen of the Job Wizard and processed there (validates, used for calculations etc.).

Choose  Continue.

The next screen of the Job Wizard appears.

       6.      Choose the desired operation (change field values, execute action, pricing, check log, execute customer exit). Choose  Continue.

A screen appears with different pushbutton functions for the desired operation.

By choosing the appropriate function, specify under which prerequisites the operation should be executed, exactly which operation should be executed and what the final checks should be like. Choose  Continue.

If you have activated the standard check in the global job parameters, this check has already been entered when you choose the function for checking the message log. Instead of the icon , the icon  is displayed on the pushbutton screen.

       7.      Repeat the last step for all further transactions that are to be executed with the selected warranty claims. Choose  Generate after the last operation. Enter the development class/package and a transport request.

The new mass processing job is copied to the list of existing mass processing jobs.

       8.      Create a variant for the new mass processing job. To do this, select the job and choose  Variant. Transport the variant with  Variant.

You can also define in the variant that the mass processing job should be executed in simulation mode.

If you change a mass processing job in retrospect, it may be that your variants are no longer valid.

General Notes for Defining Mass Processing Jobs

·        If you have defined prerequisites or checks for operations, the icon  on the appropriate screen is replaced by icon . You see immediately for which screens entries already exist.

·        You can change the descriptions of all the steps in the Job Wizard except the first one (Global Job Parameters).

·        You can enter a step ID for every operation. You only need this step ID is you want to call a customer exit as operation. The step ID has to be unique within the job.

·        You can change mass processing jobs that have already been saved in retrospect. However, you cannot change the sequence of the operations. If you desire a different sequence, you have to delete the operations and create them again in the correct sequence.

Execute Mass Processing Job (End User, Productive System)

...

       1.      Choose transaction WTYMP.

A list of the existing mass processing jobs is displayed.

       2.      Select the desired job and choose  Execute with Variant.

       3.      Choose the desired variant.

       4.      If necessary, enter the required parameter values and choose  Execute.

The mass processing job is executed and the appropriate log is displayed.

This log is saved and can be used later for checking purposes.

       5.      Check the log.

The fields Claim, Category, Version and Item are at your disposal in the log as context for the error analysis.

You can also call the log with the standard transactions SLG1 (display log) and SLG2 (delete log). Then enter: Object MP, Subobject WTYMP, External Identification (External ID): the job ID of your mass processing job.

       6.      Start the job again if a message informs you that the processing was terminated. Decide whether you want to process all claims again or just the remaining ones.

In order to avoid data inconsistencies, enter in both these cases the same parameter values as you did when you executed the job for the first time.