how to prevent automatic release of external purchase requirement ??

[former_member186143]

Now I have my issue solved of transfering the purchase requirements from r3 to srm I face the problem of how to prevent the release of the shoppingcart and use the workflow instead.

I found

some old topics like

I also tried to find badis like BBP_BADI_EXTREQ_OUT but there the field auto_source is missing or in

BBP_BADI_EXTREQ_OUT from the backend.

Is there any standard SAp way to prevent the automatic release of external purchase requirements ?

kind regards

arthur

[former_member186143]

hmmm I first will investigate the use of

BAPI_SCEC_CREATE

before making all the enhancements

kind regards

arthur

[former_member183819]

Hi Arthur

Question not clear.

Approved /Released PR transfered to SRM as a Shopping cart and sitting in the cockpit for BUYER action.

Where do you want the Work flow or Approval process?.

[former_member186143]

The released pr is transfered to srm and becomes a shoppingcart which is automaticaly approved.

The meaning of the whole procedure is that the workflow for approval in srm is triggered on these PR's and after approval becomes a PO.

sap note 505030 also describes the standard behaviour of external requirements

16. External requirements are considered to be released in SRM and, therefore, do not lead to a release approval procedure (approval workflow) in SRM.

But that is opposite of what I try to do here.

the workflow approval is already set up and working in srm so why implement a whole new approval procedure for PR's when you can transfer them to srm instead.

the main problem here is for making a PR's there is also a new Serviceorder necesarry. I can make a screen with all the fields necessary for the serviceorder and PR and create those both in 1 action. if I have to make that in BSP I have to create a lot of different elements and programmed searchhelpsback to R3 to support these requirements

kind regards

arthur

[former_member183819]

ECC release/ approve is mandatory since it has been created in ECC system.After approval only you can convert into another document like SC etc. you can not avoid this PR approval step in ECC.

The SRM design is like that

Approved PR --- SC cockpit - APPROVED then only it goes to COCKPIT.

Since it has been approved in ECC , so again Approval is not required in SRM arena.

however if you want to do again make it approval process in SRM

you can make it .By PRASANNA RENGARAJAN Blog

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

[Former Member]

Hi

The whole purpose of Plan Driven scenario is that MRP generated requisitions are sent to SRM. For PRs generated by MRP it is assumed that these are real requirement and do not require any additional approvals.

But as Muthu said, you can still have workflow activated for such Shopping Carts, You may design your workflow by writing a BRF Expression for this SC and use that in a process schema

Or you can use the One suggested by Muthu, please refer to this document

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

Regards

Virender Singh

[former_member186143]

perhaps I can better also explain the problem.

the process now is that there is a word marco with a fill in form that collects all the data necessary to process a request.

when all data is filled in the form (like 30 seperate fields) it is send to the administration who translate the form into a serviceorder and a purchaseorder with account assignment the purchase order after it is approved. the approval however for these orders goes on paper. (for example it is about construction works like building or renovations)

Now the idea was to make the approval process digital.

first option: release strategy on PR's

problem : no knowledge on how to set this up available in the company ( I also tried to figure it out, any guide for dummies on this is appreciated)

second option:

Sent PR to SRM and let SRM do the release strategy.

advantage:

- users can approve just by clicking approve in email, they don't have to login to srm for this. (is that also possible in R3 ?)

- knowledge on how release strategy works in srm is available.

- easy to trace the approval workflow for a user.

When I think of it perhaps I can also create a shoppingcart straigth away from R3 with the bapi and skip the PR at all

BAPI_SCEC_CREATE or with BBP_PD_SC_CREATE.

third option:

programm BSP for the requirement is quite challenging since all the fields that are required before a PR or SC can be created is quite a lot. further on I have to programm the generation of a serviceorder in the backend and return the number to be set as accounting order.

if you have any other suggestions they are also more than welcome.

ps nice a pdf with instructions on how to implement enhancements which are not copy pastable

kind regards

arthur

Edited by: A. de Smidt on Nov 11, 2010 4:14 PM

Edited by: A. de Smidt on Nov 11, 2010 4:18 PM