Deadline texts using the Reevaluate Agent Events

Fri Jun 16 04:39:47 EDT 2006

G'day Jocelyn,

Thanks for the response. I can see that a manual update to the container
will work, but it does seem like it shouldn't be necessary.

I've checked that the deadline job has run but for a step with a modeled
deadline it fails to set the appropriate indicators. There is no little bell
against the deadline time in WI tech display (it turns blue, but isn't
getting marked as passed deadline). Looking at the _Workitem container
element and the attribute DeadlineStatus remains at 0000.

I've checked in a 4.6C system and modeled deadlines _do_ get the
DeadlineStatus set correctly (8998 for Latest End). I'm not sure if this
purely a ECC5 issue, or whether the reevaluate agent is throwing a spanner
in the works. Time for some digging through OSS I guess. If this attribute
was getting set my text issues would be sorted as I could have a simple
IF based on it. (Thanks for the UWL tip - I need to look into this).

Can anyone comment on whether modeled deadlines in an ECC5 system are
setting the deadline status correctly or otherwise?

Thanks,
Mark

On 6/16/06, Dart, Jocelyn <jocelyn.dart at sap.com> wrote:
>
>  Mark,
>
> 1. Deadline indicators have absolutely nothing to do with the "marking
> obsolete" of the work item. Nor with the seriously annoying bouncing message
> in the SBWP inbox.  Suggest you check the deadline job SWWDHEX has run and
> check the technical work item display to make sure the work item deadline
> end has been reached and that the deadline has been escalated.  It may be
> that bouncing message only appears for simple deadlines but I had thought it
> was appearing for modelled deadlines as well.
>
> 2. Rather than playing around with a convoluted IF statement why not just
> have a container element in the task that holds some sort of "This work is
> now overdue" message that you can display in your task. When you first
> create the work item the container element is empty, when the deadline is
> triggered you use SAP_WAPI_WRITE_CONTAINER to update the task container.  So
> long as you display the message in the long text it should automatically
> appear in the work item text.
> Watch out if you are using the UWL as you need to sort out your cache
> administration to get it to read the new text.
>
>
> Regards,
> *Jocelyn Dart*
> Senior Consultant
> *SAP Australia Pty Ltd.*
> Level 1/168 Walker St.
> North Sydney
> NSW, 2060
> Australia
> T   +61 412 390 267
> M   + 61 412 390 267
> E   jocelyn.dart at sap.com
> http://www.sap.com
>
> The information contained in or attached to this electronic transmission
> is confidential and may be legally privileged. It is intended only for the
> person or entity to which it is addressed. If you are not the intended
> recipient, you are hereby notified that any distribution, copying, review,
> retransmission, dissemination or other use of this electronic transmission
> or the information contained in it is strictly prohibited. If you have
> received this electronic transmission in error, please immediately contact
> the sender to arrange for the return of the original documents.
>
> Electronic transmission cannot be guaranteed to be secure and accordingly,
> the sender does not accept liability for any such data corruption,
> interception, unauthorized amendment, viruses, delays or the consequences
> thereof.
>
> Any views expressed in this electronic transmission are those of the
> individual sender, except where the message states otherwise and the sender
> is authorized to state them to be the views of SAP AG or any of its
> subsidiaries. SAP AG, its subsidiaries, and their directors, officers and
> employees make no representation nor accept any liability for the accuracy
> or completeness of the views or information contained herein. Please be
> aware that the furnishing of any pricing information/ business proposal
> herein is indicative only, is subject to change and shall not be construed
> as an offer or as constituting a binding agreement on the part of SAP AG or
> any of its subsidiaries to enter into any relationship, unless otherwise
> expressly stated.
>
>
>  ------------------------------
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Mark Pyc
> *Sent:* Friday, 16 June 2006 1:11 AM
> *To:* WUG
> *Subject:* Deadline texts using the Reevaluate Agent Events
>
>
>  G'day all,
>
> ECC 5.0 NW04
>
> I've been playing around with the use of triggering an event in a modeled
> deadline path to recalculate agents to include the deadline recipients. I
> can get this to happen however there seem to be some side effects.
>
> Since the Workitem is not marked as obsolete the Deadline indicators do
> not get set. Therefore no little bouncing message in the item preview. No
> indicator that the item is overdue.
>
> I want to be able to have dynamic text changes so that the original
> recipient knows that it's passed deadline and the new agents know why they
> are seeing it. I can not figure it out. I have tried in vain to do an IF
> statement comparing current date and time to the deadline date/time.
>
> Part of the problem is that you can't have an IF condition that goes over
> a line in length. This is a problem since the logic is:
> IF &_WORKITEM.LATESTENDDATE& < &SY-DATUM& or &_WORKITEM.LATESTENDDATE&  =
> &SY-DATUM& and &_WORKITEM.LATESTENDTIME&  < &SY-UZEIT&.
> This can be resolved using DEFINE statements and the creation of
> abreviations.
>
> The next part is that you don't have the option of using bracketed
> statements or even having logical precedence of operators.
>
> I tried a concatenation of variable so that 'datetime' can be compared,
> but I can't get the deadline date in yyyymmdd format (I can for sy-datum)
> and therefore comparisons are pointless.
>
> I then got desperate and tried a PERFORM, but even that wouldn't work. Not
> really sure why.
>
> This all seems too difficult.
>
> Is anyone using the Agent Reevaluation technique? If so how do you handle
> it so that users recognise it as a workitem passed deadline??
>
> I was persuing this technique really primarily so that Workitem execution
> times could be reported accurately and secondly to because the design gives
> a relatively clean flow diagram. If I can't let the users know that deadline
> has passed though it doesn't seem such a hot solution.
>
> Any thoughts?
>
> Thanks Mark
>
> (PS my SRM DEV environment died from overheating and has been down for
> over a week now - I will get back on the SRM case once I've got a system
> again)
>
>
> _______________________________________________
> 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/20060616/f4984629/attachment.htm