Service Procurement in Extended Classic Scenario

[Former Member]

Hi,

We are planning to use SRM 7 EHP 1 with backend ECC 6 EHP 4. We are leaning toward the extended classic scenario. However we are a bit confused reading some documentation that saying Service Procurement classic can only be used in classic scenario.

What does this mean? To put this in more simple, can we have this scenario in extended classic deployment:

PDP:

1. We create PR with 2 items, each item have 3 sub-line services,

2. We push this PR to SRM

3. We create PO in SRM and it is copied to ECC.

4. PO will have 2 items, with each item have 3 sub-line services.

Self Service Procurement:

1. We create SC with 2 items, each items have 3 sub-line services,

2. We create PO in SRM and it is copied to ECC

3. PO will have 2 items, with each item have 3 sub-line services.

Really appreciate if someone can clarify this point.

Best regards,

Josh

[Amarjeet]

Hi,

The SRM PO does not support service hierarchy. But when a service PO with multiple line items are transferred to ECC( in extended classic scenario), it would have one service item at item overview and we can see all the line items as hierarchy/specification in services tab under item detail.

Accounting data must be same for all the line items in SRM otherwise it would create multiple line items in ECC.

Regards,

Amarjeet

[Former Member]

Dear Josh,

For your scenarios below:

Self Service Procurement:

1. We create SC with 2 items, each items have 3 sub-line services,

2. We create PO in SRM and it is copied to ECC

3. PO will have 2 items, with each item have 3 sub-line services.

The shopping cart and PO in local SRM system does not support service hierarchy (Service subline) in the system.

PDP:

1. We create PR with 2 items, each item have 3 sub-line services,

2. We push this PR to SRM

3. We create PO in SRM and it is copied to ECC.

4. PO will have 2 items, with each item have 3 sub-line services.

Here also, the system will not create po in the local srm system. The local PO cannot support service hierarchy. The system by default create the purchase order in the backend system directly.

Thanks and regards,

Ranjan

[sap_2605]

hi,

i just see this thread, what do you mean that system will default to create po in backend? does it mean that eventhough we activate the extended classic, the system will automatically behave like classic and push it to backend directly? or it will throw error?

john

[former_member22425]

Hello Josh,

By Standard, Service procurement (mm-srv) always works in Classic deployment and PO will always be created in ECC system.

Best Regards,

Rahul

[Former Member]

Hi Rahul,

Thanks for the response. However the question is can we have the scenario mentioned above in extended classic scenario?

Best regards,

Josh