SAP CZ_OV_MTK_ID_PROVIDE Function Module for NOTRANSL: Bereitstellung einer Material-Planzuordnung
CZ_OV_MTK_ID_PROVIDE is a standard cz ov mtk id provide 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: Bereitstellung einer Material-Planzuordnung 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 cz ov mtk id provide FM, simply by entering the name CZ_OV_MTK_ID_PROVIDE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CZOV
Program Name: SAPLCZOV
Main Program:
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CZ_OV_MTK_ID_PROVIDE 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 'CZ_OV_MTK_ID_PROVIDE'"NOTRANSL: Bereitstellung einer Material-Planzuordnung.
EXPORTING
* I_DATE_FROM = DATE-MIN_GRG "Valid-From Date
* I_DATE_TO = DATE-MAX_GRG "Valid-to date
* I_PLNTY = "Task List Type
* I_PLNNR = "Key for Task List Group
* I_PLNAL = "Group Counter
* I_MATNR = "Material Number
* I_WERKS = "Plant
* I_ZKRIZ = "Counter for additional criteria
* I_FLG_COM = "Generic Type
IMPORTING
E_MTK_IDENT = "
E_DATUV = "Valid-From Date
E_AENNR = "Change Number
EXCEPTIONS
NO_MTK_FOUND = 1 NO_BOM_FOUND = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCZOV_001 EWB: Exit for search field F4 help in the material/ routing assignment
IMPORTING Parameters details for CZ_OV_MTK_ID_PROVIDE
I_DATE_FROM - Valid-From Date
Data type: MTK_CLASS_DATA-DATUVDefault: DATE-MIN_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATE_TO - Valid-to date
Data type: MTK_CLASS_DATA-DATUBDefault: DATE-MAX_GRG
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNTY - Task List Type
Data type: MTK_CLASS_DATA-PLNTYOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNNR - Key for Task List Group
Data type: MTK_CLASS_DATA-PLNNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLNAL - Group Counter
Data type: MTK_CLASS_DATA-PLNALOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MATNR - Material Number
Data type: MTK_CLASS_DATA-MATNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_WERKS - Plant
Data type: MTK_CLASS_DATA-WERKSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ZKRIZ - Counter for additional criteria
Data type: MTK_CLASS_DATA-ZKRIZOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_COM - Generic Type
Data type: COptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CZ_OV_MTK_ID_PROVIDE
E_MTK_IDENT -
Data type: CZCL_MTK_IDENT_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
E_DATUV - Valid-From Date
Data type: MTK_CLASS_DATA-DATUVOptional: No
Call by Reference: No ( called with pass by value option)
E_AENNR - Change Number
Data type: MTK_CLASS_DATA-AENNROptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_MTK_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_BOM_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CZ_OV_MTK_ID_PROVIDE 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_e_mtk_ident | TYPE CZCL_MTK_IDENT_TYPE, " | |||
lv_i_date_from | TYPE MTK_CLASS_DATA-DATUV, " DATE-MIN_GRG | |||
lv_no_mtk_found | TYPE MTK_CLASS_DATA, " | |||
lv_e_datuv | TYPE MTK_CLASS_DATA-DATUV, " | |||
lv_i_date_to | TYPE MTK_CLASS_DATA-DATUB, " DATE-MAX_GRG | |||
lv_no_bom_found | TYPE MTK_CLASS_DATA, " | |||
lv_e_aennr | TYPE MTK_CLASS_DATA-AENNR, " | |||
lv_i_plnty | TYPE MTK_CLASS_DATA-PLNTY, " | |||
lv_i_plnnr | TYPE MTK_CLASS_DATA-PLNNR, " | |||
lv_i_plnal | TYPE MTK_CLASS_DATA-PLNAL, " | |||
lv_i_matnr | TYPE MTK_CLASS_DATA-MATNR, " | |||
lv_i_werks | TYPE MTK_CLASS_DATA-WERKS, " | |||
lv_i_zkriz | TYPE MTK_CLASS_DATA-ZKRIZ, " | |||
lv_i_flg_com | TYPE C. " |
  CALL FUNCTION 'CZ_OV_MTK_ID_PROVIDE' "NOTRANSL: Bereitstellung einer Material-Planzuordnung |
EXPORTING | ||
I_DATE_FROM | = lv_i_date_from | |
I_DATE_TO | = lv_i_date_to | |
I_PLNTY | = lv_i_plnty | |
I_PLNNR | = lv_i_plnnr | |
I_PLNAL | = lv_i_plnal | |
I_MATNR | = lv_i_matnr | |
I_WERKS | = lv_i_werks | |
I_ZKRIZ | = lv_i_zkriz | |
I_FLG_COM | = lv_i_flg_com | |
IMPORTING | ||
E_MTK_IDENT | = lv_e_mtk_ident | |
E_DATUV | = lv_e_datuv | |
E_AENNR | = lv_e_aennr | |
EXCEPTIONS | ||
NO_MTK_FOUND = 1 | ||
NO_BOM_FOUND = 2 | ||
. " CZ_OV_MTK_ID_PROVIDE |
ABAP code using 7.40 inline data declarations to call FM CZ_OV_MTK_ID_PROVIDE
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 DATUV FROM MTK_CLASS_DATA INTO @DATA(ld_i_date_from). | ||||
DATA(ld_i_date_from) | = DATE-MIN_GRG. | |||
"SELECT single DATUV FROM MTK_CLASS_DATA INTO @DATA(ld_e_datuv). | ||||
"SELECT single DATUB FROM MTK_CLASS_DATA INTO @DATA(ld_i_date_to). | ||||
DATA(ld_i_date_to) | = DATE-MAX_GRG. | |||
"SELECT single AENNR FROM MTK_CLASS_DATA INTO @DATA(ld_e_aennr). | ||||
"SELECT single PLNTY FROM MTK_CLASS_DATA INTO @DATA(ld_i_plnty). | ||||
"SELECT single PLNNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_plnnr). | ||||
"SELECT single PLNAL FROM MTK_CLASS_DATA INTO @DATA(ld_i_plnal). | ||||
"SELECT single MATNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_matnr). | ||||
"SELECT single WERKS FROM MTK_CLASS_DATA INTO @DATA(ld_i_werks). | ||||
"SELECT single ZKRIZ FROM MTK_CLASS_DATA INTO @DATA(ld_i_zkriz). | ||||
Search for further information about these or an SAP related objects