Explain how to retrieve the necessary information from the SAP for the report ' report bank changes VwF dd_mm_yyyy ' . Also it is explained how produce the report and how it should analysed. |
The report contains bank data modifications (creation, modification, deletion) requested via the Data Control SAP vendors´ workflow for a specific date and SAP manual updates. It is to be done on a daily basis (working days). The file is archived in the Google Drive - Internal Controls
This report aims to be an enforcement towards more effective control measures, regarding bank data.
Fields existing in the Report:
Columns | Description |
|---|---|
Vendor Country | Country Origin of Vendor |
User | User that performed the change. WF-BATCH is shown if approval is automatic. |
Vendor number | Number of vendor |
Name | Vendor's name |
Bank country | Country Origin of Bank Account |
Bank key | Bank Key |
Account number | Bank Account Number |
Change type | Type of Change: I (Insert), E (delete), U (update) |
Date | Date Processed |
WK Req. 1 | Request Number |
WK user | Requester User name |
| WK user id | Requester User ID |
DIA Validator | PM Validator User ID |
Data controller | Data Operator User ID |
| Target system | SAP system (PF1, PH4) |
Valid Document | Editable - existence of document (to be classified as Ok / Not Ok / - ) |
VAT Checked | Editable - VAT matches or not or doesn't apply ( Ok / Not Ok / - ) |
Duplicate Bank Account | Editable - Bank details duplication's found ( Ok /Not Ok/ - ) |
CC Confirmed | Editable - Correct/incorrect/nonexistent confirmation of the bank details ( Ok / Not Ok / - ) |
Bank Details Checked | Editable - Bank details correctly inserted according to all existing data ( Ok / Not Ok / - ) |
Comments | Editable - If bank details were correctly/incorrectly updated ( Ok / Not Ok / other comments) |
Verified By | Editable - ID of the person who checked the update |
TL Comments | Editable - Same as in comments but inserted by TL/person in which TL delegated |
TL ID | Editable - TL ID |
In SAP system PF1_050, the Data Controller should enter the transaction ZZR_LIST_CHG_BANK_VC:

Once inside the transaction, select the time period in the fields 'From date' and 'Date until' (e.g. 12.08.2008). Also, as the reports concern Vendors' modifications, tick the options:
Finally, choose the path where the the vendors download file should be placed. The name of the file should be ‘Report Bank changes VwF XX.XX.XXXX.xls’ (where XX.XX.XXXX is the date selected).
Click on execute
.
The following list appears.

With the presentation of this list in SAP, it implies that the list has been downloaded into the Excel file mentioned above, thus the file can be opened for formatting and analysis.
Open the program Excel, and on the file tab choose ‘Open’. Double click on the excel files created. The following window should appear:

Click on ‘Next’. Now choose ‘[none]’ in the ‘Text Qualifier’. Click on ‘Next’.

The fields ‘Bank key’, ‘Account Number’, ‘Control key’ and ‘Bank type’, should all be classified as Text:

Afterwards, click on ‘Finish’.
Before formatting the cells of the file, delete the columns with titles from 'WK Req 2' to 'WK Req 9'and insert columns "Valid Documents", "VAT Checked", "Duplicate Bank Accounts", "CC Confirmed", "Bank Details Checked", "Comments", "Validated By", "TL Comments" and "TL ID".
When formatting the excel file, the following should be done:
Select the entire column ‘Account Number’ and format the cell to ‘numbers’ (without decimal places). After this, create a copy of the worksheet and place it in last on the worksheet tabs. Also rename both worksheets:

Inside the first worksheet, on the ‘User’ column, filter in order only to appear the WF-BATCH user (when EMEA country scope) and all the users ids from D&A EMEA team.
Inside the second worksheet, on the ‘User’ column, filter in order to appear all the users not from D&A EMEA team and the WF-BATCH user (when APAC, NAM and LAM country scope).
In the end add a third tab named "Definitions", with this data:
![]()
The file needs to be uploaded in the Google drive.
Then, split file by Data Controller number to be sent to a different data controller for verification. Data Controller cannot verify changes made by himself, both for manual updates and WF.
This chapter shows how to create the Daily report of bank changes file automatically (file with Macro).
Go to Google drive and download to your computer the folder "Automation".

Inside the automation folder you need to open the "Master File_Cat", it's the file with Macro who will generate the report:

Once inside the file, ALWAYS press "Enable Content" (Warning in yellow on the top).

Now you only need to update:
Note: Ensure that the date is correct before generate the report.
When all the updates are done, press "RUN".
This will generate two files inside the folder "Reports" (One for Vendors Team and another one for Customers):

After the files creation, check if the formatting is OK and then save them here in Google Drive.
At the end, send an e-mail to the Team with the Report Bank changes of the day:

Note: The analysis made only concerns the WB-BATCH or "(D&A)" sheet.
Note: Controls described in this section, must be executed by an user different from the user responsible to perform the actions described in the following section.
Valid Document
A Bank account inserted through a Vendor Workflow Request do not need a confirmation document. Nevertheless when it is handled through a Freshdesk ticket it is mandatory.
The document needs to confirm the suppliers Name, Address, VAT ID and bank account (example: an invoice).
The VAT ID must be checked when a document is provided. It can also be confirmed on a suppliers email.
Check if bank details are duplicated using SQ00 transaction (Query areas - standard area; User group - GAC Data Management; Query name - ZZ-VEN-BNK-ACC).
Note: vendors from the same group can have the same bank account.
When based on a Freshdesk ticket a bank data update needs to confirmed by the HelpDesk colleagues. They perform the outbound and confirm the data directly with the supplier using valid contacts (available in the vendors master data or on a official website from the company).
The HelpDesk team outbound can be performed up to 3 times. In case of a telephone outbound the name of the person contacted must appear on the ticket.
Note: The Helpdesk cannot send bank details to the supplier. This action will invalidate the confirmation.
Bank details checked
Entering a system bank account follows certain rules. In this column it is needed to check the format whether the account format you entered complies with the rules (EMEA - Vendors BANK DATA).
The final conclusion is inserted here. If the bank details were correctly or incorrectly updated it is inserted OK or NOT OK with a comment if necessary.
A NOT OK is always analysed between the user responsible for the introduction and the control user. In case of doubts the Team Leader is called to clarify the procedures.
When inserted a NOT OK an email needs to be sent to the TL explaining the situation.
In this column the user id of the controller will be inserted.
The bankruptcy cases are presented by the CC Legal.
Contacts:
Reference "BANKRUPTCY" should be added in "Ref. Details" field when updating a bank account which belongs to a Lawyer, Fiscal Entity, etc which is authorised to receive the payments on behalf of a specific supplier with financial issues (the same is applied in case of use of a permitted payee). All the old bank details must be removed from the vendors master data.
Letters or e-mails received from our bank, informing us about a change of a bank key account belonging to a vendor, are sufficient proofs to proceed with the change without additional controls. The proof should be attached in the request.
The bank details must be preceded by the approval of the CAM (Company Accounting Manager). The list of CAMs can be found in the GAR companies list.
Some bank accounts can also be confirmed in the SOLIA portal - CICC bank accounts Customers & Vendors.
The vendors classified as ZZCD (miscellaneous creditors) have different bank update flows depending of the service provided:
Situations where it is not possible for the Contact Center team to confirm the bank account available on the invoice the DATA team can proceed with the bank data update if one of these two scenarios presents:
The update must be reported to the local responsible for the vendors creation with the following data:
"Vendor XXX has been updated with bank details, as in attached document, without succeeding in an outbound validation with the supplier."
Bank accounts removed as a consequence of a data cleaning can be re-introduced when there is a request stating that this account is still valid.
All bank details update requested by our Rusvinyl colleagues do not need outbound.
Chartering and Shipping suppliers can be identified on the field Search Term 2 (CH, SH). The bank data update of this vendors is considered urgent and must be preceded by the approval of a Logistic Manager (Contact Center outbound is not applicable).
The Logistic Managers are:
