SAP ISU_M_CORRNO_GET Function Module for INTERNAL: IS-U Migration - Get New Correction Number
ISU_M_CORRNO_GET is a standard isu m corrno get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: IS-U Migration - Get New Correction 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 isu m corrno get FM, simply by entering the name ISU_M_CORRNO_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: EMIG_TRANSPORT
Program Name: SAPLEMIG_TRANSPORT
Main Program: SAPLEMIG_TRANSPORT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_M_CORRNO_GET 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 'ISU_M_CORRNO_GET'"INTERNAL: IS-U Migration - Get New Correction Number.
IMPORTING
Y_TR_ORDER = "Order
Y_TR_TASK = "Task
EXCEPTIONS
NO_CORRECTION_SELECTED = 1
EXPORTING Parameters details for ISU_M_CORRNO_GET
Y_TR_ORDER - Order
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
Y_TR_TASK - Task
Data type: E070-TRKORROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_CORRECTION_SELECTED - No request was selected
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISU_M_CORRNO_GET 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_y_tr_order | TYPE E070-TRKORR, " | |||
| lv_no_correction_selected | TYPE E070, " | |||
| lv_y_tr_task | TYPE E070-TRKORR. " |
|   CALL FUNCTION 'ISU_M_CORRNO_GET' "INTERNAL: IS-U Migration - Get New Correction Number |
| IMPORTING | ||
| Y_TR_ORDER | = lv_y_tr_order | |
| Y_TR_TASK | = lv_y_tr_task | |
| EXCEPTIONS | ||
| NO_CORRECTION_SELECTED = 1 | ||
| . " ISU_M_CORRNO_GET | ||
ABAP code using 7.40 inline data declarations to call FM ISU_M_CORRNO_GET
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 TRKORR FROM E070 INTO @DATA(ld_y_tr_order). | ||||
| "SELECT single TRKORR FROM E070 INTO @DATA(ld_y_tr_task). | ||||
Search for further information about these or an SAP related objects