| Stakeholders | Unit | Meeting | Meeting
|
|---|---|---|---|
| Business | Yes | ||
| SF PM | Yes | Yes | |
| SF Functional | Yes | Yes | |
| @Nicolas Balbiani / Baud, Delphine | SAP | - | Yes |
| Web method | - | Yes | |
| SF Dev | Yes |
Technical document
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
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 ? |
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
Google Slide - Business Preso August
JIRA EPIC
| Stakeholders | Unit | Meeting | Meeting
|
|---|---|---|---|
| Business | Yes | ||
| SF PM | Yes | Yes | |
| SF Functional | Yes | Yes | |
| @Nicolas Balbiani / Baud, Delphine | SAP | - | Yes |
| Web method | - | Yes | |
| SF Dev | Yes |
Technical document
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
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 ? |
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
Google Slide - Business Preso August
JIRA EPIC