on 08-10-2018 9:35 AM
Is there an outline of this process?
When you say non-approved expert config, what do you mean. In our experience with S/4HANA Public Cloud, the process for requesting expert configuration is submitting an incident in the support launchpad documenting what you want changed, the business case and urgency, just like a normal incident, and hope that SAP agrees to make the change. They pass that request to an expert team who will reach out to you, make that change to your Q system and then you request a transport to Production once you're ready.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ryan,
A non-approved expert configuration is a request does NOT go through incident, but it's a request that should be coordinated with your CSM/Product expert. In SAP, we use the terminology impediment, the result/solution can be a non-approved expert configuration, a future release date, a workaround or rejection of the request. There is a specific document that you/SI must fill out and then taken back to SAP Product/Development for consideration. This documentation can be provided by your CSM/PE.
There are pre-approved expert configuration that can be found in the Activate roadmap under the following, titled "Expert Configuration and SSCUI Reference.xlsm (SAP Customer)" : https://go.support.sap.com/roadmapviewer/#/group/BE47098A-617A-43EF-A27E-DFD801D70483/roadmap/IMPS4H...
Guillem Oña wrote 3 extensive blogs about S/4HC implementations, including a description of the Expert Configuration process.
https://blogs.sap.com/2017/07/18/the-key-to-a-successful-implementation-of-s4hana-cloud-13/
Hi John,
In order to request any expert configurations, you should reach out to your assigned Product Expert, Customer Engagement Executive, or Customer Success Manager for more info.
While there is no documentation per se for non-approved expert configs (since they are just that, non-approved), depending on risk factors of it being a showstopper, the PE/CEE/CSM can raise an incident or JIRA impediments to SAP developers to see what can be done if a workaround is not possible.
-SB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Our example would be configuration of the ability to close ledger 0 and ledger 1 independently. It is a customer request documentation template. At least this was described to us by our Customer engagement manager.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.