SAP ITOB_SUBSCREENS_ASSIGN Function Module for NOTRANSL: Returns include subscreens to be processed for specified screen









ITOB_SUBSCREENS_ASSIGN is a standard itob subscreens assign 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: Returns include subscreens to be processed for specified screen 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 itob subscreens assign FM, simply by entering the name ITOB_SUBSCREENS_ASSIGN into the relevant SAP transaction such as SE37 or SE38.

Function Group: ITO0
Program Name: SAPLITO0
Main Program: SAPLITO0
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ITOB_SUBSCREENS_ASSIGN 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 'ITOB_SUBSCREENS_ASSIGN'"NOTRANSL: Returns include subscreens to be processed for specified screen
EXPORTING
I_OBJECT_TYPE = "Technical object types in plant maintenance
I_INTERNAL_TYPE = "Technical object types in plant maintenance
I_TABSTRIP_SCREEN = "ABAP System Field: Current Dynpro Number

IMPORTING
E_SUBSCREEN_A = "
E_SUBSCREEN_B = "
E_SUBSCREEN_C = "
E_SUBSCREEN_D = "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLITO0_001 Customer Include ITO0: Data Import (Initiator => Include)
EXIT_SAPLITO0_002 Customer Include ITO0: Data Export (Include => Caller)
EXIT_SAPLITO0_003 Customer Include Additional Fleet Data: Data Import (Caller => Include)
EXIT_SAPLITO0_004 Customer Include Additional Fleet Data: Data Export (Include => CAller)
EXIT_SAPLITO0_005 Customer Exit Fleet Identification Data: Checks

IMPORTING Parameters details for ITOB_SUBSCREENS_ASSIGN

I_OBJECT_TYPE - Technical object types in plant maintenance

Data type: ITOBTYP
Optional: No
Call by Reference: No ( called with pass by value option)

I_INTERNAL_TYPE - Technical object types in plant maintenance

Data type: ITOBTYP
Optional: No
Call by Reference: No ( called with pass by value option)

I_TABSTRIP_SCREEN - ABAP System Field: Current Dynpro Number

Data type: SY-DYNNR
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ITOB_SUBSCREENS_ASSIGN

E_SUBSCREEN_A -

Data type: ITO0T_SUBSCREEN_REC
Optional: No
Call by Reference: No ( called with pass by value option)

E_SUBSCREEN_B -

Data type: ITO0T_SUBSCREEN_REC
Optional: No
Call by Reference: No ( called with pass by value option)

E_SUBSCREEN_C -

Data type: ITO0T_SUBSCREEN_REC
Optional: No
Call by Reference: No ( called with pass by value option)

E_SUBSCREEN_D -

Data type: ITO0T_SUBSCREEN_REC
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ITOB_SUBSCREENS_ASSIGN 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_e_subscreen_a  TYPE ITO0T_SUBSCREEN_REC, "   
lv_i_object_type  TYPE ITOBTYP, "   
lv_e_subscreen_b  TYPE ITO0T_SUBSCREEN_REC, "   
lv_i_internal_type  TYPE ITOBTYP, "   
lv_e_subscreen_c  TYPE ITO0T_SUBSCREEN_REC, "   
lv_i_tabstrip_screen  TYPE SY-DYNNR, "   
lv_e_subscreen_d  TYPE ITO0T_SUBSCREEN_REC. "   

  CALL FUNCTION 'ITOB_SUBSCREENS_ASSIGN'  "NOTRANSL: Returns include subscreens to be processed for specified screen
    EXPORTING
         I_OBJECT_TYPE = lv_i_object_type
         I_INTERNAL_TYPE = lv_i_internal_type
         I_TABSTRIP_SCREEN = lv_i_tabstrip_screen
    IMPORTING
         E_SUBSCREEN_A = lv_e_subscreen_a
         E_SUBSCREEN_B = lv_e_subscreen_b
         E_SUBSCREEN_C = lv_e_subscreen_c
         E_SUBSCREEN_D = lv_e_subscreen_d
. " ITOB_SUBSCREENS_ASSIGN




ABAP code using 7.40 inline data declarations to call FM ITOB_SUBSCREENS_ASSIGN

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 DYNNR FROM SY INTO @DATA(ld_i_tabstrip_screen).
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!