i.solvay.com/display/DO/Vendor   


Table of contents

Scope


  

ERP


References


Attachments


5. Add the link to attachments (to be stored in AODocs or GDrive) or external links 



1. Objective and Scope


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.

1.1 Definitions

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 idRequester User ID

DIA Validator

PM Validator User ID

Data controller

Data Operator User ID

Target systemSAP 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


2. File extraction

2.1. Manual extraction - Transaction ZZR_LIST_CHG_BANK_VC


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:

  • Execute for vendors;
  • Download vendors data.

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:

  • All the cells should be centered;
  • The titles should be in 'Bold' with a Fill Color of orange;
  • The titles should have an Auto filter

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:

  • The first should be re-named to “RepBank changesVwFXX.XX(D&A)” [where XX.XX is the date of the retrieval selected];
  • The second worksheet should be re-named to “RepBank changesVwFXX.XX (Others)” [where XX.XX is the date of the retrival selected] and it will concern all the other modifications processed outside the D&A EMEA team (manually done by other users).


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 Controler 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.


2.2. Automation Report Bank Changes

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:

  • the date (previous day);
  • and choose the team members at the office. The ones in the office insert "yes" and the ones out of office leave empty.


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):

  • Report Bank Changes VwF_21_08_2019
  • Report Bank Changes CwF_21_08_2019


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:


3. Report Controls

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.


3.1. Controller check

  • 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).


  • VAT ID checked

The VAT ID must be checked when a document is provided. It can also be confirmed on a suppliers email.


  • Duplicate Bank Account

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.


  • CC Confirmation

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 



  • Bank details checked

  • Comments

  • Verified By


If all checks are correct, WF / manual update supported by documents. At the end, WF / manual update, supporting document and report must all share same banking information. If so, each columm related with each check identified should be inserted "OK" and in column "Verified by" the identification of the Operator that did the verification.

If for any reason the bank changes were done incorrectly, insert "Not OK" in Column each column where verification detected incorrect update and the identification of the Data Controller that did the verification on column "Verified By"

  Verifier must inform Team Leader and request correction of information incorrectly approved.


3.2. TL check

4. Particular situations

4.1. Shipping / Chartering

4.2. Bankrupcy


5. Useful information

(to add the scheme of the outbounds and the teams)