SAP CM_FV_MKAL_EXIST_CHK Function Module for NOTRANSL: Prüfen: Existiert zum Stichtag Fertigungsversion in MKAL
CM_FV_MKAL_EXIST_CHK is a standard cm fv mkal exist chk 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: Prüfen: Existiert zum Stichtag Fertigungsversion in MKAL 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 cm fv mkal exist chk FM, simply by entering the name CM_FV_MKAL_EXIST_CHK into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMFV
Program Name: SAPLCMFV
Main Program: SAPLCMFV
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CM_FV_MKAL_EXIST_CHK 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 'CM_FV_MKAL_EXIST_CHK'"NOTRANSL: Prüfen: Existiert zum Stichtag Fertigungsversion in MKAL.
EXPORTING
I_MATNR = "Material Number
I_WERKS = "Plant
* I_TRTYP = "Transaction type
RC27I_IMP = "Task lists: Indexes referring to current rec'd in rec'd tabs
* RC27S_IMP = "Ctrl. data for ctrl. during dialog processing
* I_VERID = ' ' "Production Version
* I_DATUV = SY-DATLO "Valid-From Date
* I_DATUB = SY-DATLO "Valid-to date
EXCEPTIONS
NO_MKAL_FOUND = 1
IMPORTING Parameters details for CM_FV_MKAL_EXIST_CHK
I_MATNR - Material Number
Data type: MKAL-MATNROptional: No
Call by Reference: No ( called with pass by value option)
I_WERKS - Plant
Data type: MKAL-WERKSOptional: No
Call by Reference: No ( called with pass by value option)
I_TRTYP - Transaction type
Data type: TCA05-TRTYPOptional: Yes
Call by Reference: No ( called with pass by value option)
RC27I_IMP - Task lists: Indexes referring to current rec'd in rec'd tabs
Data type: RC27IOptional: No
Call by Reference: No ( called with pass by value option)
RC27S_IMP - Ctrl. data for ctrl. during dialog processing
Data type: RC27SOptional: Yes
Call by Reference: Yes
I_VERID - Production Version
Data type: MKAL-VERIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATUV - Valid-From Date
Data type: DATUVDefault: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATUB - Valid-to date
Data type: DATUBDefault: SY-DATLO
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_MKAL_FOUND - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CM_FV_MKAL_EXIST_CHK 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_matnr | TYPE MKAL-MATNR, " | |||
lv_no_mkal_found | TYPE MKAL, " | |||
lv_i_werks | TYPE MKAL-WERKS, " | |||
lv_i_trtyp | TYPE TCA05-TRTYP, " | |||
lv_rc27i_imp | TYPE RC27I, " | |||
lv_rc27s_imp | TYPE RC27S, " | |||
lv_i_verid | TYPE MKAL-VERID, " SPACE | |||
lv_i_datuv | TYPE DATUV, " SY-DATLO | |||
lv_i_datub | TYPE DATUB. " SY-DATLO |
  CALL FUNCTION 'CM_FV_MKAL_EXIST_CHK' "NOTRANSL: Prüfen: Existiert zum Stichtag Fertigungsversion in MKAL |
EXPORTING | ||
I_MATNR | = lv_i_matnr | |
I_WERKS | = lv_i_werks | |
I_TRTYP | = lv_i_trtyp | |
RC27I_IMP | = lv_rc27i_imp | |
RC27S_IMP | = lv_rc27s_imp | |
I_VERID | = lv_i_verid | |
I_DATUV | = lv_i_datuv | |
I_DATUB | = lv_i_datub | |
EXCEPTIONS | ||
NO_MKAL_FOUND = 1 | ||
. " CM_FV_MKAL_EXIST_CHK |
ABAP code using 7.40 inline data declarations to call FM CM_FV_MKAL_EXIST_CHK
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 MATNR FROM MKAL INTO @DATA(ld_i_matnr). | ||||
"SELECT single WERKS FROM MKAL INTO @DATA(ld_i_werks). | ||||
"SELECT single TRTYP FROM TCA05 INTO @DATA(ld_i_trtyp). | ||||
"SELECT single VERID FROM MKAL INTO @DATA(ld_i_verid). | ||||
DATA(ld_i_verid) | = ' '. | |||
DATA(ld_i_datuv) | = SY-DATLO. | |||
DATA(ld_i_datub) | = SY-DATLO. | |||
Search for further information about these or an SAP related objects