SAP O2_APPL_CUSTOMIZING Function Module for
O2_APPL_CUSTOMIZING is a standard o2 appl customizing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 o2 appl customizing FM, simply by entering the name O2_APPL_CUSTOMIZING into the relevant SAP transaction such as SE37 or SE38.
Function Group: O2_THEME_CUST
Program Name: SAPLO2_THEME_CUST
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function O2_APPL_CUSTOMIZING 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 'O2_APPL_CUSTOMIZING'".
EXPORTING
* IV_SHOW_AS_SCREEN = 'X' "
* IV_SCREEN_X_VALUE = 3 "
* IV_SCREEN_Y_VALUE = 5 "
* IV_INITIAL_APPL = "Application ID
* IV_APPL_CHANGEABLE = 'X' "
IMPORTING Parameters details for O2_APPL_CUSTOMIZING
IV_SHOW_AS_SCREEN -
Data type: BOOLEANDefault: 'X'
Optional: No
Call by Reference: Yes
IV_SCREEN_X_VALUE -
Data type: IDefault: 3
Optional: No
Call by Reference: Yes
IV_SCREEN_Y_VALUE -
Data type: IDefault: 5
Optional: No
Call by Reference: Yes
IV_INITIAL_APPL - Application ID
Data type: O2APPLNAMEOptional: Yes
Call by Reference: Yes
IV_APPL_CHANGEABLE -
Data type: BOOLEANDefault: 'X'
Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for O2_APPL_CUSTOMIZING 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_iv_show_as_screen | TYPE BOOLEAN, " 'X' | |||
| lv_iv_screen_x_value | TYPE I, " 3 | |||
| lv_iv_screen_y_value | TYPE I, " 5 | |||
| lv_iv_initial_appl | TYPE O2APPLNAME, " | |||
| lv_iv_appl_changeable | TYPE BOOLEAN. " 'X' |
|   CALL FUNCTION 'O2_APPL_CUSTOMIZING' " |
| EXPORTING | ||
| IV_SHOW_AS_SCREEN | = lv_iv_show_as_screen | |
| IV_SCREEN_X_VALUE | = lv_iv_screen_x_value | |
| IV_SCREEN_Y_VALUE | = lv_iv_screen_y_value | |
| IV_INITIAL_APPL | = lv_iv_initial_appl | |
| IV_APPL_CHANGEABLE | = lv_iv_appl_changeable | |
| . " O2_APPL_CUSTOMIZING | ||
ABAP code using 7.40 inline data declarations to call FM O2_APPL_CUSTOMIZING
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_iv_show_as_screen) | = 'X'. | |||
| DATA(ld_iv_screen_x_value) | = 3. | |||
| DATA(ld_iv_screen_y_value) | = 5. | |||
| DATA(ld_iv_appl_changeable) | = 'X'. | |||
Search for further information about these or an SAP related objects