SAP Note clarification

[Former Member]

Hello Guys

I came through a SAP note that, in extended classic scenaio 'do not have the need to create SAP MM Purchase Requisition or Stock Reservation from the SAP SRM Shopping Cart''

Please let me know why.

Thanks in Advance.

[ricardo_cavedini · Accepted solution]

Hello,

In Extended Classi Scenario, shopping cart follow on document will always be created in SRM directly. As we do not have reservation or PR in SRM, PO is cred directly.

If data is not completed, PO will be created in saved status.

Regards,

Ricardo

[laurent_burtaire]

Hello,

With Extended Classic Scenario, follow-on document for a Shopping Cart is always a Purchase Order.

This PO is first created in SRM, then replicated to the backend system. Reason why PO can be modified only in SRM system: you cannot edit corresponding PO in MM.

With Classic Scenario, follow-on document for a Shopping Cart can be:

- a Reservation,

- or a Purchase request,

- or a Purchase Order.

Those three kind of purchasing documents are always created in the backend system where you can modify them.

Regards.

Laurent.

[Former Member]

Thanks for your answer

But still i feel another part is not completely answered.

Why there is no reservation in extended classic scenario.

Again, i wait for your answer to mark this thread as answered.

Thanks in Advance.

[laurent_burtaire]

Hello,

Ricardo gave you the answer: PR and Reservation do not exist in SRM.

One precision regarding what i wrote: SC follow-on document is always a Purchase Order if you do not use Sourcing Cockpit.

If you use Sourcing Cockpit, follow-on documents can be after sourcing :

- a BId Invitation (if Bidding Engine is activated),

- a Purchase Order,

- a Contract,

- an Auction.

Regards.

Laurent.

[Former Member]

In extended classic scenaio, SRM system is the leading system. SC created in SRM will help in creation of PO in further steps. For this reason ECC MM PR will be of little significance. The PO, in SRM are leading PO and it cannot be changed in backend system. Logic is to use full functionality of SRM in Extended classic scenario

thanks

Sangmesh