RE:[sap-dev] Is Long text complete after update task
Posted by
Admin at
|
Share this post:
|
|
0 Comments
 | Posted by sapwes (Jack) on Apr 27 at 11:25 AM |  Mark as helpful |
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
__.____._ 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
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
sapwesSAP Development Helper
Posted helpful replies on 5 threads in a group to earn a Bronze Achievement
Related Content
In the Spotlight
White Papers
In the Spotlight
Your SAP Security is at Risk...Learn How to Stay Protected. Read the free white paper from SenSage
View this thread online
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
Manage group e-mails
Create an FAQ on this topic
Tell us what you think
Unsubscribe from discussion
_.____.__ 
