SAP MCV_LOGGING_TEST_CREATE Function Module for
MCV_LOGGING_TEST_CREATE is a standard mcv logging test create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 mcv logging test create FM, simply by entering the name MCV_LOGGING_TEST_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MCSB
Program Name: SAPLMCSB
Main Program: SAPLMCSB
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function MCV_LOGGING_TEST_CREATE 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 'MCV_LOGGING_TEST_CREATE'".
EXPORTING
I_VBELN = "
* I_BELJR = "
* I_BUKRS = "
I_ZEITP = "
IMPORTING Parameters details for MCV_LOGGING_TEST_CREATE
I_VBELN -
Data type: VBUK-VBELNOptional: No
Call by Reference: No ( called with pass by value option)
I_BELJR -
Data type: MSEG-MJAHROptional: Yes
Call by Reference: No ( called with pass by value option)
I_BUKRS -
Data type: T001-BUKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ZEITP -
Data type: TMC2F-ZEITPOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MCV_LOGGING_TEST_CREATE 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_i_vbeln | TYPE VBUK-VBELN, " | |||
| lv_i_beljr | TYPE MSEG-MJAHR, " | |||
| lv_i_bukrs | TYPE T001-BUKRS, " | |||
| lv_i_zeitp | TYPE TMC2F-ZEITP. " |
|   CALL FUNCTION 'MCV_LOGGING_TEST_CREATE' " |
| EXPORTING | ||
| I_VBELN | = lv_i_vbeln | |
| I_BELJR | = lv_i_beljr | |
| I_BUKRS | = lv_i_bukrs | |
| I_ZEITP | = lv_i_zeitp | |
| . " MCV_LOGGING_TEST_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM MCV_LOGGING_TEST_CREATE
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 VBELN FROM VBUK INTO @DATA(ld_i_vbeln). | ||||
| "SELECT single MJAHR FROM MSEG INTO @DATA(ld_i_beljr). | ||||
| "SELECT single BUKRS FROM T001 INTO @DATA(ld_i_bukrs). | ||||
| "SELECT single ZEITP FROM TMC2F INTO @DATA(ld_i_zeitp). | ||||
Search for further information about these or an SAP related objects