SAP COMI_I_MATERIAL_SEQUENCE_CHECK Function Module for Sequence check for HUs
COMI_I_MATERIAL_SEQUENCE_CHECK is a standard comi i material 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 Sequence check for HUs 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 comi i material sequence check FM, simply by entering the name COMI_I_MATERIAL_SEQUENCE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: COMI
Program Name: SAPLCOMI
Main Program: SAPLCOMI
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function COMI_I_MATERIAL_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 'COMI_I_MATERIAL_SEQUENCE_CHECK'"Sequence check for HUs.
EXPORTING
I_AUFNR = "Production Order Number
I_RSNUM = "Reservation Number
* I_VORNR = "Operation Number
* I_PHASE = "Phase Number
I_CHECK = "
* I_CONS = "
* I_SHOW = 'Y' "
* I_VALREQ = 'Y' "
I_MODE = "
IMPORTING
E_FLAG = "
E_TEXT = "
EXCEPTIONS
INVALID_VALUE = 1 NO_HU_FOUND = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCOMIX_001 Process Bar Code
IMPORTING Parameters details for COMI_I_MATERIAL_SEQUENCE_CHECK
I_AUFNR - Production Order Number
Data type: EXBEREIT-AUFNROptional: No
Call by Reference: No ( called with pass by value option)
I_RSNUM - Reservation Number
Data type: BEREIT-RSNUMOptional: No
Call by Reference: No ( called with pass by value option)
I_VORNR - Operation Number
Data type: EXBEREIT-VORNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PHASE - Phase Number
Data type: EXBEREIT-VORNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_CHECK -
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
I_CONS -
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SHOW -
Data type: CHAR1Default: 'Y'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VALREQ -
Data type: CHAR1Default: 'Y'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MODE -
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for COMI_I_MATERIAL_SEQUENCE_CHECK
E_FLAG -
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
E_TEXT -
Data type: T100-TEXTOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INVALID_VALUE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_HU_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for COMI_I_MATERIAL_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_e_flag | TYPE CHAR1, " | |||
| lv_i_aufnr | TYPE EXBEREIT-AUFNR, " | |||
| lv_invalid_value | TYPE EXBEREIT, " | |||
| lv_e_text | TYPE T100-TEXT, " | |||
| lv_i_rsnum | TYPE BEREIT-RSNUM, " | |||
| lv_no_hu_found | TYPE BEREIT, " | |||
| lv_i_vornr | TYPE EXBEREIT-VORNR, " | |||
| lv_i_phase | TYPE EXBEREIT-VORNR, " | |||
| lv_i_check | TYPE CHAR1, " | |||
| lv_i_cons | TYPE CHAR1, " | |||
| lv_i_show | TYPE CHAR1, " 'Y' | |||
| lv_i_valreq | TYPE CHAR1, " 'Y' | |||
| lv_i_mode | TYPE CHAR1. " |
|   CALL FUNCTION 'COMI_I_MATERIAL_SEQUENCE_CHECK' "Sequence check for HUs |
| EXPORTING | ||
| I_AUFNR | = lv_i_aufnr | |
| I_RSNUM | = lv_i_rsnum | |
| I_VORNR | = lv_i_vornr | |
| I_PHASE | = lv_i_phase | |
| I_CHECK | = lv_i_check | |
| I_CONS | = lv_i_cons | |
| I_SHOW | = lv_i_show | |
| I_VALREQ | = lv_i_valreq | |
| I_MODE | = lv_i_mode | |
| IMPORTING | ||
| E_FLAG | = lv_e_flag | |
| E_TEXT | = lv_e_text | |
| EXCEPTIONS | ||
| INVALID_VALUE = 1 | ||
| NO_HU_FOUND = 2 | ||
| . " COMI_I_MATERIAL_SEQUENCE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM COMI_I_MATERIAL_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.| "SELECT single AUFNR FROM EXBEREIT INTO @DATA(ld_i_aufnr). | ||||
| "SELECT single TEXT FROM T100 INTO @DATA(ld_e_text). | ||||
| "SELECT single RSNUM FROM BEREIT INTO @DATA(ld_i_rsnum). | ||||
| "SELECT single VORNR FROM EXBEREIT INTO @DATA(ld_i_vornr). | ||||
| "SELECT single VORNR FROM EXBEREIT INTO @DATA(ld_i_phase). | ||||
| DATA(ld_i_show) | = 'Y'. | |||
| DATA(ld_i_valreq) | = 'Y'. | |||
Search for further information about these or an SAP related objects