Mass Processing: Security Measures 

Use

Mass processing is a critical function during which a large amount of sensitive data is changed irrevocably. You should therefore ensure the following:

·        the mass processing jobs have to be tested sufficiently before you make them available to the end user

·        un authorized users have to be excluded from the execution of mass processing jobs

·        Data entries when executing the mass processing jobs that lead to undesired results have to be made impossible

Prerequisites

You are the system administrator and have authorization for transaction WTYMP_A.

Features

·        Transaction WTYMP_A contains a transport connection. You can therefore define the mass processing jobs and the variants for them in the development system, test them in the test system and then make them available to the end user in the productive system.

·        Mass processing jobs can be executed in simulation mode. All the changes to the warranty claims are made but not saved.

·        You can schedule the mass processing jobs for background processing. They then run automatically without the user having to do anything.

·        There are two different transactions for the definition of mass processing jobs and the interactive execution of these jobs (see: Mass Processing). You can therefore control the access to these transactions by assigning different authorizations.

·        When defining mass processing jobs (see: Defining and Executing Mass Processing Jobs) you can define an authorization group to which you want to restrict the execution of the jobs. Technically-speaking, the mass processing transaction is a report; you can therefore work just as well with authorizations and authorization groups, as you are accustomed to with reports.

·        When defining variants you can fill specific fields with default values using the standard functionality and also protect these fields from being overwritten or hide them by using the appropriate functions. You can also define fields as selection variables. This means that you can, for example, fill the date fields with the current data minus a specific number of days, or enter the name of the user who is currently logged on in the user fields.

·        Furthermore, you can define that the job can only be executed with a variant in the first screen of the Job Wizard when you define mass processing jobs (see: Defining and Executing Mass Processing Jobs). The end users can then only execute the job with this variant and, if the variant has been defined correctly, only fill those fields for which they are themselves responsible.