Vendor replication to SUS

[Former Member]

Hi,

We are setting up the service procurement scenario with supplier enablement. We have EBP on one client (100) and SUS (110) on another client. All the XI configuration is done properly.

When we replicate vendors from EBP (XML/XI) as the communication method, using BBP_SP_SUPP_INI, the XI montior is a green message for the outbound in EBP, green in XI. when it comes to SUS, there is an error for the inbound XML.

Here is the error.

<?xml version="1.0" encoding="utf-8" ?>

- <nr1:StandardMessageFault xmlns:nr1="http://sap.com/xi/SRM/Basis/Global">

- <standard>

<faultText>An error occured within an XI interface: Exception occurredE:R11:123 -Enter at least one number for the business partner Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</faultText>

</standard>

</nr1:StandardMessageFault>

All the Business number ranges are set properly and internal no. ranges have to be taken.

Any idea to resolve this error?

I appreciate the urgent help.

Regards,

DV

[khan_voyalpadusman]

can somebdody send me documents for XI configuration to be done in SUS-EBP scenario.

I am using SRM version 5.0 and configuring SUS-EBP scenario.

I will reward points for answers

[Former Member]

Usman,

Can you drop your email id so that i can send you some useful docs on XI set up

Krishna

[khan_voyalpadusman]

hi ,

please send documents to my e-mail id

vusmankhan@yahoo.com

regards

Edited by: khan voyalpad usman on Feb 6, 2008 12:01 AM

[Former Member]

Hi Folks:

I am trying to replicate vendors from EBP to SUS using the

t-code BBP_SP_SUPP_INI.

But always internal numbers are created which I DO NOT want.

Say in EBP Portal vendor is 8536 and I need the same vendor number 8536 in SUS .I am attaching the XML payload .

How to create external vendor numbers in SUS.

<?xml version="1.0" encoding="utf-8" ?>

- <nr1:SupplierPortalTradingPartner xmlns:nr1="http://sap.com/xi/EBP">

<Method>Create</Method>

- <TradingPartnerOrganization>

<TradingPartnerRole>Seller</TradingPartnerRole>

- <Identifier>

<PartnerID>0000008536</PartnerID>

</Identifier>

- <TaxIdentifier>

<CategoryCode>US2</CategoryCode>

<TaxNumber>13-7904380</TaxNumber>

</TaxIdentifier>

<SystemID>SAPEBP_MPX_100_X</SystemID>

<Language>EN</Language>

<Currency>USD</Currency>

<Title>0003</Title>

<Name1>GRAYBAR ELECTRIC CO INC</Name1>

- <Address>

<StandardAddress>true</StandardAddress>

<AddressID>0000010270</AddressID>

<Street>650 SOUTH 108ST STREET</Street>

<City>MILWAUKEE</City>

<PostalCode>53214</PostalCode>

<Region>WI</Region>

<Country>US</Country>

</Address>

- <Communication>

<CommunicationType />

- <Telephone>

<StandardTelephone>true</StandardTelephone>

<Number>817-213-1333</Number>

<TelephoneCountry>US</TelephoneCountry>

</Telephone>

- <Fax>

<StandardFax>true</StandardFax>

<Number>817-213-1339</Number>

<FaxCountry>US</FaxCountry>

</Fax>

- <Email>

<StandardEmail>true</StandardEmail>

<EmailAddress>sutaria.ketan@mbco.com</EmailAddress>

</Email>

</Communication>

</TradingPartnerOrganization>

</nr1:SupplierPortalTradingPartner>

[Former Member]

Did u solve the problem? he have the same problem right now, could u help us?

[Former Member]

Hi DV,

I don't know the details or vendor replication.

But I guess that SRM sends its BP number, and SUS will try to create a BP with that external number, to keep the same numbering.

Have you tried to define an external number range for BP is SUS, that equals the supplier number range of SRM ?

In your XML message payload, what are the values of ....TRADING_PARTNER_ORGANIZATION-IDENTIFIER-PARTNER_ID and TRADING_PARTNER_ORGANIZATION-IDENTIFIER-RECEIVER_PARTNER_ID ?

Rgds

Christophe

[Former Member]

Can you see the payload of the XML document that is being sent across in SXMN_MONI?

Does it have the Business Partner number in it?

And is that Business Partner in a range that is acceptable in your system?

If you can see it in the XML doc then its likely the problem is in SUS Client.

If you cant see it then its probably in SRM client.

So check there first to see source of problem.

S