SAP MC_MCINF_ENQUEUE Function Module for Block MCINF









MC_MCINF_ENQUEUE is a standard mc mcinf 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 MCINF 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 mcinf enqueue FM, simply by entering the name MC_MCINF_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_MCINF_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_MCINF_ENQUEUE'"Block MCINF
EXPORTING
MCINF = "

EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for MC_MCINF_ENQUEUE

MCINF -

Data type: TMC4-MCINF
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

FOREIGN_LOCK - Information structure already bloc

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_MCINF_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_mcinf  TYPE TMC4-MCINF, "   
lv_foreign_lock  TYPE TMC4, "   
lv_system_failure  TYPE TMC4. "   

  CALL FUNCTION 'MC_MCINF_ENQUEUE'  "Block MCINF
    EXPORTING
         MCINF = lv_mcinf
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " MC_MCINF_ENQUEUE




ABAP code using 7.40 inline data declarations to call FM MC_MCINF_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 MCINF FROM TMC4 INTO @DATA(ld_mcinf).
 
 
 


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!