'API_MKT_CORPORATE_ACCOUNT_SRV' ODATA IN MULTIPLE RELATIONSHIP SCENARIO

[dmontanari]

Hello SAP Community,

INTEGRATION SCENARIO: SAP C4C - SAP MARKETING CLOUD

At the end of August I have requested to SAP SUPPORT contact to account multiple relationships activation for SAP Marketing Cloud.

After activation we have been able to create an SCPI custom package to sync relationships data using OData API_MKT_CONTACT_SRV (https://myXXXXXX-api.s4hana.ondemand.com/sap/opu/odata/sap/API_MKT_CONTACT_SRV;v=0004).

Later we realized the need to create a new package also for Business Partner integration because in 'import monitor' app (SAP MARKETING CLOUD) we have read for service CUAN_BUSINESS_PARTNER_IMP_SRV that 'B2B relationships are active. This service doesn't support B2B relations, Please use the business partner web service instead.'

So we built a new SCPI custom package using OData API_MKT_CORPORATE_ACCOUNT_SRV (https://myXXXXXX-api.s4hana.ondemand.com/sap/opu/odata/sap/API_MKT_CORPORATE_ACCOUNT_SRV;v=0003) but we receive an '500 internal server error'.
Unfortunately there is no error log on at all on 'import monitor' app in marketing cloud or SCPI http log file.
Then we did a large number of tests with Postman software but we always obtain the same error:

CX_ST_MATCH_ELEMENT/XXXXXX4641562346A1372144E7XXXXXX System expected the element '{http://www.w3.org/2005/Atom}entry'CEC-MKT-DM-IC/SAP/API_MKT_CORPORATE_ACCOUNT_SRV0002F84CBC7E128D05B0E005FB637313E58B20201119091439.9337060 For backend administrators: use ADT feed reader "SAP Gateway Error Log" or run transaction /IWFND/ERROR_LOG on SAP Gateway hub system and search for entries with the timestamp above for more details - See SAP Note 1797736 for error analysis (https://service.sap.com/sap/support/notes/1797736)

IS IT CORRECT TO USE 'API_MKT_CORPORATE_ACCOUNT_SRV' ODATA ?

Has anyone had the same problem?

[SCHNEIDERT]

Hi Davide,

I haven't yet set up this integration myself.

But as you wrote you replicate data from C4C, shouldn't you use the iFlows "Replicate Business Partner to SAP Marketing via Business Partner Web Services" and "Replicate Business Partner Relationship to SAP Marketing via Business Partner Web Services" (https://api.sap.com/package/SAPHybrisCloudforCustomerIntegrationwithSAPHybrisMarketing?section=Artifacts)?

In these iFlows the SOAP Services are used, which are able to access by using the Communication Arrangement SAP_COM_0475 (and SAP_COM_0539 for the Key Mapping).

So why do you need to use the API_MKT_CORPORATE_ACCOUNT_SRV?

BR Tobias

[dmontanari]

Hi Tobias,

I have decided to give a try with "API_MKT_CORPORATE_ACCOUNT_SRV" service because I could not verify the result of the call with the iFlow "Replicate Business Partner to SAP Marketing via Business Partner Web Services" on SAP Marketing Cloud. On SCPI Message processing was completed successfully but I can't see any log in 'Import Monitor' app on Marketing Cloud or any update in the corporate account data on Marketing Cloud. I have done the same test with Postman and the result is the same: can't see anything on 'Import Monitor'. Am I doing something wrong? I have attached the Payload of the call I'm testing.messageflow-3body.txt

messageflow-3body.txt

[SCHNEIDERT]

Hey dmontanari,

if you use SOAP I think you have to use AIF monitoring (app Message Dashboard) to see inbound and outbound messages instead of the Import Monitor app.

Not sure but I assume for the Business Partner replication you have to assign Namespace /CMDBP to your user.

Have a look if you have any error messages there and if anything is going wrong.

Maybe that helps. Sorry, but it's difficult for me to analyze your payload since I haven't done that integration before and have no comparison how it looks like when it works fine.

But if you can see any errors in the AIF do not hesitate to come back here, maybe we can find a solution.

BR Tobias

[dmontanari]

Hi Tobias,

unfortunately there isn't any log on 'Interface Monitor' app. I've already opened a Support request, hope to find an answer soon.

Thank you for the support.

[SCHNEIDERT]

Hi dmontanari,

did you assign the namespace to your user before?

There's an own app "Assign Recipients to Users" in which you can do that.

BR Tobias

[dmontanari]

Hi Tobias,

yes, it's working now. If you will have (or have now) any kind of question please feel free to ask.

DM

[dmontanari]

Hi Tobias,

we have been able to resolve due to 'Schedule an expert' call with a very trained SAP Support consultant who cheched S4HANA backend and told us this field is not 'Cloud Available'. No way to find the correct value, so he told us:

DataOriginTypeCode = 0001 ('Legacy System')

If you activate multiple relationship please use standard SCPI package:

1) Replicate BP to SAP MC via BP web services

2) Replicate BP to SAP MC via BP Relationship web services

If you have any issue or doubt please ask!

Thank you fo the support

[SCHNEIDERT]

Hi Davide,

thanks for the information, nice to know if I will come across that topic in the future.

So the integration is working now?

BR Tobias

[dmontanari]

Hi Tobias,

"Does the system take SAP_C4C_BUPA as Message-Header-ID? "

NO, I've marked the ID, but it's not relevant for the screenshot, I'm sorry.

For the payload that goes into MC I've downloaded 'Message after Receiver Adapter' payload from SCPI trace. Hope it's the right one, if not please tell me where I can see and download the right one.

messageflow-3-1.txt

Where can I have a look at mapping settings and understand which code is MC accepting for 'Origin Type Code' Field?

messageflow-3-1.txt

[SCHNEIDERT]

Hi Davide,

at least code "01" looks better for that field I think.

I've had a look at the mapping on the API Hub but didn't see any mapping for the DataOriginTypeCode field. So I'm not sure which codes stand for what or which are accepted...

Only found some information about it in the C4C OData Services Guide: https://help.sap.com/doc/77979cd206da4b7f9bd264b390d373fc/CLOUD/en-US/OData_Services.pdf

[dmontanari]

Hi Tobias,

now I can see logs on message dashboard. Error message is related to 'Origin' max length: I've used 'SAP_C4C_BUPA' but Marketing Cloud is raising an error.

[SCHNEIDERT]

Hi Davide,

okay good to hear.

But in your case you marked the ID of the Message Header. So, does the system take SAP_C4C_BUPA as Message-Header-ID? Sounds strange...

In your first payload I can see SAP_C4C_BUPA as DataOriginTypeCode. Not sure if that's correct. Maybe you have to adapt something in the mapping. The payload is the outgoing payload from C4C, right? Do you have the payload that goes into MC?