Master Data Integration - Cloud Foundry Runtime / Spaces - yes or no

[JaySchwendemann]

Hi all,

I'm receiving mixed signals here:

• In SAP Master Data Integration, the "vanilla" documentation says, to create applications / service instances per app without a space and using runtime "other"
• A scenario specific help, e.g. for Digital Manufacturing however states to use a space
• I saw that Business Process Orchestrations needs spaces

Do you / shall I use spaces? If I later need to onboard BPO, can I still do this even if I deployed the instances without space at first?

Thanks and cheers

Jens

[Chris1973]

Hi @JaySchwendemann 

In SAP Master Data Integration, the naming convention for service instances can vary by scenario. The scenarios determine the integration success.

For the General “vanilla” guidance: No spaces in instance names, runtime “other.”

For a Scenario-specific guidance e.g., Digital Manufacturing or Business Process Orchestration, it may require or recommend using spaces in instance names.

If you start with instances without spaces, you can still onboard BPO later by creating additional instances with spaces as required. This won’t impact any other earlier deployments you may have carried out.

I recommend you follow the naming convention for your current scenario but be aware of future needs and plan accordingly to ensure smooth integration.

I hope this provides the necessary information. I am happy to help if you have further questions.

Best regards

Chris

Create a Master Data Integration Instance

Naming Conventions

Configuring the SAP Master Data Integration Service Instance in SAP Ariba Solutions

[JaySchwendemann]

no offense, but I'm getting slight AI vibes 😎

To add a lil' value to the sassy comment (also for other folks) I could say that I ran into trouble when I tried to provision the MDI / MDO services like this

• Created Subaccount
• Not enabled CF
• Subscribed to MDI Tenant service
• Created / Subscribed to MDI service
• Subscribed to MDI (Orchestration) service <-- This is where I got an error. Service could not be provisioned

It seems like not having CF was causing the issue or having the  MDI Tenant service subscribed fore the MDI (Orchestration) service.

Anyways, slightly leaning towards CF enabled. I opened a case however, so let's see what SAP does have to say about this