We have added search box. Key in SAP issue keyword to search
Home
About
Site Archive
SAP Chat
Contact
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

Re: [sap-dev] Is Long text complete after update task

Posted by Admin at
Share this post:
 Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

0 Comments

Posted by Sergey Korolev (Independent ABAP developer)
on Apr 28 at 10:29 AM 		Mark this reply as helpfulMark as helpful
Neal,

You should issue SET UPDATE TASK LOCAL before any CALL ... IN UPDATE TASK.
In that case all CALLs with IN UPDATE TASK between SET statement and COMMIT
(or ROLLBACK) will be processed as local calls, no matter where the call is
(in subrouteine or in some function). It guarantees that all the DB updates
will be processed and all locks will be released by the time the program
executed COMMIT WORK.

On 28 April 2010 16:46, R. Neal Wilhite via sap-dev <
sap-dev@groups.ittoolbox.com> wrote:

> Posted by R. Neal Wilhite(Senior Project Manager)
> on Apr 28 at 8:53 AM
> Sergey,
>
> The documentation is not clear. I read about "SET UPDATE TASK LOCAL" but
> can not tell about it's scope. The "IN UPDATE TASK" is in an FM. Does the
> call to "SET UPDATE TASK LOCAL" have to be in that FM (it's an SAP FM). or
> does it apply to the whole FG or to the whole session?
>
> Neal
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: Sergey Korolev via sap-dev <sap-dev@Groups.ITtoolbox.com>
> To: R. Neal Wilhite <wilhiten@aol.com>
> Sent: Tue, Apr 27, 2010 11:53 am
> Subject: Re: [sap-dev] Is Long text complete after update task
>
>
>
>
>
>
>
>
> Posted by Sergey Korolev (Independent ABAP developer)
> on Apr 27 at 11:51 AM
> Mark as helpful
>
>
> Neal,
>
> To ensure everything is saved synchronously you can issue SET UPDATE TASK
> LOCAL before changing the long text. In that case all update FM are called
> locally, in the same task not in the update task.
>
> On 27 April 2010 19:24, sapwes via sap-dev <sap-dev@groups.ittoolbox.com>wrote:
>
>
> > Posted by sapwes(Jack)
> > on Apr 27 at 11:25 AM
> > Neal:
> > one design constraint here is how critical is the lag to your RFC system.
>
> > If the lag needs to be really short you'll need to find a way to wait for
>
> > confirmation that the update task has finished before calling the
> publish.
> > If the lag can be longer perhaps you could schedule the publish as a
> > delayed update task as well.
> > You probably already thought of this, but its my two cents.
> > Wes
> >
> >
> > ---------------Original Message---------------
> > From: R. Neal Wilhite
> > Sent: Tuesday, April 27, 2010 10:53 AM
> > Subject: Is Long text complete after update task
> >
> > > Hi All,
> > >
> > > This is in ECC6.
> > >
> > > We store a lot of critical data in long text. We also work on an
> external
> > WMS so deliveries have to be RFC'd from SAP to the WMS. We are using
> > gi_badi_delivery->save_and_publish_document to call our RFC from. However
> in
> > Commit_text, the text is commited in update task. So sometimes the RFC
> can
> > see the long text and sometimes it isn't there yet.
> > >
> > > I thought about locks. SAP does not appear to have implemented any that
> I
> > can find on long texts. Additionally, to get a user defined lock to work,
>
> > I'd have to enqueue outside of the update task and dequeue on the inside
> of
> > the update task at the end. That worries me... It's extremely invasive.
> > >
> > > Any thoughts out there?
> > >
> > > Neal
__.____._
Copyright © 2010 Toolbox.com and message author.

Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
Sergey Korolev
SAP Development Enthusiast

Contributed 100 posts in a group to earn a Bronze Achievement
_.____.__

 

0 comments:

Post a Comment

Post a Comment

Subscribe to: Post Comments (Atom)

T r a n s l a t e to your language