SAP MCS_PROTOCOL_SAVE Function Module for NOTRANSL: Speichert ein Generierungsprotokoll (Info-Struktur, FoRegeln) in









MCS_PROTOCOL_SAVE is a standard mcs protocol save 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: Speichert ein Generierungsprotokoll (Info-Struktur, FoRegeln) in 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 mcs protocol save FM, simply by entering the name MCS_PROTOCOL_SAVE into the relevant SAP transaction such as SE37 or SE38.

Function Group: MCSA
Program Name: SAPLMCSA
Main Program: SAPLMCSA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function MCS_PROTOCOL_SAVE 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 'MCS_PROTOCOL_SAVE'"NOTRANSL: Speichert ein Generierungsprotokoll (Info-Struktur, FoRegeln) in
EXPORTING
I_MCINF = "Info structure
* I_STAFO = ' ' "Update group
.



IMPORTING Parameters details for MCS_PROTOCOL_SAVE

I_MCINF - Info structure

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

I_STAFO - Update group

Data type: TMC2D-STAFO
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for MCS_PROTOCOL_SAVE 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_mcinf  TYPE TMC4-MCINF, "   
lv_i_stafo  TYPE TMC2D-STAFO. "   ' '

  CALL FUNCTION 'MCS_PROTOCOL_SAVE'  "NOTRANSL: Speichert ein Generierungsprotokoll (Info-Struktur, FoRegeln) in
    EXPORTING
         I_MCINF = lv_i_mcinf
         I_STAFO = lv_i_stafo
. " MCS_PROTOCOL_SAVE




ABAP code using 7.40 inline data declarations to call FM MCS_PROTOCOL_SAVE

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_i_mcinf).
 
"SELECT single STAFO FROM TMC2D INTO @DATA(ld_i_stafo).
DATA(ld_i_stafo) = ' '.
 


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!