cancel
Showing results for 
Search instead for 
Did you mean: 

EBP-SUS vendor replication,standard message mapping not available

Former Member
0 Kudos

Hi srm gurus,

We have already implemented MM-SUS classic scenario and recently upgraded to SRM 5.0. We are using PI 7 with latest SRM content . vendor replication working fine with MM-SUS scenario.

Now we are in process to enable EBP -SUS for standlone scenarion. Issue is that vendor is not getting replicated from EBP to SUS , it is obesrved that namespace-http://sap.com/xi/SRM/SupplierEnablement is attached to XML message generated from EBP instead of xml namespace http://sap.com/xi/EBP"; , so it is getting stuck in PI with no message mapping available for this message and namepspace .

This change in xml namespace started with recent patch level changes ,ie it was working fine with SRM_SERVER 550 SAPKIBKT11 but it is not working with SRM_SERVER 550 SAPKIBKT13 .

Process:- vendor created in EBP using manage business partner & transaction -bbp_sp_supp_ini used to replicate vendor from EBP to SUS. XML message is generated of type supplierPortalTradingPartner_CreateOrChange_Out but it appears to be llinked XML Namespace http://sap.com/xi/SRM/SupplierEnablement .

how to resolve this ?

Regards,

Santosh

Edited by: Patil Santosh D on Sep 14, 2009 6:06 AM

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member544585
Contributor
0 Kudos

Hi Santosh,

Sounds like a system bug. Take a look at SAP Note 1226920 - XML error after sending Business partner from SRM to SUS.

Cheers,

Serguei

Former Member
0 Kudos

Thanks Serguei,

For your inputs.

My issue is resolved with the solution is that , for interface SupplierPortalTradingPartner_CreateOrChange

there is no need for a message mapping, the xml data coming in XI will be passed out 1:1. However the XI system should be able to forward such messages from source to target interface

So without any mapping program assigned in interface mapping ,message processed to SUS & vendor got replicated from EBP to SUS.