SAP IAOM_CHANGE_INT_ACC_OBJECT_LC Function Module for NOTRANSL: Log-Baustein für IAOM_CHANGE_INT_ACC_OBJECT
IAOM_CHANGE_INT_ACC_OBJECT_LC is a standard iaom change int acc object lc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Log-Baustein für IAOM_CHANGE_INT_ACC_OBJECT 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 iaom change int acc object lc FM, simply by entering the name IAOM_CHANGE_INT_ACC_OBJECT_LC into the relevant SAP transaction such as SE37 or SE38.
Function Group: IAOM_SERVICE_WITH_LOG
Program Name: SAPLIAOM_SERVICE_WITH_LOG
Main Program: SAPLIAOM_SERVICE_WITH_LOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IAOM_CHANGE_INT_ACC_OBJECT_LC 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 'IAOM_CHANGE_INT_ACC_OBJECT_LC'"NOTRANSL: Log-Baustein für IAOM_CHANGE_INT_ACC_OBJECT.
EXPORTING
I_TEST_RUN = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
I_DIRECT_MESSAGES = "
* I_CPROG = ' ' "ABAP Program, Caller in External Procedures
I_BUS_SCENARIO_ID = "Business Scenario for which Controlling Is Performed
I_OBJECT_DESCRIPTION = "
I_CHANGE_ALL_OR_NOTHING = "
I_UPDATE_SETTLEMENT_RULE = "
I_DO_NOT_SAVE = "
I_RESULT = "
I_CHANGED_ATTRIBUTES = "
I_NOT_RESPONSIBLE_FOR_IAO = "
EXCEPTIONS
ERROR_OCCURRED = 1
IMPORTING Parameters details for IAOM_CHANGE_INT_ACC_OBJECT_LC
I_TEST_RUN - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
I_DIRECT_MESSAGES -
Data type: IAOMT_MESSAGE_TABOptional: No
Call by Reference: Yes
I_CPROG - ABAP Program, Caller in External Procedures
Data type: SYCPROGDefault: SPACE
Optional: Yes
Call by Reference: Yes
I_BUS_SCENARIO_ID - Business Scenario for which Controlling Is Performed
Data type: IAOM_BS_IDENTIFICATIONOptional: No
Call by Reference: Yes
I_OBJECT_DESCRIPTION -
Data type: IAOMT_OBJECT_DESCRIPTIONOptional: No
Call by Reference: Yes
I_CHANGE_ALL_OR_NOTHING -
Data type: BOOLE_DOptional: No
Call by Reference: Yes
I_UPDATE_SETTLEMENT_RULE -
Data type: BOOLE_DOptional: No
Call by Reference: Yes
I_DO_NOT_SAVE -
Data type: BOOLE_DOptional: No
Call by Reference: Yes
I_RESULT -
Data type: IAOMT_OBJECT_STATUSOptional: No
Call by Reference: Yes
I_CHANGED_ATTRIBUTES -
Data type: IAOMT_OBJECT_ATTRIBUTE_TABOptional: No
Call by Reference: Yes
I_NOT_RESPONSIBLE_FOR_IAO -
Data type: BOOLE_DOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IAOM_CHANGE_INT_ACC_OBJECT_LC 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_test_run | TYPE BOOLE_D, " | |||
| lv_error_occurred | TYPE BOOLE_D, " | |||
| lv_i_direct_messages | TYPE IAOMT_MESSAGE_TAB, " | |||
| lv_i_cprog | TYPE SYCPROG, " SPACE | |||
| lv_i_bus_scenario_id | TYPE IAOM_BS_IDENTIFICATION, " | |||
| lv_i_object_description | TYPE IAOMT_OBJECT_DESCRIPTION, " | |||
| lv_i_change_all_or_nothing | TYPE BOOLE_D, " | |||
| lv_i_update_settlement_rule | TYPE BOOLE_D, " | |||
| lv_i_do_not_save | TYPE BOOLE_D, " | |||
| lv_i_result | TYPE IAOMT_OBJECT_STATUS, " | |||
| lv_i_changed_attributes | TYPE IAOMT_OBJECT_ATTRIBUTE_TAB, " | |||
| lv_i_not_responsible_for_iao | TYPE BOOLE_D. " |
|   CALL FUNCTION 'IAOM_CHANGE_INT_ACC_OBJECT_LC' "NOTRANSL: Log-Baustein für IAOM_CHANGE_INT_ACC_OBJECT |
| EXPORTING | ||
| I_TEST_RUN | = lv_i_test_run | |
| I_DIRECT_MESSAGES | = lv_i_direct_messages | |
| I_CPROG | = lv_i_cprog | |
| I_BUS_SCENARIO_ID | = lv_i_bus_scenario_id | |
| I_OBJECT_DESCRIPTION | = lv_i_object_description | |
| I_CHANGE_ALL_OR_NOTHING | = lv_i_change_all_or_nothing | |
| I_UPDATE_SETTLEMENT_RULE | = lv_i_update_settlement_rule | |
| I_DO_NOT_SAVE | = lv_i_do_not_save | |
| I_RESULT | = lv_i_result | |
| I_CHANGED_ATTRIBUTES | = lv_i_changed_attributes | |
| I_NOT_RESPONSIBLE_FOR_IAO | = lv_i_not_responsible_for_iao | |
| EXCEPTIONS | ||
| ERROR_OCCURRED = 1 | ||
| . " IAOM_CHANGE_INT_ACC_OBJECT_LC | ||
ABAP code using 7.40 inline data declarations to call FM IAOM_CHANGE_INT_ACC_OBJECT_LC
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_cprog) | = ' '. | |||
Search for further information about these or an SAP related objects