<div>Hi Sanjay,</div>
<div> </div>
<div>Try to use tocde SWU_OBUF for buffer refresh for SAP workflow.</div>
<div> </div>
<div>Regards,</div>
<div>Chandrasekhar<br><br></div>
<div class="gmail_quote">On Wed, Jun 6, 2012 at 10:54 PM, Guru Dutt <span dir="ltr"><<a href="mailto:gurudutt.sap@gmail.com" target="_blank">gurudutt.sap@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<p>Hi Sanjay,</p>
<p>There are two measures which you can perform in your QA system:</p>
<p>1) check QA's SWU3 configs are properly defined or not.</p>
<p>2) you can re-activate event linkage inDEV and transport into QA.</p>
<p>Hope this will solve your problem.</p>
<p>Regards,<br>Guru</p>
<div class="gmail_quote">On Jun 6, 2012 5:55 PM, <<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>> wrote:<br type="attribution">
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">Send SAP-WUG mailing list submissions to<br> <a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a><br>
<br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a><br><br>You can reach the person managing the list at<br> <a href="mailto:sap-wug-owner@mit.edu" target="_blank">sap-wug-owner@mit.edu</a><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. Re: Buffer problem in SAP Workflow (Arghadip)<br><br>
<br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 5 Jun 2012 13:52:43 -0500<br>From: Arghadip <<a href="mailto:arghadip.kar@gmail.com" target="_blank">arghadip.kar@gmail.com</a>><br>
Subject: Re: Buffer problem in SAP Workflow<br>To: "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>><br>Message-ID:<br> <<a href="mailto:CAN7b8eKFyFy9ZjL8cEWN7%2Byvw7SUGkT_twbOQjsFB6O93KmRWg@mail.gmail.com" target="_blank">CAN7b8eKFyFy9ZjL8cEWN7+yvw7SUGkT_twbOQjsFB6O93KmRWg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br><br>Hi Sanjay<br><br>It seems this is a CRM system. I think I will ask you to debug and may be<br>check where that partcular message is throwing up. I do not have a CRM<br>
system to check this.<br><br>Thanks<br>Arghadip<br><br>On Tue, Jun 5, 2012 at 9:24 AM, Sanjay9 P <<a href="mailto:sanjay9.p@tcs.com" target="_blank">sanjay9.p@tcs.com</a>> wrote:<br><br>> Hi,<br>><br>> It is also not working if I triggering the event manually through SWUE.<br>
> Same problem exists.<br>> Any other inputs...???<br>><br>> Thanks and regards,<br>> Sanjay<br>><br>> Sanjay Pal<br>> SAP Workflow Consultant<br>><br>> ____________________________________________<br>
> Experience certainty. IT Services<br>> Business Solutions<br>> Outsourcing<br>> ____________________________________________<br>><br>><br>><br>> From: Arghadip <<a href="mailto:arghadip.kar@gmail.com" target="_blank">arghadip.kar@gmail.com</a>> To:<br>
> "SAP Workflow Users' Group" <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>><br>> Date: 06/05/2012 06:07 PM Subject: Re: Buffer problem in SAP Workflow Sent<br>> by: <a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a><br>
> ------------------------------<br>><br>><br>><br>> Hi Sanjay<br>><br>> Please can you check to trigger the event manually through SWUE. If it<br>> gets trigger properly there might be Performamnce issue in your Business<br>
> object.<br>><br>> Thanks<br>> Arghadip<br>><br>> On Fri, May 25, 2012 at 11:26 AM, Sanjay9 P <*<a href="mailto:sanjay9.p@tcs.com" target="_blank">sanjay9.p@tcs.com</a>*<<a href="mailto:sanjay9.p@tcs.com" target="_blank">sanjay9.p@tcs.com</a>>><br>
> wrote:<br>> Hi Experts,<br>><br>> My custom workflow is not getting triggered in QA as because "*Entry not<br>> found in object buffe*r" in event trace. Please see the below screen shot.<br>> Following points should be noted.<br>
> 1. Check function module used<br>> 2. Event linkage maintained properly<br>> 3. All the objects are present in QA in activated status<br>> 4. Same workflow is working fine in DEV<br>><br>> Is there any idea why we are getting this message in QA ?<br>
><br>><br>><br>> Sanjay Pal<br>> SAP Workflow Consultant<br>> Tata Consultancy Services<br>> TCS, Unitech Hi-tech Structures Ltd.,<br>> IT/ITES SEZ, Block-G, Tower-G -III,<br>> Plot-DH01,DH02,DH03 & DH03/1, Action Area-I, New Town<br>
> Kolkata - 700156,West Bengal<br>> India<br>> Ph:- *<a href="tel:%2B91%2033%206636%201591" target="_blank" value="+913366361591">+91 33 6636 1591</a>* <%2B91%2033%206636%201591><br>> Buzz:- 1591<br>> Cell:- *9038701729* <9038701729><br>
> Mailto: *<a href="mailto:sanjay9.p@tcs.com" target="_blank">sanjay9.p@tcs.com</a>* <<a href="mailto:sanjay9.p@tcs.com" target="_blank">sanjay9.p@tcs.com</a>><br>> Website: *<a href="http://www.tcs.com/" target="_blank">http://www.tcs.com</a>* <<a href="http://www.tcs.com/" target="_blank">http://www.tcs.com/</a>><br>
> ____________________________________________<br>> Experience certainty. IT Services<br>> Business Solutions<br>> Outsourcing<br>> ____________________________________________<br>
><br>> From: Altaf <*<a href="mailto:rahaman.ma@gmail.com" target="_blank">rahaman.ma@gmail.com</a>* <<a href="mailto:rahaman.ma@gmail.com" target="_blank">rahaman.ma@gmail.com</a>>> To: "*<br>> <a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>* <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>>" <*<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>* <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>>><br>
> Cc: "*<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>* <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>>" <*<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>*<<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>><br>
> > Date: 05/25/2012 06:22 AM Subject: Re: SAP-WUG Digest, Vol 90, Issue<br>> 17 Sent by: *<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>* <<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a>><br>
><br>> ------------------------------<br>><br>><br>><br>> Hi,<br>><br>> For issue no 1 I will check the scenario and will post you.<br>> Issue no 2 you can set the confirm end processing at the task/step so<br>
> that even after execution of work item you can hold it, the workitem<br>> will be executed but will not be in completed status, you can re<br>> execute workitem later.<br>><br>> Regards,<br>> Altaf Mohammed*<br>
> **9703322553* <9703322553><br>><br>> On 24-May-2012, at 10:00 PM, *<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>*<<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>>wrote:<br>
><br>> > Send SAP-WUG mailing list submissions to<br>> > *<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>* <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>><br>
> ><br>> > To subscribe or unsubscribe via the World Wide Web, visit<br>> > *<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug*" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug*</a><<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>><br>
> > or, via email, send a message with subject or body 'help' to<br>> > *<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>* <<a href="mailto:sap-wug-request@mit.edu" target="_blank">sap-wug-request@mit.edu</a>><br>
> ><br>> > You can reach the person managing the list at<br>> > *<a href="mailto:sap-wug-owner@mit.edu" target="_blank">sap-wug-owner@mit.edu</a>* <<a href="mailto:sap-wug-owner@mit.edu" target="_blank">sap-wug-owner@mit.edu</a>><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. Problem while calling a standard SAP transaction inside<br>> > workflow (Srinivas Reddy)<br>> ><br>> ><br>> > ----------------------------------------------------------------------<br>
> ><br>> > Message: 1<br>> > Date: Thu, 24 May 2012 16:59:44 +0530<br>> > From: Srinivas Reddy <*<a href="mailto:ootasrinivasreddy@gmail.com" target="_blank">ootasrinivasreddy@gmail.com</a>*<<a href="mailto:ootasrinivasreddy@gmail.com" target="_blank">ootasrinivasreddy@gmail.com</a>><br>
> ><br>> > Subject: Problem while calling a standard SAP transaction inside<br>> > workflow<br>> > To: "SAP Workflow Users' Group" <*<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>* <<a href="mailto:sap-wug@mit.edu" target="_blank">sap-wug@mit.edu</a>>><br>
> > Message-ID:<br>> > <CAGu01YZ-<br>> > M5V9MPRfkpzFyDN8ri9Dnr=*<a href="mailto:CfEXebpx7fNP2axU8Cg@mail.gmail.com" target="_blank">CfEXebpx7fNP2axU8Cg@mail.gmail.com</a>*<<a href="mailto:CfEXebpx7fNP2axU8Cg@mail.gmail.com" target="_blank">CfEXebpx7fNP2axU8Cg@mail.gmail.com</a>><br>
> ><br>> > Content-Type: text/plain; charset="iso-8859-1"<br>> ><br>> > Hello Experts,<br>> ><br>> ><br>> ><br>> > I am facing a strange issue in my workflow development. The workflow<br>
> > will<br>> > be started after clicking on POST button in the standard transaction<br>> > MI04.<br>> > I have used the standard event created from the business object<br>> > BUS2028<br>> > for starting the workflow. After starting the workflow I am calling<br>
> > the<br>> > standard transaction MI07 in the very first step which will be sent<br>> > to the<br>> > approver. Once the approver clicks on POST an email will be sent and<br>> > the<br>> > document will be posted.<br>
> ><br>> ><br>> ><br>> > Issue 1) When the user manually goes into the SAP transaction MI07 ,<br>> > opens<br>> > a document and clicks on back, cancel or exit buttons. The<br>> > transaction is<br>
> > working as desired but the same thing when the same user does from<br>> > executing the work item the transaction is not working as desired. A<br>> > pop-up<br>> > screen with YES, NO and CANCEL buttons and also a message whether<br>
> > to SAVE<br>> > before exit is displayed. Even though if the user clicks on NO<br>> > button the<br>> > document is getting posted. No idea what is going wrong with the<br>> > method<br>> > calling the transaction MI07.<br>
> ><br>> > Issue 2) Once the users does this process. The work item is getting<br>> > completed. But the requirement is, work item should be available as<br>> > the<br>> > POSTING is not completed. Here how can I put the work item in ready<br>
> > status<br>> > after completeion. Once the users executes the work item the work<br>> > item is<br>> > getting disappeared.<br>> ><br>> ><br>> > Where am I doing wrong?<br>> ><br>
> > --<br>> > Thanks and Regards<br>> > Srini..<br>> > SAP Technical Consultant<br>> > *<a href="tel:%2B919963307464" target="_blank" value="+919963307464">+919963307464</a>* <%2B919963307464><br>
> > -------------- next part --------------<br>> > An HTML attachment was scrubbed...<br>> > URL: *<br>> <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120524/c5d65341/attachment-0001.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120524/c5d65341/attachment-0001.htm</a><br>
> *<<a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120524/c5d65341/attachment-0001.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120524/c5d65341/attachment-0001.htm</a>><br>
> ><br>> > ------------------------------<br>> ><br>> > _______________________________________________<br>> > SAP-WUG mailing list<br>> > *<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a>* <<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a>><br>
> > *<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug*" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug*</a><<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>><br>
> ><br>> ><br>> > End of SAP-WUG Digest, Vol 90, Issue 17<br>> > ***************************************<br>> _______________________________________________<br>> SAP-WUG mailing list*<br>> **<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a>* <<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a>>*<br>
> **<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug*" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug*</a><<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>><br>
><br>> =====-----=====-----=====<br>> Notice: The information contained in this e-mail<br>> message and/or attachments to it may contain<br>> confidential or privileged information. If you are<br>> not the intended recipient, any dissemination, use,<br>
> review, distribution, printing or copying of the<br>> information contained in this e-mail message<br>> and/or attachments to it are strictly prohibited. If<br>> you have received this communication in error,<br>
> please notify us by reply e-mail or telephone and<br>> immediately and permanently delete the message<br>> and any attachments. Thank you<br>><br>><br>> _______________________________________________<br>
> SAP-WUG mailing list*<br>> **<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a>* <<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a>>*<br>> **<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug*" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug*</a><<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>><br>
><br>> _______________________________________________<br>> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>><br>><br>> _______________________________________________<br>> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120605/736794aa/attachment.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120605/736794aa/attachment.htm</a><br>
-------------- next part --------------<br>A non-text attachment was scrubbed...<br>Name: not available<br>Type: image/gif<br>Size: 10629 bytes<br>Desc: not available<br>Url : <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120605/736794aa/attachment.gif" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120605/736794aa/attachment.gif</a><br>
<br>------------------------------<br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br><br>End of SAP-WUG Digest, Vol 91, Issue 8<br>**************************************<br></blockquote></div><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" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Thanks & Regards,<br>Chandrasekhar V<br>