SAP ISH_DYNP_VALUES_READ Function Module for IS-H: DYNP_VALUES_READ from Basis with field conversion
ISH_DYNP_VALUES_READ is a standard ish dynp values read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-H: DYNP_VALUES_READ from Basis with field conversion 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 ish dynp values read FM, simply by entering the name ISH_DYNP_VALUES_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: NHLP
Program Name: SAPLNHLP
Main Program: SAPLNHLP
Appliation area: N
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ISH_DYNP_VALUES_READ 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 'ISH_DYNP_VALUES_READ'"IS-H: DYNP_VALUES_READ from Basis with field conversion.
EXPORTING
DYNAME = "
DYNUMB = "
* TRANSLATE_TO_UPPER = ' ' "Conversion of upper case for field contents
* CONVERSION = 'X' "Inout conversion (ON/OFF)
TABLES
DYNPFIELDS = "Table for reading current screen values
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 ISH_DYNP_VALUES_READ
DYNAME -
Data type: D020S-PROGOptional: No
Call by Reference: No ( called with pass by value option)
DYNUMB -
Data type: D020S-DNUMOptional: No
Call by Reference: No ( called with pass by value option)
TRANSLATE_TO_UPPER - Conversion of upper case for field contents
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
CONVERSION - Inout conversion (ON/OFF)
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ISH_DYNP_VALUES_READ
DYNPFIELDS - Table for reading current screen values
Data type: DYNPREADOptional: 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 ISH_DYNP_VALUES_READ 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_invalid_dynproname | TYPE D020S, " | |||
lv_translate_to_upper | TYPE D020S, " SPACE | |||
lv_conversion | TYPE D020S, " 'X' | |||
lv_invalid_dynpronummer | TYPE D020S, " | |||
lv_invalid_request | TYPE D020S, " | |||
lv_no_fielddescription | TYPE D020S, " | |||
lv_undefind_error | TYPE D020S. " |
  CALL FUNCTION 'ISH_DYNP_VALUES_READ' "IS-H: DYNP_VALUES_READ from Basis with field conversion |
EXPORTING | ||
DYNAME | = lv_dyname | |
DYNUMB | = lv_dynumb | |
TRANSLATE_TO_UPPER | = lv_translate_to_upper | |
CONVERSION | = lv_conversion | |
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 | ||
. " ISH_DYNP_VALUES_READ |
ABAP code using 7.40 inline data declarations to call FM ISH_DYNP_VALUES_READ
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). | ||||
DATA(ld_translate_to_upper) | = ' '. | |||
DATA(ld_conversion) | = 'X'. | |||
Search for further information about these or an SAP related objects