Implementing Characteristic Relationships and Data Slices on the SAP HANA Database (Enhanced)
In the context of BW-integrated planning, you can define the permitted combinations of characteristic values (in the form of characteristic relationships) and create data slices for the selected data that you want to protect. If the generic types of characteristic relationships (attribute, hierarchy, DataStore) and data slices (selection) do not meet specific customer requirements, you can implement characteristic relationships and data slices of type Exit.
ABAP Exit Implementation
The typical ABAP exit implementation is direct, with the external data being read from the database using SQL commands from the ABAP runtime and - taking into account further information such as user name (sy-uname) - checking, deriving or creating records in the corresponding structure.
Implementation on the SAP HANA Database
In BW, you can perform planning using internal database routines. In SAP HANA database, you can perform SAP HANA-optimized planning. If you are using the Planning Applications Kit, we recommend also implementing the customer-specific exist functionality for characteristic relationships directly in the SAP HANA database using SQLScript.
We recommend implementing the SQLScript procedures as AMDPs (ABAP Managed Database Procedures) in order to integrate these implementations into the Transport Management System in AS ABAP. For SQLScript procedures, you can therefore use the Transport and Lifecycle Management that you are acquainted with from working with ABAP development objects.