Table of Contents
Overview of the integration process
Opportunities extract from SFDC
The opportunities are extracted from SFDC based on 2 criteria :
- Product level :
Material (=Product level 5 in SFDC) must be registered in the Opportunities.
- Stage :
Opportunity management process was reviewed in July 2021. Each GBU defined from which stage the Opportunities should be integrated in DynaSys :
Opportunities are extracted from SFDC by Webmethod (Middleware) only based on the generic rules as defined during the project.
The rules to extract SFDC fields into the .csv file
SFDC Opportunities interface to DynaSys - specification
https://docs.google.com/document/edit?hgd=1&id=18chSRbj0iZZcp2O_-NKFUJt7LqZOKTWWMYsxFfk4_FA
Interface SFDC Opportunities for DynaSys DP
1.Functional Requirement
DynaSys Demand Planning is supporting the Demand Planning process to produce sales forecasts shared in each GBU organisation. Currently, forecasts are managed mainly on a 18 months horizon, on products and customers already active in SAP.
The objective of this interface is to integrate SFDC Opportunities in DynaSys Demand Planning and get a sales forecast visibility on customers which are not currently active in SAP, but with a sufficient probability to be taken into account.
The requirement is coming from the GBU Soda Ash & Derivatives. Currently this interface is also used by Technology Solutions and Novecare.
The other GBUs using DynaSys Demand Planning are not requiring this interface.
See the presentation below detailing the functional specifications :
CRM opportunities to DynaSys DP
Embedded Google Drive File docid 10gMR31ICDeK6kI0z3VDCSPgxtuiGQ3DRun4uSCo4zdE
2.SFDC Opportunities data extract
File format: CSV flat file.
...
DYS_SF_CRM.
...
Field separator = ‘;’
Decimal separator = ‘.’
Selection Rules for all GBUs :
...
Product level = Material (Product level 5)
Additional Rule for Technology Solutions (TS) :
...
Additional Rule for Novecare (CS) :
...
The specific integration rules are implemented in DynaSys (in the GetUnC).
| GBU SCo | Opportunities integration | Additional specific integration rules |
|---|---|---|
| Aroma Performance | No | N/A |
| Novecare | Yes | Opportunities stage <> Closed Priority project <> E Revenue > 50 000 € |
| Technology Solutions | Yes | / |
| GBU ECo | Opportunities integration | Additional specific integration rules |
|---|---|---|
| Perox | Yes | / |
| Silica | No | N/A |
| Soda Ash & Derivatives | Yes | / |
| Special Chem | In progress |
Prospects/CRM DFU creation and/or transcodification
Suffix based on the source system
Suffix is determined based on the Source system identified in the CRM file.
If the Source system = RCS, then the Suffix should "R"
If the Source system = PF1, then the Suffix should "S"
Note : The source system is maintained in CRM SFDC based on the Product code (in case of inconsistency, a ticket must be rasied to CRM team).
Customer/DFU transcodification
SFDC code = Account ID
Transcodification process to be described (INT_TRANSCO)
...
Additional Rule for all GBUs excepted Technology Solutions (TS) and Novecare (CS) :
Probability GREATER OR EQUAL TO 85%
Fields:
...
SFDC Field
...
Example of value
...
GBU: Code
...
‘SD’ for SA&D
...
BU
...
‘Soda Ash’
...
DC
...
Empty when the GBU is hosted by SAP-PF1
...
Account Name: Account Record Type
...
‘SAP Customer’ or ‘Non SAP Customer’
...
Account Name: Account ID
...
‘0012400000atlxb’
...
Account Name: PRS ID
...
‘338671’
...
Account Name: RCS ID
...
‘2014850’
...
Account Name: Account Name
...
‘PT SAYAP MAS UTAMA NPWP: 01.304.651.1-092.000’
...
Account Name: City
...
JAKARTA
...
Account Country: Code
...
‘ID’ for Indonesia
...
Product Information: Product Id: Product Code
...
‘60102’
...
Opportunity Owner: Employee Number
...
‘63014233’ for Markus WU
...
Employee Name
...
User
...
...
Product Information: Unit of Measure: Name
...
‘ST’ for short tons
...
Stage
...
‘3 ? Closed Won’
...
Probability (%)
...
100
...
Targeted first delivery date
...
25/01/2017
...
Product Information: Currency
...
USD
...
Opportunities volume Y+0
...
4000
...
Opportunities volume Y+1
...
5000
...
Opportunities volume Y+2
...
6000
...
Opportunities price Y+0
...
220
...
Opportunities price Y+1
...
218
...
Opportunities price Y+2
...
215
...
Opportunity ID
...
‘0062400000H5GSIAA3’
...
Pricing Method
...
78.0
...
Shipping Site
...
‘BBAA’
...
Production Site
...
‘BBAA’
Interface schedule:
Every day at 00:30 CET
Transfer file by SFTP to destination
server wdcdyap21.eua.solvay.com
folder D:\DynaSys\ITF\Files\In
3.Customer code algorithm in DynaSys datahub
-- 06/2019 VPT : add GBUs TS (Technology Solutions) and CS (Novecare)
For GBU = SD, PE
SAP code = PF1 code = PRS ID
For GBU = SI, PM, AP, TS, CS,
...
SFDC code = Account ID
...
*In DFU check, ignore the DC dimension, only check the Material:Shipto combination.
4.Mapping SFDC - DynaSys
4.1 Suffix rule
A suffix needs to be added to the product code and SAP customer codes when used:
...
If GBU = SD, PE, suffix = ‘S’
Each new opportunity is imported as Material:shipto@DC in Dynasys hierarchy based on the SFDC codification of the prospect. Once the shipto is codified into SAP, the related opportunity has to be changed into the final DFU.
This process is performed through INT_TRANSCO table.
Master table data integration
If GBU = SI, PM, AP, TS, CS suffix = ‘R’
...
- Material:Shipto@DC + Shipto@DC tables
Field | Rule |
Material | = Product code + |
Suffix | |
Shipto | Result of customer algorithm |
for PF1 : if filled, customer PF1 + 'S' else customer SFDC for WP1 : if filled, customer WP1 + 'R' else customer SFDC | |
DC | = BU from Material hierarchy |
...
for PF1 or DC + 'R' for WP1 |
- Ship-to
...
- /Prospect
Field | Rule |
Shipto | Result of customer algorithm |
(Customer transcodification) | |
City | = [Customer_Country]_ZZ_[Customer_City] |
Region | = [Customer_Country]_ZZ |
Country | = Customer Country |
...
- Sales Rep
Sales Rep. interfaced in Shipto@DC master table
If GBU = SD, PE, TS
Field | Rule |
Shipto | = Result of customer algorithm (add suffix if SAP code) for PF1 : if filled, customer PF1 + 'S' else customer SFDC for WP1 : if filled, customer WP1 + 'R' else customer SFDC |
DC | = BU from Material hierarchy for PF1 or DC + 'R' for WP1 |
Sales Rep | = Sales Rep code from DYS_BW_SREP interface for WP1 |
- Sales Rep / Account Manager
To be reviewed
If GBU = SD, PE
Interfaced in ProductGroup:Shipto@BU table
Field | Rule |
ProductGroup | = ProductGroup from Material hierarchy |
Shipto | = Result of customer algorithm (add suffix if SAP code) for PF1 : if filled, customer PF1 + 'S' else customer SFDC for WP1 : if filled, customer WP1 + 'R' else customer SFDC |
BU | = BU from Material hierarchy for PF1 or DC + 'R' for WP1 |
Account Manager | = Sales Rep Account Manager Code |
If GBU = TS, no mapping.
If GBU = SI, no mapping.
...
(no opportunities imported for SI)
- Local Currency
Parameter at level 2:
Field | Rule |
Material | = Product code + suffix |
Shipto | = Result of customer algorithm (add suffix if SAP code) |
BU | = BU from Material hierarchy |
LC | = Currency code (last column) |
...
Opportunities details integration
Opportunities details are imported in the User model U00 :
Opportunity details
Different information are imported :
- Opportunity Number
- Opportunity ID
- SFDC Link (based on the Opportunity ID)
- Opportunity Stage
- Opportunity Probability
- Opportunity Targeted First delivery
- Opportunity Project Opp
Opportunity volume and price
Parameter CRM Opportunities (ID 16795157), in U00 - Import - IN model:
Forecast volume = Expected Yearly Volume
Split by month from the Targeted First Delivery Date
Field | Rule |
Material | = Product code + |
Suffix | |
Shipto | = Result of customer algorithm (add suffix if SAP code) |
DC | = BU from Material hierarchy |
Month | - |
CRM Opportunities | Volumes are all received in tons (i.e., “Opportunities_volume_Y0”, “Opportunities_volume_Y1”, Opportunities_volume_Y2”). A conversion has to be done to kg before integrating them. The “UoM” column is only being displayed as information (i.e. the original UoM associated with the Production in SFDC BEFORE conversion to tons) and is NOT related to the volumes that are all in tons. |
CRM Opportunities Price | Prices are received in €/ton. The “Currency” column is only being displayed as information (i.e. the original Currency in SFDC). The prices are not converted when "Targeted first delivery date">current year (because volume Y+0 = 0 and no conversion is calculated) and unit of measure different from T (as in T no need to convert) => a fix was set up directly into the DH |
- Opportunity Monthly Volume
...
Pablo (ne pas lire ce qui suit, je pense que ce n est pas à jour)
Volumes
- calculation :
TFD = Target First Delivery date
If Si TFD(year) < Current year,
(Vo/12) from Jan Y0 -> Dec Y0
(V1/12) from Jan Y1 -> Dec Y1
(V2/12) from Jan Y2 -> Dec Y2
Else if TFD(year)= Current year (Y0),
(Vo/number of months from TFM -> End of TFY) from TFD -> Dec Y0
(V1/12) from Jan Y1 -> Dec Y1
(V2/12) from Jan Y2 -> Dec Y2
Else if TFD(year) = Y + 1,
0 from Jan Y0 -> Dec Y0
(V1/number of months from TFM -> End of TFY) from TFD -> Dec Y1
(V2/12) from Jan Y2 -> Dec Y2
Else if TFD(year) = Y+2
0 from Jan Y0 -> Dec Y0
0 from Jan Y1 -> Dec Y1
(V2/number of months from TFM -> End of TFY) from TFD -> Dec Y2Prix
- Opportunity Monthly Price determination
CRM price = P0 from current month -> Dec Y0
CRM price = P1 from Jan Y1 -> Dec Y1
CRM price = P2 from Jan Y2 -> Dec Y2
GBU functional documents
Not all the GBUs are currently importing the Opportunities into DPx (ex: Spe Chem). What is more, Opportunities DFUs tend to be less followed/taken into account than standard (SAP) DFUs.