3731016 - Working Together for Safe Changes: What to Expect From Support and Why Technical Support does not Make direct changes to customer environments

• Customers requesting configuration or operational changes in their SAP environments.
• A customer expects Technical Support to make configuration or operational changes in their environment (for example: create/modify user record, configure system, run jobs or processes, change provisioning settings, perform refreshes or DB copies).
• The support case is delayed or the customer is informed that Support will not proceed without additional steps (written authorisation, approved access, or routing to Operations).
• The customer reports frustration at perceived slow response or a “blocked” resolution.

BizX Successfactors 

• Employee Central

why won’t support change my system, can support modify my tenant, how to authorize support to make changes, what does support need to change my environment, why does support require written authorization, how to enable support access, how to request environment refresh or DB copy, can support create admin account for me, Compliance & security tags, support change policy, technical support changes, customer authorisation required, written authorisation support, no unauthorized changes, environment change policy, approved access only, Flex Partner Provisioning, auditable access, support access enablement, account modification policy, create/modify admin account, support scope and limits, operations escalation, service request for refresh, database copy request, system/tenant ID in case, correct case-to-system mapping, provide system details for support , KBA , LOD-SF-EC , Employee Central , How To