3401017 - Re-Provisioning in SAP S/4HANA Public Cloud (SAP Finance & Spend / SAP Supply Chain Management)

Symptom

You have questions about S/4HANA Public Cloud Reprovisioning of system for a customer,

Resolution

Quick Links:
Purpose of Re-Provisioning | When is Re-Provisioning Recommended? | Proactive Measures to Avoid Re-Provisioning | Impact of Re-Provisioning | Data Backup Options | Re-Provisioning vs. Rollback or Fixes | Re-Provisioning Process | Cost and Additional Considerations | FAQ’s regarding Re-provisioning service request | Conclusion

Purpose of Re-Provisioning

Re-provisioning in SAP S/4HANA Public Cloud (for SAP Finance & Spend and SAP Supply Chain Management) serves to restore the system’s technical and functional foundation to a clean, consistent, SAP-standard initial state. This provides an opportunity for customers to re-implement SAP-delivered best practices content to align with their current business requirements.

When is Re-Provisioning Recommended?

Re-provisioning may be necessary under the following conditions:

- Changes in organizational structure
- Modifications to the fiscal year variant
- Adjustments to group ledgers or currency settings
- Incorrect initial activation
- Faulty Central Business Configuration (CBC)
- Missing or unwanted scope items
- Request for a fresh production tenant

Proactive Measures to Avoid Re-Provisioning

To prevent the need for re-provisioning, customers should:

1. Review SAP Best Practices Documentation:
2. Validate Critical Configurations Early:
  - Group ledgers, fiscal year variants, group currency, and organizational structures must be carefully reviewed before saving configurations, as changes cannot be reverted once saved.
3. Utilize the Starter Tenant for Testing:
  - Model the implementation in the starter tenant to ensure alignment with long-term business transformation goals.
  - Partners should demonstrate the starter implementation to customers for validation before finalizing configurations.

Warning Mechanisms During Implementation

SAP provides warnings at critical phases of initial configuration to highlight irreversible settings (e.g., group ledgers, fiscal year variants, and scope items). Once configurations are saved, they cannot be modified without re-provisioning.

Impact of Re-Provisioning

Re-provisioning resets the entire system landscape (DEV, TEST, PROD) to a fresh state. Key impacts include:

- Data Loss: All existing data (including production data) will be permanently deleted.
- Configuration Loss: Custom configurations will be removed.
- System Downtime: The entire landscape will be decommissioned and reprovisioned.

Data Backup Options

- Customer Data Return App: Download production data for audit purposes (SAP Note 3088877).
- Configuration Template Export: Export development configurations for reference (SAP Help Portal).

Note: These backups are for reference only and cannot be used to rebuild the tenant.

Re-Provisioning vs. Rollback or Fixes

- Avoid Re-Provisioning: Early detection of issues allows for rollback within HFC (Hybrid Flexible Configuration) phases.
- Fixes: Currently unavailable; SAP is exploring future solutions.

Re-Provisioning Process

1. Request Submission: Raise a ticket in component XX-S4C-OPR-SRV.
2. Validation: The CBC Development Team assesses whether re-provisioning is necessary.
  - Decommissioning & Re-Provisioning:
  - Tenants are decommissioned.
  - New tenants are provisioned via SAP4Me (typically within one day).

Note: The starter tenant is not reprovisioned; the process begins with the development tenant.

Cost and Additional Considerations

- No Additional Cost: Currently, re-provisioning is free, but future policies may change.
- Effort & Data Loss: Customers must account for implementation efforts and potential production data loss.
- Pre-Re-Provisioning Discussion: Customers may request a meeting with SAP support for clarification.

Question Number	FAQ’s regarding Re-provisioning service request
1	What purpose does re-provisioning serve in S4 HANA Public Cloud / SAP Finance and Spend / SAP Supply Chain Management ? Re-provisioning in SAP S/4HANA Public Cloud— ( SAP Finance & Spend / SAP Supply Chain Management )—serves the purpose of restoring the system’s technical and functional foundation to a clean, consistent, SAP-standard initial state. This given an opportunity for the customer to re-implement the SAP delivered best practices content to meet the current requirements of their enterprise / business.
2	Under what conditions is re-provisioning recommended, and what factors usually make it necessary? Reprovisioning "might" be a necessity under the following circumstances Org Structure Fiscal Year Variant Group Ledgers / Currency Wrong Initial Activation Faulty CBC Missing/Unwanted Scope Items Fresh Production Tenant
3	How can systems be managed proactively to prevent re-provisioning scenarios? Familiarise yourself with the process by referring to the best practices document available. https://learning.sap.com/courses/implementing-sap-s-4hana-cloud-public-edition/conducting-fit-to-standard-workshops Refer to the Initial Configuration Guide : https://learning.sap.com/courses/configuring-sap-s-4hana-cloud-public-edition-manufacturing-execution/introducing-sap-central-business-configuration Customer Success Guide : https://dam.sap.com/mac/app/e/pdf/preview/embed/3mBJ3sC?ltr=a&rc=10&doi=SAP1190509 3100892 - Group Valuation in SAP S/4HANA Cloud Fiscal year variant https://support.sap.com/content/dam/SAAP/Sol_Pack/S4C/Library/Others/2508_predelivered_FYV.xlsx Supported Fiscal Year Variants.xlsx The above references will help us align your implementation with Business requirements.
4	What measures are available to avert reprovisioning during the implementation ? Sufficient warnings are enabled throughout the initial configuration to enhance your vigilant to the critical aspects - Group Ledgers, Scopes that can be chosen only during the initial scoping, Fiscal Year Variant, Group Currency and org structures. Once the configuration is saved across milestones during the initial configuration, there is no possibility to revert. The following approach is highly recommend, Utilise the starter tenant to model your implementation, prepare a checklist of the business transformation in the next 5 years, weigh the options chosen. This will help the implementation remain relevant. If you are a partner, demo the starter implementation if the requirements gathered and implementation are good match. Customer should validate, taking the time to reflect is the key.
5	Are appropriate warning mechanisms established at critical phases of implementation? Yes , Warning messages do exist at every critical phase and please make sure to read such messages without miss and proceed accordingly.
6	What impact does re-provisioning have on the existing system, including data, configurations, and availability? Re-provisioning is equivalent to starting fresh. The tenants will be decommissioned and new ones will provisioned. Entire landscape - DEV-TEST-PROD is a system, the entire tenant landscape will be decommissioned and setup again. Even if PROD Data is available, this will be scrapped.
7	What are the possibilities to save my old data ? You can use the Customer Data Return App to download your data from Production, incase you want it for your audits. https://me.sap.com/notes/0003088877 You can also download the configuration in Development system using a template configurator for your reference. https://help.sap.com/docs/CENTRAL_BUSINESS_CONFIGURATION/55c9333eed324cd284f6c4e5dab8462f/02023ac8950b4b989a7bab5d9ac5b518.html?locale=en-US&parentHref=%2Fwhats-new%2F6020626c93504655bc0160957d18ef87%3FVersion%3DCBC%25202403%253BCBC%25202406%253BCBC%25202406%2520FD1%26locale%3Den-US&parentName=What%27s%20New#loio38c4d7606ead481fa1295ff55bffd75e Currently both the possibilities are references only, however they can't be used for re-building the tenant from scratch.
8	When should re-provisioning be considered over rollback or fixes? Avoid re-provisioning, the earlier you catch an anamoly in your implementation better it is for you to restore the landscape to a state. Within HFC's it is possible for us to roll-back the entire landscape. It is important to define check points during your implementation. Fixes are not available at the moment, while internally few efforts, but a concept / service is a years away.
9	Is re-provisioning included as a standard offering in the Service Catalogue, or is it handled as an exception or special request? No, this is special request. Exception is approved by service owners internally.
10	What is the standard process for requesting re-provisioning of a system? Please raise a ticket in our component, XX-S4C-OPR-SRV. This case will be routed for validation from the CBC DEV Team, to check if correction is possible without re-provisioning. Tenants will be decommissioned, and SAP4Me, again will be enabled for requesting of tenants.
11	Is there possibility for me to hoard the development tenant as a reference during the next implementation? Yes, please add a note in the ticket. We will internal align, additional approvals are required. The old dev tenant can't be extended after the decommissioning cycle end of month.
12	How long does it take to complete re-provisioning? The time taken for reprovisioning can be split into three parts as below, Validating the Re-provisioning, Customer raises a request, request is validated, if any discussions are to happen during this time for clarification, this is entirely variable on the time taken for finishing this phase. Enabling Tenant Request in SAP4Me, Operations will have to ensure the tenant needs to be decommissioned, the CRM team has to reset the fulfilment. The request for the tenants are enabled in SAP4Me. Time to Provision, typically take a day for provisioning a tenant from the time it is requested in SAP4Me.
13	Since the entire landscape is decommissioned, will I have a chance to get the starter provisioned again ? / If my production is not yet commissioned, is there a possibility for me to have the starter as well re-provisioned? Starter is not provisioned during re-provisioning, the re-provisioning starts with DEV.
14	Is there any cost associated with re-provisioning? No, additional cost as of now. However discussions are on going for subsequent re-provisioning by the same customer. The efforts spent on the implementation from the customer side / data loss, if the production is live. Additional efforts by the operations to perform and involve for the activities.
15	Is there a conversation possible before re-provisioning? You can request for a conversation with our SRV colleague in the ticket, meeting can be scheduled for doubt clarification.

Conclusion

Re-provisioning is a last-resort solution for critical configuration errors. Customers should proactively validate settings, utilize the starter tenant, and consult SAP documentation to minimize the need for re-provisioning.

For further assistance, contact SAP Support via XX-S4C-OPR-SRV.

Keywords

Re-provisioning, Reprovisioning, , KBA , XX-S4C-OPR-SRV , S/4HANA Cloud service requests , X4-CBC-SRV , CBC Cloud Operations Support , How To

Product

SAP S/4HANA Cloud Public Edition all versions

Attachments

Pasted image.png