This article will guide you through the process of setting up SOD controls using remQ’s single action tool, the SOD tool, and using SQVI queries with the SQVI2CHECK tool.
As an example, we use a control that monitors SOD violations for posting and invoices and initiating a payment (starting a payment run).
The data required for this is logged by the SAP system in tables, and that means there is only 1 step to set up the control:
1. use the SQVI tool to extract the users who posted invoices and started payment runs where the invoices were paid;
then, we will map and format the output of the second step so that you get a formatted remQ control and you can decide which fields etc. you want to see in the alerts.
(i) payments are saved in tables REGUP and REGUH and changes to that data is not logged in the system. You could enable logging by switching on table logging or creating change objects for that data, and adding another rule to the configuration described here.
(ii) Changes to invoices are logged in change documents, type BELEG, and if you want to monitor changes of invoices and starting payment runs, an additional rule is required.
Step 1 — creating SQVI queries to map posting of invoices and creating payment runs
All SQVI queries that you want to use in remQ must start with precursor REM_<any name>, the second part of the query name can be chosen freely.
We are setting one SQVI queries,
REM_LS01 Posting of Invoice and Payment Execution
1.1 Defining the Query:
Go to transaction SQVI and create a new query, after you have entered the name (remember, needs to start with REM_) you need to select data source = Table join.
On the next screen, Choose Data Source, please add the following tables: BKPF; REGUH; BSAK; and BKPF1(as alias table).
Now add the mapping between the selected tables as shown here:
Next you need to add the selection field and fields that will be displayed in the output of the SQVI report:
On the next screen, create a variant:
Selection of payment proposal: keep this blank/empty, selection of document type:
Note: ZP is the payment document type used in our system, it can be different in your system, please investigate.
Same for invoices document types, we used SAP standard types RE and KR, but it can be different in your case.
Indicator Only Proposal Run should be Equal to Blank
The date range can be dynamic.
Save the SQVI query. You can run it to see results.
1.2 Mapping SQVI output to remQ alert details:
The output of this SQVI query can be used as input for a remQ alert. We need to set the frame for an alert and select fields for the layout of the alert details.
This is done in transaction /REM/QV2CHECK. Here select the SQVI query we just defined from the left query column, to get the mapping cockpit.
Assign a unique REM_IDs for the query.
In the MESSAGE_NAME field enter the name that will be displayed in the alerts transaction.
In MESSAGE_TEXT enter the name of the query.
Next step is to map the fields from the SQVI output to the alert details; click on input help in a field in order to get the parameters that can be selected:
Now you can run and schedule the check and it will create alerts based on the data and executed SOD transactions.