Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 55 Next »

VersionDateDescriptionAuthor
v.130.03.2017CreationJeremie Seabra
v.214.12.2017Lightning updateSophie Millet
v.325.05.2018Lightning Spring 18 updateSophie Millet

0. Definitions

0.1 Account Definition 

Accounts are Solvay’s customers, partners and distributors.
Each account stores information such as a name, address, phone numbers and customer attributes.
For each account, you can link information such as opportunities, activities, cases, visit reports, notes and attachments.

 

Record typePartner typeDefinition
Corporate Groupn.a.Account specifically created for grouping accounts under one parent. Corporate Group is not interfaced with SAP
Non SAP customerProspectSolvay's potential customers (sold-to or ship-to or both, as SAP customers), not yet recorded in SAP
Indirect CustomerCustomer Solvay is not directly doing business with, but is buying Solvay's products
Non-Buying EntityAccount not buying products to Solvay, but in relationship with Solvay (i.e. Corporate Centers, Research Centers, Universities, Laboratories, etc.)
Third PartyAccount not directly involved in a selling transaction but involved to perform specific services for a SAP Customer
VendorAccount providing goods or services to Solvay
Chemplex ProspectProspects which are not in SAP, belonging to Chemplex business - part of Novecare Chemlogics.
Chemplex CustomerCustomers which are not in SAP, belonging to Chemplex business - part of Novecare Chemlogics.
SAP customerShip-toSAP customer to whom Solvay is shipping the products
Sold-to & Ship-toSAP customer to whom Solvay is selling and shipping the products

0.2 Account Components & Layouts

Each account record type is displayed with a different layout, using different components :

ComponentDefinitionStandard / CustomCorporate GroupSAP customerProspect
iToolsAccount specifically created for grouping accounts under one parent. Corporate Group is not interfaced with SAPAppX  
Chatter StandardXXX
Related listsVisit reports, Opportunities, Quotes, VOC, ...Standard XX
Related listsCommitments, ContractsStandard X 
Sold and Pending Orders Custom, integrated with Clickview X 
Competitive Insights Custom XX
Service related listsOpen Complaints, Sample Requests, Customer Requests, Customer Specific Requirements, WebformsCustom XX
Incoterms & Payment terms Custom X 
Highlights CustomXXX
GBU customer segmentation CustomXXX
Activity StandardXXX
Prospect conversion Custom  X

0.3 Account Owner

Each Account in Salesforce must have one and only one “Account Owner”. This rule is in place differently depending if the account is a customer or a prospect:

  • For prospects, Account Owner is the creator, the sales rep who created the prospect in Salesforce
  • For customers, Account Owner is “Admin User”, a generic name meaning the account is controlled by SAP.

Account Owners

Consequences

After conversion, the Account Owner becomes an Account Team member.

Roles & Responsibilities

The Account Owner is in charge of the maintenance of his accounts. He keeps the related data up to date and maintains the account team upon request from other BU's/GBU's

0.4 GBU customer segmentation

The GBU customer segmentation object and the BU segmentation child objects records for each account the related list of GBUs and BUs working with this account, the type of relationship between the GBU / BU and the account and the classification of this account for the GBU/BU.

The "GBU customer segmentation" component shows the list of GBU customer segmentation (including BU child records) related to the account.

There is a filter on the component to show by default all the GBU customer segmentation records (collapsed, no BU records).

  • If the filter is set on "No", then all team members and all contacts relationships related to the account are listed within the component
  • If the filter is set to "Yes", then :
    • A GBU segmentation record is highlighted (the 1st by default)
    • Team members displayed are listed filtered by GBU (if the multi GBU access field of the team member user record contains the GBU value of the GBU segmentation record highlighted)
    • Contacts displayed are listed filtered by GBU (if the related GBU field of the contact record contains the GBU value of the GBU segmentation record highlighted)

0.5 Highlights

The Accounts highlights is a master-view of all the related information which might interest the user when dealing with a specific account. This component also appears in his home page and provides cross-accounts view for the accounts which the user is related to.

If an object is not used by a GBU, the count on objects never apply and the value "N/A" is displayed against the object instead of a number.  The definition of those custom settings are listed here.

 

 Aroma PerformanceCoatisFibrasNovecarePerformance PolyamidesPeroxidesSilicaSoda Ash & DerivativesSpecial ChemCorporateSolvay Energy Services
Opportunities           
Quotes          N/A
Contracts           
Visit Reports           
Customer Requests     N/A N/AN/A  
CSR N/AN/A N/AN/AN/AN/AN/AN/AN/A
Complaints           
Samples          N/A


If the count of an object is 0, the 0 is not clickable.

If the count of an object is > 0, the figure is clickable is will open a modal view listing the details of the objects :

Counts of objects are based on the accounts processed : 

  • For a SAP or non SAP account, the Highlight component counts the number of records of different objects related to the current account;
  • For a Corporate Group, the Highlight component counts the number of records of different objects related to all accounts where the Corporate group is the parent.

Then, the following rules apply:

 

  • Open Opportunities (not closed) where Creation Date > "time range" days ago, for instance creation date > April 28 if today is May 28 and time range is 1 month
  • Quotes where where Creation Date > "time range" days ago
  • Visit Reports where where Creation Date > "time range" days ago
  • Contracts where where Creation Date > "time range" days ago
  • Open Cases (not closed/inactive Complaints, Sample Requests, Customer Requests, Customer Specific Requirements) where Creation Date > "time range" days ago

Where "time range" is based on the number of months the user selected on the component.

Data are then filtered by :

  • "My Data": The record will be counted if the active user is owner of the record
  • "GBU":  the record will be counted if the GBU of that record is the same as the one the user Selected (GBUs listed in the filter are the GBU listed in the multi GBU access field of the team member user record)
  • "My Team Data":  the record will be counted if Ithe active user is on the record team (Cases, Opportunities, etc) or if the active user is the owner

1. Functional Process : Account Management

1.1 Use Cases

 

Sold-to/Ship-to customer creation requested in Salesforce (prospect in SFDC and non-existing in SAP)

 

In this scenario, when checking the request, assumption is that the request is valid and no duplicate account is found. Next scenario covers the situation when a duplicate account is identified.

A GBU customer segmentation record and a contact record, linked to the prospect account, is mandatory to convert a prospect to a SAP customer.

Duplicate sold-to/ship-to customer creation requested in Salesforce (existing in SFDC and interfaced with SAP) 

 

Note: If the prospect created already exists as an account in SFDC, the “merge” operation will be done by IS Support Team.

Duplicate sold-to/ship-to customer creation requested in Salesforce (prospect in SFDC but existing customer in SAP used by another GBU)

 

Sold-to/Ship-to customer update requested in Salesforce

 

Sold-to/Ship-to customer update in SAP

 

Sold-to/Ship-to customer deletion in SAP

 

Sold-to/Ship-to customer creation requested rejected by CSR

 

Note: typical use case: A dummy account is created by mistake by a user confusing Test and prod environments

 

1.2 API and Mail

Following information are transferred through the interfaces between Salesforce and SAP

1.2.1. APIs

  • API  : customer creation request from Salesforce

    • Salesforce account ID

    • Account Owner

    • Account Name

    • Address (street, zip/postal code, city, country)

    • Address (local language) (street, zip/postal code, city, country, language key)

    • Customer Service Representative Name

    • Customer Service Representative Email address

    • Account Partner Type (sold-to, ship-to or sold-to & ship-to)

    • If ship-to : take the Salesforce account ID of the sold-to account defined in the relationship (in order to create the relationship ship-to/sold-to in SAP)

  • API C: customer creation order from SAP

    • Salesforce ID

    • PRS ID

    • RCS ID

    • Account Name

    • Address (street, zip/postal code, city, country)

    • Address (local language) (street, zip/postal code, city, country, language key)

    • Account Partner Type (sold-to, ship-to or sold-to & ship-to)

    • Account Status ( = Validated)

  • API D: customer update order from SAP

    • Salesforce ID

    • PRS ID

    • RCS ID

    • Account Name

    • Address (street, zip/postal code, city, country)

    • Address (local language) (street, zip/postal code, city, country, language key)

    • Account Partner Type (sold-to, ship-to or sold-to & ship-to)

    • Flag for deletion

  • API E: Account Status

    • Account Status ( = Validated)

1.2.2. Mails

  • Mail B : customer update request from SFDC (will trigger a mail that contains the following values)

    • Salesforce account ID

    • PRS ID

    • RCS ID (could be blank in RCS)

    • Requested by

    • Salesforce must request the user to select the appropriate CSR based on the Account team.

    • Update requested:

      • Account Name

      • Address (street, zip/postal code, city, country)

      • Address (local language) (street, zip/postal code, city, country, language key)

      • Relationship (between a sold-to and a ship-to)

      • Flag for deletion

  • Mail F : additional information requested at customer creation in Salesforce

    • Account Information

      • Salesforce ID

    • Additional information on the Sold-to:

      • VAT Number

      • Contact (lookup to select an existing contact)

    • If the Sold-to account is also a Ship-to account, additional information :

      • Shipping Conditions

      • Full/Partial Loads

      • Delivery Hours

      • Incoterm 1

      • Incoterm 2

    • If the Sold-to account is not a Ship-to account as well, existing ship-to account and additional information:

      • Ship-to Account (lookup to select an existing ship-to in Salesforce)

      • Shipping Conditions

      • Full/Partial Loads

      • Delivery Hours

      • Incoterm 1

      • Incoterm 2

    • If the Sold-to account is also a Bill-to account, following checkbox:

      • Checkbox

    • If the Sold-to account is not a Bill-to account as well, additional information:

      • Bill-to Name

      • Bill-to Address

    • If the Sold-to account is also a Payer account, additional information:

      • VAT Number

      • Payment terms

      • Currency

      • Payment mode

      • Yearly Estimated Turnover

      • Estimated Volume

      • Estimated Value of First Order

    • If the Sold-to account is not a Payer account as well, additional information:

      • Payer Name

      • Payer Address

      • VAT Number

      • Payment terms

      • Currency

      • Payment mode

      • Yearly Estimated Turnover

      • Estimated Volume

      • Estimated Value of First Order

1.3 Processes not including an interface with SAP

1.3.1. Creation of an Account

 

1.3.2. Update of an account

 

If the sales rep is actively involved at an account, and cannot edit it, then the user should add itself to the account team using the "Manage my Account Team Role" Button.

 

 1.3.3. Corporate Group Creation

 

  • Corporate Group Creation
    • Sales Reps enter in SFDC the new Corporate Groups after Go-Live in draft status.
    • S&M will review / approve on regular basis these corporate groups in SFDC
    • SBS  will create the Corporate Group in GBR, then the code is replicated in SAP (PRS)
    • Hierarchy Updates
      • Sales Reps update the link Corporate Group – Customer in Salesforce
      • On regular basis, S&M review these links based on a report executed by GBUs data steward. This report will include the info on how many GBUs are working on the Corporate Group.
      • SBS will assign on regular basis the customers to the Customer group either in PRS and GBR.

1.3.4.  Transfer of Account Ownership

 

Figure 12: Transfer of Ownership Process

1.4 Trigger the creation of a GBU / BU customer segmentation

If not existing, a new GBU customer segmentation record is created automatically on accounts each time a transactional record is created :

  • A opportunity is created
  • A quote is created
  • A visit report is created
  • A case (any record type) is created

The newly created GBU customer segmentation records is created with the following values :

  • Record type =  GBU customer segmentation
  • GBU = GBU of the transactional record (opportunity / case etc)
  • GBU Account Sub-Type = End user

A BU customer segmentation child record is created as well with the following values :

  • Record type =  BU customer segmentation
  • BU = BU of the transactional record (opportunity / case etc)


If the account is linked to a Corporate group account, and if the GBU customer segmentation doesn't exist on the related Corporate Group, Corporate GBU/BU customer segmentation records are created as well on the related CG group.

If a contact is linked to the transactional record (opportunity / case etc), the "related GBU" field of the contact is updated as well with a new GBU value stored in a picklist with multiple values.


When a user with a single GBU value in his/her profile (not applying to MBU users) creates a new prospect, a new GBU customer segmentation record is created using the GBU of the user, as well as a Corporate GBU customer segmentation, but the BU customer segmentations records are not created.

When a user with a single GBU value in his/her profile (not applying to MBU users) creates a new contact, the "related GBU" field is populated automatically with the GBU of the active user.

2. Data Model & Security

2.1 Main objects


  1. Accounts: Standard Salesforce Object to manage the information about the Ship-to and Sold-to related with the Complaint
  2. Account Team: Salesforce object that allows to list all the Solvay users working on the account and to define for them a specific role (account manager, customer service representative, strategic marketing, etc.).
  3. Customer Segmentation: Object used to record which GBU and BU is working on the account and specify some information per GBU or BU (i.e. customer classification, GBU Account type, etc.).
  4. Contacts:  Standard Salesforce Object to manage the contact person from the Ship-to or Sold-to
  5. Contacts to Multiple Accounts: Standard object used to link multiple contacts to multiple accounts.
  6. Case: Standard Salesforce Object to store and manage all general information regarding a Complaint
  7. OpportunityStandard Salesforce Object to manage potential deals.
  8. Visit Reports: Custom object to store and manage visit reports.

2.2 Account Security Model 

 

Action

All Sales Users

Account Owner / GBU Data Steward

and hierarchical above

Account Team Member with Read/Write access

and hierarchical above

View

yes *

yes

yes

Create

yes

yes

yes

Request Conversion / Update

no

yes

yes

Edit

no

yes

yes

Delete

no

no

no

 

* Confidential accounts can only be seen by Owner and Account Team members

 

2.3 GBU customer segmentation data model 

GBU customer segmentation parent object

FieldMandatory ?Picklist valuesDefinition
Information (managed by Sales Rep)
AccountX Account involved in this GBU customer segmentation
GBU Account Sub-TypeX

Compounder

Distributor

End-User

 Original Equipment Manufacturer

Non-profit Organization (University , R&D, HQ)

Service Provider (Consultant, Testing Laboratory)

Trader

Transformer/Converter

Wholesales / Retailer

Type of relationship between this account and the GBU

 

GBUX  
Account information
General Account Information   
Information (managed by CommX)
GBU Customer Classification 

A

Potential

B

C

D

Segmentation of the account for the GBU
GBU Account type 

Prospect Account

Standard Account

Critical Account

Key Account

key account is a current or potential account who represents a major & strategic part of Solvay's growth potential and contribution, with an important marketing stake for Solvay.
A reference in the market, willing to partner with Solvay (e.g. on innovation), and a global, regional or local customer with a complex relationship to manage.

 

BU customer segmentation child object

FieldMandatory ?Picklist valuesDefinition
Information (managed by Sales Rep)
AccountX Account involved in this BU customer segmentation
BUX  
Main End-Use  Main End-Use of products sold by this BU for this account
Information (managed by CommX)
Main Customer Interaction Model (CIM) 

Broad offering provider

Customized solution provider

Lean/Reliable

Product/process innovator

Trader/transactional provider

 
Service Model 

Picklist values are defined by GBU, and dependent on the GBU

Coatis : Segment 1, Segment 2, Segment 3, Segment 4, Segment 5 and Distributor

Aroma Performance : 1 F&B RV, 1 F&F RV, 2a F&F RV, 2b F&B RV, 3 F&F LEA, 4 F&B LEA, 5 F&B RV

Fibras : Segmento 1 - KA, Segmento 2  - A&P, Segmento 3 - B, Segmento 4 - C

Peroxides : Specialty - A, Specialty - B, Specialty - C, , Industry - A, Industry - B, Industry - C

Other GBUs didn't define a service model segmentation.

Service Model info  

URL link of the GDrive folder containing the service model detailed information :

Coatis https://drive.google.com/drive/folders/15xH74ZO_0Plk81zsewJ959BDCH6qykOY?usp=sharing

Fibras:

 https://drive.google.com/drive/folders/1UFnlq_awKjSPr7IoVTu6NmZ7tVC1x0wl?usp=sharing

Aroma : https://drive.google.com/drive/u/1/folders/1dzgkKrjlZGCQGfBExt3yYIaVZTyTdTLP
 

Peroxides : https://drive.google.com/open?id=1BurO6Fimiv4qwH4DUbaVgMYSxWAH4Q2z

2.4 Contacts

 

3. Account Custom Buttons & Features

Custom Buttons

"Convert Prospect To Customer" Button

After creating a new Prospect, the user can request its conversion by clicking on the "Convert Prospect to Customer" button. This will launch a wizard asking the user to complete information needed for the Customer's creation. This button is only available on Prospects.

Users can request the customer to fill the following template, in order to request all needed information to convert the prospect into a customer : Customer Creation and Modification Form.

"Manage my Account Team Role" Button

Any Salesforce user can add it self to an account team by clicking on the "Manage my Account Team Role" button. The user will be prompted to select the role that best describes its relation with this account : Account Manager, Key Account Manager, Customer Service Representative, Sales Support, Business Development, Technical Marketing, Global Key Account Manager, Research & Innovation, Strategic Marketing. This button is available on Prospects and SAP Customers.

"Visit Preparation Report" Button

This buttons allows users to check some key information related to the selected account in order to prepare visits to the client.This button is available on Prospects and SAP Customers.

"Customer Update Request" Button

If a user identifies some out of date information, it may request to update the account information by clicking on the "Customer Update Request" button, and by filling the information that is out of date. This button is only available on SAP Customers.

 



Last modifications :

UserLast Update
Laurent Champiot-ext 3329 days ago
Jeremie Seabra-ex 3173 days ago
Sophie Millet-EXT 2867 days ago
GILLES, Anne 997 days ago
PEYTRAUD, Josiane 964 days ago
Julien Andreoli-ext 2763 days ago
MARKUS, Evita 530 days ago
BRAHIM, Walid
KANJA-ext, Zakaria
NWANGWU, Daniel
Sebastien Rouxel

 

The best way to get IT support is to use the new Service One Platform.