SAP CZ_CL_S_MTK_PROVIDE Function Module for NOTRANSL: Bereitstellung von Material-Planzuordnungen
CZ_CL_S_MTK_PROVIDE is a standard cz cl s mtk 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 von Material-Planzuordnungen 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 cl s mtk provide FM, simply by entering the name CZ_CL_S_MTK_PROVIDE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CZCL
Program Name: SAPLCZCL
Main Program: SAPLCZCL
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function CZ_CL_S_MTK_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_CL_S_MTK_PROVIDE'"NOTRANSL: Bereitstellung von Material-Planzuordnungen.
EXPORTING
* I_DATE_FROM = DATE-MIN_GRG "Valid-From Date
* I_POSNR = "Sales Document Item
* I_KUNR = "Account number of customer
* I_LIFNR = "Vendor Account Number
* I_PSPNR = "Work breakdown structure element (WBS element)
* I_SUCHFELD = "Search Field for Customer-Specific Task List Selection
* I_FLG_ALL_CRITERIA = ' ' "Generic Type
* I_FLG_PROVIDE_INV = ' ' "Generic Type
* I_MS_OBJECT = "Object for Multiple Specifications
* I_MS_OBJTYPE = "Type of Object for Multiple Specifications
* 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_VBELN = "Sales Document
IMPORTING
E_MTK_INV = "
TABLES
E_MTK_CLASS_DATA = "Data about classes in material-routing assignment
EXCEPTIONS
WRONG_KEY = 1
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_SAPLCZCL_001 EWB: Exit to the search field test in material/ routing assignment (MAPL)
IMPORTING Parameters details for CZ_CL_S_MTK_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_POSNR - Sales Document Item
Data type: MTK_CLASS_DATA-POSNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_KUNR - Account number of customer
Data type: MTK_CLASS_DATA-KUNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_LIFNR - Vendor Account Number
Data type: MTK_CLASS_DATA-LIFNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_PSPNR - Work breakdown structure element (WBS element)
Data type: MTK_CLASS_DATA-PSPNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_SUCHFELD - Search Field for Customer-Specific Task List Selection
Data type: MTK_CLASS_DATA-SUCHFELDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_ALL_CRITERIA - Generic Type
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FLG_PROVIDE_INV - Generic Type
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MS_OBJECT - Object for Multiple Specifications
Data type: MTK_CLASS_DATA-MS_OBJECTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MS_OBJTYPE - Type of Object for Multiple Specifications
Data type: MTK_CLASS_DATA-MS_OBJTYPEOptional: 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_VBELN - Sales Document
Data type: MTK_CLASS_DATA-VBELNOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CZ_CL_S_MTK_PROVIDE
E_MTK_INV -
Data type: CZCL_MTK_VERS_TAB_TYPEOptional: No
Call by Reference: Yes
TABLES Parameters details for CZ_CL_S_MTK_PROVIDE
E_MTK_CLASS_DATA - Data about classes in material-routing assignment
Data type: MTK_CLASS_DATAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
WRONG_KEY -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CZ_CL_S_MTK_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_inv | TYPE CZCL_MTK_VERS_TAB_TYPE, " | |||
lv_wrong_key | TYPE CZCL_MTK_VERS_TAB_TYPE, " | |||
lv_i_date_from | TYPE MTK_CLASS_DATA-DATUV, " DATE-MIN_GRG | |||
lt_e_mtk_class_data | TYPE STANDARD TABLE OF MTK_CLASS_DATA, " | |||
lv_i_posnr | TYPE MTK_CLASS_DATA-POSNR, " | |||
lv_i_kunr | TYPE MTK_CLASS_DATA-KUNR, " | |||
lv_i_lifnr | TYPE MTK_CLASS_DATA-LIFNR, " | |||
lv_i_pspnr | TYPE MTK_CLASS_DATA-PSPNR, " | |||
lv_i_suchfeld | TYPE MTK_CLASS_DATA-SUCHFELD, " | |||
lv_i_flg_all_criteria | TYPE C, " SPACE | |||
lv_i_flg_provide_inv | TYPE C, " SPACE | |||
lv_i_ms_object | TYPE MTK_CLASS_DATA-MS_OBJECT, " | |||
lv_i_ms_objtype | TYPE MTK_CLASS_DATA-MS_OBJTYPE, " | |||
lv_i_date_to | TYPE MTK_CLASS_DATA-DATUB, " DATE-MAX_GRG | |||
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_vbeln | TYPE MTK_CLASS_DATA-VBELN. " |
  CALL FUNCTION 'CZ_CL_S_MTK_PROVIDE' "NOTRANSL: Bereitstellung von Material-Planzuordnungen |
EXPORTING | ||
I_DATE_FROM | = lv_i_date_from | |
I_POSNR | = lv_i_posnr | |
I_KUNR | = lv_i_kunr | |
I_LIFNR | = lv_i_lifnr | |
I_PSPNR | = lv_i_pspnr | |
I_SUCHFELD | = lv_i_suchfeld | |
I_FLG_ALL_CRITERIA | = lv_i_flg_all_criteria | |
I_FLG_PROVIDE_INV | = lv_i_flg_provide_inv | |
I_MS_OBJECT | = lv_i_ms_object | |
I_MS_OBJTYPE | = lv_i_ms_objtype | |
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_VBELN | = lv_i_vbeln | |
IMPORTING | ||
E_MTK_INV | = lv_e_mtk_inv | |
TABLES | ||
E_MTK_CLASS_DATA | = lt_e_mtk_class_data | |
EXCEPTIONS | ||
WRONG_KEY = 1 | ||
. " CZ_CL_S_MTK_PROVIDE |
ABAP code using 7.40 inline data declarations to call FM CZ_CL_S_MTK_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 POSNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_posnr). | ||||
"SELECT single KUNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_kunr). | ||||
"SELECT single LIFNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_lifnr). | ||||
"SELECT single PSPNR FROM MTK_CLASS_DATA INTO @DATA(ld_i_pspnr). | ||||
"SELECT single SUCHFELD FROM MTK_CLASS_DATA INTO @DATA(ld_i_suchfeld). | ||||
DATA(ld_i_flg_all_criteria) | = ' '. | |||
DATA(ld_i_flg_provide_inv) | = ' '. | |||
"SELECT single MS_OBJECT FROM MTK_CLASS_DATA INTO @DATA(ld_i_ms_object). | ||||
"SELECT single MS_OBJTYPE FROM MTK_CLASS_DATA INTO @DATA(ld_i_ms_objtype). | ||||
"SELECT single DATUB FROM MTK_CLASS_DATA INTO @DATA(ld_i_date_to). | ||||
DATA(ld_i_date_to) | = DATE-MAX_GRG. | |||
"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). | ||||
"SELECT single VBELN FROM MTK_CLASS_DATA INTO @DATA(ld_i_vbeln). | ||||
Search for further information about these or an SAP related objects