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

Function OIF_IS_SCREEN_RELEVANT 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 'OIF_IS_SCREEN_RELEVANT'"Determine if screen is relevant for location type.
EXPORTING
IV_PGNAM = "ABAP program, current main program
IV_DYNNR = "Number of the following screen
IV_PBLTYP = "Business location type (IS-Oil MRN)
EXCEPTIONS
NOT_RELEVANT = 1
IMPORTING Parameters details for OIF_IS_SCREEN_RELEVANT
IV_PGNAM - ABAP program, current main program
Data type: SYREPIDOptional: No
Call by Reference: Yes
IV_DYNNR - Number of the following screen
Data type: DYNNROptional: No
Call by Reference: Yes
IV_PBLTYP - Business location type (IS-Oil MRN)
Data type: OIF_PBLTYPOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_RELEVANT -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIF_IS_SCREEN_RELEVANT 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_pgnam | TYPE SYREPID, " | |||
| lv_not_relevant | TYPE SYREPID, " | |||
| lv_iv_dynnr | TYPE DYNNR, " | |||
| lv_iv_pbltyp | TYPE OIF_PBLTYP. " |
|   CALL FUNCTION 'OIF_IS_SCREEN_RELEVANT' "Determine if screen is relevant for location type |
| EXPORTING | ||
| IV_PGNAM | = lv_iv_pgnam | |
| IV_DYNNR | = lv_iv_dynnr | |
| IV_PBLTYP | = lv_iv_pbltyp | |
| EXCEPTIONS | ||
| NOT_RELEVANT = 1 | ||
| . " OIF_IS_SCREEN_RELEVANT | ||
ABAP code using 7.40 inline data declarations to call FM OIF_IS_SCREEN_RELEVANT
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