SAP ISM_ISSUE_SEQUENCE_CHECK Function Module for Check Entire Issue Sequence (Opt. with Append Table)









ISM_ISSUE_SEQUENCE_CHECK is a standard ism issue sequence check 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 (Opt. with Append Table) 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 FM, simply by entering the name ISM_ISSUE_SEQUENCE_CHECK 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 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'"Check Entire Issue Sequence (Opt. with Append Table)
  EXPORTING
*  NEW_APPEND_TAB =  "
   MED_PROD =  "Media Product

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

EXCEPTIONS
   MED_PROD_INVALID = 1
.



IMPORTING Parameters details for ISM_ISSUE_SEQUENCE_CHECK

NEW_APPEND_TAB -

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

MED_PROD - Media Product

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

EXPORTING Parameters details for ISM_ISSUE_SEQUENCE_CHECK

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)

PROVED_NEW_APPEND_TAB -

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

EXCEPTIONS details

MED_PROD_INVALID -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISM_ISSUE_SEQUENCE_CHECK 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_new_append_tab  TYPE RJP_MG1_TAB, "   
lv_med_prod_invalid  TYPE RJP_MG1_TAB, "   
lv_med_prod  TYPE MATNR, "   
lv_error_line  TYPE ERROR_LINE, "   
lv_error_field  TYPE ERROR_FIELD, "   
lv_msg_error_tab  TYPE RJMSG_TAB, "   
lv_xinfo  TYPE XFELD, "   
lv_i_tab  TYPE RJP_MG1_INFO_TAB, "   
lv_msg_info_tab  TYPE RJMSG_TAB, "   
lv_proved_new_append_tab  TYPE RJP_MG1_TAB. "   

  CALL FUNCTION 'ISM_ISSUE_SEQUENCE_CHECK'  "Check Entire Issue Sequence (Opt. with Append Table)
    EXPORTING
         NEW_APPEND_TAB = lv_new_append_tab
         MED_PROD = lv_med_prod
    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
         PROVED_NEW_APPEND_TAB = lv_proved_new_append_tab
    EXCEPTIONS
        MED_PROD_INVALID = 1
. " ISM_ISSUE_SEQUENCE_CHECK




ABAP code using 7.40 inline data declarations to call FM ISM_ISSUE_SEQUENCE_CHECK

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!