S. No. | System | Request Process | Link | Remarks |
1 | SAP for Me | S-User will be provided to you after contract | SAP for Me will show you all the entitled systems as per the contract with SAP | |
2 | Requesting CALM system | Provisioning is done on Provisioning Dashboard on SAP for Me by 'IT Contact | Systems & Provisioning - SAP for Me | Prepare phase of the project |
3 | Requesting CBC System | Provisioning is done on Provisioning Dashboard on SAP for Me by 'IT Contact | Systems & Provisioning - SAP for Me | Prepare phase of the project |
4 | Request S/4HANA Cloud Starter System - Development | Provisioning is done on Provisioning Dashboard on SAP for Me by 'IT Contact | Systems & Provisioning - SAP for Me | Prepare phase of the project (This request is applicable for both the tenants in Starter) |
5 | Request S/4HANA Cloud System - Customizing | Provisioning is done on Provisioning Dashboard on SAP for Me by 'IT Contact | Systems & Provisioning - SAP for Me | Realize phase of the project (This request is applicable for both the tenants in Development) |
6 | Request S/4HANA Cloud System - Test | Provisioning is done on Provisioning Dashboard on SAP for Me by 'IT Contact | Systems & Provisioning - SAP for Me | Realize phase of the project |
7 | Request S/4HANA Cloud System - Production | Provisioning is done on Provisioning Dashboard on SAP for Me by 'IT Contact | Systems & Provisioning - SAP for Me | Realize phase of the project |
S. No. | Activity | Process in Starter System | Process in Development (Main) | Remarks |
1 | Email for CBC User Activation | Activate your user by clicking the Link in the mail and set the new password of your choice matching the password policy. | You will get this email just once for the CBC system. | System Administrator will create user for you and this will trigger an email. CBC Users (other than Admin) are created in IAS (identity Authentication Service). |
2 | Log in to the project experience in the Central Business Configuration | Log in to CBC | Log in to CBC | - |
3 | Pre-requisites | Request SAP S/4HANA Cloud Starter System | > A starter System must be available, and Development System has been requested > Completed task Conduct Project Quality Gate for Explore, including the following: - Fit-to-standard Analysis completed - Configuration definition completed - Organizational Structure defined - Chart of Accounts defined - Fiscal Year Variant defined - Group Currency defined | - |
4 | Project Creation | Create Evaluation Project for the Starter Customizing Tenant | Create Implementation Project for the Development System | Each project (evaluation or Implementation) is assigned to a target deployment system. This decides whether the project’s config and change are related to Customising (client 100) or Development (client 080) |
4.1 | Add users in the project | Add users in the Evaluation project. Only added users would be able to see and work on this project. | Add users in the Implementation project. Only added users would be able to see and work on this project. | - |
5 | Define Scope | |||
5.1 | Select Countries | Select scoped country(ies) of the project. (It is recommended that one by one country activation. However, you can select multiple countries also at a time) | Select scoped country(ies) of the project. One or multiple at a time. When you define your scope for the first time or use the Initiate Change functionality, SAP strongly recommends limiting the number of countries/regions to no more than five. | > A sector selection (private/public) is available if the USA is the only selected country/region in scope. > You can also extend your scope later via Initiate Change. |
5.2 | Scope Bundle | Select scope bundle any one from below ones: 1. Baseline Accelerator bundle 2. Enterprise Management bundle (in starter it will be pre-selected) 3. Retail bundle | Select scope bundle any one from below ones: 1. Baseline Accelerator bundle 2. Enterprise Management bundle 3. Retail bundle(Finance-Led and Professional Services bundles have been deprecated.) | > Standard scope items will get activated with scope selection and activation > Bundles 1. Baseline Accelerator bundle - It contains mainly finance-related scenarios. 2. Enterprise Management bundle - This extensive bundle is appropriate for large enterprises. 3. Retail bundle - Enterprise Management bundle and scenarios relevant for the retail industry. |
5.3 | Ledger Scenario | Select IFRS or US GAAP or both > Accounting and Financial Close - Group Ledger IFRS (1GA) = 2L (IFRS) > Accounting and Financial Close - Group Ledger US GAAP (2VA) = 3L (US GAAP) | Select IFRS or US GAAP or both > Accounting and Financial Close - Group Ledger IFRS (1GA) = 2L (IFRS) > Accounting and Financial Close - Group Ledger US GAAP (2VA) = 3L (US GAAP) | Up to two group ledgers can be selected. And the Local ledger comes by default for local accounting, ledger 0L. Now you have three ledgers in S/4HANA Cloud and additionally extension ledgers as your business needs. Extension ledgers are defined during the Product-Specific Configuration phase. |
5.4 | Additional scope items (non-standard) activation) | Select scope items which are non-standard and applicable for the project. | Select scope items which are non-standard and applicable for the project. | Scope items which are Most Non-Standard and the scope items which requires additional license will not be available here for activation. These are activated by Incident/request. |
5.5 | Define Scope | Complete Activity in Define Scope | Complete Activity in Define Scope | Define activity is complete with this step |
6 | Requesting SAP S/4HANA Cloud License-Dependent or Non-Standard Scenarios | You need to request SAP S/4HANA Cloud license-dependent and most non-standard scenarios via ticket. See Requesting SAP S/4HANA Cloud License-Dependent or Non-Standard Scenarios. | You need to request SAP S/4HANA Cloud license-dependent and most non-standard scenarios via ticket. See Requesting SAP S/4HANA Cloud License-Dependent or Non-Standard Scenarios. | Create a ticket for component XX-S4C-OPR-SRV with customer OSS ID. |
7 | Assigning a Deployment Target | Assignment of Deployment Target (Starter – Customising (100) or Starter – Development (080)) | Assignment of Deployment Target (Dev - Customising (100) or Dev – Development (080)) | Deployment target tells you where the config and changes would move to. |
8 | Confirm Scoping is Completed | Confirm Scoping is Confirmed | Confirm Scoping is Confirmed (it will take some time to get completed) | It will bring more options/activities: a. Finance Primary setting b. Org Structure Conf C. Confirm Org Structure |
9 | Specifying Primary Finance Settings | Fiscal year variant and Group Currency are fixed (you cannot change) in starter system as below: > FYV: K4 (Fixed) > Group Currency = USD (Fixed) | Fiscal year variant and Group Currency are defined as per business requirement. FYV =? Group Currency =?For fiscal year variant, if you choose configurable template SZ, you will be able to configure the fiscal year variant in the Product-Specific Configuration phase with configuration activity Maintain Fiscal Year Variants. | Alternative fiscal year or Additional fiscal year variant is/are assigned during the Product-Specific Configuration phase. It can be assigned to a non-leading ledger only. It can also be assigned at ledger level or at Ledger and company code combination level. |
10 | Setting Up Organizational Structure | The evaluation project (in starter) contains an existing organizational structure, with all organizational units confirmed already. You can choose to have standard organization structure (it will come along with demo data). Or you can define your own set of org structure. Generally, we go with standard org. structure. Complete Activity - Click | You defined org structure based on business need. You model your organizational structure with predefined organizational units and templates. You can also enhance the organizational structure later via Initiate Change. | - |
11 | Completing the Scope and Organizational Structure Phase milestone | Confirm Scope and Org Structure Phase - Milestone After activation, the starter system contains the following: SAP Best Practices content and demo master data Preselected scope that you can extend Preconfigured organizational structure that you can enhance | Confirm Scope and Org Structure Phase: After confirming this milestone, the configuration settings will be deployed. | Your project gets locked due to an activation process. Please wait until the process is completed. After this you shall be able to do config as per your requirement. This activity might take somewhere 8 to 14 hours if single country selected. |
S. No. | Activity | Process in Starter System | Process in Development | Remarks |
1 | Initiate Change | You do not need to create another evaluation project for activating another country on the activated system Note: If you create second project for Product specific configuration; second and other projects will be Implementation Project (not as Evaluation Project) | You do not need to create another Implementation project for activating another country on the activated system | > Here we are focussing on adding additional country(ies). |
2 | Process to be followed as you did while activated the very first country(ies) on the system. Few steps do not need to be done in subsequent country(ies) activation as those were tenant-wide activities and hence would not require on every country activation | These activities would not be logically required in subsequent country activation: 1. Scope Bundle selection: Scope bundle is applicable for entire system and does not need to be selected at every country activation. It was selected initially during first country(ies) activation. Hence this option will not appear anymore.2. Ledger Selection: Ledger selection is also applicable for entire system and has already been selected during first country(ies) activation. Now ledger selection would not be applicable.3. Primary Finance Settings: Fiscal year variant and Group currency are also system level settings and not need to do again. This activity will also not appear now. | These activities would not be logically required: 1. Scope Bundle selection: Scope bundle is applicable for entire system and does not need to be selected at every country activation. It was selected initially during first country(ies) activation. Hence this option will not appear anymore.2. Ledger Selection: Ledger selection is also applicable for entire system and has already been selected during first country(ies) activation. Now ledger selection would not be applicable. 3. Primary Finance Settings: Fiscal year variant and Group currency are also system level settings and not need to do again. This activity will also not appear now. | |
3 | SAP Support Link | Evaluation Project | SAP Help Portal | Implementation Project | SAP Help Portal |
Sr. No. | Scope ID Category | Remarks |
1 | Standard Scope Items | It comes along with Scope bundle selection during initial scoping |
2 | Non-Standard Scope Items- Activated at the time of initial activation | It can only be activated during the initial activation (e.g. Scope Item 1GA, 2VA,) |
3 | Most Non-Standard Scope Items- Request via ticket during initial scoping. Before confirming the scoping activity | Can be requested via ticket during initial scope (e.g. Scope Item 5W2). If you fail to do so and you need such scope items then the only possibility left is re-provisioning which might consume a few days from your projects. Be Extra conscious. |
4 | Non-Standard Scope Items | Can be activated during initial scope or later as scope extension (e.g. Scope Item 2I3) |
5 | Most Non-Standard Scope Items- Request via ticket | Can be requested via ticket as scope extension (e.g. Scope Item 3AF) |
License required Non-Standard Scope Items- Request via ticket | Can be requested via ticket (Create a ticket for component XX-S4C-OPR-SRV with customer OSS ID). as scope extension. This scope items requires additional license (e.g. Scope Item J78) | |
Go to www.rapid.sap.com and look for "Reason for exclusion from default activation“ section on the a scope item page |
Sl. No. | Activity | System To Be Used | Transport Request Type | Release and TR Movement App |
1 | Deploying Scope and Organization Configuration from Central Business Configuration (CBC) to the customizing tenant using a CBC Transport. | CBC | Customizing (CBC) | How to Transport? Follow the link |
2 | Project specific Configuration/ Configurations | CBC (Automatically, data will go to Dev: Customazing Client 100) | Customizing | |
3 | Key User Extensibility (Custom Fields, Analytical Report etc.) | Dev: Customazing Client 100 | Software Collection | |
4 | Developer Extensibility (e.g., BaDI implementation) | Dev: Development Client 080 | Workbench |
3-System Landscape has only two project phases:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
3 | |
2 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |