SAP BAPI_IOBJ_CHANGE Function Module for Changes an InfoObject
BAPI_IOBJ_CHANGE is a standard bapi iobj change SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Changes 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 bapi iobj change FM, simply by entering the name BAPI_IOBJ_CHANGE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSBAPI_IOBJ
Program Name: SAPLRSBAPI_IOBJ
Main Program: SAPLRSBAPI_IOBJ
Appliation area: B
Release date: 09-Nov-1999
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_IOBJ_CHANGE 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 'BAPI_IOBJ_CHANGE'"Changes an InfoObject.
EXPORTING
INFOOBJECT = "InfoObject
DETAILS = "InfoObject with all properties
* DETAILS_2 = "InfoObjects - Details - Additions
IMPORTING
RETURN = "BAPI Return Parameter
TABLES
* COMPOUNDS = "Compounding
* ATTRIBUTES = "Attributes
* NAVIGATIONATTRIBUTES = "Navigation Attributes
* ATRNAVINFOPROVIDER = "Navigation Attributes of Characteristic as InfoProvider
* HIERARCHYCHARACTERISTICS = "Characteristics that occur in hierarchies
* ELIMINATION = "Elimination of Internal Business Volume
* RETURNTABLE = "Detailed log in case of error
* HANAFIELDSMAPPING = "Assignm. of fields of a SAP HANA View to InfoObject (Attributes, Texts)
IMPORTING Parameters details for BAPI_IOBJ_CHANGE
INFOOBJECT - InfoObject
Data type: BAPI6108-INFOOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
DETAILS - InfoObject with all properties
Data type: BAPI6108Optional: No
Call by Reference: No ( called with pass by value option)
DETAILS_2 - InfoObjects - Details - Additions
Data type: BAPI6108_2Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_IOBJ_CHANGE
RETURN - BAPI Return Parameter
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_IOBJ_CHANGE
COMPOUNDS - Compounding
Data type: BAPI6108CMOptional: Yes
Call by Reference: Yes
ATTRIBUTES - Attributes
Data type: BAPI6108ATOptional: Yes
Call by Reference: Yes
NAVIGATIONATTRIBUTES - Navigation Attributes
Data type: BAPI6108ANOptional: Yes
Call by Reference: Yes
ATRNAVINFOPROVIDER - Navigation Attributes of Characteristic as InfoProvider
Data type: BAPI6108NPOptional: Yes
Call by Reference: Yes
HIERARCHYCHARACTERISTICS - Characteristics that occur in hierarchies
Data type: BAPI6108HCOptional: Yes
Call by Reference: Yes
ELIMINATION - Elimination of Internal Business Volume
Data type: BAPI6108IEOptional: Yes
Call by Reference: Yes
RETURNTABLE - Detailed log in case of error
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
HANAFIELDSMAPPING - Assignm. of fields of a SAP HANA View to InfoObject (Attributes, Texts)
Data type: BAPI6108HANA_MAPOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BAPI_IOBJ_CHANGE 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_return | TYPE BAPIRET2, " | |||
| lt_compounds | TYPE STANDARD TABLE OF BAPI6108CM, " | |||
| lv_infoobject | TYPE BAPI6108-INFOOBJECT, " | |||
| lv_details | TYPE BAPI6108, " | |||
| lt_attributes | TYPE STANDARD TABLE OF BAPI6108AT, " | |||
| lv_details_2 | TYPE BAPI6108_2, " | |||
| lt_navigationattributes | TYPE STANDARD TABLE OF BAPI6108AN, " | |||
| lt_atrnavinfoprovider | TYPE STANDARD TABLE OF BAPI6108NP, " | |||
| lt_hierarchycharacteristics | TYPE STANDARD TABLE OF BAPI6108HC, " | |||
| lt_elimination | TYPE STANDARD TABLE OF BAPI6108IE, " | |||
| lt_returntable | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_hanafieldsmapping | TYPE STANDARD TABLE OF BAPI6108HANA_MAP. " |
|   CALL FUNCTION 'BAPI_IOBJ_CHANGE' "Changes an InfoObject |
| EXPORTING | ||
| INFOOBJECT | = lv_infoobject | |
| DETAILS | = lv_details | |
| DETAILS_2 | = lv_details_2 | |
| IMPORTING | ||
| RETURN | = lv_return | |
| TABLES | ||
| COMPOUNDS | = lt_compounds | |
| ATTRIBUTES | = lt_attributes | |
| NAVIGATIONATTRIBUTES | = lt_navigationattributes | |
| ATRNAVINFOPROVIDER | = lt_atrnavinfoprovider | |
| HIERARCHYCHARACTERISTICS | = lt_hierarchycharacteristics | |
| ELIMINATION | = lt_elimination | |
| RETURNTABLE | = lt_returntable | |
| HANAFIELDSMAPPING | = lt_hanafieldsmapping | |
| . " BAPI_IOBJ_CHANGE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_IOBJ_CHANGE
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.| "SELECT single INFOOBJECT FROM BAPI6108 INTO @DATA(ld_infoobject). | ||||
Search for further information about these or an SAP related objects