Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from lizard_rgm on Jul 3 at 2:37 AM Yer I thought some would not like what I said, and i agree that integrity is critical, and that's why you should not use explicit commits, leave it up to the system auto commits and you will have 100% referential integrity. Do your own and then all of a sudden only half your update rolls back one day and your searching for all your commits to remove them.
o yer - one more place to put a commit is when your using IDOCS, as you can't roll back an idoc send, SAP expects you to "commit work" to initiate the send.
:-)
Regards, Ralph McKnight
| | | ---------------Original Message---------------
From: Terry Barker
Sent: Monday, July 02, 2012 1:32 PM
Subject: SAP Buffering Table
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 |
| Reply to this email to post your response. __.____._ |   _.____.__ |
