SAP OIJ_SCREEN_LAYOUT_GET Function Module for Retrieve screen layout for a tabstrip
OIJ_SCREEN_LAYOUT_GET is a standard oij screen layout get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Retrieve screen layout for a tabstrip 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 oij screen layout get FM, simply by entering the name OIJ_SCREEN_LAYOUT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIJ_IMG_LAYOUT
Program Name: SAPLOIJ_IMG_LAYOUT
Main Program: SAPLOIJ_IMG_LAYOUT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIJ_SCREEN_LAYOUT_GET 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 'OIJ_SCREEN_LAYOUT_GET'"Retrieve screen layout for a tabstrip.
EXPORTING
* IV_LAYOUTSET = "Screen layout set
IV_TABSTRIP = "Tabstrip identifier
TABLES
ET_SCREENS = "Screen configuration structure
IMPORTING Parameters details for OIJ_SCREEN_LAYOUT_GET
IV_LAYOUTSET - Screen layout set
Data type: OIJ_LAYOUTSETOptional: Yes
Call by Reference: Yes
IV_TABSTRIP - Tabstrip identifier
Data type: OIJ_TABSTRIPOptional: No
Call by Reference: Yes
TABLES Parameters details for OIJ_SCREEN_LAYOUT_GET
ET_SCREENS - Screen configuration structure
Data type: ROIJ_SCREEN_CONFIGURATIONOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIJ_SCREEN_LAYOUT_GET 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: | ||||
| lt_et_screens | TYPE STANDARD TABLE OF ROIJ_SCREEN_CONFIGURATION, " | |||
| lv_iv_layoutset | TYPE OIJ_LAYOUTSET, " | |||
| lv_iv_tabstrip | TYPE OIJ_TABSTRIP. " |
|   CALL FUNCTION 'OIJ_SCREEN_LAYOUT_GET' "Retrieve screen layout for a tabstrip |
| EXPORTING | ||
| IV_LAYOUTSET | = lv_iv_layoutset | |
| IV_TABSTRIP | = lv_iv_tabstrip | |
| TABLES | ||
| ET_SCREENS | = lt_et_screens | |
| . " OIJ_SCREEN_LAYOUT_GET | ||
ABAP code using 7.40 inline data declarations to call FM OIJ_SCREEN_LAYOUT_GET
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