SAP ISM_JSTSTRUPDA_SELECT Function Module for
ISM_JSTSTRUPDA_SELECT is a standard ism jststrupda select SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ism jststrupda select FM, simply by entering the name ISM_JSTSTRUPDA_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JUPDA
Program Name: SAPLJUPDA
Main Program: SAPLJUPDA
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_JSTSTRUPDA_SELECT 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 'ISM_JSTSTRUPDA_SELECT'".
EXPORTING
IN_STREETNUMBER = "
IN_VALIDFROM = "
IN_VALIDTO = "
IN_COUNTRY = "
IN_CHANGENUMBER = "
IMPORTING
STREET_UPDA_TAB = "
OUT_MSG = "
EXCEPTIONS
INVALID_INPUT = 1 WRONG_CHANGENUMBER = 2 CHANGES_FOUND = 3
IMPORTING Parameters details for ISM_JSTSTRUPDA_SELECT
IN_STREETNUMBER -
Data type: JSTSTRPRO-STRASSENNROptional: No
Call by Reference: No ( called with pass by value option)
IN_VALIDFROM -
Data type: JSTSTRPRO-GUELTIGABOptional: No
Call by Reference: No ( called with pass by value option)
IN_VALIDTO -
Data type: JSTSTRPRO-GUELTIGBISOptional: No
Call by Reference: No ( called with pass by value option)
IN_COUNTRY -
Data type: JSTSTRPRO-LAND1Optional: No
Call by Reference: No ( called with pass by value option)
IN_CHANGENUMBER -
Data type: JSTAENDER-AENDNROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISM_JSTSTRUPDA_SELECT
STREET_UPDA_TAB -
Data type: JUPDA_JSTSTRUPDA_TABOptional: No
Call by Reference: Yes
OUT_MSG -
Data type: RJMSGOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_INPUT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_CHANGENUMBER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CHANGES_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISM_JSTSTRUPDA_SELECT 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_invalid_input | TYPE STRING, " | |||
| lv_in_streetnumber | TYPE JSTSTRPRO-STRASSENNR, " | |||
| lv_street_upda_tab | TYPE JUPDA_JSTSTRUPDA_TAB, " | |||
| lv_out_msg | TYPE RJMSG, " | |||
| lv_in_validfrom | TYPE JSTSTRPRO-GUELTIGAB, " | |||
| lv_wrong_changenumber | TYPE JSTSTRPRO, " | |||
| lv_in_validto | TYPE JSTSTRPRO-GUELTIGBIS, " | |||
| lv_changes_found | TYPE JSTSTRPRO, " | |||
| lv_in_country | TYPE JSTSTRPRO-LAND1, " | |||
| lv_in_changenumber | TYPE JSTAENDER-AENDNR. " |
|   CALL FUNCTION 'ISM_JSTSTRUPDA_SELECT' " |
| EXPORTING | ||
| IN_STREETNUMBER | = lv_in_streetnumber | |
| IN_VALIDFROM | = lv_in_validfrom | |
| IN_VALIDTO | = lv_in_validto | |
| IN_COUNTRY | = lv_in_country | |
| IN_CHANGENUMBER | = lv_in_changenumber | |
| IMPORTING | ||
| STREET_UPDA_TAB | = lv_street_upda_tab | |
| OUT_MSG | = lv_out_msg | |
| EXCEPTIONS | ||
| INVALID_INPUT = 1 | ||
| WRONG_CHANGENUMBER = 2 | ||
| CHANGES_FOUND = 3 | ||
| . " ISM_JSTSTRUPDA_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM ISM_JSTSTRUPDA_SELECT
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 STRASSENNR FROM JSTSTRPRO INTO @DATA(ld_in_streetnumber). | ||||
| "SELECT single GUELTIGAB FROM JSTSTRPRO INTO @DATA(ld_in_validfrom). | ||||
| "SELECT single GUELTIGBIS FROM JSTSTRPRO INTO @DATA(ld_in_validto). | ||||
| "SELECT single LAND1 FROM JSTSTRPRO INTO @DATA(ld_in_country). | ||||
| "SELECT single AENDNR FROM JSTAENDER INTO @DATA(ld_in_changenumber). | ||||
Search for further information about these or an SAP related objects