External requirement handling in SRM using classic scenario

[Former Member]

Hi Experts,

We have a requirement in Classic scenario:

PRs for MRO / indirect materials generated in PM / PS of ERP will be transferred to SRM using WF interface for approval process.

Upon final approval in SRM, Follow-on document PO should be created in the back end.

The SC in SRM should have the status u201CApprovedu201D & u2018Follow-on Documentu2019 created.

My question is SRM standard will create a PO as follow-on doc after the SC is approved in SRM. How to control this creation of PO in SRM & only approval message should be transferred to back end ERP.

Pls provide any suggestions or inputs on technical settings / adjustments to be carried out.

Note that we cannot use PDP scenario as SRM will be used only for SC approval process.

Tks.

[former_member183819 · Accepted solution]

Hello irahed

According to standard

you are released PR so thats why PRs are turned to SC .

it is valid logically. though you want more validation

in the srm side. you can go for developments

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5082a622-7310-2c10-1a9b-ef31dd69a...

br

Muthu

[Former Member]

Thanks Muthu for the reply.

The doc flow in the link above shows that after SC is approved, it will be available in sourcing cockpit for further processing (i.e. RFX, PO etc) in SRM. Our requirement should not be allowed to create PO in SRM and it should be allowed only in back end ECC.

SRM is used to centralize the approval process where multiple back end systems are connected. (How ever, in future follow-on docs are also created in SRM).

Current Target steps:

1. Create PR from PM/PS in ECC (PR status will be "In release").

2. Transfer PR to SRM and SC will be created (SC status will be "In approval").

3. SC will be Approved / or Rejected in SRM. (PR status will be updated to Approved / or Rejected in ECC).

4. If approved, follow-on doc PO (manual or automatic) will be created in ECC. (SC status will be updated to EX: "PO cretaed")

When the SC is in the process of approval, user in ECC may add new items or make changes to PR from PM/PS. After these changes, the current approval WF for SC in SRM should be cancelled and new SC is created and so on...

Sophisticated message synchronization is required between ECC & SRM.

Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications.

Forgot to mention the following system details:

ERP - ECC with EhP4

SRM - SRM 7.0

Thanks,

[former_member183819]

Hi Irhad,

1 .Are you using SRM for only Approval purposes?

2. normally it comes to buyer for vendor decision (if not a vendor / or more than one source of supply)

3. PO can be created in ECC if you have unique source of supply or more than one SOS upon logic.

4. Hope in SRM 7.0 EHP4 -ECC . we dont run job to bring the PR to SRM. automatically PRs converted into SC or RFX in the cockpit.

send business id and send you one PDP doc.

Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications. - i dont have this to comment.

br

Muthu

[Former Member]

Hi Muthu,

1. SRM is also used for SSP (Text, Service & catalog items).

2. Sourcing is done in ECC.

4. Yes, we dont run job to bring the PR to SRM. automatically PRs converted into SC.

Pls send the PDP doc to my Id - <harade> in rediffmail account .

The doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" is nothing but the link (http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5082a622-7310-2c10-1a9b-ef31dd69a770?quicklink=index&overridelayout=true) mentioned by you earlier.

Tks,

Irahed

[former_member183819]

Hi

once released PR means it is equivalent to APPROVAl right . Again why we require approval in SRM side.

since you have a valid sos in ECC and create PO there itself.

if you want bring PRs to SRM only if you want buyer intervention for vendor assignment.

br

Muthu

[Former Member]

Muthu,

PR will not be approved in ECC. It is sent to SRM.

In SRM, multistep approval WFs are defined with complex variants (1st manager, Technical approver, reviewer etc).

We want to take benifit of this SRM approval process in the 1st phase.

In next phase, SRM will also be used for sourcing, follow-on docs creation etc.

So, our current req. is to send PRs(creeated for MRO materials from PM/PS) from ERP to SRM only for approval WFs and update the approval/rejection message to PRs..

Thanks,

[former_member183819]

PR will not be approved in ECC. It is sent to SRM

without releasing PR, Are PRs moved to SRM - in SRM 700 ? or this is your main question

br

muthu

[Former Member]

Muthu,

When PR is sent to SRM for approval, release code is set to "AB" to indicate

that PR is sent to transfered to SRM for approval. It will remain as "AB" till final approval in SRM.

When SC is finally approved, release code is set to "CD" to indicate that

PR is approved (i.e. SC is fully approved in SRM).

Thanks,

[former_member183819]

Hello Irhad

SRM may not understand your release value.

if the PR is released (FINAL) then only it creates a shopping cart.

try to check bbpsccreate*external function module.

indepth need to look how really and when object gets triggered from PR to SC conversion.

br

Muthu

[Former Member]

Hi,

External requirements from SAP/NON SAP system sent to SRM system are created directlly in approved status

and will be placed in sourcing cockpit for assignment of source of supply

Enable SRM workflow Approval for Ext. PR ..please follow the link given below could be very useful for your requirement

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5082a622-7310-2c10-1a9b-ef31dd69a...

Thanks & Regards,

siva prasad sesetty

[Former Member]

Hello Everyone,

We are facing a issue to view the Shopping cart in Sourcing Cockpit.

We are replicating PR from ECC using BBP_EXTREQ_TRANSFER report and it is created as Shopping cart but not visible in Sourcing Cockpit.

Sourcing relevant indicator is "X" and the status is approved.

in BBP_PD it shows "Item Displayed in Sourcing Cockpit"

but still not visible in sourcing cockpit.

Kindly help us by providing your inputs.

We are in SRM 7.03 with ECC 6.04 extended classic scenario.

SPRO setting for sourcing is done and set to always carry out sourcing.

Regards,

Kiran.

[Former Member]

Thanks Muthu for the reply.

The doc flow in the link above shows that after SC is approved, it will be available in sourcing cockpit for further processing (i.e. RFX, PO etc) in SRM. Our requirement should not be allowed to create PO in SRM and it should be allowed only in back end ECC.

SRM is used to centralize the approval process where multiple back end systems are connected. (How ever, in future follow-on docs are also created in SRM).

Current Target steps:

1. Create PR from PM/PS in ECC (PR status will be "In release").

2. Transfer PR to SRM and SC will be created (SC status will be "In approval").

3. SC will be Approved / or Rejected in SRM. (PR status will be updated to Approved / or Rejected in ECC).

4. If approved, follow-on doc PO (manual or automatic) will be created in ECC. (SC status will be updated to EX: "PO cretaed")

When the SC is in the process of approval, user in ECC may add new items or make changes to PR from PM/PS. After these changes, the current approval WF for SC in SRM should be cancelled and new SC is created and so on...

Sophisticated message synchronization is required between ECC & SRM.

Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications.

Forgot to mention the following system details:

ERP - ECC with EhP4

SRM - SRM 7.0

Thanks,