General presentation

Objective of the application

BIP SRM (Supplier Relationship Management) is the standard SAP module for supply used within our

organization and a migration project is currently under way to implement a new version called SRM7.

The SRM7 project will have an impact on all of the nearly 4 000 users worldwide with the introduction of new

processes and structures. Following phase 1 in which the process and technical designs were analyzed and

agreed, we now move to phase 2 which turns to implementation, user training and roll out.

The aim of this newsletter is to give an overview of this second phase of the project and briefly describe the

changes that will take place with the introduction of SRM7. In future editions, we will focus on particular topics

and explain them more fully, as well as giving more details of the implementation planning.

News in SRM7

Why a new version ?

• The GBUs, Functions and RBS had demands for the improvement of our transactional procurement tools.
• In accordance to Move for Growth, the IT / RBS Board decided to meet these expectations by the launch of the SRM 7 Project.
• The SRM 7 migration +is not+an upgrade; it is a new implementation on new processes & a new version.

Who are the users?

The SRM module is used on all sites working with RCS => 95% of Rhodia activities.

Non RCS Acetow Freiburg users are still using SRM4. We will keep loading in BW for this application.

What are the main changes ?

• New functionalities:
  Simplification of transactional procurement processes for Procurers and Requesters
  Align approval structure and threshold with “Move for Growth” organization for GBUs and functions
  Involve Buyers directly in SRM to input the sourcing result & to perform Purchasing approval
  Allow central Engineering to manage WW projects expenses in SRM
• New designs:
  Graphical interface
  Workflow e-mails format for approval requests
  E-catalogue searching tool

source: SRM7 Project Newsletters

Roles & Access

Roles and access

SRM7 s part of the Purchasing application Info Area AREA_PUR in BW)

To access SRM7 queries, users need to have access to GSV Applications with the role menu ZR_RCS_CA_M02 and the role of the application (* nd, super, key user or AMTS*)

Queries are published in Purchasing role, in a sub folder SRM7 - Purchasing Shopping Cart

Authorisation objects

For all providers, the authorisation object is the company

Dataflow presentation

Overview

Info providers

In SRM7, we have 2 DSO, 1 Info cube and 1 Infoset mixing the 2 DSO and some master datas.

DSO_SC03* contains data about shopping cart, ie prices, material, etc...

• We created * UB_SC01* to have better reporting performance.
  DSO_SC04* concerns approval workflow with a split by approval type: purchasing, financial, etc...
• We mix shopping cart data and approval information in Infoset * ST_SC02*. In this solution, an infoset works better than a multiprovider.

Data loadings

Info providers and objects loaded

In the Excel file attached Technical dataflow SRM7.xls ou will find a list of all objects included in:

• Data Sources used for master datas, texts, DSO
• DSO
• Cube
• Infoset
• Queries

There are also details of routines (in start routine or in the rules) and the process chain.
For the moment, loading of DSO_SC04 is not scheduled.

Loading frequency

SRM7 is loaded every working day fter SRM4 loading, around 0:30 am (Paris time)

BW and SRM7 systems

• BD2 is linked to WBD
• BQ2 is linked to WBQ
• BP2 is linked to WBP

BS2, BV2 and BM2 are not linked to BW environment.

Queries presentation

2 queries are available for reporting in BW

BW - Shopping Cart Prices (Core Query)

Technical name of the query : BW_QRY_CUB_SC01_0001
This query allows user to display the list of shopping carts with values, material, DSF, attachments.

BW - Shopping Cart - Prices and Workflow (Core Query)

Technical name of the query : BW_QRY_IST_SC02_0001
This query allows user to display the workflow of a shopping cart with all the approval steps with the approver.

THIS QUERY IS NOT PUBLISHED BECAUSE NOT VALIDATED FOR THE MOMENT !