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

Search SAP Function Modules

DYNP_VALUES_UPDATE is a standard dynp values update 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 values update FM, simply by entering the name DYNP_VALUES_UPDATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: SHL2
Program Name: SAPLSHL2
Main Program: SAPLSHL2
Appliation area: S
Release date: 10-Jan-1995
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DYNP_VALUES_UPDATE 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_VALUES_UPDATE'"Change screen field contents w/o PBO
  EXPORTING
   DYNAME =  "Program Name
   DYNUMB =  "Screen number

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_VALUES_UPDATE

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)

TABLES Parameters details for DYNP_VALUES_UPDATE

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_VALUES_UPDATE 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.

ABAP code using 7.40 inline data declarations to call FM DYNP_VALUES_UPDATE

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