SAP IDOC_QUEUE_SUS_MM Function Module for NOTRANSL: Create unique IDoc Queue
IDOC_QUEUE_SUS_MM is a standard idoc queue sus mm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Create unique IDoc Queue 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 idoc queue sus mm FM, simply by entering the name IDOC_QUEUE_SUS_MM into the relevant SAP transaction such as SE37 or SE38.
Function Group: MMPUR_EINM
Program Name: SAPLMMPUR_EINM
Main Program: SAPLMMPUR_EINM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IDOC_QUEUE_SUS_MM 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 'IDOC_QUEUE_SUS_MM'"NOTRANSL: Create unique IDoc Queue.
EXPORTING
CONTROL = "Control Record (IDoc)
IMPORTING
NAME = "Field of Length 16
TABLES
DATA = "IDoc Data Records from 4.0 onwards
IMPORTING Parameters details for IDOC_QUEUE_SUS_MM
CONTROL - Control Record (IDoc)
Data type: EDIDCOptional: No
Call by Reference: Yes
EXPORTING Parameters details for IDOC_QUEUE_SUS_MM
NAME - Field of Length 16
Data type: CHAR16Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for IDOC_QUEUE_SUS_MM
DATA - IDoc Data Records from 4.0 onwards
Data type: EDID4Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IDOC_QUEUE_SUS_MM 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: | ||||
| lt_data | TYPE STANDARD TABLE OF EDID4, " | |||
| lv_name | TYPE CHAR16, " | |||
| lv_control | TYPE EDIDC. " |
|   CALL FUNCTION 'IDOC_QUEUE_SUS_MM' "NOTRANSL: Create unique IDoc Queue |
| EXPORTING | ||
| CONTROL | = lv_control | |
| IMPORTING | ||
| NAME | = lv_name | |
| TABLES | ||
| DATA | = lt_data | |
| . " IDOC_QUEUE_SUS_MM | ||
ABAP code using 7.40 inline data declarations to call FM IDOC_QUEUE_SUS_MM
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