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 :
Link to the project presentation
Opportunities are extracted from SFDC by Webmethod (Middleware) only based on the generic rules as defined during the project.
Here is the link to the specification document with the the rules to extract SFDC fields into the .csv file DYS_SF_CRM.
The specific specific rules are implemented in DynaSys (to be completed - Get UNC)
| GBU | Opportunities integration | Additional specific integration rules |
|---|---|---|
| Aroma Performance | No | N/A |
| Novecare | Yes | Opportunities stage <> Closed Priority project <> E Revenue > 50 000 € |
| Perox | Yes | / |
| Silica | No | N/A |
| Soda Ash & Derivatives | Yes | / |
| Special Chem | In progress | |
| Technology Solutions | Yes | / |
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
Customer tra
INT_TRANSCO
Transcodification process to be described (INT_TRANSCO)
Opportunities integration
See the presentation below detailing the functional specifications :
CRM opportunities to DynaSys DP
SFDC Opportunities data extract
3.Customer code algorithm in DynaSys datahub
SFDC code = Account ID
*In DFU check, ignore the DC dimension, only check the Material:Shipto combination.
4.Mapping SFDC - DynaSys
4.2 Material:Shipto@DC + Shipto@DC tables
Field | Rule |
Material | = Product code + Suffix |
Shipto | Result of customer algorithm |
DC | = BU from Material hierarchy |
New Prospect creation
Field | Rule |
Shipto | Result of customer algorithm |
City | = [Customer_Country]_ZZ_[Customer_City] |
Region | = [Customer_Country]_ZZ |
Country | = Customer Country |
4.4 Sales Rep / Account Manager
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) |
BU | = BU from Material hierarchy |
Account Manager | = Sales Rep Account Manager Code |
If GBU = SI, no mapping.
4.5 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) |
4.6 Opportunity volume and price
Forecast volume = Expected Yearly Volume
split by month from the Targeted First Delivery Date
⇒ For information in a new data field “ CRM Opportunities”.
No impact in the forcing loop
Price: not required for the moment
Parameter CRM Opportunities (ID 16795157), in U00 - Import - IN model:
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). |
Volume integration rule :
Volumes
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 Y2
Prix
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.
Here below of the functional rules defined for GBU Novecare:
Novecare functional Opportunites document