SWU_OBUF

[kaukabr@yahoo.com]

Hello Manish:
That's very true. When ever you develop a new stuff in
workflow and Activate, come back and call this
transaction SWU_OBUF to clear the buffers. And if you
constructing lots of functionalities every day or you
creating workflows everyday submit this program for
background job to run once in a day. So your workflows
won't hang around and effects systematically. And just
take this program out from background job so that you
don't run in Production.
My Regards,
Aziz

--- "Khanna, Manish" <manish.khanna at amd.com> wrote:

> Thanks Aziz. 
> 
> This means following are true 
> 
> 1. Every midnight some process is run to synchronize
> SAP buffers. As
> Jocelyn mentioned SAP runs some HR function.
> 2. New/Updated WF definitions that are transported
> earlier in day get
> activated only after the SYNC process (at midnight)
> 
> Regards,
> Manish
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of kaukabr at yahoo.com
> Sent: Thursday, June 29, 2006 9:40 PM
> To: SAP Workflow Users' Group
> Subject: RE: SWU_OBUF
> 
> Hello Manish:
> Here is the RHWFINDEXRESET THIS PROGRAM IS OF THE
> TRANSACTION SWU_OBUF, WHAT IT DOES IT SYNCHRONIZE
> THE
> WORKFLOW BUFFERS.
> I hope this what you are looking for.
> Regards,
> AZIZ
> --- "Khanna, Manish" <manish.khanna at amd.com> wrote:
> 
> > Thanks Jocelyn for the explanation.
> > 
> >  
> > 
> > However I too have always observed that
> new/updated
> > WF definitions (sent
> > through transports) are activated only after
> > midnight. Till now I had an
> > understanding that this is due to some buffer sync
> > process running at
> > midnight everyday. 
> > 
> >  
> > 
> > However I would like to get rid of this assumption
> > if it is not correct.
> > Please advice.
> > 
> >  
> > 
> > Regards,
> > 
> > Manish
> > 
> >  
> > 
> > ________________________________
> > 
> > From: sap-wug-bounces at mit.edu
> > [mailto:sap-wug-bounces at mit.edu] On Behalf
> > Of Dart, Jocelyn
> > Sent: Thursday, June 29, 2006 11:22 AM
> > To: SAP Workflow Users' Group
> > Subject: RE: SWU_OBUF
> > 
> >  
> > 
> > No this transaction is not run at midnight - the
> HR
> > system runs an
> > equivalent function.
> > 
> >  
> > 
> > Try function module RH_SWWUSERWI_TIMESTAMP_RESET 
> > 
> >  
> > 
> > You might be able to put it in an after transport
> > method for the
> > relevant tables. 
> > 
> >  
> > 
> >  
> > 
> > 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 <http://www.sap.com/>  
> > 
> > The information contained in or attached to this
> > electronic transmission
> > is confidential and may be legally privileged. It
> is
> > intended only for
> > the person or entity to which it is addressed. If
> > you are not the
> > intended recipient, you are hereby notified that
> any
> > distribution,
> > copying, review, retransmission, dissemination or
> > other use of this
> > electronic transmission or the information
> contained
> > in it is strictly
> > prohibited. If you have received this electronic
> > transmission in error,
> > please immediately contact the sender to arrange
> for
> > the return of the
> > original documents. 
> > 
> > Electronic transmission cannot be guaranteed to be
> > secure and
> > accordingly, the sender does not accept liability
> > for any such data
> > corruption, interception, unauthorized amendment,
> > viruses, delays or the
> > consequences thereof.
> > 
> > Any views expressed in this electronic
> transmission
> > are those of the
> > individual sender, except where the message states
> > otherwise and the
> > sender is authorized to state them to be the views
> > of SAP AG or any of
> > its subsidiaries. SAP AG, its subsidiaries, and
> > their directors,
> > officers and employees make no representation nor
> > accept any liability
> > for the accuracy or completeness of the views or
> > information contained
> > herein. Please be aware that the furnishing of any
> > pricing information/
> > business proposal herein is indicative only, is
> > subject to change and
> > shall not be construed as an offer or as
> > constituting a binding
> > agreement on the part of SAP AG or any of its
> > subsidiaries to enter into
> > any relationship, unless otherwise expressly
> stated.
> > 
> > 
> >  
> > 
> >  
> > 
> > ________________________________
> > 
> > From: sap-wug-bounces at mit.edu
> > [mailto:sap-wug-bounces at mit.edu] On Behalf
> > Of Nietz, Karl K
> > Sent: Thursday, 29 June 2006 3:39 PM
> > To: sap-wug at mit.edu
> > Subject: SWU_OBUF
> > 
> > Hi, 
> > 
> > This transaction is run at midnight in every
> system
> > to refresh workflow
> > buffers.  However, we need to run it immediately
> > after our transports in
> > order to avoid integrity confilicts between
> > workflows templates and
> > tasks.
> > 
> > We can't find the job that submits this
> transaction
> > at midnight, so is
> > anybody aware of a jobname or program name that we
> > can schedule to
> > automatically execute it at the complete of our
> > transports.  Otherwise
> > we would have to create a BDC session to achieve
> the
> > result.
> > 
> > Thanks. 
> > 
> > Karl Nietz
> > GSAP Workflow Team Leader
> > Melbourne
> > 
> > This message and any attached files may contain
> > information that is
> > confidential and/or subject of legal privilege
> 
=== message truncated ===