<style>
.toc-macro ul {display: block; counter-reset: item}
.toc-macro li {list-style-type:none}
.toc-macro li:before {content: counters (item, ".")". "; counter-increment: item}
</style> |
This document describes the process to handle Customer Master Data to create, modify and extend a new/existing customer accounts in PRS (PF1_50) and RCS (WP1_400) environment and describes the roles and responsibilities of each actor in this process.
Data Operations Team based in Riga is responsible to handle all Technology Solutions, Composites, Novecare Customer Master Data for all regions and Intercompany extensions and Sales area data updates.
Requests for Intercompany customer record general data creation/general data modification are within Lisbon SBS team’s scope.
Abbreviation | Description | Abbreviation | Description | Abbreviation | Description |
|---|---|---|---|---|---|
PRS | Permanent Reference System (PF1_50) | COA | Certificate of Analysis | IC | Intercompany |
RCS | Rhodia Core system (WP1_400) | MSDS | Material Safety Data Sheet | DBA | Doing Business As |
SBS | Solvay Business Services | NAM | North America | T/A | Trading as |
PO | Purchase Order | LAM | Latin America | C/O | Care of |
PO BOX | Postal Office Box | EMEA | Europe Middle East Africa | ||
WF / CWF | Customer Workflow | APAC | Asia Pacific | ||
SO | Sales Organization | TrZones / TZ | Transportation Zones | ||
FD | Freshdesk | CRM (a.k.a. SF) | Customer Relationship Management (Salesforce) | ||
CSR | Customer Service Representative | FAO | For the attention of |
In Solvay customer master data is being maintained in four systems – PF1_050, PF1_020, WP1_400, PI_020.

CRM - (Customer Relationship Management Tool) - used to manage a company's interaction with current and potential customers. Salesforce (SF) is the CRM tool used at Solvay.
Salesforce request is initiated in CRM by Customer Service. Once customer general data is completed by Customer Service Representative, created prospect can be converted into SAP account. It happens through Customer Workflow, which is created automatically once request for conversion is submitted.
CRM/Salesforce is not used by Composite Materials. New customer requests are received via Freshdesk and Workflow is manually created and submitted by Data Operations Representative. |
Customer Workflow functionality is used in PRS to request customer creation and changes. Data Management team modifies and approves Workflows initiated by CRM or submits Workflows manually in PRS (PF1_50). After that the Workflow is routed for validation and as soon as it is approved, customer code is generated in the system. Data Operations Representative completes the setup in PRS (PF1_50) and RCS (WP1_400) and Credit Manager completes credit data in CICC (PI1_20).
PRS (PF1_050) – is used to maintain general data of the customer (name, address, registration number, general contact information, bank details). This information is automatically distributed to the rest of the systems (WP1, PI1, PF1_020 ).
RCS (WP1_400) – is used to maintain customer company code and sales organization information. Once customer general information has been changed in RCS (WP1_400) changes will appear in the CRM system.
PRS (PF1_020) – has similar functionality as RCS, but used by Solvay companies, which are not in Riga Data Operations scope.
CICC (PI1_20) - is used by Credit Management to set up and maintain customer credit data.
New creations and changes made in PRS will be distributed to one or both of the systems (WP1 and/or PF1_020).
Sales Area Data (sales organization) – created manually by DM Riga in WP1 (shipping information, partner functions etc.).
Company code data is created automatically in WP1 based on the sales organization for which customer was opened, if transaction SWOC06T is used.

Every regular customer consists of 4 roles:
| Customer Role | Setup | Usage |
|---|---|---|
| Sold-to | Can be used as sold-to and as ship-to | Sold-to is used to store information relevant to sales, shipping and billing. This is the account on which Sales Orders are created. |
| Payer | Always a separate record even if address matches with other parties as it is set up under specific account group. For records created before 2015, payer can have the same number as sold-to and therefore in case of changes/extension, we should leave the set up as it is without creating a separate Payer party. Payer can be used as Payer or Bill-to. Linked with sold-to. | Payer (Main Payer) is the single account where Credit Management team maintains financial/credit data for the customer. The links are kept in "Extra Master data - Solvay Cross Reference". Billing documents are created on this account. |
| Payer-bis | Used when payer already exists in SAP with a different address (same country). In such case Payer-bis is created and linked with the existing Payer (Main Payer). | Billing document is created on this account. Financial/credit data is maintained in Main Payer. |
| Ship-to | Created as separate record, if ship-to address differs from sold-to. Linked with sold-to. | Ship-to is used to indicate the address to which goods will be delivered. |
| Bill-to | Created as separate record, if bill-to address differs from payer. Linked with sold-to. | Bill-to is used to indicate the location to which invoice needs to be physically sent. |
Customer account group defines role of the customer and is chosen upon customer creation.
| Customer Role | Account Groups in PRS Only following account groups should be used | Corresponding account Groups in RCS (WP1) |
|---|---|---|
Ship-to | Z**2 | 0002 |
Payer | Z**4 | 0003 |
Payer Bis | Z**5 | 0003 |
Sold-to | Z**8 | 0001 |
Bill-to | Not maintained in PRS | 0004 (only maintained in WP1) |
Sold-to & payer - should not be used for new creations. "old" main payer all-in one (PY-SP-SH-BP) - Credit account is not being created, but still is being used??? | Z**1 | 0001 |
In case if checking for duplicates there is found an existing appropriate account in PRS 1st account account group, this account can be used:
|
New customer creation (including new ship-to accounts) requests must be initiated only through CRM (SF) by CSR. Once request has been submitted in CRM, workflow will be created in PRS and DM Riga will receive automatically generated CRM request form which should include all necessary documentation.
CRM/Salesforce is not used by Composite Materials - 75 division. New customer requests are received via Freshdesk and Workflow is manually created and submitted by Data Operations Representative. |
Request for Account Conversion
This form should include all necessary general and sales data information. If mandatory information is missing, you must contact requester in order to receive it. Mandatory documentation and information depends on GBU.

[Production] - Request number

In case if in area Additional Ship-to Account is indicated data for separate ship-to creation, it means that WF number for ship-to creation has been generated, but has not been provided as notification from Salesforce.
In order to find this WF number use transaction Z1S_CWF_REQUEST in PF1_50 (field - Display or change existing request). Search by company name, WF creation date or requester name to find correct WF.


In case of duplication, (existing account with matching information is found) - generated WF is not needed, that's why it needs to be rejected, but Sales Force IDs needs to be merged by submitting FD ticket to SF CRM Team. |
Following checks need to be performed before proceeding with customer creation/change.
Duplicate check is mandatory before customer creation, name/address modification and extension. |
To check if the customer already exists in the system, execute transaction XD03. The check should be performed in both systems: PRS and RCS. Duplicate check in PRS is also done automatically by the workflow, but it’s not as specific, therefore manual duplicate check is mandatory.
It’s advised to use three types of searches:
In order to access search enter transaction XD03 and click on the “search box”. In PRS/RCS you can choose several options on how to search for duplicates. It’s advised to use Customers (general), Customers by Address Attributes, Customers by Tax Information.
Remember to use “*” before and after the significant part of the customer's name to search for it, this will show all customers that have any character written after or before the name typed. This can be used for any search field in SAP.

If the customer is not created in the system, you can proceed with its creation. If it is already created, check for possible updates and forward the number to the requester.
In order to check, to which target system customer has been extended (WP1, PF1_20 or both) - the following check can be performed:

Upon receiving request for customer creation, changes, extension, re-activation check whether mandatory documentation is attached.
All rules and document requirements depending on GBU can be found by following the links below:
Technology Solutions: https://docs.google.com/document/d/1_dVLkxxZJBVQ-_U3ECyoCPbpMKfM-BNXyn5MXUfb-Ok/edit
Novecare & Aroma: https://drive.google.com/file/d/1Nb0fUdMjTaUsT-dDiGbI1xL_NyyN75yt/view?usp=sharing
Aerospace: https://docs.google.com/document/d/1CMnBHoT1MQlcqslMFlB2rFzH8Rdzzldtnvx7h84BCgU/edit?usp=sharing
In order to create customers correctly, there are mandatory data validation rules. Please follow this link to see validation WI with all the rules for specific systems and web pages where validation is performed.
For WP1 customers mandatory validation applies to:
When creating a new WF request, there are some rules that must be strictly followed:
“ | ‘ | ` | = | ( ) | [ ] | < > | # | * | ^ | \\\\ | /// | á | ö | ç | ã |
Company | CO | Street | ST | Suite | STE |
Incorporated | INC | Road | RD | Building | BLDG |
Corporation | CORP | Drive | DR | Apartment | APT |
Manufacturing | MFG | Court | CT | South | S |
Limited | LTD | Avenue | AVE | South East | SE |
Limited Liability Corp | LLC | Boulevard | BLVD | East | E |
Limited Liability Partnership | LLP | Lane | LN | North East | NE |
Public Limited Company | PLC | Highway | HWY | North | N |
Place | PL | West | W | North West | NW |
Plaza | PLZ | South West | SW |
|
|
PRS (PF1) is the main system where all customer general data is stored. It’s connected with WP1 where data is transferred after submitting a Workflow.
Once logged you can access your Business Workplace (Workflows) by entering transaction Z1S_CWF_REQUEST.

There will be 3 options available:
| New customer creation | Used to create Workflow for new customer creation. To proceed populate customer name, city and country,
| |
| Existing customer data modification | If customers general data needs updating, it should be changed through WF by entering PRS account code and modifying as requested. Both Payer and Sold-to should be updated accordingly. | |
| Display or change an existing request | Used to display or modify WF. Workflow created in Salesforce has status - N-SAVED, therefore it’s not visible in WF inbox before Data Team modifies and saves it by using Display or change an existing request. |

Transaction Z1S_CWF_REQUEST_LIST can be used to review the list of requests and their current status.
If Salesforce generated WF for incorrect account group, or you want to create payer and sold-to in one WF, in order to avoid double work caused by separate account creations, you can use the steps described below:
See below fields to be completed/verified in the Workflow:
|
Save record: ![]()
Confirm Sold-to creation (if needed):

Once confirmed, workflow is submitted and will appear in the inbox of Data Operations teams. Once the record is reviewed and approved by Data Controller you will receive a notification to your e-mail containing sold-to/payer or ship-to number in PRS - for sold-to and payer you will receive two separate notifications to your personal mailbox with PRS account numbers provided.
New customer creation always needs to be started with PAYER party creation! |
After you have received system notification that a new PRS payer customer has been created, you can proceed with customer setup in WP1.

Transaction ZWOC06T - Customer management is used to create the required extension for Sales Organization/ Distribution Channel/ Division.

In notification received there is only PRS payer or sold-to account number mentioned, therefore you need to find corresponding RCS number. Click on search icon
and select Customers by DUNS and Xref codes tab in order to find customer RCS number.
If customer data has been transferred to WP1, one record should appear in the search results.

Test for Info |
Test for Note |
Test for Tip |
Test for Warning |
Panel Example |
<style>
#backToTopButton {
position: fixed;
right: 20px;
bottom: 20px;
Z-index: 1;
}
</style> |