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
2.SFDC Opportunities data extract
File format: CSV flat file.
Name: DYS_SF_CRM.csv
Field separator = ‘;’
Decimal separator = ‘.’
Selection Rules for all GBUs :
Opportunity type = “Growth - Product Qualified” or “Growth - Product Requiring Qualification””
Product level = Material (Product level 5)
Additional Rule for Technology Solutions (TS) :
Stage = “3 - Industrial testing” or “4 - Negotiate” or “2 - Negotiate”
Additional Rule for Novecare (CS) :
Stage = “3 - Industrial testing” or “4 - Negotiate” or “1 - Qualify” or “2 - Negotiate”
Yearly Revenue at Maturity >= 50 k€
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,
SAP code = WP1 code = RCS ID
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’
If GBU = SI, PM, AP, TS, CS suffix = ‘R’
4.2 Material:Shipto@DC + Shipto@DC tables
Field | Rule |
Material | = Product code + suffix |
Shipto | Result of customer algorithm (add suffix ‘S’ if SAP code) |
DC | = BU from Material hierarchy |
4.3 Ship-to Hierarchy
Field | Rule |
Shipto | Result of customer algorithm (add suffix if SAP code) |
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
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 :
Pablo (ne pas lire ce qui suit, je pense que ce n est pas à jour)
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