SAP CKML_MGV_PROCESSES_READ Function Module for









CKML_MGV_PROCESSES_READ is a standard ckml mgv processes read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ckml mgv processes read FM, simply by entering the name CKML_MGV_PROCESSES_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function CKML_MGV_PROCESSES_READ 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 'CKML_MGV_PROCESSES_READ'"
EXPORTING
IV_WERKS = "Plant of the material
IV_MATNR = "Material
* IV_BTYP = 'BF' "
* IV_NFELDER = "InspChar.Field
* IV_PKOSA_STATUS = ' ' "
* IV_PLWRK = "Planning Plant for Order
* IV_CHECK_PP_DATA = ' ' "

IMPORTING
ET_PROCESS_TBL = "

EXCEPTIONS
WRONG_CHARACTERISTICS = 1 RULE_NOT_FOUND = 2 MULTIPLE_PKOSA_FOUND = 3
.



IMPORTING Parameters details for CKML_MGV_PROCESSES_READ

IV_WERKS - Plant of the material

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

IV_MATNR - Material

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

IV_BTYP -

Data type: CKMLMV001-BTYP
Default: 'BF'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_NFELDER - InspChar.Field

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

IV_PKOSA_STATUS -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_PLWRK - Planning Plant for Order

Data type: CKMLMV001-PLWRK_ND
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CHECK_PP_DATA -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CKML_MGV_PROCESSES_READ

ET_PROCESS_TBL -

Data type: CKML_T_PROCESS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

WRONG_CHARACTERISTICS -

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

RULE_NOT_FOUND -

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

MULTIPLE_PKOSA_FOUND -

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

Copy and paste ABAP code example for CKML_MGV_PROCESSES_READ 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_iv_werks  TYPE CKMLMV001-WERKS, "   
lv_et_process_tbl  TYPE CKML_T_PROCESS, "   
lv_wrong_characteristics  TYPE CKML_T_PROCESS, "   
lv_iv_matnr  TYPE CKMLMV001-MATNR, "   
lv_rule_not_found  TYPE CKMLMV001, "   
lv_iv_btyp  TYPE CKMLMV001-BTYP, "   'BF'
lv_multiple_pkosa_found  TYPE CKMLMV001, "   
lv_iv_nfelder  TYPE CKMLI_NDEF_FELDER, "   
lv_iv_pkosa_status  TYPE C, "   SPACE
lv_iv_plwrk  TYPE CKMLMV001-PLWRK_ND, "   
lv_iv_check_pp_data  TYPE C. "   SPACE

  CALL FUNCTION 'CKML_MGV_PROCESSES_READ'  "
    EXPORTING
         IV_WERKS = lv_iv_werks
         IV_MATNR = lv_iv_matnr
         IV_BTYP = lv_iv_btyp
         IV_NFELDER = lv_iv_nfelder
         IV_PKOSA_STATUS = lv_iv_pkosa_status
         IV_PLWRK = lv_iv_plwrk
         IV_CHECK_PP_DATA = lv_iv_check_pp_data
    IMPORTING
         ET_PROCESS_TBL = lv_et_process_tbl
    EXCEPTIONS
        WRONG_CHARACTERISTICS = 1
        RULE_NOT_FOUND = 2
        MULTIPLE_PKOSA_FOUND = 3
. " CKML_MGV_PROCESSES_READ




ABAP code using 7.40 inline data declarations to call FM CKML_MGV_PROCESSES_READ

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 WERKS FROM CKMLMV001 INTO @DATA(ld_iv_werks).
 
 
 
"SELECT single MATNR FROM CKMLMV001 INTO @DATA(ld_iv_matnr).
 
 
"SELECT single BTYP FROM CKMLMV001 INTO @DATA(ld_iv_btyp).
DATA(ld_iv_btyp) = 'BF'.
 
 
 
DATA(ld_iv_pkosa_status) = ' '.
 
"SELECT single PLWRK_ND FROM CKMLMV001 INTO @DATA(ld_iv_plwrk).
 
DATA(ld_iv_check_pp_data) = ' '.
 


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!