<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="country-region"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="City"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="place"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thanks Stephane,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>The log says that the wf has been approved
by the 1<sup>st</sup> approver and is completed. However when I look at the
approval preview SC the line is still awaiting approval by the 2<sup>nd</sup> approver.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>When I test the BADI directly with the
shopping cart all the approvers are there.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Richard<o:p></o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Stéphane Bailleul<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, October 05, 2006
3:17 AM<br>
<b><span style='font-weight:bold'>To:</span></b> sap-wug@mit.edu<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE:Issue with shopping
cart not reaching subsequent approver</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'><br>
Hi Richard, <br>
<br>
What is the workflow log saying ? <br>
Does your workflow status indicate an error ( not in BBP_PD but in SWI6)<br>
<br>
Otherwise when you are testing your BADI directly with the shopping cart do you
have all the approvers in it ?<br>
<br>
Cheers<br>
Stephane<o:p></o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
<hr size=2 width="100%" align=center id=stopSpelling>
</span></font></div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=2 face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma'><br>
> From: sap-wug-request@mit.edu<br>
> Subject: SAP-WUG Digest, Vol 23, Issue 8<br>
> To: sap-wug@mit.edu<br>
> Date: Wed, 4 Oct 2006 21:51:14 -0400<br>
> <br>
> Send SAP-WUG mailing list submissions to<br>
> sap-wug@mit.edu<br>
> <br>
>
To subscribe or unsubscribe via the World Wide Web, visit<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
>
or, via email, send a message with subject or body 'help' to<br>
> sap-wug-request@mit.edu<br>
> <br>
> You can reach the person managing the list at<br>
> sap-wug-owner@mit.edu<br>
> <br>
>
When replying, please edit your Subject line so it is more specific<br>
>
than "Re: Contents of SAP-WUG digest..."<br>
> <br>
> <br>
> Today's Topics:<br>
> <br>
>
1. Issue with shopping cart not reaching subsequent approver<br>
> (Smart, Richard )<br>
>
2. RE: Deadlines based on factory calendar - is The Book wrong?<br>
> (Dart, Jocelyn)<br>
>
3. RE: Deadlines based on factory calendar - is The Book wrong?<br>
> (Paul.Bakker@osr.treasury.qld.gov.au)<br>
> <br>
> <br>
> ----------------------------------------------------------------------<br>
> <br>
> Message: 1<br>
> Date: Wed, 4 Oct 2006 13:09:34 -0500<br>
>
From: "Smart, Richard " <Richard.Smart@Honeywell.com><br>
>
Subject: Issue with shopping cart not reaching subsequent approver<br>
>
To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> Message-ID:<br>
>
<C8C2AFE688BA2445ADF7302790EFE96F6E0646@MN65EV801.global.ds.honeywell.com><br>
> <br>
> Content-Type: text/plain; charset="us-ascii"<br>
> <br>
> Hi,<br>
> <br>
>
I have a question on the N-step line item approval of shopping cart<br>
>
workflow (WS14500015 - BADI BBP_WFL_APPROV_BADI). This workflow has been<br>
>
working fine in DEV. Today I noticed a problem in that if an item has<br>
>
more than 1 approver the SC will go to the first approver who approves<br>
> it. It then never appears in the 2nd approvers inbox. Despite this the<br>
>
approval preview looks fine. It indicates that the item has been<br>
>
approved by the first approver and that it is awaiting approval from the<br>
>
2nd approver - the 2nd approver just never gets it.<br>
> <br>
> <br>
> <br>
> Any ideas?<br>
> <br>
> <br>
> <br>
> We're on SRM 4.0 SAPKB64016.<br>
> <br>
> <br>
> <br>
> Thanks<br>
> <br>
> Richard<br>
> <br>
> <br>
> <br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061004/9aca4cca/attachment-0001.htm<br>
> <br>
> ------------------------------<br>
> <br>
> Message: 2<br>
> Date: Thu, 5 Oct 2006 09:20:43 +0800<br>
> From: "Dart, Jocelyn" <<st1:PersonName w:st="on">jocelyn.dart@sap.com</st1:PersonName>><br>
>
Subject: RE: Deadlines based on factory calendar - is The Book wrong?<br>
> To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> Message-ID:<br>
> <F843AF000027394A9F3D3194109269F49846E2@sgsine11.sin.sap.corp><br>
> Content-Type: text/plain; charset="us-ascii"<br>
> <br>
> Hi Folks, <br>
>
The Book wrong??? !!! Say it isn't so! ;-)<br>
> <br>
> No seriously folks this one definitely works. <br>
>
There are a couple of different ways of coding it but all should end up<br>
>
using fm END_TIME_DETERMINE which does count up the working days from<br>
> your base date/time. <br>
> <br>
>
Things that sometimes can go wrong on site are:<br>
> * You aren't passing a factory calendar id or aren't passing the correct<br>
> factory calendar id<br>
>
* Your factory calendar doesn't exist - or doesn't extend to the dates<br>
>
you are using - default approach is usually to try again without factory<br>
> calendar<br>
> * Ditto for the holiday calendar linked to your factory calendar<br>
>
* Your baseline date/time is wrong - e.g. the date/time passed in is<br>
>
from the wrong timezone - remember the baseline date/time needs to be<br>
>
based on the work being done - not the agents doing it<br>
> <br>
> If you want to pass in a specific start date/time rather than use<br>
>
today's date/time that's fine of course - you would simply need to<br>
>
extend the solution in the book a little further. <br>
> <br>
>
You should not have to write your own code unless you don't want to use<br>
>
a factory calendar at all - e.g. if you only have a holiday calendar (in<br>
> which case you are on your own...).<br>
> <br>
>
And yes if you want to calculate long deadlines based on working days -<br>
>
60 days is more effective than 2 months. <br>
> <br>
> Oh and if you have to work out an "early" deadline - i.e. number of days<br>
>
BEFORE a certain date, then use fm START_TIME_DETERMINE. Works a treat.<br>
> <br>
> Regards,<br>
> Jocelyn Dart<br>
> Senior Consultant<br>
> SAP Australia Pty Ltd.<br>
> Level <st1:Street w:st="on"><st1:address w:st="on">1/168 Walker St</st1:address></st1:Street>.<br>
> North <st1:City w:st="on"><st1:place w:st="on">Sydney</st1:place></st1:City> <br>
> NSW, 2060<br>
> <st1:country-region w:st="on"><st1:place w:st="on">Australia</st1:place></st1:country-region><br>
> T +61 412 390 267<br>
> M + 61 412 390 267<br>
> E <st1:PersonName w:st="on">jocelyn.dart@sap.com</st1:PersonName><br>
> http://www.sap.com<br>
> <br>
>
The information contained in or attached to this electronic transmission<br>
>
is confidential and may be legally privileged. It is intended only for<br>
>
the person or entity to which it is addressed. If you are not the<br>
>
intended recipient, you are hereby notified that any distribution,<br>
>
copying, review, retransmission, dissemination or other use of this<br>
> electronic transmission or the information contained in it is strictly<br>
>
prohibited. If you have received this electronic transmission in error,<br>
>
please immediately contact the sender to arrange for the return of the<br>
> original documents. <br>
>
Electronic transmission cannot be guaranteed to be secure and<br>
>
accordingly, the sender does not accept liability for any such data<br>
>
corruption, interception, unauthorized amendment, viruses, delays or the<br>
> consequences thereof.<br>
>
Any views expressed in this electronic transmission are those of the<br>
> individual sender, except where the message states otherwise and the<br>
>
sender is authorized to state them to be the views of SAP AG or any of<br>
>
its subsidiaries. SAP AG, its subsidiaries, and their directors,<br>
>
officers and employees make no representation nor accept any liability<br>
>
for the accuracy or completeness of the views or information contained<br>
>
herein. Please be aware that the furnishing of any pricing information/<br>
>
business proposal herein is indicative only, is subject to change and<br>
> shall not be construed as an offer or as constituting a binding<br>
>
agreement on the part of SAP AG or any of its subsidiaries to enter into<br>
>
any relationship, unless otherwise expressly stated. <br>
> <br>
> <br>
> -----Original Message-----<br>
> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<br>
> Of Mike Pokraka<br>
> Sent: Tuesday, 03 October 2006 6:37 PM<br>
> To: SAP Workflow Users' Group<br>
>
Subject: Re: Deadlines based on factory calendar - is The Book wrong?<br>
> <br>
>
Got onto a system and grabbed a quick moment to test it:<br>
> <br>
>
FM END_TIME_DETERMINE, offset 5 unit TAG (day), fcal 99 (International):<br>
>
5 days from now is Sunday 8-Oct. The FM correctly spits out Tuesday<br>
>
10-Oct, which is NOT simply the next working day.<br>
>
Today -2 days is Sunday 1-Oct, it returns Friday 29-Sep.<br>
> <br>
>
The thing it doesn't do is factory time. Run it at 3am and it returns<br>
> 3am<br>
> of the correct day.<br>
> <br>
> Cheers,<br>
> Mike<br>
> <br>
> <br>
>
On Tue, October 3, 2006 00:43, Mike Pokraka wrote:<br>
>
> Huh? Confused is me. I think it's due to answering wugs late at night<br>
> as<br>
>
> a distraction from the tedium of doing overdue stuff for the taxman.<br>
>
> I don't have the book handy but I think I've based mine on the book<br>
> and<br>
> > it works.<br>
>
> Maybe the book uses a different FM, I use END_TIME_DETERMINE and it<br>
> does<br>
> > the job for me. I think.<br>
>
> The nice thing about the FM is it will also work backwards.<br>
> ><br>
> > Cheers,<br>
> > Mike<br>
> ><br>
> ><br>
> > Paul.Bakker@osr.treasury.qld.gov.au wrote:<br>
>
>> Actually, I think you are missing something!<br>
> >><br>
> >> The problem with the code in The Book is that if you specify a 3-day<br>
>
>> deadline on a Friday, it will be triggered on the Monday. (It simply<br>
> >> adds 3<br>
>
>> days, and then checks that Monday is a working day).<br>
> >><br>
>
>> It should instead be triggered on the Wednesday, because that is when<br>
> 3<br>
> >> full working days have elapsed.<br>
> >><br>
> >> cheers<br>
> >> Paul<br>
> >><br>
> >><br>
> >><br>
> >> |---------+------------------------------><br>
>
>> | | Mike Pokraka |<br>
>
>> | | <asap@workflowconne|<br>
> >> | | ctions.com> |<br>
>
>> | | Sent by: |<br>
>
>> | | sap-wug-bounces@mit|<br>
>
>> | | .edu |<br>
>
>> | | |<br>
>
>> | | |<br>
>
>> | | 03/10/2006 08:23 |<br>
>
>> | | Please respond to |<br>
>
>> | | "SAP Workflow |<br>
>
>> | | Users' Group" |<br>
>
>> | | |<br>
> >> |---------+------------------------------><br>
> >><br>
>
>-----------------------------------------------------------------------<br>
> ---------------------------------------------------|<br>
> >> |<br>
>
>> |<br>
>
>> | To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
>
>> |<br>
> >> | cc:<br>
>
>> |<br>
>
>> | Subject: Re: Deadlines based on factory calendar - is The<br>
>
>> Book wrong? |<br>
> >><br>
>
>-----------------------------------------------------------------------<br>
> ---------------------------------------------------|<br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> Hi Paul,<br>
>
>> Perhaps I misunderstood, but I grasped it differently. What I got was<br>
>
>> that factory calendars become less relevant as time goes on. You<br>
> might<br>
>
>> as well specify 15 working days as three weeks / 21 days because an<br>
> >> extra day won't make much difference, as opposed to a 2 day deadline<br>
>
>> kicking in on a task created on a Friday afternoon, giving the poor<br>
> >> bloke an hour to do his job.<br>
> >><br>
>
>> I've not had to trawl through working days either. The book and the<br>
> doc<br>
> >> Kjetil sent both refer to the same principle. Specify an offset and<br>
> the<br>
>
>> deadline object gives you the end date in working days from TODAY. Do<br>
>
>> not add anything, just plug the object attributes into the<br>
> expression.<br>
>
>> So an instance of a deadline object with a key including an offset of<br>
>
>> today+howevermanydaysuntilnextsaturday should have Monday in it's<br>
> >> DEADLINEDATE attribute.<br>
> >><br>
> >> ....or am I missing something?<br>
> >><br>
> >> Cheers,<br>
> >> Mike<br>
> >><br>
> >> Paul.Bakker@osr.treasury.qld.gov.au wrote:<br>
> >>> WUG Experts,<br>
> >>><br>
>
>>> Thank you very much for all your valuable comments on the factory<br>
> >> calendar<br>
> >>> / deadline problem.<br>
> >>><br>
>
>>> I am going to go ahead and code the solution that was suggested :<br>
> >> increment<br>
> >>> one WORKING day at a time, until the deadline offset is reached. I<br>
> will<br>
>
>>> share the code with you once it's bedded down.<br>
> >>><br>
>
>>> At first I didn't grasp the distinction that Kjetil made between<br>
> short<br>
> >> and<br>
>
>>> long deadlines, but now I get it. A deadline specified in DAYs<br>
> should<br>
> >>> be<br>
>
>>> interpreted as working days, whereas a deadline specified in MONTHS<br>
> or<br>
> >>> YEARS would not be.<br>
> >>><br>
>
>>> thanks again - this group is great!<br>
> >>> Paul<br>
> >>><br>
> >>><br>
> >>><br>
> >>> |---------+----------------------------><br>
>
>>> | | "Kjetil Kilhavn" |<br>
>
>>> | | <KJETILK@statoil.|<br>
>
>>> | | com> |<br>
>
>>> | | Sent by: |<br>
>
>>> | | sap-wug-bounces@m|<br>
>
>>> | | it.edu |<br>
>
>>> | | |<br>
>
>>> | | |<br>
>
>>> | | 28/09/2006 18:30 |<br>
>
>>> | | Please respond to|<br>
>
>>> | | "SAP Workflow |<br>
>
>>> | | Users' Group" |<br>
>
>>> | | |<br>
> >>> |---------+----------------------------><br>
> >>><br>
> >>><br>
> ------------------------------------------------------------------------<br>
> --------------------------------------------------|<br>
> >><br>
> >>> |<br>
> >> |<br>
>
>>> | To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> >> |<br>
>
>>> | cc:<br>
> >> |<br>
>
>>> | Subject: RE: Deadlines based on factory calendar - is The<br>
> >>> Book<br>
> >> wrong? |<br>
> >>><br>
> ------------------------------------------------------------------------<br>
> --------------------------------------------------|<br>
> >><br>
> >>><br>
> >>><br>
> >>><br>
>
>>> Hmmmm... I looked a little more at the code in the presentation<br>
>
>>> (embedded text file), and it looks like it is exactly the same<br>
> solution<br>
> >>> as the appendix in the book.<br>
> >>><br>
>
>>> However, there is one thing that makes me wonder about your<br>
> >>> requirement.<br>
> >>> You say that not only should the deadline be a working day, but only<br>
>
>>> working days should be taken into account. It may make some sense<br>
> for<br>
>
>>> very short deadlines, e.g. a two-day deadline, but should a 15-day<br>
>
>>> deadline be a three-week deadline? In the worst case (I don't know<br>
> what<br>
>
>>> options the standard function modules give you) you will have to<br>
> loop<br>
>
>>> over every date in the range and check if it is a working day or<br>
> not.<br>
> >>> --<br>
>
>>> Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP<br>
> >>><br>
> >>><br>
> >>>> -----Original Message-----<br>
> >>>> From: Kjetil Kilhavn<br>
> >>>> Sent: 28. september 2006 10:14<br>
> >>>> To: 'SAP Workflow Users' Group'<br>
>
>>>> Subject: RE: Deadlines based on factory calendar - is The Book<br>
> wrong?<br>
> >>>><br>
>
>>>> I think this has been discussed several times before (have<br>
>
>>>> you searched the archives?) in this group, but I can't recall<br>
>
>>>> if anyone has had quite the same requirements as you.<br>
> >>>><br>
>
>>>> I have attached a PDF file (can't remember where I got it,<br>
> >>>> whether it was in this group or perhaps on ASUG's site) with<br>
>
>>>> another implementation, and a PowerPoint file with an<br>
>
>>>> implementation that seems to be exactly what you want.<br>
> >>>><br>
>
>>>> If you find none of these match your needs than please create<br>
> >>>> the ultimate solution and share it with the rest of us.<br>
> >>>> --<br>
>
>>>> Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP<br>
> >>>><br>
> >>>><br>
> >>>>> -----Original Message-----<br>
> >>>>> From: sap-wug-bounces@mit.edu<br>
>
>>>>> [mailto:sap-wug-bounces@mit.edu] On Behalf Of<br>
> >>>>> Paul.Bakker@osr.treasury.qld.gov.au<br>
>
>>>>> Sent: 28. september 2006 09:13<br>
> >>>>> To: sap-wug@mit.edu<br>
>
>>>>> Subject: Deadlines based on factory calendar - is The Book wrong?<br>
> >>>>><br>
> >>>>> Hello all,<br>
> >>>>><br>
>
>>>>> We have a requirement to calculate the deadline for a<br>
> >>>>> workitem (eg Latest<br>
>
>>>>> Start) based on the Factory Calendar.<br>
> >>>>><br>
>
>>>>> For example, if the workitem was created on a Thursday and<br>
>
>>>>> the 'Latest Start' deadline is +3 days, then it should be<br>
> >>>>> triggered on the following Tuesday (not Sunday). In other<br>
>
>>>>> words, it should only take working days into account.<br>
> >>>>><br>
>
>>>>> Surprisingly, SAP standard does not cater for this scenario.<br>
>
>>>>> I therefore implemented the solution suggested in the The<br>
> >>>>> Book, in Appendix A9. It shows you how to create a custom<br>
>
>>>>> deadline object based on the factory calendar, and use the<br>
>
>>>>> expression ZDEADLINE.DATE as the reference date in the step.<br>
> >>>>><br>
>
>>>>> Surprisingly (again), this solution DOES NOT work. Deadlines<br>
>
>>>>> are triggered without taking weekends into account.<br>
> >>>>><br>
>
>>>>> When I had a closer look at it, I noticed that the Factory<br>
>
>>>>> Calendar is only being used to determine the Workitem<br>
>
>>>>> _Creation Date_; it is not being used to calculate the Latest<br>
>
>>>>> Start Date. The book even seems to concede this:<br>
> >>>>><br>
>
>>>>> "Note that the reference date gives the date based on<br>
>
>>>>> the factory calendar, but any offset will simply be added to<br>
> >>>>> the reference date as normal".<br>
> >>>>><br>
>
>>>>> If this really is the case, then what is the point of<br>
> >>>>> implementing this solution?<br>
> >>>>><br>
>
>>>>> Has anyone gotten it to work? I'm sure it must be me... sigh.<br>
> >>>>><br>
> >>>>> cheers<br>
> >>>>> Paul<br>
> >>>>><br>
> >>>>><br>
> >>>>> **************************************************************<br>
>
>>>>> **************************************************************<br>
> >>>>> **************************<br>
> >>>>><br>
>
>>>>> Only an individual or entity who is intended to be a<br>
> >>>>> recipient of this e-mail may access or use the information<br>
>
>>>>> contained in this e-mail or any of its attachments. Opinions<br>
>
>>>>> contained in this e-mail or any of its attachments do not<br>
>
>>>>> necessarily reflect the opinions of Queensland Treasury.<br>
> >>>>><br>
>
>>>>> The contents of this e-mail and any attachments are<br>
>
>>>>> confidential and may be legally privileged and the subject of<br>
>
>>>>> copyright. If you have received this e-mail in error, please<br>
>
>>>>> notify Queensland Treasury immediately and erase all copies<br>
>
>>>>> of the e-mail and the attachments. Queensland Treasury uses<br>
>
>>>>> virus scanning software. However, it is not liable for<br>
>
>>>>> viruses present in this e-mail or in any attachment.<br>
> >>>>><br>
> >>>>> **************************************************************<br>
>
>>>>> **************************************************************<br>
> >>>>> **************************<br>
> >>>>><br>
> >>>>> _______________________________________________<br>
> >>>>> SAP-WUG mailing list<br>
> >>>>> SAP-WUG@mit.edu<br>
> >>>>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >>>>><br>
> >>><br>
>
>>> -------------------------------------------------------------------<br>
>
>>> The information contained in this message may be CONFIDENTIAL and is<br>
> >>> intended for the addressee only. Any unauthorised use, dissemination<br>
> of<br>
> >> the<br>
>
>>> information or copying of this message is prohibited. If you are not<br>
> >>> the<br>
>
>>> addressee, please notify the sender immediately by return e-mail and<br>
> >> delete<br>
> >>> this message.<br>
> >>> Thank you.<br>
> >>><br>
> >>> _______________________________________________<br>
> >>> SAP-WUG mailing list<br>
> >>> SAP-WUG@mit.edu<br>
> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >>><br>
> >>><br>
> >>><br>
> >>> _______________________________________________<br>
> >>> SAP-WUG mailing list<br>
> >>> SAP-WUG@mit.edu<br>
> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >><br>
> >> _______________________________________________<br>
> >> SAP-WUG mailing list<br>
> >> SAP-WUG@mit.edu<br>
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> SAP-WUG mailing list<br>
> >> SAP-WUG@mit.edu<br>
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> ><br>
> > _______________________________________________<br>
> > SAP-WUG mailing list<br>
> > SAP-WUG@mit.edu<br>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> ><br>
> <br>
> <br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> <br>
> <br>
> <br>
> ------------------------------<br>
> <br>
> Message: 3<br>
> Date: Thu, 5 Oct 2006 11:52:53 +1000<br>
> From: Paul.Bakker@osr.treasury.qld.gov.au<br>
>
Subject: RE: Deadlines based on factory calendar - is The Book wrong?<br>
>
To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> Message-ID:<br>
> <OFFABF19CA.7804EE95-ON4A2571FE.000A18D1-4A2571FE.000A89F8@treasury.qld.gov.au><br>
> <br>
> Content-Type: text/plain; charset=US-ASCII<br>
> <br>
> Jocelyn,<br>
> <br>
>
You are right - and the book is right! I was simply using the ZDeadline<br>
>
objects the wrong way. Mike P set me straight on that.<br>
> <br>
> Apologies for the confusion. I'll never question The Book again :-)<br>
> <br>
> cheers<br>
> Paul<br>
> <br>
> <br>
> <br>
> <br>
> |---------+----------------------------><br>
>
| | "Dart, Jocelyn" |<br>
>
| | <jocelyn.dart@sap|<br>
>
| | .com> |<br>
>
| | Sent by: |<br>
>
| | sap-wug-bounces@m|<br>
>
| | it.edu |<br>
>
| | |<br>
>
| | |<br>
>
| | 05/10/2006 11:20 |<br>
>
| | Please respond to|<br>
>
| | "SAP Workflow |<br>
>
| | Users' Group" |<br>
>
| | |<br>
> |---------+----------------------------><br>
> >--------------------------------------------------------------------------------------------------------------------------|<br>
>
| |<br>
>
| To: "SAP Workflow Users' Group" <sap-wug@mit.edu> |<br>
>
| cc: |<br>
> | Subject: RE: Deadlines based on factory calendar - is The Book wrong? |<br>
>
>--------------------------------------------------------------------------------------------------------------------------|<br>
> <br>
> <br>
> <br>
> <br>
> Hi Folks,<br>
>
The Book wrong??? !!! Say it isn't so! ;-)<br>
> <br>
>
No seriously folks this one definitely works.<br>
>
There are a couple of different ways of coding it but all should end up<br>
>
using fm END_TIME_DETERMINE which does count up the working days from<br>
> your base date/time.<br>
> <br>
>
Things that sometimes can go wrong on site are:<br>
>
* You aren't passing a factory calendar id or aren't passing the correct<br>
> factory calendar id<br>
>
* Your factory calendar doesn't exist - or doesn't extend to the dates<br>
> you are using - default approach is usually to try again without factory<br>
> calendar<br>
>
* Ditto for the holiday calendar linked to your factory calendar<br>
>
* Your baseline date/time is wrong - e.g. the date/time passed in is<br>
>
from the wrong timezone - remember the baseline date/time needs to be<br>
>
based on the work being done - not the agents doing it<br>
> <br>
>
If you want to pass in a specific start date/time rather than use<br>
>
today's date/time that's fine of course - you would simply need to<br>
> extend the solution in the book a little further.<br>
> <br>
>
You should not have to write your own code unless you don't want to use<br>
>
a factory calendar at all - e.g. if you only have a holiday calendar (in<br>
> which case you are on your own...).<br>
> <br>
>
And yes if you want to calculate long deadlines based on working days -<br>
>
60 days is more effective than 2 months.<br>
> <br>
>
Oh and if you have to work out an "early" deadline - i.e. number of days<br>
>
BEFORE a certain date, then use fm START_TIME_DETERMINE. Works a treat.<br>
> <br>
> Regards,<br>
> Jocelyn Dart<br>
> Senior Consultant<br>
> SAP Australia Pty Ltd.<br>
> Level <st1:Street w:st="on"><st1:address w:st="on">1/168 Walker St</st1:address></st1:Street>.<br>
> North <st1:City w:st="on"><st1:place w:st="on">Sydney</st1:place></st1:City><br>
> NSW, 2060<br>
> <st1:country-region w:st="on"><st1:place w:st="on">Australia</st1:place></st1:country-region><br>
> T +61 412 390 267<br>
> M + 61 412 390 267<br>
> E <st1:PersonName w:st="on">jocelyn.dart@sap.com</st1:PersonName><br>
> http://www.sap.com<br>
> <br>
>
The information contained in or attached to this electronic transmission<br>
>
is confidential and may be legally privileged. It is intended only for<br>
>
the person or entity to which it is addressed. If you are not the<br>
>
intended recipient, you are hereby notified that any distribution,<br>
> copying, review, retransmission, dissemination or other use of this<br>
>
electronic transmission or the information contained in it is strictly<br>
>
prohibited. If you have received this electronic transmission in error,<br>
>
please immediately contact the sender to arrange for the return of the<br>
> original documents.<br>
>
Electronic transmission cannot be guaranteed to be secure and<br>
>
accordingly, the sender does not accept liability for any such data<br>
>
corruption, interception, unauthorized amendment, viruses, delays or the<br>
> consequences thereof.<br>
>
Any views expressed in this electronic transmission are those of the<br>
>
individual sender, except where the message states otherwise and the<br>
>
sender is authorized to state them to be the views of SAP AG or any of<br>
> its subsidiaries. SAP AG, its subsidiaries, and their directors,<br>
>
officers and employees make no representation nor accept any liability<br>
>
for the accuracy or completeness of the views or information contained<br>
>
herein. Please be aware that the furnishing of any pricing information/<br>
> business proposal herein is indicative only, is subject to change and<br>
>
shall not be construed as an offer or as constituting a binding<br>
>
agreement on the part of SAP AG or any of its subsidiaries to enter into<br>
> any relationship, unless otherwise expressly stated.<br>
> <br>
> <br>
> -----Original Message-----<br>
>
From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<br>
> Of Mike Pokraka<br>
> Sent: Tuesday, 03 October 2006 6:37 PM<br>
> To: SAP Workflow Users' Group<br>
>
Subject: Re: Deadlines based on factory calendar - is The Book wrong?<br>
> <br>
>
Got onto a system and grabbed a quick moment to test it:<br>
> <br>
>
FM END_TIME_DETERMINE, offset 5 unit TAG (day), fcal 99 (International):<br>
>
5 days from now is Sunday 8-Oct. The FM correctly spits out Tuesday<br>
> 10-Oct, which is NOT simply the next working day.<br>
>
Today -2 days is Sunday 1-Oct, it returns Friday 29-Sep.<br>
> <br>
>
The thing it doesn't do is factory time. Run it at 3am and it returns<br>
> 3am<br>
> of the correct day.<br>
> <br>
> Cheers,<br>
> Mike<br>
> <br>
> <br>
> On Tue, October 3, 2006 00:43, Mike Pokraka wrote:<br>
>
> Huh? Confused is me. I think it's due to answering wugs late at night<br>
> as<br>
>
> a distraction from the tedium of doing overdue stuff for the taxman.<br>
>
> I don't have the book handy but I think I've based mine on the book<br>
> and<br>
> > it works.<br>
>
> Maybe the book uses a different FM, I use END_TIME_DETERMINE and it<br>
> does<br>
> > the job for me. I think.<br>
>
> The nice thing about the FM is it will also work backwards.<br>
> ><br>
> > Cheers,<br>
> > Mike<br>
> ><br>
> ><br>
> > Paul.Bakker@osr.treasury.qld.gov.au wrote:<br>
>
>> Actually, I think you are missing something!<br>
> >><br>
>
>> The problem with the code in The Book is that if you specify a 3-day<br>
>
>> deadline on a Friday, it will be triggered on the Monday. (It simply<br>
> >> adds 3<br>
>
>> days, and then checks that Monday is a working day).<br>
> >><br>
>
>> It should instead be triggered on the Wednesday, because that is when<br>
> 3<br>
> >> full working days have elapsed.<br>
> >><br>
> >> cheers<br>
> >> Paul<br>
> >><br>
> >><br>
> >><br>
> >> |---------+------------------------------><br>
>
>> | | Mike Pokraka |<br>
>
>> | | <asap@workflowconne|<br>
>
>> | | ctions.com> |<br>
>
>> | | Sent by: |<br>
>
>> | | sap-wug-bounces@mit|<br>
>
>> | | .edu |<br>
>
>> | | |<br>
>
>> | | |<br>
>
>> | | 03/10/2006 08:23 |<br>
>
>> | | Please respond to |<br>
>
>> | | "SAP Workflow |<br>
> >> | | Users' Group" |<br>
>
>> | | |<br>
> >> |---------+------------------------------><br>
> >><br>
>
>-----------------------------------------------------------------------<br>
> ---------------------------------------------------|<br>
> >> |<br>
>
>> |<br>
>
>> | To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
>
>> |<br>
> >> | cc:<br>
>
>> |<br>
>
>> | Subject: Re: Deadlines based on factory calendar - is The<br>
>
>> Book wrong? |<br>
> >><br>
>
>-----------------------------------------------------------------------<br>
> ---------------------------------------------------|<br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> Hi Paul,<br>
>
>> Perhaps I misunderstood, but I grasped it differently. What I got was<br>
>
>> that factory calendars become less relevant as time goes on. You<br>
> might<br>
> >> as well specify 15 working days as three weeks / 21 days because an<br>
>
>> extra day won't make much difference, as opposed to a 2 day deadline<br>
>
>> kicking in on a task created on a Friday afternoon, giving the poor<br>
> >> bloke an hour to do his job.<br>
> >><br>
> >> I've not had to trawl through working days either. The book and the<br>
> doc<br>
>
>> Kjetil sent both refer to the same principle. Specify an offset and<br>
> the<br>
>
>> deadline object gives you the end date in working days from TODAY. Do<br>
>
>> not add anything, just plug the object attributes into the<br>
> expression.<br>
>
>> So an instance of a deadline object with a key including an offset of<br>
>
>> today+howevermanydaysuntilnextsaturday should have Monday in it's<br>
> >> DEADLINEDATE attribute.<br>
> >><br>
> >> ....or am I missing something?<br>
> >><br>
> >> Cheers,<br>
> >> Mike<br>
> >><br>
> >> Paul.Bakker@osr.treasury.qld.gov.au wrote:<br>
> >>> WUG Experts,<br>
> >>><br>
>
>>> Thank you very much for all your valuable comments on the factory<br>
> >> calendar<br>
> >>> / deadline problem.<br>
> >>><br>
>
>>> I am going to go ahead and code the solution that was suggested :<br>
> >> increment<br>
>
>>> one WORKING day at a time, until the deadline offset is reached. I<br>
> will<br>
>
>>> share the code with you once it's bedded down.<br>
> >>><br>
>
>>> At first I didn't grasp the distinction that Kjetil made between<br>
> short<br>
> >> and<br>
>
>>> long deadlines, but now I get it. A deadline specified in DAYs<br>
> should<br>
> >>> be<br>
>
>>> interpreted as working days, whereas a deadline specified in MONTHS<br>
> or<br>
> >>> YEARS would not be.<br>
> >>><br>
>
>>> thanks again - this group is great!<br>
> >>> Paul<br>
> >>><br>
> >>><br>
> >>><br>
> >>> |---------+----------------------------><br>
>
>>> | | "Kjetil Kilhavn" |<br>
>
>>> | | <KJETILK@statoil.|<br>
>
>>> | | com> |<br>
>
>>> | | Sent by: |<br>
>
>>> | | sap-wug-bounces@m|<br>
>
>>> | | it.edu |<br>
>
>>> | | |<br>
>
>>> | | |<br>
>
>>> | | 28/09/2006 18:30 |<br>
> >>> | | Please respond to|<br>
>
>>> | | "SAP Workflow |<br>
>
>>> | | Users' Group" |<br>
>
>>> | | |<br>
> >>> |---------+----------------------------><br>
> >>><br>
> >>><br>
> ------------------------------------------------------------------------<br>
> --------------------------------------------------|<br>
> >><br>
> >>> |<br>
> >> |<br>
>
>>> | To: "SAP Workflow Users' Group" <sap-wug@mit.edu><br>
> >> |<br>
>
>>> | cc:<br>
> >> |<br>
> >>> | Subject: RE: Deadlines based on factory calendar - is The<br>
> >>> Book<br>
>
>> wrong? |<br>
> >>><br>
> ------------------------------------------------------------------------<br>
> --------------------------------------------------|<br>
> >><br>
> >>><br>
> >>><br>
> >>><br>
>
>>> Hmmmm... I looked a little more at the code in the presentation<br>
>
>>> (embedded text file), and it looks like it is exactly the same<br>
> solution<br>
> >>> as the appendix in the book.<br>
> >>><br>
> >>> However, there is one thing that makes me wonder about your<br>
> >>> requirement.<br>
>
>>> You say that not only should the deadline be a working day, but only<br>
>
>>> working days should be taken into account. It may make some sense<br>
> for<br>
>
>>> very short deadlines, e.g. a two-day deadline, but should a 15-day<br>
>
>>> deadline be a three-week deadline? In the worst case (I don't know<br>
> what<br>
>
>>> options the standard function modules give you) you will have to<br>
> loop<br>
>
>>> over every date in the range and check if it is a working day or<br>
> not.<br>
> >>> --<br>
>
>>> Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP<br>
> >>><br>
> >>><br>
> >>>> -----Original Message-----<br>
> >>>> From: Kjetil Kilhavn<br>
> >>>> Sent: 28. september 2006 10:14<br>
> >>>> To: 'SAP Workflow Users' Group'<br>
>
>>>> Subject: RE: Deadlines based on factory calendar - is The Book<br>
> wrong?<br>
> >>>><br>
>
>>>> I think this has been discussed several times before (have<br>
>
>>>> you searched the archives?) in this group, but I can't recall<br>
>
>>>> if anyone has had quite the same requirements as you.<br>
> >>>><br>
> >>>> I have attached a PDF file (can't remember where I got it,<br>
>
>>>> whether it was in this group or perhaps on ASUG's site) with<br>
>
>>>> another implementation, and a PowerPoint file with an<br>
>
>>>> implementation that seems to be exactly what you want.<br>
> >>>><br>
> >>>> If you find none of these match your needs than please create<br>
>
>>>> the ultimate solution and share it with the rest of us.<br>
> >>>> --<br>
>
>>>> Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP<br>
> >>>><br>
> >>>><br>
> >>>>> -----Original Message-----<br>
> >>>>> From: sap-wug-bounces@mit.edu<br>
>
>>>>> [mailto:sap-wug-bounces@mit.edu] On Behalf Of<br>
> >>>>> Paul.Bakker@osr.treasury.qld.gov.au<br>
>
>>>>> Sent: 28. september 2006 09:13<br>
> >>>>> To: sap-wug@mit.edu<br>
>
>>>>> Subject: Deadlines based on factory calendar - is The Book wrong?<br>
> >>>>><br>
> >>>>> Hello all,<br>
> >>>>><br>
>
>>>>> We have a requirement to calculate the deadline for a<br>
> >>>>> workitem (eg Latest<br>
>
>>>>> Start) based on the Factory Calendar.<br>
> >>>>><br>
>
>>>>> For example, if the workitem was created on a Thursday and<br>
> >>>>> the 'Latest Start' deadline is +3 days, then it should be<br>
>
>>>>> triggered on the following Tuesday (not Sunday). In other<br>
>
>>>>> words, it should only take working days into account.<br>
> >>>>><br>
>
>>>>> Surprisingly, SAP standard does not cater for this scenario.<br>
>
>>>>> I therefore implemented the solution suggested in the The<br>
>
>>>>> Book, in Appendix A9. It shows you how to create a custom<br>
>
>>>>> deadline object based on the factory calendar, and use the<br>
>
>>>>> expression ZDEADLINE.DATE as the reference date in the step.<br>
> >>>>><br>
>
>>>>> Surprisingly (again), this solution DOES NOT work. Deadlines<br>
>
>>>>> are triggered without taking weekends into account.<br>
> >>>>><br>
>
>>>>> When I had a closer look at it, I noticed that the Factory<br>
> >>>>> Calendar is only being used to determine the Workitem<br>
>
>>>>> _Creation Date_; it is not being used to calculate the Latest<br>
>
>>>>> Start Date. The book even seems to concede this:<br>
> >>>>><br>
>
>>>>> "Note that the reference date gives the date based on<br>
> >>>>> the factory calendar, but any offset will simply be added to<br>
>
>>>>> the reference date as normal".<br>
> >>>>><br>
>
>>>>> If this really is the case, then what is the point of<br>
> >>>>> implementing this solution?<br>
> >>>>><br>
>
>>>>> Has anyone gotten it to work? I'm sure it must be me... sigh.<br>
> >>>>><br>
> >>>>> cheers<br>
> >>>>> Paul<br>
> >>>>><br>
> >>>>><br>
>
>>>>> **************************************************************<br>
>
>>>>> **************************************************************<br>
> >>>>> **************************<br>
> >>>>><br>
>
>>>>> Only an individual or entity who is intended to be a<br>
>
>>>>> recipient of this e-mail may access or use the information<br>
>
>>>>> contained in this e-mail or any of its attachments. Opinions<br>
>
>>>>> contained in this e-mail or any of its attachments do not<br>
>
>>>>> necessarily reflect the opinions of Queensland Treasury.<br>
> >>>>><br>
>
>>>>> The contents of this e-mail and any attachments are<br>
>
>>>>> confidential and may be legally privileged and the subject of<br>
>
>>>>> copyright. If you have received this e-mail in error, please<br>
>
>>>>> notify Queensland Treasury immediately and erase all copies<br>
>
>>>>> of the e-mail and the attachments. Queensland Treasury uses<br>
>
>>>>> virus scanning software. However, it is not liable for<br>
> >>>>> viruses present in this e-mail or in any attachment.<br>
> >>>>><br>
>
>>>>> **************************************************************<br>
>
>>>>> **************************************************************<br>
> >>>>> **************************<br>
> >>>>><br>
> >>>>> _______________________________________________<br>
> >>>>> SAP-WUG mailing list<br>
> >>>>> SAP-WUG@mit.edu<br>
> >>>>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >>>>><br>
> >>><br>
>
>>> -------------------------------------------------------------------<br>
> >>> The information contained in this message may be CONFIDENTIAL and is<br>
>
>>> intended for the addressee only. Any unauthorised use, dissemination<br>
> of<br>
> >> the<br>
>
>>> information or copying of this message is prohibited. If you are not<br>
> >>> the<br>
> >>> addressee, please notify the sender immediately by return e-mail and<br>
> >> delete<br>
> >>> this message.<br>
> >>> Thank you.<br>
> >>><br>
> >>> _______________________________________________<br>
> >>> SAP-WUG mailing list<br>
> >>> SAP-WUG@mit.edu<br>
> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >>><br>
> >>><br>
> >>><br>
> >>> _______________________________________________<br>
> >>> SAP-WUG mailing list<br>
> >>> SAP-WUG@mit.edu<br>
> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >><br>
> >> _______________________________________________<br>
> >> SAP-WUG mailing list<br>
> >> SAP-WUG@mit.edu<br>
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> >><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> SAP-WUG mailing list<br>
> >> SAP-WUG@mit.edu<br>
> >> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> ><br>
> > _______________________________________________<br>
> > SAP-WUG mailing list<br>
> > SAP-WUG@mit.edu<br>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> ><br>
> <br>
> <br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> <br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> <br>
> <br>
> <br>
> <br>
> <br>
> ------------------------------<br>
> <br>
> _______________________________________________<br>
> SAP-WUG mailing list<br>
> SAP-WUG@mit.edu<br>
> http://mailman.mit.edu/mailman/listinfo/sap-wug<br>
> <br>
> <br>
> End of SAP-WUG Digest, Vol 23, Issue 8<br>
> **************************************<br>
<br>
<o:p></o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p class=MsoNormal><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma'>Appelez vos amis de PC à PC -- C'EST GRATUIT <a
href="http://get.live.com/messenger/overview" target="_new">Essayez-le
maintenant !</a><o:p></o:p></span></font></p>
</div>
</body>
</html>