When, during the save sequence, the RAP BO runtime triggers the save( ) method of the saver class, the implementation of this class triggers the copying of the application buffer content to the database.

 

The Save Sequence

Methods of the Saver Class and the Save Sequence

 

As well as the mandatory FOR SAVE method, you can define and implement several other methods in the local saver class. They are executed in a given sequence during the save phase, that is, after at least one successful modification was performed during the interaction phase.

 

The save sequence starts with finalize( ) performing the final calculations before data can be persisted. If the subsequent check_before_save( ) call is positive for all transactional changes, the point-of-no-return is reached. From now on, a successful save( ) is guaranteed by all involved BOs. After the point-of-no-return, the adjust_numbers( ) call can occur to take care of late numbering. The save( ) call persists all BO instance data from the transactional buffer in the database. The final cleanup( ) call resets the transactional buffer.