SAP BW_RFC_IOBJ_CREATE Function Module for Creates an InfoObject
BW_RFC_IOBJ_CREATE is a standard bw rfc iobj 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 Creates an InfoObject 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 bw rfc iobj create FM, simply by entering the name BW_RFC_IOBJ_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: TBL_BW
Program Name: SAPLTBL_BW
Main Program: SAPLTBL_BW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BW_RFC_IOBJ_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 'BW_RFC_IOBJ_CREATE'"Creates an InfoObject.
EXPORTING
I_RFCDEST = "Logical Destination (Specified in Function Call)
I_STR_IOBJDETAILS = "InfoObjects - Details
* I_TAB_COMPOUNDS = "InfoObjects - Compound
* I_TAB_ATTRIBUTES = "InfoObjects - Attributes
* I_TAB_NAVATTRIBUTES = "InfoObjects - Navigation Attributes
* I_TAB_ATTRNAVINFOPROV = "Navigation Attributes of Characteristic as InfoProvider
* I_TAB_HIERCHARACTERISTICS = "Characteristics That Can Be Used In Hierarchies
IMPORTING
E_INFOOBJECT = "InfoObject
E_TAB_RETURN = "Table with BAPI Return Information
E_STR_RETURN = "Return Parameter(s)
EXCEPTIONS
IOBJ_CREATE_FAILED = 1 COMM_ERROR = 2 FAILED = 3
IMPORTING Parameters details for BW_RFC_IOBJ_CREATE
I_RFCDEST - Logical Destination (Specified in Function Call)
Data type: RFCDESTOptional: No
Call by Reference: Yes
I_STR_IOBJDETAILS - InfoObjects - Details
Data type: STR_BW_BAPI6108Optional: No
Call by Reference: Yes
I_TAB_COMPOUNDS - InfoObjects - Compound
Data type: TTY_TAB_BAPI6108CMOptional: Yes
Call by Reference: Yes
I_TAB_ATTRIBUTES - InfoObjects - Attributes
Data type: TTY_TAB_BAPI6108ATOptional: Yes
Call by Reference: Yes
I_TAB_NAVATTRIBUTES - InfoObjects - Navigation Attributes
Data type: TTY_TAB_BAPI6108ANOptional: Yes
Call by Reference: Yes
I_TAB_ATTRNAVINFOPROV - Navigation Attributes of Characteristic as InfoProvider
Data type: TTY_TAB_BAPI6108NPOptional: Yes
Call by Reference: Yes
I_TAB_HIERCHARACTERISTICS - Characteristics That Can Be Used In Hierarchies
Data type: TTY_TAB_BAPI6108HCOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BW_RFC_IOBJ_CREATE
E_INFOOBJECT - InfoObject
Data type: RSIOBJNMOptional: No
Call by Reference: Yes
E_TAB_RETURN - Table with BAPI Return Information
Data type: BAPIRETTABOptional: No
Call by Reference: Yes
E_STR_RETURN - Return Parameter(s)
Data type: BAPIRET2Optional: No
Call by Reference: Yes
EXCEPTIONS details
IOBJ_CREATE_FAILED - Error When Creating InfoObject
Data type:Optional: No
Call by Reference: Yes
COMM_ERROR - Communication Error
Data type:Optional: No
Call by Reference: Yes
FAILED - Error When Processing
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BW_RFC_IOBJ_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_rfcdest | TYPE RFCDEST, " | |||
| lv_e_infoobject | TYPE RSIOBJNM, " | |||
| lv_iobj_create_failed | TYPE RSIOBJNM, " | |||
| lv_comm_error | TYPE RSIOBJNM, " | |||
| lv_e_tab_return | TYPE BAPIRETTAB, " | |||
| lv_i_str_iobjdetails | TYPE STR_BW_BAPI6108, " | |||
| lv_failed | TYPE STR_BW_BAPI6108, " | |||
| lv_e_str_return | TYPE BAPIRET2, " | |||
| lv_i_tab_compounds | TYPE TTY_TAB_BAPI6108CM, " | |||
| lv_i_tab_attributes | TYPE TTY_TAB_BAPI6108AT, " | |||
| lv_i_tab_navattributes | TYPE TTY_TAB_BAPI6108AN, " | |||
| lv_i_tab_attrnavinfoprov | TYPE TTY_TAB_BAPI6108NP, " | |||
| lv_i_tab_hiercharacteristics | TYPE TTY_TAB_BAPI6108HC. " |
|   CALL FUNCTION 'BW_RFC_IOBJ_CREATE' "Creates an InfoObject |
| EXPORTING | ||
| I_RFCDEST | = lv_i_rfcdest | |
| I_STR_IOBJDETAILS | = lv_i_str_iobjdetails | |
| I_TAB_COMPOUNDS | = lv_i_tab_compounds | |
| I_TAB_ATTRIBUTES | = lv_i_tab_attributes | |
| I_TAB_NAVATTRIBUTES | = lv_i_tab_navattributes | |
| I_TAB_ATTRNAVINFOPROV | = lv_i_tab_attrnavinfoprov | |
| I_TAB_HIERCHARACTERISTICS | = lv_i_tab_hiercharacteristics | |
| IMPORTING | ||
| E_INFOOBJECT | = lv_e_infoobject | |
| E_TAB_RETURN | = lv_e_tab_return | |
| E_STR_RETURN | = lv_e_str_return | |
| EXCEPTIONS | ||
| IOBJ_CREATE_FAILED = 1 | ||
| COMM_ERROR = 2 | ||
| FAILED = 3 | ||
| . " BW_RFC_IOBJ_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM BW_RFC_IOBJ_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.Search for further information about these or an SAP related objects