Hello All,
With the growing popularity of SAP S/4HANA Cloud and a number of customer adopting to SAP S/4 HANA cloud solution for its high end features such as AI capabilities, Continuous innovation and Enhanced user experience, the need for gaining the knowledge of SAP S/4 HANA cloud has increased among the consultants.
The SAP S/4 HANA cloud, has a multiple improvement from his predecessor such as Automated Testing, Central Business configuration, Configuration Localization etc...
The first steps and an important thing to know in any SAP S/4 HANA cloud project is the Central Business configuration(CBC) workspace which is used to carry out all the activities in a SAP S/4 Cloud environment.
The CBC(Project Experience app) is the only place which will be used to centrally manage the configuration activities instead of SPRO and allows to carry out the following activities such as
- Scoping
- Organizational Structure configuration
- Product specific Configuration
- Assignment of Tenant system or Production system setting
Before going in detail about each milestone or Activity mentioned above we need to first understand the SAP S/4 HANA cloud Landscape.
SAP S/4 HANA Cloud Landscape
The below is the systematic diagram of a 3 system Landscape in SAP S/4 HANA cloud:
The CBC is a different workspace which is inside a S/4 HANA cloud system, which has a direct link to the Development system as shown.
The SAP S/4 HANA cloud has 3 system same like the on-prem called as 3-SL system. There is also another type of landscape 2 SL, where there will be no Development system.
The Development system has 2 client, One is used for Configuration and another client is used for the Technical activities such as extensibility.
The remaining systems Tester and the Production system has a single client.
Note: Each client has a different tenant(link) to access it.
TR Movements : The configurations done in the CBC will be synced with the Development system automatically by SAP, whereas the movement between Q and P system should be done manually same like the On-prem through "
Export Customizing Transports" Fiori app.
Let's go in detail regarding each step,
Scoping:
Scoping is the first phase or Milestones which need to be completed to move to the next phase.
The first step scoping includes selecting the country for which the solution is going to be implemented and need to choose the Sector(Private or Public).
Then there are bundles and Scenarios, where we need to select the required scenarios which the client follows, only these scenarios can be configured later.
Some scenarios will be locked and if those scenarios are required then we need to raise a ticket to SAP to activate those scenarios through the XX-S4C-OPR-SRV ticket and attach the accelerator template.
In this step we assign the deployment system to the required project.
Organizational Structure:
In this milestone we need to finalize the organizational structure.
The first thing we need to do is to select some financial setting such as
Company code currency, Fiscal Year variant.
Then we need to create the Organizational structure for all modules and do the required assignment of org structure in the CBC workspace which will be automatically created in the S/4 system in the background, once this is completed we need to confirm this milestone.
Make use of the Graphical organizational structure creation app in CBC.
Note: Once this milestone is confirmed, we can only add new organizational structure and we can not delete the old one, kindly keep that in mind!!!!
Product Specific configuration:
Now in the CBC, the configuration Tab will be available to do the required configuration, according to the scenarios chosen the configuration steps will be available.
When any of the links are clicked then we will be taken to the HTML GUI screen to do the configuration activities which needs to be saved in required TR or WR, and then they can be moved by using the app mentioned above.
Production system:
Here we will do all the production system related settings.
Stay tuned for more SAP S/4 HANA Cloud content!!!!!!!!!
Thanks and Regards,
Suryaprakash.