cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Master Data Integration how to connect a QAS Tenant?

cadiraca
Explorer
0 Kudos
804

Hello Experts,

I’m in charge of setting up the QAS subaccount for our implementation project (S/4HANA Public Cloud). We are configuring Master Data Integration (BTP Service) in the QAS subaccount. According to the documentation, Tenant == Subaccount. We were able to connect S4 to MDI using the DEV instance for basic testing, but now that we have created the new subaccount for QAS, we have subscribed to MDO and set up the service instances for each app we need to integrate. The problem is that we are not able to reach the new MDI with the service key—we get a 401 error. My question is: How can we identify which MDI tenant we are connecting to? What I see in all the service keys is the same URI: https://one-mds.cfapps.eu10.hana.ondemand.com, no matter which subaccount I’m using. Can an MDI expert help me? Thanks in advance.

Accepted Solutions (1)

Accepted Solutions (1)

anildeep7
Explorer
0 Kudos

Hi @cadiraca,

I would like to understand where do you get 401 Error, is it in S4 ?

The URI could be the same. Authentication happens with the help of the Client ID, Client secret, and URL available in the service key.

If you are connecting MDI with S4 Hana Public Cloud, make sure to create the communication arrangements SAP_COM_0659 and SAP_COM_0594 and respective Communication System and Communication User and Destination In SAP BTP Subaccount.

@ebsor , please let us know if we can check any specific Configuration to fix this issue ?

@cadiraca Please provide more details to understand the issue.

 

Kind Regards,

Anil

 

cadiraca
Explorer
0 Kudos

Hey .@anildeep7 Thanks for your response. Yep. The 401 was on S4 communication arrangement. I was setting the BP replication between S4 and Subscription Billing via MDI. I realized that I had to send a parameter like tenantID at the end of the SOAP URL on MDI. Added and the end (Keep in mind this parameter must be the name of the subaccount) and that is. Now it is working. Thanks!!!

cadiraca
Explorer
0 Kudos

Hey @anildeep7  Thanks for your response. Yep. The 401 was on S4 communication arrangement. I was setting the BP replication between S4 and Subscription Billing via MDI. I realized that I had to send a parameter like tenantID at the end of the SOAP URL on MDI. Added and the end (Keep in mind this parameter must be the name of the subaccount) and that is. Now it is working. Thanks!!!

Answers (2)

Answers (2)

anildeep7
Explorer
0 Kudos

@cadiraca, i have now added 4 properties, now the destination is showing in consumer in Distribution Model, but when i make a initial replication from Distribution Model, no new data is coming.

i have changed name of the person but it is not yet updated, what could be the issue ?

Thanks, Anil

anildeep7
Explorer
0 Kudos

Hi @cadiraca ,

I have created Communication Arrangement SAP_COM_0008 and connection works fine, and also i have created destination and it works fine as well, but in MDO how do i select this destination, the destination is not coming in MDO Under Consumer, could you please help ? what did i miss ?

Thanks, 

Anil

cadiraca
Explorer
0 Kudos
Sorry if I ask you stupid questions. Do you have in BTP the Master data instances running and set for every single system? For BP sync using soap there are more steps to be done, like create at least 2 more destinations.
anildeep7
Explorer
0 Kudos
@cadarica, yes i have created instances for s4 and subscription billing, and also i have creted one destination taking the api from SAP_COM_0008 inbound services with this option Business Partner - Replicate from Client to SAP S/4HANA Cloud and destination works fine as well as mentioned previously, are there any additional steps ? i understand that we need to create one more destination, but my issue is why the destination is not showing up in MDO in consumer ? could you pleas e help ?
cadiraca
Explorer
0 Kudos

Have you added additional properties to the destination??

cadiraca_0-1727107127346.png

 

MDIInstanceId

MDOBusinessSystem

MDOConsumer

MDOProvider