Best practices using SAP_ALL for implementations

[step158]

Hi there, 

I am currently leading the end-to-end implementation of the embedded EWM module. As we approach the cutover phase in the client’s production environment, I have requested broad access permissions to perform certain client-specific technical activities. These activities often involve complex object configurations that do not follow the typical transport order process. Given these requirements, I believe it is necessary to have a temporary, consultant-level user role with SAP_ALL access. However, the client has raised concerns about audit compliance and is hesitant to grant this access.

Is there any official documentation or best practice guideline available that supports the need for extended permissions during critical implementation phases? This would help the client understand the necessity of SAP_ALL for certain technical tasks during cutover and allow us to proceed effectively

Thanks in advance

[Sandra_Rossi]

Please don't post to Questions about SAP Websites (issue with community Website, etc.) if it's a question about SAP software. Instead, ask in Technology Q&A: https://community.sap.com/t5/technology-q-a/qa-p/technology-questions. Hopefully someone will fix it for you.

[dennispadia · Accepted solution]

Hello Christian,

Patch 06 of Revision 24 is recently released and now the update path is directly to 2.00.035.00 but Revision 35 is not yet released. You can open message to SAP asking for its release date. In parallel, you can always start with the pre-requisites so by the time Revision 35 is released you can move things further.

Also just to put under your notice that the third party compatibility for S/4HANA 1809 is still not released. So check with third party vendor on S/4HANA 1809 comparability. Below is the SAP Note for compatible partner products for S/4HANA 1809, which is still creation phase.

Regards,

Dennis