Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM (Application Component) Warehouse Management⤷
RSIMG (Package) IMG Texts and Release Notes
IMG Activity
| ID | BW_BADI_PLA | Integrated Planning: Logging of Planning Data |
| Transaction Code | S_B4S_38000002 | (empty) |
| Created on | 20130926 | |
| Customizing Attributes | BW_BADI_PLA | Integrated Planning: Logging of Planning Data |
| Customizing Activity | BW_BADI_PLA | Integrated Planning: Logging of Planning Data |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_RSPLS_LOGGING_ON_SAVE |
Use
Using this BAdI you can access and log data that is saved for a BW-IP planning application. Logging can be implemented for real-time InfoCubes and DataStore objects for direct updates by selecting the #planning mode# flag. These InfoProviders are referred to in the following text as "suitable InfoProviders#.
Requirements
Activities
The BAdI is filter-dependent. Create an implementation of interface IF_RSPLS_LOGGING_ON_SAVE for every suitable InfoProvider that you want to log. The methods of this interface are described in the interface documentation (see transaction SE24).
Without SAP HANA Database
The idea is that the methods log_defined or log_structure are used to specify whether or in which format the data is provided. 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 the 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 following is very important: Specifying a DDIC structure in the method log_structure and mapping the InfoObjects (or a part of the InfoObject), of the InfoProvider to be logged, to fields in this DDIC structure. It is also possible to predict fields in the DDIC structure for certain context information: Name of user who saves the data, date, time and SAVE-ID. Using the SAVE-ID you can identify a #save# action in a planning application.
Example: If a user saves data three times in a planning application and describes two real-time InfoCubes while logging is active for both InfoCubes, the system creates the three SAVE-IDs. These IDs can be passed to both logging calls of the two InfoCubes if required. In the logs of the two InfoCubes, you can therefore identify which data from InfoCube1 was saved together with which data from InfoCube2.
With SAP HANA Database
If you run your BW system on a SAP HANA database, the logging procedure described in the "Without SAP HANA Database" applies. In this case however, you cannot perform SAP HANA-optimized planning in the BW system.
To make this possible, you can implement additional interface methods:
- Using method log_defined_db, you activate logging on the SAP HANA database for an InfoCube that you have classified for logging using method log_defined. Once you have done this, method log_write is not called any more for the InfoCube in question. Method log_write_db is called instead.
- Method log_write_db provides you with the name of a database table containing structure i_structure_name and the data to be logged. Whereas method log_write is an internal table however, note that this method is a database table. It is not known in the DDIC and therefore has to be processed using database tools (ADBC API or EXEC SQL - i.e. Native SQL). You can persist the log information to your storage location by transforming the content of the database table in question to a storage location of your choosing.
Warning
Methods log_write and log_write_db are called during the update process and can be subsequently updated. When implementing the methods, you therefore need to adhere to the restrictions that apply to ABAP coding for updating (see documentation for the ABAP command #CALL FUNCTION ... IN UPDATE TASK#).
The current BAdI is called if data is saved for an application for BW-integrated planning in a real-time InfoCube or in a DataStore object for a direct update by using the activated #planning mode# flag. The BAdI is not called if the real-time InfoCube is described differently, for example, in loading mode using the Warehouse Management. This has no effect on the existing logging operations, as long as the data of the infoProvider is partially or completed deleted..
Business Attributes
| ASAP Roadmap ID | 252 | Prepare Data Transfer Fields |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20130926 |
| SAP Release Created in | 740 |
