Vendor replication and exchange documents from SRM to SUS (using PI)

[Former Member]

Hi Gurus,

We are implementing scenario plan driven procurement with suppllier collaboration on SRM 7.0.

Our architecture involve:

A server machine with SRM 7.0 (SRM server and SUS components both in this machine)

A server machine with Netweaver PI 7.0

A server machine with EP 7.0

A server machine with SAP R/3 4.6C

Now we are working on vendor replication process in order to carry out vendors from R/3 to SUS (on portal enviroment) and we made following steps:

- Replication of vendor from R/3 to SRM by mean tx BBPGETVD: OK

- Replication of vendor from SRM to SUS (on portal enviroment) by mean tx BBP_SP_SUPP_INI:

In this step we put the BP (created with tx BBPGETVD) on field "Supplier" but we obtained the Message no. BBP_XP004

"No vendor allowed for vendor portal"

So we want to know, in connection with mentioned architecture, the way to perform this activity in order to replicate the suppliers in SUS.

Is possible perform activities related to exchange documents (by mean Netweaver PI) between SRM and SUS (as necessary for our implementation scenario) if these mentioned components are installed and configured on the same phisical server machine?

What is the best recommendation about installation of SRM and SUS? A unique server machine or separated server machines?

Is there any inconvenience or technical reason having SRM and SUS in the same server machine?

Thanks in advance.

Regards,

Horacio

[Former Member · Accepted solution]

Thank you again Nikhil,

Thinking in two clients, one for SRM and the other for SUS/ROS, I have some aspects to ask about Middleware (customizing objects and material/service masters).

Since in MM-SUS scenario the PO is sended from MM only to SUS to be confirmed and invoiced there; Is neccesary transfer via middleware cust. objects and material/service masters to SRM and/or SUS/ROS?

We believe is not neccesary because we sent a PO with a material item to SUS and it was created OK, but we have doubts about if those master data are necessary in SRM.

Thanks in advance.

Regards,

Horacio

[Former Member · Accepted solution]

Hi,

No, middleware customisation is not needed for SUS.

Nikhil

[Former Member]

Thank you very much for your help Nikhil.

Regards,

Horacio

[Former Member]

Hi Nikhil,

About recommendation related to SRM and SUS installed in separated clients:

Could you please indicate to me information (a SAP Note, a guides, etc) where that recommendation is asked to deploy scenarios like plan driven procurement with supplier integration?. Up to now, I never found information about that prerrequisite.

I checked in SRM 40 configuration guide for plan driven procurement with supplier integration and there it wasn´t necessary two clients because SUS is a part of SRM server; Why is necessary two clients SRM and SUS in SRM 70?.

Thanks in advance.

Regards,

Horacio

[Former Member]

Hi Nikhil,

Thanks for your soon response.

Our process involve PR and PO manual creation in MM and then PO (with ALE message type) is routed to a supplier in SUS via XI. We could achieve that steps succsesfully.

We don´t have in scope neither use SRM for sourcing nor PO creation (via IDOC) in MM.

In connection with my previous explanation; Would you say that our process is MM-SUS?.

If yes, can I follow the steps mentioned in below link described at point u201CProcess Flow Without Supplier Registrationu201D?. What´s the difference between creating and replicating bussiness partner data?.

http://help.sap.com/saphelp_srm40/helpdata/en/c0/7a0859ee91d54aa48a69fb5d2c4089/content.htm

Thanks in advance.

Regards,

Horacio

[Former Member]

Hi,

Yes you can follow that reference.

Indeed its MM-SUS in your case as a PO created in MM is being routed to SUS via XI.

Usually SUS and ROS clients are the same and hence SAP recommends that you have SRM and SUS in different clients because SRM client will house the user org structure whereas SUS will house the external registered vendors in addition to the replicated vendors.

Regards,

Nikhil

Edited by: Nikhil RGupta on Apr 4, 2011 6:36 PM

[Former Member]

Hi,

I guess its MM-SUS in your case.

PR created in MM will be routed to SRM for sourcing - after finding a source of supply a PO is created in MM - this PO is then routed to a supplier in SUS via XI.

SAP recommends that your SRM and SUS clients should be separate. (Can be on the same server though). You can replicate vendors from MM to SUS using Tcode BD14.

Regards,

Nikhil

[Former Member]

Hi Nikhil,

Really we are bulding the scenario plan driven procurement with supplier collaboration, so we never knew that there are an SRM-SUS or MM-SUS distingueshed from available documentation we had obtained from service.sap.com.

In connection with my original question and the alternatives showed by you; Could you please to clear relevant aspects and steps to take in account and perform?.

Thank you very much.

Regards,

Horacio

[Former Member]

Hi Horacio,

Are you looking @ implementing MM-SUS or SRM-SUS?

Regards,

Nikhil

[masa_139]

Hi,

For "No vendor allowed for vendor portal" error, please check the BP ID does not exist in SUS side.

For SUS deployment option, Security guide may help you.

http://service.sap.com/srm-inst

Regards,

Masa