to standardize and automate general warranty claim processing With this function, mass processing replaces or enhances the report used until present (report RWTY0001). Mass processing jobs are then started in the background and run automatically without the user having to do anything (see: Processing with Postcrediting/Precrediting ).

to execute certain operations with more than one warranty claim at the same time , for example, change the decision code, change the defect code, forward claims to manual processing, reduce amounts for specific defect materials by a specific percentage, adopt changes to master data or Customizing settings etc.

to execute actions that should not be triggered manually and are therefore hidden in the action box, for example, actions for setting and/or removing the Archiving indicator .

WTYMP_A Define Mass Processing Jobs: this transaction has been designed for system administrators or members of the project team with special authorizations. Here you can define, in the development system and in accordance with the end user requirements, which warranty claims should be processed, which operations with which parameters with these warranty claims should be executed and how any error that occur should be handled. You can link in any amount of operations.

Furthermore, you define variants with predefined parameter values for the job execution. Finally, you ensure that mass processing jobs and variants are transported to the test system and/or productive system.

The Job Wizard supports you in the definition of the mass processing job. It guides you through the individual steps.

WTYMP Mass Processing Warranty Claim: this transaction has been designed for the end user , i.e. the warranty claim processor or the manager who is responsible for the claims. Here you execute, in the productive system , the mass processing jobs that have been defined in transaction WTYMP_A and you use the predefined variants. This transaction supports the case when mass processing jobs do not run in the background but require the user to make entries and are therefore started interactively.