SAP CKML_F_GET_NEW_STATUS Function Module for









CKML_F_GET_NEW_STATUS is a standard ckml f get new status 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 f get new status FM, simply by entering the name CKML_F_GET_NEW_STATUS into the relevant SAP transaction such as SE37 or SE38.

Function Group: CKM0
Program Name: SAPLCKM0
Main Program: SAPLCKM0
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CKML_F_GET_NEW_STATUS 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_F_GET_NEW_STATUS'"
EXPORTING
I_VORGANG = "
* I_ABSCHLUSSPERIODE = "
* I_OLD_STATUS = "
* I_QUANTITY_UPDATE = "Checkbox
* I_LBKUM = "Total Valuated Stock
* I_XOBJWIP = "

IMPORTING
O_NEW_STATUS = "
O_FALLBACK_STATUS = "
OT_INVALID_STATUS = "
OT_POSTPROCESSING_STATUS = "
OS_RESET_CLOSING_STATUS = "
OS_RESET_OTHER_STATUS = "
.



IMPORTING Parameters details for CKML_F_GET_NEW_STATUS

I_VORGANG -

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

I_ABSCHLUSSPERIODE -

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

I_OLD_STATUS -

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

I_QUANTITY_UPDATE - Checkbox

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

I_LBKUM - Total Valuated Stock

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

I_XOBJWIP -

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

EXPORTING Parameters details for CKML_F_GET_NEW_STATUS

O_NEW_STATUS -

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

O_FALLBACK_STATUS -

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

OT_INVALID_STATUS -

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

OT_POSTPROCESSING_STATUS -

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

OS_RESET_CLOSING_STATUS -

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

OS_RESET_OTHER_STATUS -

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

Copy and paste ABAP code example for CKML_F_GET_NEW_STATUS 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_vorgang  TYPE CKM0_VORGANG, "   
lv_o_new_status  TYPE CK_MLSTAT, "   
lv_o_fallback_status  TYPE CK_MLSTAT, "   
lv_i_abschlussperiode  TYPE XFELD, "   
lv_i_old_status  TYPE CKMLPP-STATUS, "   
lv_ot_invalid_status  TYPE CKI_T_RANGES_STATUS, "   
lv_i_quantity_update  TYPE XFELD, "   
lv_ot_postprocessing_status  TYPE CKI_T_RANGES_STATUS, "   
lv_i_lbkum  TYPE CKMLPP-LBKUM, "   
lv_os_reset_closing_status  TYPE CKML_S_CLOSING_STATUS, "   
lv_i_xobjwip  TYPE CKML_XOBJWIP, "   
lv_os_reset_other_status  TYPE CKML_S_OTHER_STATUS. "   

  CALL FUNCTION 'CKML_F_GET_NEW_STATUS'  "
    EXPORTING
         I_VORGANG = lv_i_vorgang
         I_ABSCHLUSSPERIODE = lv_i_abschlussperiode
         I_OLD_STATUS = lv_i_old_status
         I_QUANTITY_UPDATE = lv_i_quantity_update
         I_LBKUM = lv_i_lbkum
         I_XOBJWIP = lv_i_xobjwip
    IMPORTING
         O_NEW_STATUS = lv_o_new_status
         O_FALLBACK_STATUS = lv_o_fallback_status
         OT_INVALID_STATUS = lv_ot_invalid_status
         OT_POSTPROCESSING_STATUS = lv_ot_postprocessing_status
         OS_RESET_CLOSING_STATUS = lv_os_reset_closing_status
         OS_RESET_OTHER_STATUS = lv_os_reset_other_status
. " CKML_F_GET_NEW_STATUS




ABAP code using 7.40 inline data declarations to call FM CKML_F_GET_NEW_STATUS

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 STATUS FROM CKMLPP INTO @DATA(ld_i_old_status).
 
 
 
 
"SELECT single LBKUM FROM CKMLPP INTO @DATA(ld_i_lbkum).
 
 
 
 


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!