SAP OIO_FS_GET_STATUS_2 Function Module for Get status for screen field using combined field name









OIO_FS_GET_STATUS_2 is a standard oio fs get status 2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get status for screen field using combined field name 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 oio fs get status 2 FM, simply by entering the name OIO_FS_GET_STATUS_2 into the relevant SAP transaction such as SE37 or SE38.

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



Function OIO_FS_GET_STATUS_2 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 'OIO_FS_GET_STATUS_2'"Get status for screen field using combined field name
  EXPORTING
   I_APPID =  "Application for field status handling
   I_SGPID =  "Identifier for field status selection group
   I_SCREEN_FIELD =  "Name of screen field
*  I_SCREEN =  "Flag: set screen parameters

 IMPORTING
   E_FLDST =  "Field status code

EXCEPTIONS
   INVALID_APPLICATION = 1    INVALID_SELECTION_GROUP = 2    FIELD_NOT_DEFINED = 3
.



IMPORTING Parameters details for OIO_FS_GET_STATUS_2

I_APPID - Application for field status handling

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

I_SGPID - Identifier for field status selection group

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

I_SCREEN_FIELD - Name of screen field

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

I_SCREEN - Flag: set screen parameters

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

EXPORTING Parameters details for OIO_FS_GET_STATUS_2

E_FLDST - Field status code

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

EXCEPTIONS details

INVALID_APPLICATION - Application is invalid

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

INVALID_SELECTION_GROUP - Selection group is invalid

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

FIELD_NOT_DEFINED - Field is not defined for the application

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

Copy and paste ABAP code example for OIO_FS_GET_STATUS_2 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_fldst  TYPE OIO_FS_FLDST, "   
lv_i_appid  TYPE OIO_FS_APPID, "   
lv_invalid_application  TYPE OIO_FS_APPID, "   
lv_i_sgpid  TYPE OIO_FS_SGPID, "   
lv_invalid_selection_group  TYPE OIO_FS_SGPID, "   
lv_i_screen_field  TYPE C, "   
lv_field_not_defined  TYPE C, "   
lv_i_screen  TYPE FLAG. "   

  CALL FUNCTION 'OIO_FS_GET_STATUS_2'  "Get status for screen field using combined field name
    EXPORTING
         I_APPID = lv_i_appid
         I_SGPID = lv_i_sgpid
         I_SCREEN_FIELD = lv_i_screen_field
         I_SCREEN = lv_i_screen
    IMPORTING
         E_FLDST = lv_e_fldst
    EXCEPTIONS
        INVALID_APPLICATION = 1
        INVALID_SELECTION_GROUP = 2
        FIELD_NOT_DEFINED = 3
. " OIO_FS_GET_STATUS_2




ABAP code using 7.40 inline data declarations to call FM OIO_FS_GET_STATUS_2

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



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!