Deadline monitoring using requested end

Shaurya Jain jain.shaurya at gmail.com
Wed Aug 11 05:46:42 EDT 2010


Hello Srutha,

You can check in transaction SWU3 if your background job for deadline
monitoring is scheduled or not. If it is not then schedule it & you will
find your work item to end & control will then move to next step in your
workflow.

Regards,
Shaurya Jain

On Wed, Aug 11, 2010 at 12:28 PM, srutha keerthi <srutha.s at gmail.com> wrote:

> Hello Team,
>
> We have a requirement to forward the work item to the next level approver
> if the agent assigned to the work item doesnt perform any action untill  a
> specific time( for this we are using 'Requested end').
> But after reaching the requested end duration, no mail is sent to the
> assigned agent indicating the missed deadline at the same time the work item
> is also not sent to the next level approver.
>
> Are there any settings which i missed out.
> Please help me in resolving this issue.
>
> Thanks & Regards,
> Srutha
> On Sun, Jun 13, 2010 at 9:35 PM, <sap-wug-request at mit.edu> wrote:
>
>> 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. Event not triggering on Change Document (Kyle McCarter)
>>   2. RE: Event not triggering on Change Document (Alon Raskin)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Sat, 12 Jun 2010 17:47:51 -0700
>> From: Kyle McCarter <kmccarter at csc.com>
>> Subject: Event not triggering on Change Document
>> To: sap-wug at mit.edu
>> Message-ID:
>>        <OF53E075FF.848C7DE3-ON85257741.00039EFA-07257741.00046243 at csc.com
>> >
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Greetings WUGgers,
>>
>> I have kept this initial request brief, but am happy to expound as
>> necessary. I know you are all busy, and will be grateful for any
>> assistance you can provide.
>>
>> ISSUE:
>> Need to generate an event via Change Documents to Routings (BUS1012).
>> Specifically when PLKO-STATU is changed.
>>
>> STEPS TAKEN:
>> 1) Extended BUS1012 by creating sub-type ZWOBUS1012 with event
>> ZSTATUSCHANGED.
>>
>> 2) Identified the relevant change document object (PLAN) via tcode SCDO.
>>
>> 3. Entry in SWED was left unchanged:
>>        Chg Doc Object = PLAN
>>        Leading Table in CD = PLKO
>>        CD Key w/ Structure = CCPLN
>>        Create = X
>>        Change = X
>>        Delete = X
>>        Create Inst = <blank>
>>        Client Specific = X
>>        Structure = <blank>
>>        Function Module = <blank>
>>
>> 4) Created entry in SWEC:
>>        Chg Doc Object = PLAN
>>        Obj Category = BO
>>        Object Type = BUS1012
>>        Event = ZSTATUSCHANGED
>>        On Create = <blank>
>>        On Change = X
>>        On Delete = <blank>
>> with field restrictions:
>>        Table = PLKO
>>        Field = STATU
>>        Old Value = *
>>        New Value = *
>>
>> All changes were saved to a change request.
>>
>> Test:
>> 1) Turn on event trace (SWELS)
>> 2) Create a change to PLKO-STATU. I did this via CEWB.
>> 3) Turn off event trace (SWELS).
>> 4) Evaluate Trace (SWEL) - Nothing :(
>> 5) Evaluate Change log via CDHDR & CDPOS. My changes appear as expected.
>>
>> Question:
>> Why is my event not being raised? I expect to encounter additional issues,
>> Specifically, I will need to pass old and new values to the event
>> container and then the workflow container. However, I need to be able to
>> successfully raise this event first.
>>
>> Any insights you may have are greatly appreciated.
>>
>> The MadABAPper :)
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://mailman.mit.edu/pipermail/sap-wug/attachments/20100612/ba9e42f8/attachment-0001.htm
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Sat, 12 Jun 2010 21:15:58 -0400
>> From: Alon Raskin <araskin at go3i.com>
>> Subject: RE: Event not triggering on Change Document
>> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>> Message-ID:
>>
>>  <7DEF3CA60BA28D4484A482714C1AFA6D03A08EA675 at 3IExchange01.3I-Consulting.loc
>> >
>>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Did you setup delegation relationship between BUS1012 and ZWOBUS1012?
>>
>> Alon Raskin
>> e: araskin at go3i.com<mailto:araskin at 3i-consulting.com>
>> p: +1 713 513 4820
>> 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 Kyle McCarter
>> Sent: Saturday, June 12, 2010 7:48 PM
>> To: sap-wug at mit.edu
>> Subject: Event not triggering on Change Document
>>
>> Greetings WUGgers,
>>
>> I have kept this initial request brief, but am happy to expound as
>> necessary. I know you are all busy, and will be grateful for any assistance
>> you can provide.
>>
>> ISSUE:
>> Need to generate an event via Change Documents to Routings (BUS1012).
>> Specifically when PLKO-STATU is changed.
>>
>> STEPS TAKEN:
>> 1) Extended BUS1012 by creating sub-type ZWOBUS1012 with event
>> ZSTATUSCHANGED.
>>
>> 2) Identified the relevant change document object (PLAN) via tcode SCDO.
>>
>> 3. Entry in SWED was left unchanged:
>>        Chg Doc Object = PLAN
>>        Leading Table in CD = PLKO
>>        CD Key w/ Structure = CCPLN
>>        Create = X
>>        Change = X
>>        Delete = X
>>        Create Inst = <blank>
>>        Client Specific = X
>>        Structure = <blank>
>>        Function Module = <blank>
>>
>> 4) Created entry in SWEC:
>>        Chg Doc Object = PLAN
>>        Obj Category = BO
>>        Object Type = BUS1012
>>        Event = ZSTATUSCHANGED
>>        On Create = <blank>
>>        On Change = X
>>        On Delete = <blank>
>> with field restrictions:
>>        Table = PLKO
>>        Field = STATU
>>        Old Value = *
>>        New Value = *
>>
>> All changes were saved to a change request.
>>
>> Test:
>> 1) Turn on event trace (SWELS)
>> 2) Create a change to PLKO-STATU. I did this via CEWB.
>> 3) Turn off event trace (SWELS).
>> 4) Evaluate Trace (SWEL) - Nothing :(
>> 5) Evaluate Change log via CDHDR & CDPOS. My changes appear as expected.
>>
>> Question:
>> Why is my event not being raised? I expect to encounter additional issues,
>> Specifically, I will need to pass old and new values to the event container
>> and then the workflow container. However, I need to be able to successfully
>> raise this event first.
>>
>> Any insights you may have are greatly appreciated.
>>
>> The MadABAPper :)
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> http://mailman.mit.edu/pipermail/sap-wug/attachments/20100612/b4ed0561/attachment-0001.htm
>>
>> ------------------------------
>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>> End of SAP-WUG Digest, Vol 67, Issue 37
>> ***************************************
>>
>
>
> _______________________________________________
> 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/20100811/e32e28b4/attachment.htm


More information about the SAP-WUG mailing list