1. Functional Process
Process Overview
Products are products sold by Solvay. We can also have few products under development.
They are created with a possible hierarchy on 5 levels.
Definition & use cases
Novecare Marketing Managers Permissions to manage MSP information on Novecare products
Novecare Marketing Managers are people in charge of managing MSP information in Novecare products, specifically on level 4 products. However, they could edit the information in the sections mentioned below, on level 4 or level 5 products that are active.
Novecare Marketing Managers are able to read only (but not modify) the fields in Product Information, Product details, Description information and Translations sections. On the other side, they are only be able to read the remaining info on products.
User Name | |
|---|---|
Caroline Fontenaille | |
Anais Marquilly | |
Astrid TAY | |
Marie Arzel | |
Cleyver MATUSALEN |
Their profile is End Users Lightning to see the information in products. They have the Reports and Customer Product Association Management""permission set assigned to have edit access on the fields in the MSP product sections. Additionally, there is a rule to prevent them from editing the product name and the active checkbox.
They cannot activate or deactivate products and they can never change a product name.
Definition
A Product contains the following information:
- Name
- Code
- GBU
- Status: Standard or Product in Dev.
- MDG code (for Level 4 and 5 if MDG interface is active for the GBU)
- Active flag
- Unit of Measure
- SAP origin
- Density
- Concentration
- Level
- Parent (except for Level 1)
- Translations
- SAP External ID: Used with MDG interface
Creation process
2. Security
Product security model
Who can create? | |
Who can see? | Any user |
Who can update? | |
Who can delete? |
3. Specific rules & automation
Product Creation
The following fields are mandatory at Product creation:
- Name
- GBU
- Level
Product Update
4. MDG Interface
Interface Specification Document
MDG is a SAP system where products are defined with all their information (production, sales, plant, ...). It's interfaced with back end system: WP1 and PF1 and with CRM.
For the moment, only 3 GBUs are live in this system: Soda Ash & Derivatives, Special Chem and Novecare. And so only them are interfaced with Core CRM.
The interface runs once a day around 1:00 AM french time. Each time a product is created or updated in MDG, it's sent to CRM.
As depending on the GBU, the level 4 is not managed the same way in SAP, the creation or update of such products is sent only with the update of a products Level 5. For example if you have product level 5 named AAA linked to level 4 named BBB, if BBB is updated, nothing is sent to Core CRM. BUT if AAA is updated, then the interface will send the information of AAA AND the information of BBB.
If we receive an update for a product which doesn't exist in Core CRM, it will be created.
Only level 5 have a MDG code. That's why it's not the MDG code which is used as interface key. We've created a specific field visible only by Admin named "SAP External ID". This field is the concatenation of 3 information: SAP origin + GBU code on 2 characters + Product Code.
Example of SAP Exernal ID for product 90076419 from Novecare: RCSCS90076419.
The GBU codes are stored in the custom settings "GBU Code". But to summarize, we have:
- Novecare: CS
- Soda Ash & Derivatives: SD
- Special Chem: CH
- Peroxides PE
DANGER: if a user creates manually a product, he will not populate the SAP External ID as he can't see this field. Then if we receive this product with the interface, the system will not find it and create a new one. So at the end, we'll have duplicate. That's why, if some one from Soda Ash, Special Chem or Novecare creates a product Level 4 or 5, he must advise us, so we can update this field. BUT as there is an interface, this should not happen as all products should be created with it. But, as very often they forget, it's good to run a report to track situation. There is one in the folder SBS User Support named "Products with no SAP External ID". There can be few exception when there is no code or no real one.
There is a logic involved to map ISACTIVE Level 4/5 fields from SAP to Salesforce's "IsActive" field:
For Level 4 products-
- If ISACTIVE_L4 from SAP=true, check level 1/2/3 flag in Salesforce for (SLV11_PRO_SAP_External_ID__c = ORIGIN_L4+GBU_L4+PROD_CODE_L4 )
- If level 1/2/3 are set in Salesforce, only then set Salesforce IsActive=true
- Else set Salesforce IsActive=false
- If ISACTIVE_L4 from SAP=false or blank, set Salesforce IsActive=false
For Level 5 Products-
- If ISACTIVE from SAP=true, check level 1/2/3 flag in Salesforce for (SLV11_PRO_SAP_External_ID__c = ORIGIN+GBU+PROD_CODE )
- If level 1/2/3 are set in Salesforce, only then set Salesforce IsActive=true
- Else set Salesforce IsActive=false
- If ISACTIVE from SAP=false or blank, set Salesforce IsActive=false
Rules in Webmethods
| No | SAP Products | SAP status | Webemethods Logic | CRM user Action |
| 1 | New L4 + New L5 Created | L4 and L5 is active | Query CRM to check L4 is active with L3,L2,L1. Send L4 and L5 as inactive if both not present | For the first time creation User will manually update the L4,L3,L2,L1 in L5 and set them as active. |
| 2 | Old L4 + New L5 | L4 and L5 is active | Query CRM to check L4 is active with L3,L2,L1. If L4 is active, send L4 and L5 as active. Elseif L4 is not active set L5 as Inactive | L4 needs to be updated correctly by CRM user |
| 3 | Old L4 + Old L5 | L4 and L5 is active | Query CRM to check L4 is active with L3,L2,L1. If L4 is active, send L4 and L5 as active. Elseif L4 is not active set L5 as Inactive | No Action required |
| 4 | New L4 + New L5 Created | L4 is inactive and L5 is inactive | Query CRM to check L4 is active with L3,L2,L1. Send L4 and L5 as inactive. | No Action required |
| 5 | Old L4 + New L5 | L4 is active and L5 is INactive | Query CRM to check L4 is active with L3,L2,L1. If L4 is active, send L4 as active and L5 as inactive. Elseif L4 is not active with sublevels set L4 & L5 as Inactive | L4 needs to be updated correctly by CRM user |
| 6 | Old L4 + New L5 | L4 is inactive and L5 is active | Query CRM to check L4 is active with L3,L2,L1. If L4 is active, send L4 as inactive and L5 as inactive. Elseif L4 is not active with sublevels set L4 & L5 as Inactive | No Action required |
| 7 | Old L4 + Old L5 | L4 is inactive and L5 is active | Query CRM to check L4 is active with L3,L2,L1. If L4 is active, send L4 and L5 as inactive. Elseif L4 is not active set L5 as Inactive | No Action required |
| 8 | Old L4 + Old L5 | L4 is active and L5 is inactive | Query CRM to check L4 is active with L3,L2,L1. If L4 is active, send L4 as active L5 as inactive. Elseif L4 is inactive set L5 as Inactive | L4 needs to be updated correctly by CRM user |
Last modifications : |
|---|
| User | Last Update |
|---|---|
| Alves, Susana | 485 days ago |
| MENDES, Dina | 1465 days ago |
| PEYTRAUD, Josiane | 1940 days ago |
| MILIC-ext, Nikola | 483 days ago |
| GILLES, Anne | 807 days ago |
| BRAHIM, Walid | |
| KANJA-ext, Zakaria | |
| NWANGWU, Daniel |
The best way to get IT support is to use the new
Service One Platform.
