Catalog vendor having different vendor number in different R/3 system

[Former Member]

Hello Experts,

We are in SRM 7.0 classic scenario and we are facing an issue as described below:-

We are using a punched out catalog which has different venor number in different backend system.We have 2 R/3 backend system say R/3 sys1 & R/3 sys2.

Vendor No for the Catalog vendor is say:-

Vendor No R/3 sys

V123 R/3 sys1

V567 R/3 sys2

We have connected the R/3 sys2 just a week back.We have replicated the catalog vendor number V567 from R/3 sys2 into SRM system and we are able to successfully create a Shopping cart in R/3 sys2 using catalog.

However,we are facing a problem and the problem is that,

When we create a shopping cart in R/3 sys2 using catalog,by default we get a message that "Vendor V123 is not intended for plant"

We are able to change the vendor from V123 to V567 in the portal,but we are unable to understand why the vendor V123 is picked up as a default catalog vendor.

Can you all experts,plz help us understand why this vendor V123 is picked up as default vendor and how we can ensure that Vendor V123 is picked up when we are creating SHC is system R/3 sys1 & vendor V567 is picked up as default vendor when we are creating SHC in system R/3 sys2?

Any pointers will be highly appreciated.

Thanks & Regards,

RKS

[laurent_burtaire]

Hello RKS,

>

> (...)
> Can you all experts,plz help us understand why this vendor V123 is picked up as default vendor and how we can ensure that Vendor V123 is picked up when we are creating SHC is system R/3 sys1 & vendor V567 is picked up as default vendor when we are creating SHC in system R/3 sys2?
>(...)

This means for same Product Category (and same material ID) coming from your Punch-Out catalog, you can create a Purchase Requisition in R/3 sys1 OR R/3 sys2 ?

If i am correct, how can you manage in your catalog two vendor numbers for same Product Category (and material ID) ?

I guess only one vendor number (V123) is maintained in your catalog. That's why, even if your management rule is to send your SC to R/3 sys2, you will have always vendor V123 as the default one, as it is the only one in your catalog...

Regards.

Laurent.

[jason_boggans]

Hi,

As no unique key exists (i.e. there are >1 of the same vendor id's) then the application just chooses the first one, best to assign also (using the BBP_CATALOG_TRANSFER Badi) the vendor GUID during the transfer so that the correct vendor is selected and retained.

Regards,

Jason

[former_member324993]

For this issue,you replicate vendor from you every r/3 system to SRM, then the srm have diff bp code.

[Former Member]

Hi Bill,

Thank you for your response.We have already replicated the vendor from the all the R/3 Backend system into SRM system.

But still vendor V123 is getting picked up as the default vendor which is causing a concern.

Can you plz suggest something else which we can try?

Thank you in advance.

Thanks & Regards,

RKS