SAP ISH_N2_SHIFT_DOC_CREATE_NEW Function Module for









ISH_N2_SHIFT_DOC_CREATE_NEW is a standard ish n2 shift doc create new 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 n2 shift doc create new FM, simply by entering the name ISH_N2_SHIFT_DOC_CREATE_NEW into the relevant SAP transaction such as SE37 or SE38.

Function Group: N2SHIFT
Program Name: SAPLN2SHIFT
Main Program: SAPLN2SHIFT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISH_N2_SHIFT_DOC_CREATE_NEW 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_N2_SHIFT_DOC_CREATE_NEW'"
EXPORTING
I_EINRI = "
I_SHIFTMODE = "
I_PROCESS = "
I_AUTHORITY_CHECK = "
* I_DELETE_CASE = "
* I_CANCEL_REASON = "
* I_TESTRUN = "
I_SOURCE_FALNR = "
I_SOURCE_LFDNR = "
I_SOURCE_TYPE = "
* IT_SOURCE_ID = "
* I_DEST_FALNR = "
* I_DEST_LFDNR = "
I_DEST_TYPE = "
* IT_SOURCE_TAB = "

CHANGING
* CT_DEST_TAB = "
CT_CORR_TAB = "
C_ERRORHANDLER = "
CT_PROTOCOL = "
CT_PROTOCOL_ID = "
.



IMPORTING Parameters details for ISH_N2_SHIFT_DOC_CREATE_NEW

I_EINRI -

Data type: EINRI
Optional: No
Call by Reference: Yes

I_SHIFTMODE -

Data type: ISH_SHIFTMODE
Optional: No
Call by Reference: Yes

I_PROCESS -

Data type: STRING
Optional: No
Call by Reference: Yes

I_AUTHORITY_CHECK -

Data type: ISH_ON_OFF
Optional: No
Call by Reference: Yes

I_DELETE_CASE -

Data type: ISH_ON_OFF
Optional: Yes
Call by Reference: Yes

I_CANCEL_REASON -

Data type: N1STOID
Optional: Yes
Call by Reference: Yes

I_TESTRUN -

Data type: ISH_ON_OFF
Optional: Yes
Call by Reference: Yes

I_SOURCE_FALNR -

Data type: FALNR
Optional: No
Call by Reference: Yes

I_SOURCE_LFDNR -

Data type: LFDBEW
Optional: No
Call by Reference: Yes

I_SOURCE_TYPE -

Data type: ISH_SHIFT_TYPE
Optional: No
Call by Reference: Yes

IT_SOURCE_ID -

Data type: ISH_T_SHIFT_ID
Optional: Yes
Call by Reference: Yes

I_DEST_FALNR -

Data type: FALNR
Optional: Yes
Call by Reference: Yes

I_DEST_LFDNR -

Data type: LFDBEW
Optional: Yes
Call by Reference: Yes

I_DEST_TYPE -

Data type: ISH_SHIFT_TYPE
Optional: No
Call by Reference: Yes

IT_SOURCE_TAB -

Data type: ISH_T_SHIFT_OBJECT
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for ISH_N2_SHIFT_DOC_CREATE_NEW

CT_DEST_TAB -

Data type: ISH_T_SHIFT_OBJECT
Optional: Yes
Call by Reference: Yes

CT_CORR_TAB -

Data type: ISH_T_SHIFT_CORR
Optional: No
Call by Reference: Yes

C_ERRORHANDLER -

Data type: CL_ISHMED_ERRORHANDLING
Optional: No
Call by Reference: Yes

CT_PROTOCOL -

Data type: ISH_T_NSHIFT
Optional: No
Call by Reference: Yes

CT_PROTOCOL_ID -

Data type: ISH_T_NSHIFT_ID
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISH_N2_SHIFT_DOC_CREATE_NEW 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_ct_dest_tab  TYPE ISH_T_SHIFT_OBJECT, "   
lv_i_shiftmode  TYPE ISH_SHIFTMODE, "   
lv_i_process  TYPE STRING, "   
lv_i_authority_check  TYPE ISH_ON_OFF, "   
lv_i_delete_case  TYPE ISH_ON_OFF, "   
lv_i_cancel_reason  TYPE N1STOID, "   
lv_i_testrun  TYPE ISH_ON_OFF, "   
lv_ct_corr_tab  TYPE ISH_T_SHIFT_CORR, "   
lv_i_source_falnr  TYPE FALNR, "   
lv_c_errorhandler  TYPE CL_ISHMED_ERRORHANDLING, "   
lv_i_source_lfdnr  TYPE LFDBEW, "   
lv_ct_protocol  TYPE ISH_T_NSHIFT, "   
lv_i_source_type  TYPE ISH_SHIFT_TYPE, "   
lv_it_source_id  TYPE ISH_T_SHIFT_ID, "   
lv_ct_protocol_id  TYPE ISH_T_NSHIFT_ID, "   
lv_i_dest_falnr  TYPE FALNR, "   
lv_i_dest_lfdnr  TYPE LFDBEW, "   
lv_i_dest_type  TYPE ISH_SHIFT_TYPE, "   
lv_it_source_tab  TYPE ISH_T_SHIFT_OBJECT. "   

  CALL FUNCTION 'ISH_N2_SHIFT_DOC_CREATE_NEW'  "
    EXPORTING
         I_EINRI = lv_i_einri
         I_SHIFTMODE = lv_i_shiftmode
         I_PROCESS = lv_i_process
         I_AUTHORITY_CHECK = lv_i_authority_check
         I_DELETE_CASE = lv_i_delete_case
         I_CANCEL_REASON = lv_i_cancel_reason
         I_TESTRUN = lv_i_testrun
         I_SOURCE_FALNR = lv_i_source_falnr
         I_SOURCE_LFDNR = lv_i_source_lfdnr
         I_SOURCE_TYPE = lv_i_source_type
         IT_SOURCE_ID = lv_it_source_id
         I_DEST_FALNR = lv_i_dest_falnr
         I_DEST_LFDNR = lv_i_dest_lfdnr
         I_DEST_TYPE = lv_i_dest_type
         IT_SOURCE_TAB = lv_it_source_tab
    CHANGING
         CT_DEST_TAB = lv_ct_dest_tab
         CT_CORR_TAB = lv_ct_corr_tab
         C_ERRORHANDLER = lv_c_errorhandler
         CT_PROTOCOL = lv_ct_protocol
         CT_PROTOCOL_ID = lv_ct_protocol_id
. " ISH_N2_SHIFT_DOC_CREATE_NEW




ABAP code using 7.40 inline data declarations to call FM ISH_N2_SHIFT_DOC_CREATE_NEW

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!