Saving Changed Values 

If you save your data in a BW-integrated planning application, the system persists the data changed since the last save on the database. The changes to the data are posted, not the absolute values.

Logging Saved Values

You can use BAdI BADI_RSPLS_LOGGING_ON_SAVE from enhancement spot RSPLS_LOGGING_ON_SAVE to log data saved in a BW-integrated planning application. This logging can be implemented for real-time InfoCubes.

The BAdI is filter-dependent. Create an implementation of the interface IF_RSPLS_LOGGING_ON_SAVE for every real-time InfoCube that you want to log.

Methods log_defined and log_structure are used to specify whether or in which format the data is provided. In method log_structure, you can specify that context information about the name of the writing user, the date, the time and the SAVE ID are displayed using special InfoObjects in the DDIC structure. Using the SAVE-ID you can identify a ‘save’ action in a planning application.

If a user saves data three times in a planning application and describes two real-time InfoCubes while logging is active for both InfoCubes for example, the system therefore creates the three SAVE-IDs. These IDs can be passed to both logging calls of the two InfoCubes, if required. You can therefore identify in the logs of the two InfoCubes, which data from InfoCube1 was saved together with which data from InfoCube2.

Methods log_write calls the actual logging for every ‘Save’ event in the application that transfers the data in the structure specified for log_structure. The actual logging is implemented in method log_write. In other words, the data is written to a transparent table. Besides the data, the request ID of the real-time InfoCube (where the data is saved) is also passed to the method log_write.

The methods in this interface are described in detail in the interface documentation (see Class Builder, transaction SE24).

You can use statistics events 50098 and 50099 to measure the processing times (see Overview of Statistics Events (Table RSDDSTATEVENTS)).

Checking Data Before Saving with a Planning Sequence

To prevent users in a planning application from saving invalid changed data, you can run a report. For every “Save” event for a specific real time-enabled InfoProvider, this report ensures that a specific planning sequence runs, thus checking the data in this InfoProvider.

...

       1.      To use this function, call ABAP Editor (transaction SE38) and run report RSPLS_PLSEQ_MAINTAIN.

       2.      Enter the required InfoProvider. You can use input help for this.

       3.      Enter the planning sequence that checks the data to be saved for this InfoProvider. You can use input help for this.

       4.      In the default setting, Only Process Changed Records is selected.

       5.      Enter an aggregation level as the Delta Determination level. 

If the planning sequence reports an error, the data will not be saved.