PO service in classic scenario and its confirmation

[Former Member]

Dear experts,

We are in the middle of blueprint phase for implementation of SRM 7.01 and using backend ECC 6.05. We are considering to use self service procurement (creation of Shopping Cart) and classic scenario, so the PO later will be created in ECC.

The problem is we dont really know what is the behaviour of the system if we use item type service. We see that if we create SC with service item, it is different compared if we create service in PR in ECC. While PR in ECC will have hierarchy, SC for service item will have service item as flat (no hierarchy). The questions are:

1. Say I have created SC with 5 items service with different delivery dates. When PO classic scenario is created, how the PO will be created in ECC. Is it:

   a. One PO created in ECC. Each item service will become items in PO, where each item have one sub-line service

       Eg. SC have item 1: service A, item 2: service B.

       Then PO is created --> PO have item 1: with sub-line 1.1: service A

                                                      item 2: with sub-line 2.1: service B

   b. Several PO created in ECC, each PO will have one item with one sub-line item

   c. One PO created in ECC. There will only be one item with 5 sub-line service

        Eg. SC have item 1: service A, item 2: service B.

       Then PO is created --> PO have ONLY item 1: with subline 1.1: service A

                                                                                  subline 1.2: service B

How the PO in ECC will be created?

2. Another question is in regards of the confirmation. Say that the PO service have 2 item where each item hav 2 sub-line:

   Eg: PO X have item 1: subline 1.1: service A

                                  subline 1.2: service B

                      item 2: subline 2.1: service C

                                 subline 2.2: service D

   If I create confirmation for PO X, can I select item 1 and item 2 in the same time? Note that if this happens in ECC, one service entry can only be created

   for one PO item.

Best regards,

Josh

[Former Member]

Hi,

As you have SRM7.01 and ECC6.05 you can use service procurement classic scenario.

That means if the ECC PR has hierarchy and if you transfer the PR to SRM through PDP or CPPR via XI/PI, shopping cart will be created with hierarchy (SOA interface).

In this case you wont have the problem of delivery date as there will be one to one mapping of delivery date from PR to shopping cart to PO.

Please note that when you create shopping cart manually you can not create with service hierarchy. In this case only there will be different line items as you have explained above.

Question number 2 is answered automatically with shopping cart with service hierarchy.

With Regards,

Malay

[Former Member]

Hi Malay,

Thanks for the response. But in our company it has been decided that Shopping Cart will be used instead of PR (due to approval workflow, attachment flowing, etc). So can you advice me what happen if we use Shopping Cart?

Best regards,

Josh

[Former Member]

If you use shopping cart manually then it do not support service hierarchy.

In that case services will be there under item level only.

To answer your question, if different line items have different delivery dates while converting SC to PO in sourcing cock pit the PO splitting happens and there will be multiple PO get generated.

With Regards,

Malay