Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from TerryB on Jul 2 at 1:31 PM I respectfully disagree with Ralph. COMMIT WORK should be used when appropriate to collect a group of database commands into a "logical unit of work" (LUW). One of the primary purposes of the LUW is to make sure that ALL data for a particular document get saved to the database, or, in the case of some error, that NONE of the data for that particular document get saved to the database. This is one of the pillars of "referential integrity."
Cheers,
TerryB
| | | ---------------Original Message---------------
From: Pierre Richer
Sent: Wednesday, June 27, 2012 3:31 PM
Subject: SAP Buffering Table
Hi Gurus,
Have you ever encountered a situation where in a job a program update a fully buffered table (with a commit work and wait) and 40 seconds later, a BW Extractor is called in wich there is a user-exit that is called. This user-exit reads the updated records but gets the old value for the first pass, not the recently updated one.
The extractor is called many times because of the package size so all subsequent passes are ok. I assumed that the buffer has been refresh between the first pass and the second one.
I changed the select clause in the user-exit by adding the "bypassing buffer" option.
Basis guy told me that the buffer refresh rate was set to 120 seconds and it is the SAP standard. What do you think about that ? Do you that by adding "bypassing buffer" is sufficient? |
| Reply to this email to post your response. __.____._ |   _.____.__ |
