<div>100% agree. Book is not good to calculate X number of working days. Happened to me last Monday.</div> <div> </div> <div>Jammi<BR><BR><B><I>Mark Pyc <mark.pyc@gmail.com></I></B> wrote:</div> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"> <DIV>Very true. I hadn't thought of this really, but I think Kjetil is also right to point out the relevance of short versus long deadlines. If you did make the deadlines take each "off day" into account then when you're deciding how long you need the deadline you'd need to think about weeks as multiples of 5 days (assuming simple calendar). And really if you're going to have a deadline over 10 days shirely you start talking in weeks or months and then the adjustment to a working day is a nicety but not that important anyway. </DIV> <DIV> </DIV> <DIV>However I appreciate that in other scenarios true FC calculations are important.</DIV>
<DIV> </DIV> <DIV>My 2p (soon to be 2c again!)</DIV> <DIV>Mark<BR><BR> </DIV> <DIV><SPAN class=gmail_quote>On 9/28/06, <B class=gmail_sendername>Soady, Phil</B> <<A href="mailto:phil.soady@sap.com">phil.soady@sap.com</A>> wrote:</SPAN> <BLOCKQUOTE class=gmail_quote style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Kjetil,<BR>I think you have hit the nail on the head and this is why Paul<BR>correctly believes the sample solutions are wrong (don't address his <BR>issue).<BR><BR>The sample solutions only convert a calculated date into a working day.<BR>They do not calculate an offset of x working days from now.<BR><BR>The only way to do this is to call the calendar test x times for each <BR>day<BR>from now until the number of days tested as positive as as work days<BR>equals the desired offset.<BR><BR>The sample solutions simply correct a date to next factory calendar<BR>date.<BR>That's my quick
interpretation of the code at least. <BR><BR>I have also seen this logic mistake around factory calendar in other<BR>custom code stretches.<BR><BR>ie incorrect.<BR>today (t) + offset (n) = y.<BR>corrected date (df) = factory_cal( y).<BR>df is now = to y or higher to reach first working after y. <BR><BR>However this is flawed, since Y is not (n) working days more than (t).<BR>A loop to call the calendar check (n) times is required.<BR><BR>Cheers<BR>Phil.<BR><BR><BR>Phil Soady<BR>Solution Architect<BR>Netweaver Consulting <BR>SAP Australia<BR>M +61 412 213 079<BR>F +61 2 9957 7263<BR>mailto:<A href="mailto:phil.soady@sap.com">phil.soady@sap.com</A><BR><BR><BR>-----Original Message-----<BR>From: <A href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu </A>[mailto:<A href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A>] On Behalf<BR>Of Kjetil Kilhavn<BR>Sent: Thursday, 28 September 2006 6:31 PM<BR>To: SAP Workflow Users'
Group<BR>Subject: RE: Deadlines based on factory calendar - is The Book wrong? <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 solution<BR>as the appendix in the book.<BR><BR>However, there is one thing that makes me wonder about your 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 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 what <BR>options the standard function modules give you) you will have to loop<BR>over every date in the range and check if it is a working day or 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 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: <A href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A><BR>> > [mailto: <A
href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A>] On Behalf Of<BR>> > <A href="mailto:Paul.Bakker@osr.treasury.qld.gov.au">Paul.Bakker@osr.treasury.qld.gov.au</A><BR>> > Sent: 28. september 2006 09:13 <BR>> > To: <A href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A><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>> > <A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR>> > <A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A> <BR>> ><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 of <BR>the<BR>information or copying of this message is prohibited. If you are not 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><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR>_______________________________________________ <BR>SAP-WUG mailing list<BR><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></BLOCKQUOTE></DIV><BR>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR></BLOCKQUOTE><BR><p> 
<hr size=1>Get your own <a href=" http://us.rd.yahoo.com/evt=43290/*http://smallbusiness.yahoo.com/domains"
>web address for just $1.99/1st yr</a>. We'll help. <a href="http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/"
>Yahoo! Small Business</a>.