SAP MC_AUSW_ENQUEUE Function Module for Block LIS evaluation
MC_AUSW_ENQUEUE is a standard mc ausw enqueue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Block LIS evaluation 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 mc ausw enqueue FM, simply by entering the name MC_AUSW_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCS3
Program Name: SAPLMCS3
Main Program:
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MC_AUSW_ENQUEUE 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 'MC_AUSW_ENQUEUE'"Block LIS evaluation.
EXPORTING
JOB = "
MCINF = "
EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
IMPORTING Parameters details for MC_AUSW_ENQUEUE
JOB -
Data type: TMCSA-JOBOptional: No
Call by Reference: No ( called with pass by value option)
MCINF -
Data type: TMCSA-MCINFOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOREIGN_LOCK - Evaluation already blocked
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE - Internal error (for example lock t
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MC_AUSW_ENQUEUE 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_job | TYPE TMCSA-JOB, " | |||
| lv_foreign_lock | TYPE TMCSA, " | |||
| lv_mcinf | TYPE TMCSA-MCINF, " | |||
| lv_system_failure | TYPE TMCSA. " |
|   CALL FUNCTION 'MC_AUSW_ENQUEUE' "Block LIS evaluation |
| EXPORTING | ||
| JOB | = lv_job | |
| MCINF | = lv_mcinf | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " MC_AUSW_ENQUEUE | ||
ABAP code using 7.40 inline data declarations to call FM MC_AUSW_ENQUEUE
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 JOB FROM TMCSA INTO @DATA(ld_job). | ||||
| "SELECT single MCINF FROM TMCSA INTO @DATA(ld_mcinf). | ||||
Search for further information about these or an SAP related objects