Tasks to be completed when creating an operating procedure (from creation to publication)

  1. Enter the Title of the procedure.
  2. Add the following Labels Labels: 
  3. Fill all fields as described
  4. Once the procedure is completed, publish it using the PtP Procure to Pay approval workflow


 

Table of contents 

By default the table of contents displays Heading 1 & Heading 2 (other levels can be added)


Scope

1. Remove the icon(s) when not applicable

   

2. Add countries when the procedure is for a specific country (optional)

ERP

3. Remove the icon(s) when not applicable

  
  

References

4. Add the link to SAP procedures (when it exists)

Attachments

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

Objective and Scope

This OP explains the steps necessary to update the confirmation control - ARIBA NETWORK

Maintained in WP1_400 and PF1_020.

 

ARIBA is an online platform that aims to facilitate Buyer-Supplier transactional activities.
Allows the supplier:
- to receive and process electronic purchase orders;
- submit eletronic invoices;
- track status of their invoices

1. Manual procedure

  • Go to transaction XK02, insert vendor number and purchasing org.
  • Select Purchasing data
  • In field Confirmation Control insert Z017 (Conf - ARIBA Network)

The master data of the vendor must also be changed:
It is also possible to receive a request to add an email address at company level:
  • Go to transaction XK02, insert vendor number and company code;
  • Select correspondence;
  • In field ACC w/vendor insert the company code and in field Clrk´s internet the email address.


Save the changes and inform Materials team. They will proceed with the request.


NOTE: To remove the vendor for the ARIBA enrolment the action is first by the Materials team and only later by the Vendors team.

2. Mass update procedure

Through the transaction ZMM_ARN_VND_ACT_DCT (PF1_020 and WP1_400) it is possible to update the suppliers master data at general level, purchasing level, output level and contracts level.


The account type is provided by the requester. Nevertheless for the Ariba Enrolment team it is always Enterprise (do not forget in this cases to update the team file). For the task Ariba Report it is used the Standard.

3. ARIBA report

A ticket is daily created with a list of enrolled vendors. To create it the team needs to follow this steps:

  1. Download the file ARIBA to the PC;

  2. In the excel file click in the Prompt button:



  3. A SAP window will appear. It is always the client 400 so click OK;

  4. Select the intended date (previous working day, on weekends select since friday to sunday) and ok:



  5. Then click in the macro button 

  6. Create a Freshdesk ticket with this information (Template already created with the name - ARIBA Execution Report):

    1. To: ptp-data.analysis@support.solvay.com 

      Subject: ARIBA Execution Report - BE Pilot  dd.mm.yyyy (extraction date) 

      Description: Please check the information below and proceed with the ARIBA enrollment for the new vendors. 

      Priority: Medium

      Status: Activities before closure

      Group: PTP D&A EMEA

      Type: PTP Request

      PTP-Process: Data & Analysis

      PTP-Subprocess: Vendor Master Data

      PTP-Category: Creation


  7. Insert the vendor number on the Input File, the RPA will add the Search Term 2 - ARIBA - and send the NL to the supplier and the execution report to us via Freshdesk, in order to confirm if the robot was able to complete all necessary steps.

    (At the moment we are on a pilot phase only for BE)


  8. Run transaction ZMM_ARN_VND_ACT_DCT in PF1, WP1 or both system, depending on the supplier is created.

  9. Fill in the Google sheet created to monetized the ARIBA enrollment.


Useful information