Ansicht
Dokumentation

/VIRSA/ZVRAT_MT2 - Conversion Utility Report for CC New Release

TXBHW - Original Tax Base Amount in Local Currency   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Title

Compliance Calibrator Release 4.0 Conversion Utility

Purpose

This utility is used to convert data from Release VRAT 3.0/ VRAT 3.0C to Compliance Calibrator 4.0 for following tables:

/VIRSA/ZMITREF,,,,Mitigating Control

/VIRSA/ZMITMON,,,,Mitigating Monitors and Approvers

/VIRSA/ZMITCNTL,,,,Mitigating Control - User

/VIRSA/ZMITROLE,,,,Mitigating Control - Role

/VIRSA/ZMITPROF,,,,Mitigating Control - Profile

The following two new tables are also populated:

/VIRSA/ZBUSUNIT,,,,Business Units

/VIRSA/BUAPPVR,,,,Business Unit Approvers

Input

For input the data is taken from the text files downloaded from VRAT 3.0/ VRAT 3.0C release.

Screens

It has total five screens:

1.,,Selecting the type of files and tables to be uploaded

2.,,Business Units

3.,,Business Unit Approvers

4.,,Mitigating Controls

5.,,Monitors And Controls

1.,,Selecting the type of files and tables to be uploaded: This is a Selection screen in which you specify the path of the different tables or Tab delaminated text files. In this screen you can also store the variants. After giving the paths press Execute Button (F8) to start the conversion.

2.,,Business Units: This screen displays the list of all the business units uploaded to the utility. Here you can define the new Business Unit ID ands its description. The Business Unit Id can be of Maximum 4 Characters and Description can be maximum 128 characters. Here data is inserted into /VIRSA/BUSUNIT table.

3.,,Business Unit Approvers: This screen is used to define Approvers for different Business Units. Business Unit Id, Description and already defined approvers are taken from the uploaded data and you can define a new Approver Id, Full Name and Email ID for them.

,,If the Approver Id already exists in the SAP database the Full Name of the Approver and its Email Id is taken from the database by the utility. The role for all the Ids is defined as Approvers i.e. 'A' (In Monitors and Controls screen you can also define as Monitors, so they can have both Roles.) The data from this screen is inserted into /VIRSA/BUAPVR and /VIRSA/ZMITMON tables.

4.,,Mitigating Controls: This screen shows Control Id, Description, Business Unit Id and Approvers as the output of the conversion process. Data from this screen is stored in /VIRSA/ZMITREF table.

5.,,Monitors and Controls: This screen shows Control ID and Monitors from the uploaded files. You can define Monitor Id, Full Name and Email id.

,,If the Monitor Id already exists in the SAP database the Full Name of the Approver and its Email Id is taken from the database by the utility. The role for all the Ids is defined as Monitor i.e. 'M'.

,,But if that Id also exists as Approver then that ID is defined as 'C' i.e. this Id is both Approver as well as Monitor.

From this screen data is saved into /VIRSA/ZMITCNTL, /VIRSA/ZMITROLE, /VIRSA/ZMITPROF, and /VIRSA/ZMITMON tables.

Flow

The flow of the utility starts from first selection screen where you define the files to be uploaded, then you come to 'Business Units' Screen where you do the required entries and save the data with 'SAVE' button. Then click 'NEXT' button to move to the next screen i.e. 'Business Unit Approvers'. Here again make the required entry, 'SAVE' and move to 'NEXT' screen. Similarly make entries in 'Mitigating Controls' screen and 'Monitors and Approvers' screen.

Always remember to save the data before leaving the screen i.e. when you move to next screen or previous screen.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

Example

PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.

Length: 4278 Date: 20240419 Time: 074315     sap01-206 ( 72 ms )