This document will be describing the check and actions to perform when a Supplier is deleted and/or replaced by a new Supplier.

Take into considerations that this  Step by Step is directed specifically for Contracts and Info Records.

1. Objective and Scope

This document will explain on how to analyze and proceed with source management for Vendor to be deleted and respective replacements if detailed.

 It defines the main rules and best practices that should be applied to have the highest level of compliance and data quality within Solvay Group rules, while attending the internal customer needs

1. Requests to be analyzed in scope should always be forward by Vendor Master Data Team without exceptions.
2. Information mandatory from the request detailed in Vendor master data Procedure
3. The Objective is to transfer all the documents and Purchasing sources from the old to the new vendor
4. If no new vendor information is given, the document deletion should be the only objective

2. Analysis Pre Action

1. Check if the Vendor to be deleted is defined as GTBU 
2. Check if the Vendor to be deleted is defined as SELF BILLING
3. Check if the Vendor to be deleted is marked as ARIBA 

3. Vendor to Delete without replacement

1. If Vendor is defined as GTBU no actions is taken before Local confirmation (Contracts should not be deleted)
2. If Vendor is defined as Self Billing , action can be taken regarding source deletion . The last action is to inform AP File of the deletion 
3. If the Vendor is defined as Ariba, check if it's liked with ARIBA Catalog. If so, escalate to PSL Data & Reporting team.
4. Extract Contract and PIR information relevant for the target vendor (preferably standard EKKO / EINA )
5. Contact respective buyer(s) informing about the source deletion and attach the report
   
   1. If Buyer challenges the vendor deletion, Transfer the ticket for Vend Master data without action. 
6. On D+1 Contact, reinforce the message and include Vendor PANEL
7. On D+2 if no reaction, Delete sources and inform Buyer, again with the sources deleted in a report
8. Transfer the ticket to Provisioning EMEA

3. Vendor to Delete with identified replacement

1. If Vendor is defined as GTBU no actions is taken before Local confirmation (Contracts should not be deleted)
2. If the Vendor is defined as Ariba, check if it's liked with ARIBA Catalog. If so, escalate to PSL Data & Reporting team.
   1. Additionally inquire if the new Vendor should be considered
   2. If so, replicate Catalogs if exist
   3. Transfer Child ticket with the information to SRM7 Team
3. Extract Contract and PIR information relevant for the target vendor (preferably standard EKKO / EINA )
4. Contact respective buyer(s) informing about the source deletion and the new Supplier to replace. attach the report
   
   1. If Buyer challenges the vendor deletion or the vendor replacement , Transfer the ticket for Vend Master data without action. 
5. On D+1 Contact, reinforce the message and include Vendor PANEL
6. On D+2 if no reaction, Replicate Sources for the new Vendor and Delete sources for the former Vendor, informing  Buyer, again with the sources deleted in a report
   1. Replicate only sources for materials bought in the last 18 months if no confirmation arrives from the Buyer
7. Transfer the ticket to Provisioning EMEA

Related articles

Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.