Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from jeansagi on Mar 18 at 5:46 PM Looks like the second approach might be the choice adding the option of
commit after n reservations had been processed.
J.
| | | ---------------Original Message---------------
From: Pierre Richer
Sent: Monday, March 18, 2013 1:50 PM
Subject: Mass Delete of Reservations Using BAPI_RESERVATION_CHANGE
Hi Jean,
First of all, I think 1 Million records for a commit is too much (redo log
limits). Split your load in batches of n records (like the package
concept) for the second concept.
Your first approach is far from being efficient but safe. First step in
your program is to select Undeleted Reservations. In fact, a million
commit is heavy. But if time does not matter, run it in a batch job and
it will run for a long time. The program skips the Reservation that could
not be deleted (lock by other), no abend. Rerun the job until no more
reservations are to be deleted (no record selected).
In the other hand, your second approach is more efficient but split in
batches. Skip only batches for those a commit could not be done. Run it
in background during night when nobody is logged in...or rerun until no
more records are to be deleted.
In both ways, you can execute many jobs at the same time with different
ranges of Reservation number.
Pierre |
| Reply to this email to post your response. __.____._ |   _.____.__ |
