Table of contents

Scope

ERP

  

References

List of SOPS related to PRO 20.1

Attachments

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

1. INTRODUCTION

1.1 Objective of this IOP

This IOP has the purpose to help Data Control in the process to check CODIFHQ tasks, if all updated performed directly, in Master Data, Customers and Vendors are justified by external users, respecting Data & Analysis procedures.

1.2 Scope

This OP applies to manual activities to non authorized users in master data.

2. MAIN PARTS

Responsibilities and description of the steps to follow.

2.1 Responsibility (who does what)

Data Control – to process CODIFHQ requests and tasks

2.2 Procedure

 

Trigger

Verification through the transaction ZZR_CUS_VEND_LOG_CH2 of what were the actions performed in the previous working day beyond the data controllers (belonging to D&A teams in all SC sites). This control is to be made for the key fields:

  • Bank data;
  • Activation of customers or vendors;
  • Transfer links;

 

 

Checks

This OP explains how to extract information and how to check and confirm that the updates were properly executed. And if needed, to revert the actions performed together with the warning to the users not performing valid updates.
This action is done under the scope of CodifHQ.

 

 

CODIFHQ Checks

Use Transaction ZZR_CUST_VEND_LOG_CH2
 
  
 
Select icon  

Select the first variant for the control of PRS data

 Select the second variant for the control of PF1_020; PI1_020 and WP1_400 data

 

 

Toggle if the check is to be made for Vendors or Customers

 

Press  

List retrieved by system

Select Print Preview

List is screen

Select Spreadsheet

Select  

Excel file retrieved

Save file as type Microsoft Office Excel Workbook with name PRS Output DDMMYYYY.xls (for PRS vendors and customers*); and Pf1_020 Output DDMMYYYY.xls (for PF1_020, PI1_020 and WP1_400 vendors and customers*)

 

 

perform the same extraction twice – 1 for vendors and 1 for customers and gather both outcomes in these single files for PRS and for PF1_020 (+ PI1,+ WP1).

 

Corrective Actions:

  • In case of non SBS authorized user send an email [containing attached report extracted] to the user requesting documentation or justification of the action(s), using the following template:

  • Revert the update performed (in case it is PRS)
    In case of update in one of the target systems (PF1_020, PI1_020 or WP1_400) run the IDOC transport transaction Z2RA (vendors) or Z2R8 (customers) to transfer the master data from PRS to the target systems, thus overwriting any local update by the data from PRS (thus following the Solvay Group rules).

Reports Storage

Such reports are to be stored in an accessible storage location to be retrievable in case of need. They are kept in GDrive shared folder: PRS External Users