Initial queries for 'Sourcing with Bid Invitation '

[Former Member]

Hello all,

Just starting a new implementation project!

So will keep bugging you guys daily.

Confident, that gurus here are quite capable of answering my every question

Here are my queries:

1. Our basis has just installed SRM server 5.5 (sorry,not aware about patch) and created a sandbox client.

We are mainly interested in 'Startegic sourcing with Bid invitation'.

On our ECC side we have IDES of ECC 6.0 and no sandbox client yet.

So we are thinking to use IDES only as a backend (co cd 1000)

Logically this seems OK

but I want to ask forum if you forsee any problems in this?

2. Our basis is reluctant to create a seperate client for ROS

so can i bundle EBP and ROS in one client?

Do we need a seprate installation of ROS?

If not installed intially can they arrange ROS in the same client as of that of EBP?

3. We may not be permitted SUS.

So I belive there can not be any vendor user admiministartion.

But can I get atleast one log in user per vendor?

After I transfer vendors from ROS to EBP, is it possible to cretae more users per vendor in EBP itself?

Will be grateful if anybody can send me self-made docs for 'Startegic sourcing with Bid invitation'.

dinesh.powale@googlemail.com

BR

Dinesh

<b>Don't worry about points :-)</b>

[Ramki · Accepted solution]

1) No problem.

2) You need not need any installation for ROS. You just need to create a client. would strongly recommend this.

Technically, it is possible to have EBP & ROS in the same client. But, there are lot of problems in Business partner area. Search this forum..I remember there is somebody who is trying todo EBP & SUS in the same client.

Finally SAP does not recommend EBP, ROS & SUS in same client in productive environment. ROS& SUS can be in the same client.

3) You do not need to use SUS. Suplier self changing the data will not be there.

In this case, you will create supplier users only in EBP.

4) Service.sap.com/ibc-srm has strategic sourcing config guide for SRM40 and it is still valid.

Best regards

Ramki

[Former Member · Accepted solution]

Hello Ramki,

Thanks,

I was expecting answer from you only.

1. accepted. will go ahead.

2. For ROS you have said that"You just need to create a client"

is this a purely basis activity?

can you ellaborate a little?

3. Client has a requirement that the bid invitations raised by the strat

purchaser should be seggrigated depending upon the prod cat and region

and should be shown on EP for vendor viewing.

Is it possible without SUS?

4. OK. I have it.

BR

Dinesh

[Ramki · Accepted solution]

Hi Dinesh

2) I meant ' no installations required' and just creating a client in SRM server -->this is basis. After that you need to configure as per sourcing config guide.

3) You need to make prod cat field in the header mandatory (use check badi). For region, you may need custom field (check note 672960). For the list as required, you need to use bbp_wf_list badi.

Best rgds

Ramki

[Former Member · Accepted solution]

Hello Ramki,

Thanks again!

2. Understood but has to give a detailed justification to management.

Reason: In our landscape there are only two servers for SRM.

One for development and one for production.

On development server already following clients have been created

100 : Master configuration

200 : Prototype

300 : SandBox

400 : Development

500 : User Acceptant Test

800 : Training

Now if we have to create ROS for each enviornment we need atleast 4 more clients i.e. corresponding ROS clients for Prototype,SandBox,User Acceptant Test and Training.

This may affect the server performance.

Can I ask you one question?

What is the basic need for a seperate client for ROS functionality?

Is it that when the prospect suppliers are transferred from ROS to EBP their BPs are changed?

Customers would expect that for a small functionality they need not create a seperate client.

BR

Dinesh

[Ramki · Accepted solution]

Hi Dinesh

I think you have too many 'administrative' clients unnecessarily.

I do not recommend a client structure as you would normally do in R/3. Review once again..may be you can merge 'Master', 'prototype', 'sandbox', 'development' .

Best regards

Ramki

[Former Member · Accepted solution]

Thanks, Ramki.

Will talk in team.

But my other question remains unanswered

Can I ask you one question?

What is the basic need for a seperate client for ROS functionality?

Is it that when the prospect suppliers are transferred from ROS to EBP their BPs are changed?

Customers would expect that for a small functionality they need not create a seperate client.

BR

Dinesh

[Ramki · Accepted solution]

I think we should be clear.

ROS and SUS are external interfacing systems mostly...they are mainly used by 'external' organizations.

EBP is mainly used by internal employees.

Organizations may not be willing to open their systems to external organizations and hence this demarcation was done in the design.

Also: ROS creates a 'prospect' BP which is different from regular BP.

Best regards

Ramki

[Former Member · Accepted solution]

Thanks again Ramki.

Principally I understand the concept of internal and external

systems.

But it will be difficult for me to sell this concept to team that

if we bundle these two functionlities in one client, EBP data will not

be secure.

i.e. when the bid invitation will be sent to the bidder

the link will carry the business object no of BI and the BP of the bidder

and will bring him back to quote for that only

so how he can be exposed to other information?

ANYWAY I am parking this issue here.

Will come back with more questions

(Hope you don't mind)

BR

Dinesh

[Former Member]

constraint for seperate client