SAP ISH_PROCEDURE_SHIFT Function Module for
ISH_PROCEDURE_SHIFT is a standard ish procedure shift 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 ish procedure shift FM, simply by entering the name ISH_PROCEDURE_SHIFT into the relevant SAP transaction such as SE37 or SE38.
Function Group: NSHIFT
Program Name: SAPLNSHIFT
Main Program: SAPLNSHIFT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISH_PROCEDURE_SHIFT 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_PROCEDURE_SHIFT'".
EXPORTING
I_EINRI = "Institution
I_LEVEL = "Nesting Depth
I_SOURCE_FALNR = "Source Case Number
I_SOURCE_LFDNR = "Sequence Number of Source Movement
* I_DEST_FALNR = ' ' "Target Case Number
* I_DEST_LFDNR = ' ' "Sequence Number of Target Movement
I_SOURCE_ID = "
* I_TESTRUN = ' ' "Test Run
I_SHIFTMODE = "Mode (Copy, Reassign, Merge)
* I_ACTION = 'T' "
IMPORTING Parameters details for ISH_PROCEDURE_SHIFT
I_EINRI - Institution
Data type: EINRIOptional: No
Call by Reference: No ( called with pass by value option)
I_LEVEL - Nesting Depth
Data type: ISH_LEVELOptional: No
Call by Reference: No ( called with pass by value option)
I_SOURCE_FALNR - Source Case Number
Data type: NFAL-FALNROptional: No
Call by Reference: No ( called with pass by value option)
I_SOURCE_LFDNR - Sequence Number of Source Movement
Data type: NBEW-LFDNROptional: No
Call by Reference: No ( called with pass by value option)
I_DEST_FALNR - Target Case Number
Data type: NFAL-FALNRDefault: ' '
Optional: No
Call by Reference: No ( called with pass by value option)
I_DEST_LFDNR - Sequence Number of Target Movement
Data type: NBEW-LFDNRDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SOURCE_ID -
Data type: ISH_T_SHIFT_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_TESTRUN - Test Run
Data type: ISH_ON_OFFDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SHIFTMODE - Mode (Copy, Reassign, Merge)
Data type: ISH_SHIFTMODEOptional: No
Call by Reference: No ( called with pass by value option)
I_ACTION -
Data type: ISH_SHIFTACTIONDefault: 'T'
Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISH_PROCEDURE_SHIFT 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_i_einri | TYPE EINRI, " | |||
| lv_i_level | TYPE ISH_LEVEL, " | |||
| lv_i_source_falnr | TYPE NFAL-FALNR, " | |||
| lv_i_source_lfdnr | TYPE NBEW-LFDNR, " | |||
| lv_i_dest_falnr | TYPE NFAL-FALNR, " ' ' | |||
| lv_i_dest_lfdnr | TYPE NBEW-LFDNR, " ' ' | |||
| lv_i_source_id | TYPE ISH_T_SHIFT_ID, " | |||
| lv_i_testrun | TYPE ISH_ON_OFF, " ' ' | |||
| lv_i_shiftmode | TYPE ISH_SHIFTMODE, " | |||
| lv_i_action | TYPE ISH_SHIFTACTION. " 'T' |
|   CALL FUNCTION 'ISH_PROCEDURE_SHIFT' " |
| EXPORTING | ||
| I_EINRI | = lv_i_einri | |
| I_LEVEL | = lv_i_level | |
| I_SOURCE_FALNR | = lv_i_source_falnr | |
| I_SOURCE_LFDNR | = lv_i_source_lfdnr | |
| I_DEST_FALNR | = lv_i_dest_falnr | |
| I_DEST_LFDNR | = lv_i_dest_lfdnr | |
| I_SOURCE_ID | = lv_i_source_id | |
| I_TESTRUN | = lv_i_testrun | |
| I_SHIFTMODE | = lv_i_shiftmode | |
| I_ACTION | = lv_i_action | |
| . " ISH_PROCEDURE_SHIFT | ||
ABAP code using 7.40 inline data declarations to call FM ISH_PROCEDURE_SHIFT
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 FALNR FROM NFAL INTO @DATA(ld_i_source_falnr). | ||||
| "SELECT single LFDNR FROM NBEW INTO @DATA(ld_i_source_lfdnr). | ||||
| "SELECT single FALNR FROM NFAL INTO @DATA(ld_i_dest_falnr). | ||||
| DATA(ld_i_dest_falnr) | = ' '. | |||
| "SELECT single LFDNR FROM NBEW INTO @DATA(ld_i_dest_lfdnr). | ||||
| DATA(ld_i_dest_lfdnr) | = ' '. | |||
| DATA(ld_i_testrun) | = ' '. | |||
| DATA(ld_i_action) | = 'T'. | |||
Search for further information about these or an SAP related objects