SAP RSQ_ISET_F4_DYNP_UPD_IOBJ Function Module for F4 for InfoSet with screen update









RSQ_ISET_F4_DYNP_UPD_IOBJ is a standard rsq iset f4 dynp upd iobj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for F4 for InfoSet with screen update 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 rsq iset f4 dynp upd iobj FM, simply by entering the name RSQ_ISET_F4_DYNP_UPD_IOBJ into the relevant SAP transaction such as SE37 or SE38.

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



Function RSQ_ISET_F4_DYNP_UPD_IOBJ 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 'RSQ_ISET_F4_DYNP_UPD_IOBJ'"F4 for InfoSet with screen update
EXPORTING
I_INFOSET = "InfoSet
I_APPENDNM = "Name of Append (Enhancement)
I_REPID = "Program Name (Dynpro)
I_DYNNR = "Screen Number
I_FNAME = "Field Name
* I_FNAME_TXT = "Field Name (Text Field)
* I_FNAME_ICON = "Field Name (Icon)
* I_OBJVERS = RS_C_OBJVERS-ACTIVE "Version
* I_DISPLAY = RS_C_FALSE "Flag: Display Only

IMPORTING
E_TXTLG = "Description
E_F4 = "InfoObject
.



IMPORTING Parameters details for RSQ_ISET_F4_DYNP_UPD_IOBJ

I_INFOSET - InfoSet

Data type: RSQINFOSET
Optional: No
Call by Reference: Yes

I_APPENDNM - Name of Append (Enhancement)

Data type: RSAPPENDNM
Optional: No
Call by Reference: Yes

I_REPID - Program Name (Dynpro)

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

I_DYNNR - Screen Number

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

I_FNAME - Field Name

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

I_FNAME_TXT - Field Name (Text Field)

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

I_FNAME_ICON - Field Name (Icon)

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

I_OBJVERS - Version

Data type: RS_OBJVERS
Default: RS_C_OBJVERS-ACTIVE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_DISPLAY - Flag: Display Only

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

EXPORTING Parameters details for RSQ_ISET_F4_DYNP_UPD_IOBJ

E_TXTLG - Description

Data type: RS_TXTLG
Optional: No
Call by Reference: Yes

E_F4 - InfoObject

Data type: RSDIOBJ-IOBJNM
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSQ_ISET_F4_DYNP_UPD_IOBJ 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_txtlg  TYPE RS_TXTLG, "   
lv_i_infoset  TYPE RSQINFOSET, "   
lv_e_f4  TYPE RSDIOBJ-IOBJNM, "   
lv_i_appendnm  TYPE RSAPPENDNM, "   
lv_i_repid  TYPE SYREPID, "   
lv_i_dynnr  TYPE SYDYNNR, "   
lv_i_fname  TYPE DYNFNAM, "   
lv_i_fname_txt  TYPE DYNFNAM, "   
lv_i_fname_icon  TYPE DYNFNAM, "   
lv_i_objvers  TYPE RS_OBJVERS, "   RS_C_OBJVERS-ACTIVE
lv_i_display  TYPE RS_BOOL. "   RS_C_FALSE

  CALL FUNCTION 'RSQ_ISET_F4_DYNP_UPD_IOBJ'  "F4 for InfoSet with screen update
    EXPORTING
         I_INFOSET = lv_i_infoset
         I_APPENDNM = lv_i_appendnm
         I_REPID = lv_i_repid
         I_DYNNR = lv_i_dynnr
         I_FNAME = lv_i_fname
         I_FNAME_TXT = lv_i_fname_txt
         I_FNAME_ICON = lv_i_fname_icon
         I_OBJVERS = lv_i_objvers
         I_DISPLAY = lv_i_display
    IMPORTING
         E_TXTLG = lv_e_txtlg
         E_F4 = lv_e_f4
. " RSQ_ISET_F4_DYNP_UPD_IOBJ




ABAP code using 7.40 inline data declarations to call FM RSQ_ISET_F4_DYNP_UPD_IOBJ

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 IOBJNM FROM RSDIOBJ INTO @DATA(ld_e_f4).
 
 
 
 
 
 
 
DATA(ld_i_objvers) = RS_C_OBJVERS-ACTIVE.
 
DATA(ld_i_display) = RS_C_FALSE.
 


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!