SAP DYNP_UPDATE_FIELDS Function Module for Change screen field contents w/o PBO









DYNP_UPDATE_FIELDS is a standard dynp update fields SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Change screen field contents w/o PBO 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 dynp update fields FM, simply by entering the name DYNP_UPDATE_FIELDS into the relevant SAP transaction such as SE37 or SE38.

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



Function DYNP_UPDATE_FIELDS 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 'DYNP_UPDATE_FIELDS'"Change screen field contents w/o PBO
EXPORTING
DYNAME = "Program Name
DYNUMB = "Screen Number
* REQUEST = ' ' "
* START_SEARCH_IN_CURRENT_SCREEN = ' ' "
* START_SEARCH_IN_MAIN_SCREEN = ' ' "
* START_SEARCH_IN_STACKED_SCREEN = ' ' "
* START_SEARCH_ON_SCR_STACKPOS = ' ' "
* SEARCH_OWN_SUBSCREENS_FIRST = ' ' "
* SEARCHPATH_OF_SUBSCREEN_AREAS = ' ' "

TABLES
DYNPFIELDS = "Screen field value reset table

EXCEPTIONS
INVALID_ABAPWORKAREA = 1 INVALID_DYNPROFIELD = 2 INVALID_DYNPRONAME = 3 INVALID_DYNPRONUMMER = 4 INVALID_REQUEST = 5 NO_FIELDDESCRIPTION = 6 UNDEFIND_ERROR = 7
.



IMPORTING Parameters details for DYNP_UPDATE_FIELDS

DYNAME - Program Name

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

DYNUMB - Screen Number

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

REQUEST -

Data type: D020S-TYPE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

START_SEARCH_IN_CURRENT_SCREEN -

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

START_SEARCH_IN_MAIN_SCREEN -

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

START_SEARCH_IN_STACKED_SCREEN -

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

START_SEARCH_ON_SCR_STACKPOS -

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

SEARCH_OWN_SUBSCREENS_FIRST -

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

SEARCHPATH_OF_SUBSCREEN_AREAS -

Data type: STRING
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for DYNP_UPDATE_FIELDS

DYNPFIELDS - Screen field value reset table

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

EXCEPTIONS details

INVALID_ABAPWORKAREA - No valid work area

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

INVALID_DYNPROFIELD - No valid screen field

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

INVALID_DYNPRONAME - No valid screen name

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

INVALID_DYNPRONUMMER - Invalid screen number

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

INVALID_REQUEST - General request error

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

NO_FIELDDESCRIPTION - No field description

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

UNDEFIND_ERROR - Undefined error

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

Copy and paste ABAP code example for DYNP_UPDATE_FIELDS 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_dyname  TYPE D020S-PROG, "   
lt_dynpfields  TYPE STANDARD TABLE OF DYNPREAD, "   
lv_invalid_abapworkarea  TYPE DYNPREAD, "   
lv_dynumb  TYPE D020S-DNUM, "   
lv_invalid_dynprofield  TYPE D020S, "   
lv_request  TYPE D020S-TYPE, "   SPACE
lv_invalid_dynproname  TYPE D020S, "   
lv_invalid_dynpronummer  TYPE D020S, "   
lv_start_search_in_current_screen  TYPE CHAR1, "   SPACE
lv_invalid_request  TYPE CHAR1, "   
lv_start_search_in_main_screen  TYPE CHAR1, "   SPACE
lv_no_fielddescription  TYPE CHAR1, "   
lv_start_search_in_stacked_screen  TYPE DYNPRO_ID, "   SPACE
lv_undefind_error  TYPE DYNPRO_ID, "   
lv_start_search_on_scr_stackpos  TYPE SYTABIX, "   SPACE
lv_search_own_subscreens_first  TYPE CHAR1, "   SPACE
lv_searchpath_of_subscreen_areas  TYPE STRING. "   SPACE

  CALL FUNCTION 'DYNP_UPDATE_FIELDS'  "Change screen field contents w/o PBO
    EXPORTING
         DYNAME = lv_dyname
         DYNUMB = lv_dynumb
         REQUEST = lv_request
         START_SEARCH_IN_CURRENT_SCREEN = lv_start_search_in_current_screen
         START_SEARCH_IN_MAIN_SCREEN = lv_start_search_in_main_screen
         START_SEARCH_IN_STACKED_SCREEN = lv_start_search_in_stacked_screen
         START_SEARCH_ON_SCR_STACKPOS = lv_start_search_on_scr_stackpos
         SEARCH_OWN_SUBSCREENS_FIRST = lv_search_own_subscreens_first
         SEARCHPATH_OF_SUBSCREEN_AREAS = lv_searchpath_of_subscreen_areas
    TABLES
         DYNPFIELDS = lt_dynpfields
    EXCEPTIONS
        INVALID_ABAPWORKAREA = 1
        INVALID_DYNPROFIELD = 2
        INVALID_DYNPRONAME = 3
        INVALID_DYNPRONUMMER = 4
        INVALID_REQUEST = 5
        NO_FIELDDESCRIPTION = 6
        UNDEFIND_ERROR = 7
. " DYNP_UPDATE_FIELDS




ABAP code using 7.40 inline data declarations to call FM DYNP_UPDATE_FIELDS

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 PROG FROM D020S INTO @DATA(ld_dyname).
 
 
 
"SELECT single DNUM FROM D020S INTO @DATA(ld_dynumb).
 
 
"SELECT single TYPE FROM D020S INTO @DATA(ld_request).
DATA(ld_request) = ' '.
 
 
 
DATA(ld_start_search_in_current_screen) = ' '.
 
 
DATA(ld_start_search_in_main_screen) = ' '.
 
 
DATA(ld_start_search_in_stacked_screen) = ' '.
 
 
DATA(ld_start_search_on_scr_stackpos) = ' '.
 
DATA(ld_search_own_subscreens_first) = ' '.
 
DATA(ld_searchpath_of_subscreen_areas) = ' '.
 


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!