SAP MKAL_SAVE Function Module for NOTRANSL: Verbuchung der Fertigungs-Versions-Änderungen

Search SAP Function Modules

MKAL_SAVE is a standard mkal 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: Verbuchung der Fertigungs-Versions-Änderungen 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 mkal save FM, simply by entering the name MKAL_SAVE into the relevant SAP transaction such as SE37 or SE38.

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

Function MKAL_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 'MKAL_SAVE'"NOTRANSL: Verbuchung der Fertigungs-Versions-Änderungen
  EXPORTING
   DISMM =  "MRP type for MRP records
   DISST =  "MRP level for MRP level
   FLGMKAL_EXI =  "Indicator, production versions already exist in the database
   MATNR =  "
   WERKS =  "

TABLES
   VMKAL =  "

EXCEPTIONS
   MKAL_DELETE_ERROR = 1    MKAL_INSERT_ERROR = 2 

.

IMPORTING Parameters details for MKAL_SAVE

DISMM - MRP type for MRP records

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

DISST - MRP level for MRP level

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

FLGMKAL_EXI - Indicator, production versions already exist in the database

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

MATNR -

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

WERKS -

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

TABLES Parameters details for MKAL_SAVE

VMKAL -

Data type: MKAL
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

MKAL_DELETE_ERROR -

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

MKAL_INSERT_ERROR -

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

Copy and paste ABAP code example for MKAL_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.

ABAP code using 7.40 inline data declarations to call FM MKAL_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.

Search for further information about these or an SAP related objects