PR workflow : item level release

[akshay.bhagwat@wipro.com]

Thanks for the Inputs Florin..

Another basic doubt..
As we need to do customizing at MM level also if we want to link the PR
Workflow for release strategy , will it interfere with the other
existing PR workflows? ( they are having different release strategy and
custom developed triggering ie. MM customizing for release strategy not
used for them).

Thanks and Regards, 

Akshay Bhagwat

SAP Practice 

Wipro Technologies

': +91 20 2293 3700 x 3608 
Fax: +91 20 2293 3756


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Florin Wach
Sent: Tuesday, April 15, 2008 7:21 PM
To: SAP Workflow Users' Group
Subject: Re: PR workflow : item level release

Hi Akshay,

you'll need to add an event BUS2009.Changed (or similar) and get this
involved in your scenario.

The event BUS2009.ReleaseStepCreated is only send **once** for each
release code, as soon as it becomes "open", e.g. required, but not set,
yet.
The (only) case that the event is send a second (or more) time for the
same release code, is, after the appropriate release code has been set
and
- a full new release strategy has been determined
- a full reset of all release codes was performed (due to value change
within the same release strategy)

So you'll need to filter this constellation when hooking a workflow
under the .Changed event and also keep in mind, that a given approval
may raise the same event, so you might need to consult the latest
written change documents.
It is safe to read the change documents in the check function module.

That's my very first ideas about it.

Best wishes,
   Florin

-------- Original-Nachricht --------
> Datum: Tue, 15 Apr 2008 19:02:31 +0530
> Von: akshay.bhagwat at wipro.com
> An: sap-wug at mit.edu
> Betreff: PR workflow : item level release

> Hi All,
>  
> We are in ECC6.0 and want to use the PR release workflow for item 
> level release. Due to some of the custom requirements, we will have to

> extend
> WS00000038 and then use the custom workflow.
> With this aspect , wanted to know what approach should be taken to 
> achieve the following:
>  
> One of the requirements was to have custom role resolution i.e. may be

> using user exit - in this case , however if agent determination fails,

> notification should be sent to creator and current workflow should
end.
>  Once creator maintains Ztable properly for agent determination , 
> workflow needs to be restarted again for any changes to the PR item . 
> ( Need not be necessarily SignificantlyChanged Event !) as earlier 
> workflow might have been ended due to agent determination error.
>  In this case , I was wondering how std event of ReleaseStepCreated 
> will be created again while changing the PR item?
>  
> Appreciate any inputs on this front.
>   
> 
> Thanks and Regards,
> 
> Akshay Bhagwat
> 
> SAP Practice
> 
> Wipro Technologies
> 
>  
> 
>  
> 
> The information contained in this electronic message and any 
> attachments to this message are intended for the exclusive use of the 
> addressee(s) and may contain proprietary, confidential or privileged 
> information. If you are not the intended recipient, you should not 
> disseminate, distribute or copy this e-mail. Please notify the sender 
> immediately and destroy all copies of this message and any
attachments.
> 
> WARNING: Computer viruses can be transmitted via email. The recipient 
> should check this email and any attachments for the presence of 
> viruses. The company accepts no liability for any damage caused by any

> virus transmitted by this email.
> 
> www.wipro.com
> 
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com