SAP ISM_ISSUE_SEQUENCE_CHECK_1 Function Module for Check Entire Issue Sequence (Inc. Planned Values)









ISM_ISSUE_SEQUENCE_CHECK_1 is a standard ism issue sequence check 1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Entire Issue Sequence (Inc. Planned Values) 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 issue sequence check 1 FM, simply by entering the name ISM_ISSUE_SEQUENCE_CHECK_1 into the relevant SAP transaction such as SE37 or SE38.

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



Function ISM_ISSUE_SEQUENCE_CHECK_1 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_ISSUE_SEQUENCE_CHECK_1'"Check Entire Issue Sequence (Inc. Planned Values)
  EXPORTING
   LF_DYNPRO_TAB =  "Selected Issue Sequence
   MAUS_SEL_TAB =  "
   MAUS_DB_ALL_TAB =  "
   LF_OUT_SEL_TAB =  "
   XMPS_ACTIVE =  "
   XRETAIL =  "
   MIN_SEL_EK_LFDNR =  "
   MAX_SEL_EK_LFDNR =  "
*  XCHRON_PROCESSES =  "IS-M: Issue Sequence with Chronological Subsequent Processes

 IMPORTING
   XERROR =  "
   ERROR_LINE =  "
   ERROR_FIELD =  "
   MSG_ERROR_TAB =  "
   XINFO =  "
   I_TAB =  "
   MSG_INFO_TAB =  "
.



IMPORTING Parameters details for ISM_ISSUE_SEQUENCE_CHECK_1

LF_DYNPRO_TAB - Selected Issue Sequence

Data type: RJP_MG1_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

MAUS_SEL_TAB -

Data type: RJP_MAUS1_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

MAUS_DB_ALL_TAB -

Data type: RJP_MAUS_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

LF_OUT_SEL_TAB -

Data type: RJP_LF1_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

XMPS_ACTIVE -

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

XRETAIL -

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

MIN_SEL_EK_LFDNR -

Data type: MPG_LFDNR
Optional: No
Call by Reference: No ( called with pass by value option)

MAX_SEL_EK_LFDNR -

Data type: MPG_LFDNR
Optional: No
Call by Reference: No ( called with pass by value option)

XCHRON_PROCESSES - IS-M: Issue Sequence with Chronological Subsequent Processes

Data type: XCHRONOLOGICALPROCESSES
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISM_ISSUE_SEQUENCE_CHECK_1

XERROR -

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_LINE -

Data type: ERROR_LINE
Optional: No
Call by Reference: No ( called with pass by value option)

ERROR_FIELD -

Data type: ERROR_FIELD
Optional: No
Call by Reference: No ( called with pass by value option)

MSG_ERROR_TAB -

Data type: RJMSG_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

XINFO -

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

I_TAB -

Data type: RJP_MG1_INFO_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

MSG_INFO_TAB -

Data type: RJMSG_TAB
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ISM_ISSUE_SEQUENCE_CHECK_1 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_xerror  TYPE XFELD, "   
lv_lf_dynpro_tab  TYPE RJP_MG1_TAB, "   
lv_error_line  TYPE ERROR_LINE, "   
lv_maus_sel_tab  TYPE RJP_MAUS1_TAB, "   
lv_error_field  TYPE ERROR_FIELD, "   
lv_maus_db_all_tab  TYPE RJP_MAUS_TAB, "   
lv_msg_error_tab  TYPE RJMSG_TAB, "   
lv_lf_out_sel_tab  TYPE RJP_LF1_TAB, "   
lv_xinfo  TYPE XFELD, "   
lv_xmps_active  TYPE XFELD, "   
lv_i_tab  TYPE RJP_MG1_INFO_TAB, "   
lv_xretail  TYPE XFELD, "   
lv_msg_info_tab  TYPE RJMSG_TAB, "   
lv_min_sel_ek_lfdnr  TYPE MPG_LFDNR, "   
lv_max_sel_ek_lfdnr  TYPE MPG_LFDNR, "   
lv_xchron_processes  TYPE XCHRONOLOGICALPROCESSES. "   

  CALL FUNCTION 'ISM_ISSUE_SEQUENCE_CHECK_1'  "Check Entire Issue Sequence (Inc. Planned Values)
    EXPORTING
         LF_DYNPRO_TAB = lv_lf_dynpro_tab
         MAUS_SEL_TAB = lv_maus_sel_tab
         MAUS_DB_ALL_TAB = lv_maus_db_all_tab
         LF_OUT_SEL_TAB = lv_lf_out_sel_tab
         XMPS_ACTIVE = lv_xmps_active
         XRETAIL = lv_xretail
         MIN_SEL_EK_LFDNR = lv_min_sel_ek_lfdnr
         MAX_SEL_EK_LFDNR = lv_max_sel_ek_lfdnr
         XCHRON_PROCESSES = lv_xchron_processes
    IMPORTING
         XERROR = lv_xerror
         ERROR_LINE = lv_error_line
         ERROR_FIELD = lv_error_field
         MSG_ERROR_TAB = lv_msg_error_tab
         XINFO = lv_xinfo
         I_TAB = lv_i_tab
         MSG_INFO_TAB = lv_msg_info_tab
. " ISM_ISSUE_SEQUENCE_CHECK_1




ABAP code using 7.40 inline data declarations to call FM ISM_ISSUE_SEQUENCE_CHECK_1

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!