cancel
Showing results for 
Search instead for 
Did you mean: 

SUS Vendor data update

0 Kudos
92

Hi experts,

We are implementing SRM-SUS scenario.

When I update vendor data in SUS,  the same vendor is not updated in SRM system.

No XML message is generated.

Data update from SRM to SUS is successful.

I have configured PI as follows:

SUS

Interface:SupplierPortalTradingPartner_CreateOrChange_Out

namespace: http://sap.com/xi/SRM/SupplierEnablement

SRM

Interface:SupplierPortalTradingPartner_CreateOrChange_In

namespace: http://sap.com/xi/EBP

Are there any settings I'm missing?

Regards,

Mio

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member208675
Active Contributor
0 Kudos

Hi,

Can you check have you selected 'Protal Supplier' indicator for that vendor?

When this indicator is set, the data is replicated automatically.

If not; then you have to select it before you replicate supplier. It sync vendor data of both the systems.

Regards,

0 Kudos

Hi,

Thanks for the reply.

Yes 'Protal Supplier' indicator is set in SRM.

I wonder why XML isn't even triggered...

Regards,

Mio

Former Member
0 Kudos

Hi Mio,

Portal Supplier indicator will not resolve your issue. Portal Supplier check box will only help you replicate vendor data from SRM to SUS and not vice versa which is your requirement.

As of SRM 7.0, I don't think your vendor data changes can be replicated from SUS to SRM.

Regards,

Nikhil

0 Kudos

Hi Nikhil,

According to note 1703204, vendor data change will be replicated to SRM.

Supplier created in SRM in the BP maintenance transaction with the flag Portal Supplier is replicated to SUS. A SUS supplier can login to SUS and change his company data in the Self-Service Maintenance. As soon as the supplier data was changed, the text 'Data must be replicated' is displayed in the Self-Service Maintenance screen. This is so because the supplier changes are first stored temporarily in the staging tables in SUS and must be transferred by XML to a leading system SRM or ERP-MM.

Now I'm asking OSS about this issue.

Regards,

Mio