SAP ISM_CHANGENUMBER_REQUEST Function Module for IS-M: Remove Locks and Check Status of Change Number
ISM_CHANGENUMBER_REQUEST is a standard ism changenumber request 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-M: Remove Locks and Check Status of Change Number 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 ism changenumber request FM, simply by entering the name ISM_CHANGENUMBER_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: JS02_BAPI
Program Name: SAPLJS02_BAPI
Main Program: SAPLJS02_BAPI
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISM_CHANGENUMBER_REQUEST 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_CHANGENUMBER_REQUEST'"IS-M: Remove Locks and Check Status of Change Number.
EXPORTING
IN_AKTION = "
IN_AENDNR = "
IMPORTING
OUT_RETURN = "IS-M/SD: Internal Structure for Transferring Error Messages
OUT_JSTAENDER = "
IMPORTING Parameters details for ISM_CHANGENUMBER_REQUEST
IN_AKTION -
Data type: JS002_ACTIONOptional: No
Call by Reference: Yes
IN_AENDNR -
Data type: JSTAENDER-AENDNROptional: No
Call by Reference: Yes
EXPORTING Parameters details for ISM_CHANGENUMBER_REQUEST
OUT_RETURN - IS-M/SD: Internal Structure for Transferring Error Messages
Data type: JYMSG_T_MSGOptional: No
Call by Reference: Yes
OUT_JSTAENDER -
Data type: JSTAENDEROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISM_CHANGENUMBER_REQUEST 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_in_aktion | TYPE JS002_ACTION, " | |||
| lv_out_return | TYPE JYMSG_T_MSG, " | |||
| lv_in_aendnr | TYPE JSTAENDER-AENDNR, " | |||
| lv_out_jstaender | TYPE JSTAENDER. " |
|   CALL FUNCTION 'ISM_CHANGENUMBER_REQUEST' "IS-M: Remove Locks and Check Status of Change Number |
| EXPORTING | ||
| IN_AKTION | = lv_in_aktion | |
| IN_AENDNR | = lv_in_aendnr | |
| IMPORTING | ||
| OUT_RETURN | = lv_out_return | |
| OUT_JSTAENDER | = lv_out_jstaender | |
| . " ISM_CHANGENUMBER_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM ISM_CHANGENUMBER_REQUEST
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 AENDNR FROM JSTAENDER INTO @DATA(ld_in_aendnr). | ||||
Search for further information about these or an SAP related objects