Technology Blog Posts by SAP
cancel
Showing results for 
Search instead for 
Did you mean: 
0012anirban
Contributor
4,217

Hi All,

In October 2023, SAP launched a new operational mode in MDG "CLOUD-READY MODE" for S/4 HANA 2023, following the principles of ABAP cloud and clean core methodology. Cloud-ready mode is only available for Business partners with Product domains in the MDG future roadmap. 

I briefly wrote about how this mode works in a previous blog post, hence if you have missed that you find the link below

Introducing MDG cloud ready mode for Business partners in S/4 HANA 2023

INTRODUCTION:

To setup cloud ready mode, we have following pre-requisites:

  1. An S/4 HANA 2023 private cloud edition system.
  2. A BTP tenant with at least one subaccount.
  3. Running instances of SAP build process automation, SAP Build workzone (standard Edition) and cloud connector

In this blog post, I will provide a detailed step by step approach to setup SAP build process automation and backend S/4 HANA 2023 for cloud ready mode.

MAIN CONTENT

BTP configuration:

  1.  We start by subscribing to SAP build process automation and SAP build workzone( standard edition ) in the BTP cockpit.0012anirban_0-1725280039762.png0012anirban_1-1725280070185.png
  2.  Assign the below role collections to your user. 0012anirban_3-1725280101337.png0012anirban_4-1725280136787.png
  3. On the destination tab in BTP cockpit, create the WM_CF_SPACE_PROVIDER destination. This destination will be used to import the live process packages in SAP build process automation.0012anirban_5-1725280149720.png

    Note: The cloud foundry API end point and the URL for the destination should match as given in the SAP help portal. The user can be a generic user who doesn't have 2 factor authentication enabled. The details can be found Default Identity Provider | SAP Help Portal

     
  4. From Instances tab, launch the SAP build process automation lobby and import the Master data process approval & visualization project from the Store. 0012anirban_6-1725280226525.png
  5. Activate the 5 visibility scenarios, which we will use at a later stage. 0012anirban_0-1725280300666.png

    0012anirban_1-1725280300681.png

     

  6. In the Instances tab in BTP cockpit, check sap_processautomation instance is created. Click on this and create a service key for the backend S4 HANA system.0012anirban_2-1725280360450.png

     

  7. Assign MDG-specific BTP role collections to your user. 0012anirban_3-1725280403319.png
  8. The next step would be to setup the SAP build workzone. For the sap_processautomation instance create a service key for the workzone. 

  9. Once the key is created, create a destination for workzone. For details on how various parameters of the destination will be set, please refer to Configure SAP Build Process Automation Destinations | SAP Help Portal

    0012anirban_0-1725280686546.png

     

  10. From the instances & subscription tag, launch the SAP build workzone standard edition application.
  11. In workzone, navigate to the content manager and choose the below 5 apps.0012anirban_2-1725280742409.png0012anirban_3-1725280742410.png0012anirban_2-1725280970973.png
  12.  Create a local copy of the Visibility Scenario Dashboard app, change the title to Process Path Overview, and provide the navigation parameter scenarioID with the value com.sap.mdg.pv.ProcessVis.0012anirban_3-1725281020940.png0012anirban_4-1725281031755.png

     

  13. Create a group MDG and enable the My inbox and process path overview apps0012anirban_5-1725281093488.png
  14. Assign the permissions for this 5 apps to everyone. 0012anirban_6-1725281152248.png
  15. Create a site with the same alias name as the group we created in step 13. 0012anirban_7-1725281232906.png0012anirban_0-1725281291070.png

     

  16. Create the below destinations in BTP for your workflow and process path overview. Configure BTP Destinations | SAP Help Portal0012anirban_9-1725282837970.png

     

S/4 HANA on-premise configuration:

Cloud ready mode should be activated in the S/4 HANA system, once activated classic MDG related apps for mass processing and consolidation will stop working and the new consolidation & mass processing apps for S/4 HANA 2023 needs to be used.

1.  Create an SM59 destination in S/4 HANA system and provide the host by pasting the same hostname as the MDG workzone site. The path prefix should be /site/mdg.

0012anirban_1-1725281759538.png

2. Create an entry in the SM30 view /UI2/V_ALIASMAP as below.

0012anirban_2-1725281856899.png

3. Go to MDGIMG-> cloud-ready mode and follow the path as per below screenshot to begin with integration of Build process automation with MDG. The subsequent steps will cover all the configurations in detail.

0012anirban_0-1725282026968.png

4. In Maintain the destination to an external server, create a destination MDG_BTP_SBPA_API. The host will be same as the API endpoint for the service key created in step6 of the BTP configuration section. You have to set SSL to active.

0012anirban_1-1725282215169.png

0012anirban_2-1725282237285.png

5. Now we maintain the OAuth Client 2.0 for secure communication between SBPA & S4 HANA.

0012anirban_3-1725282288807.png

Create a new profile configuration:
For the OAuth 2.0 client profile, choose SWF_CPPA_OAUTH_PROFILE. Enter a configuration name, for example, the name of the subaccount of your service.
For the client ID, enter the JSON value $.uaa.clientid from your service key card.
Enter the client secret by copying it from the BTP instance sap_processautomation service key for S4 HANA system.
Navigate to the Authorization Server Settings section, paste the uaa-URL from your service key to the Authorization Endpoint field, and add the /oauth/authorize suffix. In the same section, add the uaa-URL from your service key to the Token Endpoint field, and add the /oauth/token suffix.

6. Activate the following OData Services:
• MASTERDATACHANGEPROCESSSB
• C_MDCHGPROCESSBPMATCH_SRV
• SWF_CPWF_NOTIFICATION_SRV
• SWF_CPPV_INTEGRATION_SRV

7.  Authorization needs to be assigned to the user which will communicate between S4 HANA and SBPA. I have used a generic user with all the MDG roles. Hence not sharing the details for this step. 

0012anirban_5-1725282450443.png

8.  We maintain the connectivity with workflow capability. The configuration name is same as the configuration done for OAuth 2.0 client configuration in step 5

0012anirban_7-1725282616781.png

0012anirban_6-1725282578681.png

9.Maintain connectivity for generic event API of visibility capability. The configuration name is same as the configuration done for OAuth 2.0 client configuration in step 5.

0012anirban_8-1725282679644.png

10. Create a destination which will call back the S/4 HANA system. Here the URL should be the same as the one exposed in the cloud connector. The generic user should have sufficient authorizations. The user I used has all the MDG roles, hence not shared in detail.

0012anirban_0-1725283156309.png

CONCLUSION:

By following through the steps mentioned in this blog post, you will be able to setup MDG cloud ready mode with a fully functional workflow in SAP build process automation. 

Cloud ready mode is the stepping-stone for next-gen master data management providing features like Data federation, integration with address provider CDQ.

Hope this will help you start your MDG cloud ready mode journey.

Feel free to reach out if you have any questions.

SAP Master Data Governance SAP Build Process Automation  SAP Build Work Zone, standard edition SAP S/4HANA  SAP S/4HANA Cloud Private Edition SAP Business Technology Platform ABAP Cloud SAP S/4HANA business partner 

Regards

Anirban

 

 

1 Comment