SAP HDB_OLAP_CREATE Function Module for Create an OLAP-View on HDB
HDB_OLAP_CREATE is a standard hdb olap create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create an OLAP-View on HDB processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for hdb olap create FM, simply by entering the name HDB_OLAP_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HDB_SERVICE
Program Name: SAPLHDB_SERVICE
Main Program: SAPLHDB_SERVICE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HDB_OLAP_CREATE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'HDB_OLAP_CREATE'"Create an OLAP-View on HDB.
EXPORTING
I_VIEWNAME = "Name of OLAP View
I_FACT_TABLE = "'Fact Table' on HDB
IT_KEYFIGURE = "Keyfigures (Fields from Fact Table of Formular)
IT_JOIN = "Joined Attribute Tables
IT_ATTRIBUTE = "Attributes
* I_APPLICATION = "Application (Default: Cross application)
* I_SUBAPPLICATION = ' ' "Subapplication
* I_KEY_VALUE = ' ' "Key Value
* I_HDBC_CHECK = ' ' "Check main switches in HDBC
EXCEPTIONS
DBCON_NOT_EXIST = 1 DBCON_NO_USE = 2 DBCON_ERROR = 3 VIEW_ALREADY_EXIST = 4 DDIC_ERROR = 5 HDB_ERROR = 6
IMPORTING Parameters details for HDB_OLAP_CREATE
I_VIEWNAME - Name of OLAP View
Data type: TABNAMEOptional: No
Call by Reference: Yes
I_FACT_TABLE - 'Fact Table' on HDB
Data type: TABNAMEOptional: No
Call by Reference: Yes
IT_KEYFIGURE - Keyfigures (Fields from Fact Table of Formular)
Data type: HDB_T_OLAP_KEYFIGUREOptional: No
Call by Reference: Yes
IT_JOIN - Joined Attribute Tables
Data type: HDB_T_OLAP_JOINOptional: No
Call by Reference: Yes
IT_ATTRIBUTE - Attributes
Data type: HDB_T_OLAP_ATTRIBUTEOptional: No
Call by Reference: Yes
I_APPLICATION - Application (Default: Cross application)
Data type: HDB_APPLICATIONOptional: Yes
Call by Reference: Yes
I_SUBAPPLICATION - Subapplication
Data type: HDB_SUBAPPLICATIONDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_KEY_VALUE - Key Value
Data type: HDB_KEY_VALUEDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_HDBC_CHECK - Check main switches in HDBC
Data type: FLAGDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
DBCON_NOT_EXIST - HDB Connection Does Not Exist
Data type:Optional: No
Call by Reference: Yes
DBCON_NO_USE - HDB Connection should not be used in this context (see HDBC)
Data type:Optional: No
Call by Reference: Yes
DBCON_ERROR - HDB Connection Cannot be Reached
Data type:Optional: No
Call by Reference: Yes
VIEW_ALREADY_EXIST - View already exists on HDB
Data type:Optional: No
Call by Reference: Yes
DDIC_ERROR - Table definition not available or incorrect
Data type:Optional: No
Call by Reference: Yes
HDB_ERROR - HDB SQL Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HDB_OLAP_CREATE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_i_viewname | TYPE TABNAME, " | |||
| lv_dbcon_not_exist | TYPE TABNAME, " | |||
| lv_dbcon_no_use | TYPE TABNAME, " | |||
| lv_i_fact_table | TYPE TABNAME, " | |||
| lv_dbcon_error | TYPE TABNAME, " | |||
| lv_it_keyfigure | TYPE HDB_T_OLAP_KEYFIGURE, " | |||
| lv_it_join | TYPE HDB_T_OLAP_JOIN, " | |||
| lv_view_already_exist | TYPE HDB_T_OLAP_JOIN, " | |||
| lv_ddic_error | TYPE HDB_T_OLAP_JOIN, " | |||
| lv_it_attribute | TYPE HDB_T_OLAP_ATTRIBUTE, " | |||
| lv_hdb_error | TYPE HDB_T_OLAP_ATTRIBUTE, " | |||
| lv_i_application | TYPE HDB_APPLICATION, " | |||
| lv_i_subapplication | TYPE HDB_SUBAPPLICATION, " SPACE | |||
| lv_i_key_value | TYPE HDB_KEY_VALUE, " SPACE | |||
| lv_i_hdbc_check | TYPE FLAG. " SPACE |
|   CALL FUNCTION 'HDB_OLAP_CREATE' "Create an OLAP-View on HDB |
| EXPORTING | ||
| I_VIEWNAME | = lv_i_viewname | |
| I_FACT_TABLE | = lv_i_fact_table | |
| IT_KEYFIGURE | = lv_it_keyfigure | |
| IT_JOIN | = lv_it_join | |
| IT_ATTRIBUTE | = lv_it_attribute | |
| I_APPLICATION | = lv_i_application | |
| I_SUBAPPLICATION | = lv_i_subapplication | |
| I_KEY_VALUE | = lv_i_key_value | |
| I_HDBC_CHECK | = lv_i_hdbc_check | |
| EXCEPTIONS | ||
| DBCON_NOT_EXIST = 1 | ||
| DBCON_NO_USE = 2 | ||
| DBCON_ERROR = 3 | ||
| VIEW_ALREADY_EXIST = 4 | ||
| DDIC_ERROR = 5 | ||
| HDB_ERROR = 6 | ||
| . " HDB_OLAP_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM HDB_OLAP_CREATE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| DATA(ld_i_subapplication) | = ' '. | |||
| DATA(ld_i_key_value) | = ' '. | |||
| DATA(ld_i_hdbc_check) | = ' '. | |||
Search for further information about these or an SAP related objects