Purchase Req - Multiple Release codes

Sharma, Sharad Sharad.Sharma at pdl.com
Mon Aug 20 15:32:34 EDT 2007


Security should be setup so that a person with a higher release code is
allowed to approve the lower level release codes also. 

Eg. A director can approve for manager and director, a VP can approve
for VP , Director and Manager .

Thanks,
Sharad.

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Prasad, Prashanthi
Sent: Monday, August 20, 2007 11:27 AM
To: sap-wug at mit.edu
Subject: RE: Purchase Req - Multiple Release codes

 Hello again,

  I did check with the MM folks and they said that they can make each
release code as required which means the releasecode R5 must release it
before anyone in the hierarchy can release it.
But the requirement is the purchase req can be released in a chain and
in Ememrgency situations, the higher release code should be able to
release it.

Thanks

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of sap-wug-request at mit.edu
Sent: Monday, August 20, 2007 1:07 PM
To: sap-wug at mit.edu
Subject: SAP-WUG Digest, Vol 33, Issue 47

Send SAP-WUG mailing list submissions to
	sap-wug at mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
	http://mailman.mit.edu/mailman/listinfo/sap-wug
or, via email, send a message with subject or body 'help' to
	sap-wug-request at mit.edu

You can reach the person managing the list at
	sap-wug-owner at mit.edu

When replying, please edit your Subject line so it is more specific than
"Re: Contents of SAP-WUG digest..."


Today's Topics:

   1. Purchase Req - Multiple Release codes (Prasad, Prashanthi)
   2. RE: DEADLINE MONITORING NOT WORKING (Alon Raskin)
   3. RE: Archiving (yves.lebacq at skynet.be)
   4. Re: Purchase Req - Multiple Release codes (Mike Pokraka)
   5. Re: DEADLINE MONITORING NOT WORKING (Joe_Toledo at capgroup.com)


----------------------------------------------------------------------

Message: 1
Date: Mon, 20 Aug 2007 11:51:56 -0500
From: "Prasad, Prashanthi" <pprasad at citgo.com>
Subject: Purchase Req - Multiple Release codes
To: <sap-wug at mit.edu>
Message-ID: <D898BFBBE838A04892FC5B15925B0F2F182C9E at houex01.citgo.com>
Content-Type: text/plain; charset="us-ascii"

Hello MIT Friends,

   I have an issue with my Purchase requsition workflow. The only
triggering event for this workflow is 'Releasestepcreated'. Everything
was working great until now just because we had only one releasecode At
ONE TIME. But now they have come up with the idea that suppose if the
Release code is greaterr than release codeR5(250,000 to 500,000), the
config has been changed in such a way that for example, 3 release codes
will appear in the 'Release Strategy' tab R5, R6 and R7. Before R7 was
the only release code and when he approves it, that's it. But now before
R7 approves it, the workflow should first go to R5 and he has to hit the
Release button and save it and then it has to go the next release code
'R6' and then after he releases it, the workflow should go to R7. I have
taken care of all these logic.
Now the problem I am facing is the 'ReleaseStepCreated' event is being
triggered 3 time when the purchase req is created. How do I restrict
this event to be triggered just once at anytime?

Any help is greatly appreciated.

Thanks,
Prashanthi Prasad
SAP ABAP/Workflow
CITGO Petroleum Corporation
pprasad at citgo.com
832-486-4899

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20070820/8163c8c7/a
ttachment-0001.htm

------------------------------

Message: 2
Date: Mon, 20 Aug 2007 11:56:52 -0400
From: "Alon Raskin" <araskin at 3i-consulting.com>
Subject: RE: DEADLINE MONITORING NOT WORKING
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	<CEF21C1C5BF2FA42A42CEC87B91BBCDE03A87761 at ms07.mse2.exchange.ms>
Content-Type: text/plain; charset="us-ascii"

Is SWWDHEX scheduled?

 

Alon Raskin

e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 

p: +1 207 523 3489

c: +1 207 409 4983

f:  +1 806 403-4983

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Nash John
Sent: Monday, August 20, 2007 11:15 AM
To: SAP Workflow Users' Group
Subject: DEADLINE MONITORING NOT WORKING

 

Hi Friends,

 

Hope someone could help me out!!!.

 

I'm trying to send an external email to level2 manager if level1 manager
didn't execute workitem for 2 days. But my readline monitoring not
working. This is what I did in deadline monitoring;

 

  1. Requested end

   2. selected modeled

  3.  time : 2 days

  4. outcome requested end activated.

 

 

Please help

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20070820/e7652eea/a
ttachment-0001.htm

------------------------------

Message: 3
Date: Mon, 20 Aug 2007 19:19:19 +0200
From: yves.lebacq at skynet.be
Subject: RE: Archiving
To: ssreddy at hotmail.com, sap-wug at mit.edu
Message-ID: <67i09g$oeqc7 at relay.skynet.be>
Content-Type: text/plain; charset="us-ascii"



Hi,

I'm just coming back from my holidays, hope not to late for answers to
you.
You can not reload the already archived work item, it is not like IDOC
or others objects.
To archive, use the transaction SARA, WORKITEM as object.
The way to archive is really easy to find in sap help portal and OSS
note.
We are archiving the workitems since 6 months ago and everything is
going right.

Just pay attention when you archive objects attached to a workflow:
i.e. let think you archive the IDOCs objects first, and one of these
IDOC is an object included in an active workflow, you will havev some
problem with it.

For your information, workitems are only archived if the main workitem
has its status completed, cancelled or deleted. I mean if a sub workflow
has its status 'COMPLETED' but the main workflow is not yet completed,
not one workitem will be archived.

Hope this help you.
Do no hesitate to reach me in case of questions.

Cheers.

Yves






Hi All,Can anybody help me in archiving the UWL workitems ? Also help me
in how to load already archived items?Thanks for your help in
Advance.Thank
youSrinivas_____________________________________________________________
____Tried the new MSN Messenger? It's cool! Download now.
http://messenger.msn.com/Download/Default.aspx?mkt=en-in
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20070820/995eaf7b/a
ttachment-0001.htm

------------------------------

Message: 4
Date: Mon, 20 Aug 2007 18:32:34 +0100 (BST)
From: "Mike Pokraka" <asap at workflowconnections.com>
Subject: Re: Purchase Req - Multiple Release codes
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	
<32152.199.4.27.122.1187631154.squirrel at pluto.workflowconnections.com>
Content-Type: text/plain;charset=iso-8859-1

Hello,
This should be configured in the release strategy, please talk to your
MM folks.
Cheers,
Mike

On Mon, August 20, 2007 5:51 pm, Prasad, Prashanthi wrote:
> Hello MIT Friends,
>
>    I have an issue with my Purchase requsition workflow. The only 
> triggering event for this workflow is 'Releasestepcreated'. Everything

> was working great until now just because we had only one releasecode 
> At ONE TIME. But now they have come up with the idea that suppose if 
> the Release code is greaterr than release codeR5(250,000 to 500,000), 
> the config has been changed in such a way that for example, 3 release 
> codes will appear in the 'Release Strategy' tab R5, R6 and R7. Before 
> R7 was the only release code and when he approves it, that's it. But 
> now before
> R7 approves it, the workflow should first go to R5 and he has to hit 
> the Release button and save it and then it has to go the next release 
> code 'R6' and then after he releases it, the workflow should go to R7.

> I have taken care of all these logic.
> Now the problem I am facing is the 'ReleaseStepCreated' event is being

> triggered 3 time when the purchase req is created. How do I restrict 
> this event to be triggered just once at anytime?
>
> Any help is greatly appreciated.
>
> Thanks,
> Prashanthi Prasad
> SAP ABAP/Workflow
> CITGO Petroleum Corporation
> pprasad at citgo.com
> 832-486-4899
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>


--
Mike Pokraka
Senior Consultant
Workflow Connections
Mobile: +44(0)7786 910855



------------------------------

Message: 5
Date: Mon, 20 Aug 2007 08:31:57 -0700
From: Joe_Toledo at capgroup.com
Subject: Re: DEADLINE MONITORING NOT WORKING
To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
Message-ID:
	
<OFC2EB026B.4BAE9437-ON8825733D.005534C5-8825733D.005552C6 at capgroup.com>
	
Content-Type: text/plain; charset="us-ascii"

Good morning,

I might be stating the obvious, but have you checked to see if job
SWWDHEX 
is running?

Joe Toledo | The Capital Group Companies
Location: BRO | Extension: 55417 | Outside: 714-257-5417
E-mail: Joe_Toledo at CapGroup.Com
[ Mailing: 135 So. State College Blvd  Brea, CA 92821  ]




"Nash John" <emailtonash at gmail.com> 

Sent by: sap-wug-bounces at mit.edu
08/20/2007 08:14 AM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>


To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc

Subject
DEADLINE MONITORING NOT WORKING






Hi Friends,
 
Hope someone could help me out!!!.
 
I'm trying to send an external email to level2 manager if level1 manager

didn't execute workitem for 2 days. But my readline monitoring not 
working. This is what I did in deadline monitoring;
 
  1. Requested end
   2. selected modeled
  3.  time : 2 days
  4. outcome requested end activated.
 
 
Please help_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.mit.edu/pipermail/sap-wug/attachments/20070820/437b0700/a
ttachment.htm

------------------------------

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


End of SAP-WUG Digest, Vol 33, Issue 47
***************************************

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug




More information about the SAP-WUG mailing list