Issue with shopping cart not reaching subsequent approver
Stéphane Bailleul
bailleul_s at hotmail.com
Thu Oct 5 04:16:34 EDT 2006
Hi Richard,
What is the workflow log saying ?
Does your workflow status indicate an error ( not in BBP_PD but in SWI6)
Otherwise when you are testing your BADI directly with the shopping cart do you have all the approvers in it ?Cheers
Stephane
> From: sap-wug-request at mit.edu> Subject: SAP-WUG Digest, Vol 23, Issue 8> To: sap-wug at mit.edu> Date: Wed, 4 Oct 2006 21:51:14 -0400> > 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. Issue with shopping cart not reaching subsequent approver> (Smart, Richard )> 2. RE: Deadlines based on factory calendar - is The Book wrong?> (Dart, Jocelyn)> 3. RE: Deadlines based on factory calendar - is The Book wrong?> (Paul.Bakker at osr.treasury.qld.gov.au)> > > ----------------------------------------------------------------------> > Message: 1> Date: Wed, 4 Oct 2006 13:09:34 -0500> From: "Smart, Richard " <Richard.Smart at Honeywell.com>> Subject: Issue with shopping cart not reaching subsequent approver> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> Message-ID:> <C8C2AFE688BA2445ADF7302790EFE96F6E0646 at MN65EV801.global.ds.honeywell.com>> > Content-Type: text/plain; charset="us-ascii"> > Hi,> > I have a question on the N-step line item approval of shopping cart> workflow (WS14500015 - BADI BBP_WFL_APPROV_BADI). This workflow has been> working fine in DEV. Today I noticed a problem in that if an item has> more than 1 approver the SC will go to the first approver who approves> it. It then never appears in the 2nd approvers inbox. Despite this the> approval preview looks fine. It indicates that the item has been> approved by the first approver and that it is awaiting approval from the> 2nd approver - the 2nd approver just never gets it.> > > > Any ideas?> > > > We're on SRM 4.0 SAPKB64016.> > > > Thanks> > Richard> > > > -------------- next part --------------> An HTML attachment was scrubbed...> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061004/9aca4cca/attachment-0001.htm> > ------------------------------> > Message: 2> Date: Thu, 5 Oct 2006 09:20:43 +0800> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>> Subject: RE: Deadlines based on factory calendar - is The Book wrong?> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> Message-ID:> <F843AF000027394A9F3D3194109269F49846E2 at sgsine11.sin.sap.corp>> Content-Type: text/plain; charset="us-ascii"> > Hi Folks, > The Book wrong??? !!! Say it isn't so! ;-)> > No seriously folks this one definitely works. > There are a couple of different ways of coding it but all should end up> using fm END_TIME_DETERMINE which does count up the working days from> your base date/time. > > Things that sometimes can go wrong on site are:> * You aren't passing a factory calendar id or aren't passing the correct> factory calendar id> * Your factory calendar doesn't exist - or doesn't extend to the dates> you are using - default approach is usually to try again without factory> calendar> * Ditto for the holiday calendar linked to your factory calendar> * Your baseline date/time is wrong - e.g. the date/time passed in is> from the wrong timezone - remember the baseline date/time needs to be> based on the work being done - not the agents doing it> > If you want to pass in a specific start date/time rather than use> today's date/time that's fine of course - you would simply need to> extend the solution in the book a little further. > > You should not have to write your own code unless you don't want to use> a factory calendar at all - e.g. if you only have a holiday calendar (in> which case you are on your own...).> > And yes if you want to calculate long deadlines based on working days -> 60 days is more effective than 2 months. > > Oh and if you have to work out an "early" deadline - i.e. number of days> BEFORE a certain date, then use fm START_TIME_DETERMINE. Works a treat.> > 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. > > > -----Original Message-----> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf> Of Mike Pokraka> Sent: Tuesday, 03 October 2006 6:37 PM> To: SAP Workflow Users' Group> Subject: Re: Deadlines based on factory calendar - is The Book wrong?> > Got onto a system and grabbed a quick moment to test it:> > FM END_TIME_DETERMINE, offset 5 unit TAG (day), fcal 99 (International):> 5 days from now is Sunday 8-Oct. The FM correctly spits out Tuesday> 10-Oct, which is NOT simply the next working day.> Today -2 days is Sunday 1-Oct, it returns Friday 29-Sep.> > The thing it doesn't do is factory time. Run it at 3am and it returns> 3am> of the correct day.> > Cheers,> Mike> > > On Tue, October 3, 2006 00:43, Mike Pokraka wrote:> > Huh? Confused is me. I think it's due to answering wugs late at night> as> > a distraction from the tedium of doing overdue stuff for the taxman.> > I don't have the book handy but I think I've based mine on the book> and> > it works.> > Maybe the book uses a different FM, I use END_TIME_DETERMINE and it> does> > the job for me. I think.> > The nice thing about the FM is it will also work backwards.> >> > Cheers,> > Mike> >> >> > Paul.Bakker at osr.treasury.qld.gov.au wrote:> >> Actually, I think you are missing something!> >>> >> The problem with the code in The Book is that if you specify a 3-day> >> deadline on a Friday, it will be triggered on the Monday. (It simply> >> adds 3> >> days, and then checks that Monday is a working day).> >>> >> It should instead be triggered on the Wednesday, because that is when> 3> >> full working days have elapsed.> >>> >> cheers> >> Paul> >>> >>> >>> >> |---------+------------------------------>> >> | | Mike Pokraka |> >> | | <asap at workflowconne|> >> | | ctions.com> |> >> | | Sent by: |> >> | | sap-wug-bounces at mit|> >> | | .edu |> >> | | |> >> | | |> >> | | 03/10/2006 08:23 |> >> | | Please respond to |> >> | | "SAP Workflow |> >> | | Users' Group" |> >> | | |> >> |---------+------------------------------>> >>> >-----------------------------------------------------------------------> ---------------------------------------------------|> >> |> >> |> >> | To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> >> |> >> | cc:> >> |> >> | Subject: Re: Deadlines based on factory calendar - is The> >> Book wrong? |> >>> >-----------------------------------------------------------------------> ---------------------------------------------------|> >>> >>> >>> >>> >> Hi Paul,> >> Perhaps I misunderstood, but I grasped it differently. What I got was> >> that factory calendars become less relevant as time goes on. You> might> >> as well specify 15 working days as three weeks / 21 days because an> >> extra day won't make much difference, as opposed to a 2 day deadline> >> kicking in on a task created on a Friday afternoon, giving the poor> >> bloke an hour to do his job.> >>> >> I've not had to trawl through working days either. The book and the> doc> >> Kjetil sent both refer to the same principle. Specify an offset and> the> >> deadline object gives you the end date in working days from TODAY. Do> >> not add anything, just plug the object attributes into the> expression.> >> So an instance of a deadline object with a key including an offset of> >> today+howevermanydaysuntilnextsaturday should have Monday in it's> >> DEADLINEDATE attribute.> >>> >> ....or am I missing something?> >>> >> Cheers,> >> Mike> >>> >> Paul.Bakker at osr.treasury.qld.gov.au wrote:> >>> WUG Experts,> >>>> >>> Thank you very much for all your valuable comments on the factory> >> calendar> >>> / deadline problem.> >>>> >>> I am going to go ahead and code the solution that was suggested :> >> increment> >>> one WORKING day at a time, until the deadline offset is reached. I> will> >>> share the code with you once it's bedded down.> >>>> >>> At first I didn't grasp the distinction that Kjetil made between> short> >> and> >>> long deadlines, but now I get it. A deadline specified in DAYs> should> >>> be> >>> interpreted as working days, whereas a deadline specified in MONTHS> or> >>> YEARS would not be.> >>>> >>> thanks again - this group is great!> >>> Paul> >>>> >>>> >>>> >>> |---------+---------------------------->> >>> | | "Kjetil Kilhavn" |> >>> | | <KJETILK at statoil.|> >>> | | com> |> >>> | | Sent by: |> >>> | | sap-wug-bounces at m|> >>> | | it.edu |> >>> | | |> >>> | | |> >>> | | 28/09/2006 18:30 |> >>> | | Please respond to|> >>> | | "SAP Workflow |> >>> | | Users' Group" |> >>> | | |> >>> |---------+---------------------------->> >>>> >>>> ------------------------------------------------------------------------> --------------------------------------------------|> >>> >>> |> >> |> >>> | To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> >> |> >>> | cc:> >> |> >>> | Subject: RE: Deadlines based on factory calendar - is The> >>> Book> >> wrong? |> >>>> ------------------------------------------------------------------------> --------------------------------------------------|> >>> >>>> >>>> >>>> >>> Hmmmm... I looked a little more at the code in the presentation> >>> (embedded text file), and it looks like it is exactly the same> solution> >>> as the appendix in the book.> >>>> >>> However, there is one thing that makes me wonder about your> >>> requirement.> >>> You say that not only should the deadline be a working day, but only> >>> working days should be taken into account. It may make some sense> for> >>> very short deadlines, e.g. a two-day deadline, but should a 15-day> >>> deadline be a three-week deadline? In the worst case (I don't know> what> >>> options the standard function modules give you) you will have to> loop> >>> over every date in the range and check if it is a working day or> not.> >>> --> >>> Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP> >>>> >>>> >>>> -----Original Message-----> >>>> From: Kjetil Kilhavn> >>>> Sent: 28. september 2006 10:14> >>>> To: 'SAP Workflow Users' Group'> >>>> Subject: RE: Deadlines based on factory calendar - is The Book> wrong?> >>>>> >>>> I think this has been discussed several times before (have> >>>> you searched the archives?) in this group, but I can't recall> >>>> if anyone has had quite the same requirements as you.> >>>>> >>>> I have attached a PDF file (can't remember where I got it,> >>>> whether it was in this group or perhaps on ASUG's site) with> >>>> another implementation, and a PowerPoint file with an> >>>> implementation that seems to be exactly what you want.> >>>>> >>>> If you find none of these match your needs than please create> >>>> the ultimate solution and share it with the rest of us.> >>>> --> >>>> Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP> >>>>> >>>>> >>>>> -----Original Message-----> >>>>> From: sap-wug-bounces at mit.edu> >>>>> [mailto:sap-wug-bounces at mit.edu] On Behalf Of> >>>>> Paul.Bakker at osr.treasury.qld.gov.au> >>>>> Sent: 28. september 2006 09:13> >>>>> To: sap-wug at mit.edu> >>>>> Subject: Deadlines based on factory calendar - is The Book wrong?> >>>>>> >>>>> Hello all,> >>>>>> >>>>> We have a requirement to calculate the deadline for a> >>>>> workitem (eg Latest> >>>>> Start) based on the Factory Calendar.> >>>>>> >>>>> For example, if the workitem was created on a Thursday and> >>>>> the 'Latest Start' deadline is +3 days, then it should be> >>>>> triggered on the following Tuesday (not Sunday). In other> >>>>> words, it should only take working days into account.> >>>>>> >>>>> Surprisingly, SAP standard does not cater for this scenario.> >>>>> I therefore implemented the solution suggested in the The> >>>>> Book, in Appendix A9. It shows you how to create a custom> >>>>> deadline object based on the factory calendar, and use the> >>>>> expression ZDEADLINE.DATE as the reference date in the step.> >>>>>> >>>>> Surprisingly (again), this solution DOES NOT work. Deadlines> >>>>> are triggered without taking weekends into account.> >>>>>> >>>>> When I had a closer look at it, I noticed that the Factory> >>>>> Calendar is only being used to determine the Workitem> >>>>> _Creation Date_; it is not being used to calculate the Latest> >>>>> Start Date. The book even seems to concede this:> >>>>>> >>>>> "Note that the reference date gives the date based on> >>>>> the factory calendar, but any offset will simply be added to> >>>>> the reference date as normal".> >>>>>> >>>>> If this really is the case, then what is the point of> >>>>> implementing this solution?> >>>>>> >>>>> Has anyone gotten it to work? I'm sure it must be me... sigh.> >>>>>> >>>>> cheers> >>>>> Paul> >>>>>> >>>>>> >>>>> **************************************************************> >>>>> **************************************************************> >>>>> **************************> >>>>>> >>>>> Only an individual or entity who is intended to be a> >>>>> recipient of this e-mail may access or use the information> >>>>> contained in this e-mail or any of its attachments. Opinions> >>>>> contained in this e-mail or any of its attachments do not> >>>>> necessarily reflect the opinions of Queensland Treasury.> >>>>>> >>>>> The contents of this e-mail and any attachments are> >>>>> confidential and may be legally privileged and the subject of> >>>>> copyright. If you have received this e-mail in error, please> >>>>> notify Queensland Treasury immediately and erase all copies> >>>>> of the e-mail and the attachments. Queensland Treasury uses> >>>>> virus scanning software. However, it is not liable for> >>>>> viruses present in this e-mail or in any attachment.> >>>>>> >>>>> **************************************************************> >>>>> **************************************************************> >>>>> **************************> >>>>>> >>>>> _______________________________________________> >>>>> SAP-WUG mailing list> >>>>> SAP-WUG at mit.edu> >>>>> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>>>>> >>>> >>> -------------------------------------------------------------------> >>> The information contained in this message may be CONFIDENTIAL and is> >>> intended for the addressee only. Any unauthorised use, dissemination> of> >> the> >>> information or copying of this message is prohibited. If you are not> >>> the> >>> addressee, please notify the sender immediately by return e-mail and> >> delete> >>> this message.> >>> Thank you.> >>>> >>> _______________________________________________> >>> SAP-WUG mailing list> >>> SAP-WUG at mit.edu> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>>> >>>> >>>> >>> _______________________________________________> >>> SAP-WUG mailing list> >>> SAP-WUG at mit.edu> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>> >> _______________________________________________> >> SAP-WUG mailing list> >> SAP-WUG at mit.edu> >> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>> >>> >>> >> _______________________________________________> >> SAP-WUG mailing list> >> SAP-WUG at mit.edu> >> http://mailman.mit.edu/mailman/listinfo/sap-wug> >> > _______________________________________________> > SAP-WUG mailing list> > SAP-WUG at mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >> > > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > > > ------------------------------> > Message: 3> Date: Thu, 5 Oct 2006 11:52:53 +1000> From: Paul.Bakker at osr.treasury.qld.gov.au> Subject: RE: Deadlines based on factory calendar - is The Book wrong?> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> Message-ID:> <OFFABF19CA.7804EE95-ON4A2571FE.000A18D1-4A2571FE.000A89F8 at treasury.qld.gov.au>> > Content-Type: text/plain; charset=US-ASCII> > Jocelyn,> > You are right - and the book is right! I was simply using the ZDeadline> objects the wrong way. Mike P set me straight on that.> > Apologies for the confusion. I'll never question The Book again :-)> > cheers> Paul> > > > > |---------+---------------------------->> | | "Dart, Jocelyn" |> | | <jocelyn.dart at sap|> | | .com> |> | | Sent by: |> | | sap-wug-bounces at m|> | | it.edu |> | | |> | | |> | | 05/10/2006 11:20 |> | | Please respond to|> | | "SAP Workflow |> | | Users' Group" |> | | |> |---------+---------------------------->> >--------------------------------------------------------------------------------------------------------------------------|> | |> | To: "SAP Workflow Users' Group" <sap-wug at mit.edu> |> | cc: |> | Subject: RE: Deadlines based on factory calendar - is The Book wrong? |> >--------------------------------------------------------------------------------------------------------------------------|> > > > > Hi Folks,> The Book wrong??? !!! Say it isn't so! ;-)> > No seriously folks this one definitely works.> There are a couple of different ways of coding it but all should end up> using fm END_TIME_DETERMINE which does count up the working days from> your base date/time.> > Things that sometimes can go wrong on site are:> * You aren't passing a factory calendar id or aren't passing the correct> factory calendar id> * Your factory calendar doesn't exist - or doesn't extend to the dates> you are using - default approach is usually to try again without factory> calendar> * Ditto for the holiday calendar linked to your factory calendar> * Your baseline date/time is wrong - e.g. the date/time passed in is> from the wrong timezone - remember the baseline date/time needs to be> based on the work being done - not the agents doing it> > If you want to pass in a specific start date/time rather than use> today's date/time that's fine of course - you would simply need to> extend the solution in the book a little further.> > You should not have to write your own code unless you don't want to use> a factory calendar at all - e.g. if you only have a holiday calendar (in> which case you are on your own...).> > And yes if you want to calculate long deadlines based on working days -> 60 days is more effective than 2 months.> > Oh and if you have to work out an "early" deadline - i.e. number of days> BEFORE a certain date, then use fm START_TIME_DETERMINE. Works a treat.> > 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.> > > -----Original Message-----> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf> Of Mike Pokraka> Sent: Tuesday, 03 October 2006 6:37 PM> To: SAP Workflow Users' Group> Subject: Re: Deadlines based on factory calendar - is The Book wrong?> > Got onto a system and grabbed a quick moment to test it:> > FM END_TIME_DETERMINE, offset 5 unit TAG (day), fcal 99 (International):> 5 days from now is Sunday 8-Oct. The FM correctly spits out Tuesday> 10-Oct, which is NOT simply the next working day.> Today -2 days is Sunday 1-Oct, it returns Friday 29-Sep.> > The thing it doesn't do is factory time. Run it at 3am and it returns> 3am> of the correct day.> > Cheers,> Mike> > > On Tue, October 3, 2006 00:43, Mike Pokraka wrote:> > Huh? Confused is me. I think it's due to answering wugs late at night> as> > a distraction from the tedium of doing overdue stuff for the taxman.> > I don't have the book handy but I think I've based mine on the book> and> > it works.> > Maybe the book uses a different FM, I use END_TIME_DETERMINE and it> does> > the job for me. I think.> > The nice thing about the FM is it will also work backwards.> >> > Cheers,> > Mike> >> >> > Paul.Bakker at osr.treasury.qld.gov.au wrote:> >> Actually, I think you are missing something!> >>> >> The problem with the code in The Book is that if you specify a 3-day> >> deadline on a Friday, it will be triggered on the Monday. (It simply> >> adds 3> >> days, and then checks that Monday is a working day).> >>> >> It should instead be triggered on the Wednesday, because that is when> 3> >> full working days have elapsed.> >>> >> cheers> >> Paul> >>> >>> >>> >> |---------+------------------------------>> >> | | Mike Pokraka |> >> | | <asap at workflowconne|> >> | | ctions.com> |> >> | | Sent by: |> >> | | sap-wug-bounces at mit|> >> | | .edu |> >> | | |> >> | | |> >> | | 03/10/2006 08:23 |> >> | | Please respond to |> >> | | "SAP Workflow |> >> | | Users' Group" |> >> | | |> >> |---------+------------------------------>> >>> >-----------------------------------------------------------------------> ---------------------------------------------------|> >> |> >> |> >> | To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> >> |> >> | cc:> >> |> >> | Subject: Re: Deadlines based on factory calendar - is The> >> Book wrong? |> >>> >-----------------------------------------------------------------------> ---------------------------------------------------|> >>> >>> >>> >>> >> Hi Paul,> >> Perhaps I misunderstood, but I grasped it differently. What I got was> >> that factory calendars become less relevant as time goes on. You> might> >> as well specify 15 working days as three weeks / 21 days because an> >> extra day won't make much difference, as opposed to a 2 day deadline> >> kicking in on a task created on a Friday afternoon, giving the poor> >> bloke an hour to do his job.> >>> >> I've not had to trawl through working days either. The book and the> doc> >> Kjetil sent both refer to the same principle. Specify an offset and> the> >> deadline object gives you the end date in working days from TODAY. Do> >> not add anything, just plug the object attributes into the> expression.> >> So an instance of a deadline object with a key including an offset of> >> today+howevermanydaysuntilnextsaturday should have Monday in it's> >> DEADLINEDATE attribute.> >>> >> ....or am I missing something?> >>> >> Cheers,> >> Mike> >>> >> Paul.Bakker at osr.treasury.qld.gov.au wrote:> >>> WUG Experts,> >>>> >>> Thank you very much for all your valuable comments on the factory> >> calendar> >>> / deadline problem.> >>>> >>> I am going to go ahead and code the solution that was suggested :> >> increment> >>> one WORKING day at a time, until the deadline offset is reached. I> will> >>> share the code with you once it's bedded down.> >>>> >>> At first I didn't grasp the distinction that Kjetil made between> short> >> and> >>> long deadlines, but now I get it. A deadline specified in DAYs> should> >>> be> >>> interpreted as working days, whereas a deadline specified in MONTHS> or> >>> YEARS would not be.> >>>> >>> thanks again - this group is great!> >>> Paul> >>>> >>>> >>>> >>> |---------+---------------------------->> >>> | | "Kjetil Kilhavn" |> >>> | | <KJETILK at statoil.|> >>> | | com> |> >>> | | Sent by: |> >>> | | sap-wug-bounces at m|> >>> | | it.edu |> >>> | | |> >>> | | |> >>> | | 28/09/2006 18:30 |> >>> | | Please respond to|> >>> | | "SAP Workflow |> >>> | | Users' Group" |> >>> | | |> >>> |---------+---------------------------->> >>>> >>>> ------------------------------------------------------------------------> --------------------------------------------------|> >>> >>> |> >> |> >>> | To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> >> |> >>> | cc:> >> |> >>> | Subject: RE: Deadlines based on factory calendar - is The> >>> Book> >> wrong? |> >>>> ------------------------------------------------------------------------> --------------------------------------------------|> >>> >>>> >>>> >>>> >>> Hmmmm... I looked a little more at the code in the presentation> >>> (embedded text file), and it looks like it is exactly the same> solution> >>> as the appendix in the book.> >>>> >>> However, there is one thing that makes me wonder about your> >>> requirement.> >>> You say that not only should the deadline be a working day, but only> >>> working days should be taken into account. It may make some sense> for> >>> very short deadlines, e.g. a two-day deadline, but should a 15-day> >>> deadline be a three-week deadline? In the worst case (I don't know> what> >>> options the standard function modules give you) you will have to> loop> >>> over every date in the range and check if it is a working day or> not.> >>> --> >>> Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP> >>>> >>>> >>>> -----Original Message-----> >>>> From: Kjetil Kilhavn> >>>> Sent: 28. september 2006 10:14> >>>> To: 'SAP Workflow Users' Group'> >>>> Subject: RE: Deadlines based on factory calendar - is The Book> wrong?> >>>>> >>>> I think this has been discussed several times before (have> >>>> you searched the archives?) in this group, but I can't recall> >>>> if anyone has had quite the same requirements as you.> >>>>> >>>> I have attached a PDF file (can't remember where I got it,> >>>> whether it was in this group or perhaps on ASUG's site) with> >>>> another implementation, and a PowerPoint file with an> >>>> implementation that seems to be exactly what you want.> >>>>> >>>> If you find none of these match your needs than please create> >>>> the ultimate solution and share it with the rest of us.> >>>> --> >>>> Kjetil Kilhavn, Statoil OFT GBS BAS DEV SAP> >>>>> >>>>> >>>>> -----Original Message-----> >>>>> From: sap-wug-bounces at mit.edu> >>>>> [mailto:sap-wug-bounces at mit.edu] On Behalf Of> >>>>> Paul.Bakker at osr.treasury.qld.gov.au> >>>>> Sent: 28. september 2006 09:13> >>>>> To: sap-wug at mit.edu> >>>>> Subject: Deadlines based on factory calendar - is The Book wrong?> >>>>>> >>>>> Hello all,> >>>>>> >>>>> We have a requirement to calculate the deadline for a> >>>>> workitem (eg Latest> >>>>> Start) based on the Factory Calendar.> >>>>>> >>>>> For example, if the workitem was created on a Thursday and> >>>>> the 'Latest Start' deadline is +3 days, then it should be> >>>>> triggered on the following Tuesday (not Sunday). In other> >>>>> words, it should only take working days into account.> >>>>>> >>>>> Surprisingly, SAP standard does not cater for this scenario.> >>>>> I therefore implemented the solution suggested in the The> >>>>> Book, in Appendix A9. It shows you how to create a custom> >>>>> deadline object based on the factory calendar, and use the> >>>>> expression ZDEADLINE.DATE as the reference date in the step.> >>>>>> >>>>> Surprisingly (again), this solution DOES NOT work. Deadlines> >>>>> are triggered without taking weekends into account.> >>>>>> >>>>> When I had a closer look at it, I noticed that the Factory> >>>>> Calendar is only being used to determine the Workitem> >>>>> _Creation Date_; it is not being used to calculate the Latest> >>>>> Start Date. The book even seems to concede this:> >>>>>> >>>>> "Note that the reference date gives the date based on> >>>>> the factory calendar, but any offset will simply be added to> >>>>> the reference date as normal".> >>>>>> >>>>> If this really is the case, then what is the point of> >>>>> implementing this solution?> >>>>>> >>>>> Has anyone gotten it to work? I'm sure it must be me... sigh.> >>>>>> >>>>> cheers> >>>>> Paul> >>>>>> >>>>>> >>>>> **************************************************************> >>>>> **************************************************************> >>>>> **************************> >>>>>> >>>>> Only an individual or entity who is intended to be a> >>>>> recipient of this e-mail may access or use the information> >>>>> contained in this e-mail or any of its attachments. Opinions> >>>>> contained in this e-mail or any of its attachments do not> >>>>> necessarily reflect the opinions of Queensland Treasury.> >>>>>> >>>>> The contents of this e-mail and any attachments are> >>>>> confidential and may be legally privileged and the subject of> >>>>> copyright. If you have received this e-mail in error, please> >>>>> notify Queensland Treasury immediately and erase all copies> >>>>> of the e-mail and the attachments. Queensland Treasury uses> >>>>> virus scanning software. However, it is not liable for> >>>>> viruses present in this e-mail or in any attachment.> >>>>>> >>>>> **************************************************************> >>>>> **************************************************************> >>>>> **************************> >>>>>> >>>>> _______________________________________________> >>>>> SAP-WUG mailing list> >>>>> SAP-WUG at mit.edu> >>>>> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>>>>> >>>> >>> -------------------------------------------------------------------> >>> The information contained in this message may be CONFIDENTIAL and is> >>> intended for the addressee only. Any unauthorised use, dissemination> of> >> the> >>> information or copying of this message is prohibited. If you are not> >>> the> >>> addressee, please notify the sender immediately by return e-mail and> >> delete> >>> this message.> >>> Thank you.> >>>> >>> _______________________________________________> >>> SAP-WUG mailing list> >>> SAP-WUG at mit.edu> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>>> >>>> >>>> >>> _______________________________________________> >>> SAP-WUG mailing list> >>> SAP-WUG at mit.edu> >>> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>> >> _______________________________________________> >> SAP-WUG mailing list> >> SAP-WUG at mit.edu> >> http://mailman.mit.edu/mailman/listinfo/sap-wug> >>> >>> >>> >> _______________________________________________> >> SAP-WUG mailing list> >> SAP-WUG at mit.edu> >> http://mailman.mit.edu/mailman/listinfo/sap-wug> >> > _______________________________________________> > SAP-WUG mailing list> > SAP-WUG at mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >> > > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > > > > > ------------------------------> > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > > End of SAP-WUG Digest, Vol 23, Issue 8> **************************************
_________________________________________________________________
Appelez vos amis de PC à PC -- C'EST GRATUIT
http://get.live.com/messenger/overview
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20061005/c811ec59/attachment.htm
More information about the SAP-WUG
mailing list