Customer Exit For Planning Functionen On HANA
Customer Exit For Planning Functionen On HANA
Customer Exit For Planning Functionen On HANA
Customers can implement own planning functionality by creating own planning function types and
assigning their own class to this planning function type. Such a class has to implement some
interfaces.
Starting from NW730 SP10 it is possible to implement customer planning logic in own SQL script
procedures which run in the HANA layer. Such procedures can be called by implementing the
Method TREX_EXECUTE in one of the following interfaces:
IF_RSPLFA_SRVTYPE_TREX_EXEC
IF_RSPLFA_SRVTYPE_TREX_EXEC_R
With NW740 once can also use ABAP managed database procedures to create SQL-Script.
* Other examples to get the name of the HANA-procedure name which will be called can be
* - you use the technical name of the planning function type:
l_srvtypenm = p_r_srv->get_srvtypenm( ).
l_procedure_name = l_srvtypenm.
r_s_view-view = l_r_sql_script->execute_sql_script(
i_view = i_view
i_view_ref = i_view_ref
i_t_iobj_param = l_t_iobj_param
i_proc_name = l_procedure_name
i_r_msg = i_r_msg ).
ENDMETHOD. "IF_RSPLFA_SRVTYPE_TREX_EXEC_R~TREX_EXECUTE
Blocking
Blocking has to be considered in the SQL script procedure itself.
Result table
The result table is treated as delta. So the values from the result table are aggregated to the original
values. This behavior is different from the behavior of the result table in the ABAP-Exit.
Tool Report
With the tool report RSPLS_SQL_SCRIPT_TOOL you can create the following Object on HANA
A table with the structure corresponding to the aggregation level. This table can be used to
give the type of the table parameters in your SQL script procedure
A body of the SQL script procedure. This procedure body contains the table parameters by
which data (on which the procedure shall operate) is passed and the returning table with the
procedure result. Additionally the elementary parameters from the function are listed with
the corresponding types.