CORE - SAP Interface Process Flow
Diagram: https://app.diagrams.net/#G1y-kvF_vTRCxg1pJKVO6L07nzspPC7FpM
Meeting
Meeting
Technical document
| Embedded Google Drive File | ||||
|---|---|---|---|---|
|
Technical sending data should be synchronous (can the middle-ware handle this?). Any error coming from SAP should be consumed in SF immediately
Nicolas Balbiani informed that the response time from SAP may be up to 30 seconds due to geographic distances.
"Send to SAP" button- this action is meant to go to:
Questions to address in SAP interface
- Data mapping -Fields needed to send to SAP (preferably automatically - not requiring User input) - see table below.
- What is the mandatory information to send a quote to SAP?
- if the information is missing, who will provide it?
- should we put the fields as mandatory?
- What other data points are CSR's checking before pushing data to SAP? Is it just the basic data from the Google Slides? Or does it include the data points from Quotes as well (aka, prices, incoterms, etc).UI for CSRs - use Case object what data is needed to display at Case Task object to be able to send the needed data in SAP
- Allocation of Cases tasks for SAP data upload - Queue or specific individual
- What responses can we expect from SAP (error messages/etc)? (Nicolas Balbiani & HISLER, Olivier)
- how to handle the error messages - via a log record under the Opportunity?
- ie, mis-mapping on SF Accounts / SAP entries
- error /discrepancies happening before sending the data to SAPerror happening after sending the data to SAP - CSR to delete manually the entry in SAP - then correct in SF and re-send the data.
- how do CSR's identify an entry wrongfully sent to SAP in SAP (to be able to delete it?)
Basic Flow for CSR handling SAP automation
Data mapping - Fields needed to send to SAP
(as per Google Slide) - complement with Technical document (section 2.3.1)Field Name | Salesforce field |
|---|
Action
Comment
Division
Under investigation in this Google Sheet
Scenario 1 : Automatically filled if can be retrieve from products. In that case a migration will be needed on products
Scenario 2 : To be filled on the quote by the CSR or the KAM
Could we retrieve it from the product or should be different depending of the quote ?
If depending of the quote do we need to have potentially different values by products ?
Business region
Under investigation in this Google Sheet
To be filled on the quote by the KAM
Sales Organization
Under investigation in this Google Sheet
To be filled on the quote by the CSR
Product Hierarchy
Product Hierarchy Code (tbc)
Automatically filled
Material group (level 4)
Material Group Code
Automatically filled
Incoterm
Standard incoterm or deviated incoterm
To be filled on the quote by the KAM
Should we give the possibility to quote several incoterms.
Impact on webshops ?
Sold to
Account Name
To be filled on the quote by the KAM
Go-Live - can only happen after due to SAP cloud migration
Google Slide - Business Preso April
| Embedded Google Drive File | ||
|---|---|---|
|
Google Slide - Business Preso August
Embedded Google Drive File docid 17KPmnLpe_VcZQIXk0Gi0LJzTupiiyDblYAWmQbHl7gs
JIRA EPIC
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
| Jira | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Meeting
Meeting
Technical document
| Embedded Google Drive File | ||||
|---|---|---|---|---|
|
Technical sending data should be synchronous (can the middle-ware handle this?). Any error coming from SAP should be consumed in SF immediately
Nicolas Balbiani informed that the response time from SAP may be up to 30 seconds due to geographic distances.
"Send to SAP" button- this action is meant to go to:
- A queue (either Case or Task)? OR
- A specific Primary CSR of the Opp/Account (If CSR - all Accounts need to have a Primary CSR filled in OR any CSR in Account Team (not Primary of the Account)?
Questions to address in SAP interface
- Data mapping -Fields needed to send to SAP (preferably automatically - not requiring User input) - see table below.
- What other data points are CSR's checking before pushing data to SAP? Is it just the basic data from the Google Slides? Or does it include the data points from Quotes as well (aka, prices, incoterms, etc).
- UI for CSRs - use Case object
- what data is needed to display at Case object to be able to send the needed data in SAP
- Allocation of Cases for SAP data upload - Queue or specific individual
- What responses can we expect from SAP (error messages/etc)? (Nicolas Balbiani & HISLER, Olivier)
- how to handle the error messages - via a log record under the Opportunity?
- ie, mis-mapping on SF Accounts / SAP entries
- how to handle the error messages - via a log record under the Opportunity?
- Loopback between CSR and Account Managers in case there are errors/discrepancies in data at OLI level - Chatter?
- error/discrepancies happening before sending the data to SAP
- error happening after sending the data to SAP - CSR to delete manually the entry in SAP - then correct in SF and re-send the data.
- how do CSR's identify an entry wrongfully sent to SAP in SAP (to be able to delete it?)
Basic Flow for CSR handling SAP automation
Embedded Google Drive File docid 1nGj3R289nABjeGLz5puC2llw9HB4UkPzt1jn6mJidfg width 75% height 75%
Data mapping - Fields needed to send to SAP (as per Google Slide) - complement with Technical document (section 2.3.1)
SAP Field
Salesforce field
Action
Comment
Division
Under investigation in this Google Sheet
Scenario 1 : Automatically filled if can be retrieve from products. In that case a migration will be needed on products
Scenario 2 : To be filled on the quote by the CSR or the KAM
Could we retrieve it from the product or should be different depending of the quote ?
If depending of the quote do we need to have potentially different values by products ?
Business region
Under investigation in this Google Sheet
To be filled on the quote by the KAM
Sales Organization
Under investigation in this Google Sheet
To be filled on the quote by the CSR
Product Hierarchy
Product Hierarchy Code (tbc)
Automatically filled
Material group (level 4)
Material Group Code
Automatically filled
Incoterm
Standard incoterm or deviated incoterm
To be filled on the quote by the KAM
Should we give the possibility to quote several incoterms.
Impact on webshops ?
Field Type | Salesforce Object | ||
|---|---|---|---|
Price Valid From | SLV44_Quote_valid_from_internal_only__c | date | SLV44_ONE_Quote__c |
Price Valid To | SLV44_Quote_valid_to_External__c | date | SLV44_ONE_Quote__c |
| Sales Organization | PP_SAP_Sales_Org__c | restricted picklist | SLV44_ONE_Quote__c |
| Division | SLV44_SAP_Division__c | text | SLV44_ONE_Quote_Line_Item__c |
| Distribution Channel | PP_SAP_Distr_Channel__c | restricted picklist | SLV44_ONE_Quote_Line_Item__c |
Bracket From | PP_Bracket_From__c | double (18, 2) | SLV44_ONE_Quote_Line_Item__c |
Bracket To | PP_Bracket_To__c | double (18, 2) | SLV44_ONE_Quote_Line_Item__c |
| Incoterms | SLV44_Incoterms__c | restricted picklist | SLV44_ONE_Quote_Line_Item__c |
| Manufacturing Plant | SLV44_Manufacturing_Plant__c | Id | SLV44_ONE_Quote_Line_Item__c |
| Shipping Plant | SLV47_Shipping_Plants__c | id | SLV44_ONE_Quote_Line_Item__c |
| Manufacturing Plant Name | PP_Manufacturing_Plant_Name__c | text | SLV44_ONE_Quote_Line_Item__c |
| Shipping Plant Name | PP_Shipping_Plant_Name__c | text | SLV44_ONE_Quote_Line_Item__c |
| Quote Line Item ID | Id | Id | SLV44_ONE_Quote_Line_Item__c |
Bracket (From-To) | SLV44_Bracket_From_To__c | text | SLV44_ONE_Quote_Line_Item__c |
| Annual Volume | SLV44_Estimated_Annual_Volume__c | double (18, 2) | SLV44_ONE_Quote_Line_Item__c |
| Quote Id | SLV44_ONE_Quote__c | Id | SLV44_ONE_Quote__c |
Product Level 4 (Product) | SLV44_Product_Level_4__c | Product2 | SLV44_ONE_Quote_Line_Item__c |
Product Level 5 (Material) | SLV44_Product_Level_5__c | Product2 | SLV44_ONE_Quote_Line_Item__c |
Quoted Price | SLV44_Quoted_Price__c | currency (18, 2) | SLV44_ONE_Quote_Line_Item__c |
| Currency Iso COde | SLV44_SAP_Cond_currency__c | text | SLV44_ONE_Quote_Line_Item__c |
Condition Type | SLV44_SAP_Condition_Type__c | text | SLV44_ONE_Quote_Line_Item__c |
| Customer Number | SLV44_SAP_Customer__c | text | SLV44_ONE_Quote_Line_Item__c |
| Customer Name | SLV44_SAP_Name__c | text | SLV44_ONE_Quote_Line_Item__c |
| Material Name | SLV44_SAP_Material__c | text | SLV44_ONE_Quote_Line_Item__c |
Unit of measure | SLV44_SAP_Unit_of_measure__c | text | SLV44_ONE_Quote_Line_Item__c |
Valid From | SLV44_SAP_Valid_From__c | text | SLV44_ONE_Quote_Line_Item__c |
Valid To | SLV44_SAP_Valid__c | text | SLV44_ONE_Quote_Line_Item__c |
Ship-to | SLV44_Ship_to__c | Id | SLV44_ONE_Quote_Line_Item__c |
Unit of Measurement | SLV44_Unit_of_Measurement__c | restricted picklist | SLV44_ONE_Quote_Line_Item__c |
| Lead Time | SLV49_Lead_Time__c | double (16, 0) | SLV44_ONE_Quote_Line_Item__c |
Fields to save the response from SAP - to be created in Salesforce CORE
| Field Name | Salesforce field | Field Type | Description |
|---|---|---|---|
SAP Response | oli_SAP_Respon | text | Updated by CORE System, based on the integration status SAP Integration In Progress, SAP Integration Completed, SAP Integration Failed, Manually Created in SAP, Closed - No action needed |
SAP Response(Detail) | SAP_Response_Detail__c | text | Save the answer coming from SAP |
Sold to
Account Name
To be filled on the quote by the KAM
Go-Live - can only happen after due to SAP cloud migration
Google Slide - Business Preso April
| Embedded Google Drive File | ||
|---|---|---|
|
Google Slide - Business Preso August
Embedded Google Drive File docid 17KPmnLpe_VcZQIXk0Gi0LJzTupiiyDblYAWmQbHl7gs
JIRA EPIC
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|