SRM-Add-on and Self Service Procurement scenario

[former_member189501]

As for note 963000 it's possible to install the SRm as add-on over an existing ECC60, with the SAINT transaction in order to save hardware resources.

NOte 963000 says the Self-Service Scenario is supported in "classic deployment" form.

What does it means ?

We need the SRM scenario where the documents are created both in SRM and ECC6. It is that the "classic deployment" ?

regards

[Former Member]

Hi Mauro,

Classic deployment means :

You can create shopping cart in SRM system but follow-on documents such as PR / PO / Goods confirmation / invoice and payment will be created in backend system. However, you can do goods confirmation and invoice creation in srm system.

Extended classic deployment means :

You can create shopping cart and follow-on docs in srm system. You can also replicate these docs in backend system. The po which is created in srm system will be called leading purchase order.Hence, you can't change this po in backend system. You can only display them. Goods confirmation and invoice creation may be done in either of the system.

Thanks

Vikram

[former_member189501]

Thanks for the prompteness.

So to resume the Extended Scenario can't be used with the SRM Add-on, as the system will be the same of the ECC60 right ?

Another question about SRM add-on:

In this configuratin the ECC60 and the SRM are in the same client ? Or to deploy the SRM is needed another client, different from that one used for the ECC60 ?

regards