OFF_NUMBER_LOCAL_SCREEN_ID SAP Function module - OBNL-Schnittstelle: Feldmodifikationen auf Screen während PBO

OFF_NUMBER_LOCAL_SCREEN_ID is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name OFF_NUMBER_LOCAL_SCREEN_ID into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: ID_OFNUM_ID
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM OFF_NUMBER_LOCAL_SCREEN_ID - OFF NUMBER LOCAL SCREEN ID

CALL FUNCTION 'OFF_NUMBER_LOCAL_SCREEN_ID' "OBNL-Schnittstelle: Feldmodifikationen auf Screen während PBO
  EXPORTING
    i_fin1_param_ex =           " fin1_param_ex
    i_input =                   " bpib0-bp_flag
    i_output =                  " bpib0-bp_flag
    i_invisible =               " bpib0-bp_flag
  IMPORTING
    o_input =                   " bpib0-bp_flag
    o_output =                  " bpib0-bp_flag
    o_invisible =               " bpib0-bp_flag
  EXCEPTIONS
    INPUT_INCOMPLETE = 1        "
    .  "  OFF_NUMBER_LOCAL_SCREEN_ID

ABAP code example for Function Module OFF_NUMBER_LOCAL_SCREEN_ID

The ABAP code below is a full code listing to execute function module OFF_NUMBER_LOCAL_SCREEN_ID including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_o_input  
 
 TYPE BPIB0-BP_FLAG
,
ld_o_output  
 
 TYPE BPIB0-BP_FLAG
,
ld_o_invisible  
 
 TYPE BPIB0-BP_FLAG
.


DATA(ld_i_fin1_param_ex) = 'Check type of data required'.


DATA(ld_i_input) = some text here


DATA(ld_i_output) = some text here


DATA(ld_i_invisible) = some text here
.

CALL FUNCTION 'OFF_NUMBER_LOCAL_SCREEN_ID'
  EXPORTING
    i_fin1_param_ex =            ld_i_fin1_param_ex
    i_input =                    ld_i_input
    i_output =                   ld_i_output
    i_invisible =                ld_i_invisible
  IMPORTING
    o_input =                    ld_o_input
    o_output =                   ld_o_output
    o_invisible =                ld_o_invisible
  EXCEPTIONS
    INPUT_INCOMPLETE =           1
    .  "  OFF_NUMBER_LOCAL_SCREEN_ID

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_o_input
 
 TYPE BPIB0-BP_FLAG ,
ld_i_fin1_param_ex
 
 TYPE FIN1_PARAM_EX ,
ld_o_output
 
 TYPE BPIB0-BP_FLAG ,
ld_i_input
 
 TYPE BPIB0-BP_FLAG ,
ld_o_invisible
 
 TYPE BPIB0-BP_FLAG ,
ld_i_output
 
 TYPE BPIB0-BP_FLAG ,
ld_i_invisible
 
 TYPE BPIB0-BP_FLAG .


ld_i_fin1_param_ex = 'Check type of data required'.

ld_i_input = some text here

ld_i_output = some text here

ld_i_invisible = some text here