SAP CKMO_SPLIT_ADD Function Module for









CKMO_SPLIT_ADD is a standard ckmo split add 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 ckmo split add FM, simply by entering the name CKMO_SPLIT_ADD into the relevant SAP transaction such as SE37 or SE38.

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



Function CKMO_SPLIT_ADD 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 'CKMO_SPLIT_ADD'"
  EXPORTING
   I_AKT_POPER =  "Posting Period
   I_AKT_BDATJ =  "Posting date YYYY
   I_BWKEY =  "Valuation Area
   I_BUKRS =  "Company Code
   I_MATNR =  "Material Number
   I_BWTAR =  "Valuation Type
   I_WERKS =  "Plant

TABLES
   IT_OUTPUTS_CR =  "Material Ledger Currency Table for Order History
   IT_KEPH =  "ML: Cost Component Split (Components) for Order History
   ET_KEPH_WEWRT =  "ML: Cost Component Split (Components) for Order History
*  ET_KEPH_REWRT =  "ML: Cost Component Split (Components) for Order History
*  ET_KEPH_AREWR =  "ML: Cost Component Split (Components) for Order History

EXCEPTIONS
   INVALID_CALL = 1
.



IMPORTING Parameters details for CKMO_SPLIT_ADD

I_AKT_POPER - Posting Period

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

I_AKT_BDATJ - Posting date YYYY

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

I_BWKEY - Valuation Area

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

I_BUKRS - Company Code

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

I_MATNR - Material Number

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

I_BWTAR - Valuation Type

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

I_WERKS - Plant

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

TABLES Parameters details for CKMO_SPLIT_ADD

IT_OUTPUTS_CR - Material Ledger Currency Table for Order History

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

IT_KEPH - ML: Cost Component Split (Components) for Order History

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

ET_KEPH_WEWRT - ML: Cost Component Split (Components) for Order History

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

ET_KEPH_REWRT - ML: Cost Component Split (Components) for Order History

Data type: MLAUFKEPH
Optional: Yes
Call by Reference: Yes

ET_KEPH_AREWR - ML: Cost Component Split (Components) for Order History

Data type: MLAUFKEPH
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

INVALID_CALL -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CKMO_SPLIT_ADD 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_akt_poper  TYPE POPER, "   
lv_invalid_call  TYPE POPER, "   
lt_it_outputs_cr  TYPE STANDARD TABLE OF MLAUFCRPP, "   
lt_it_keph  TYPE STANDARD TABLE OF MLAUFKEPH, "   
lv_i_akt_bdatj  TYPE BDATJ, "   
lv_i_bwkey  TYPE BWKEY, "   
lt_et_keph_wewrt  TYPE STANDARD TABLE OF MLAUFKEPH, "   
lv_i_bukrs  TYPE BUKRS, "   
lt_et_keph_rewrt  TYPE STANDARD TABLE OF MLAUFKEPH, "   
lv_i_matnr  TYPE MATNR, "   
lt_et_keph_arewr  TYPE STANDARD TABLE OF MLAUFKEPH, "   
lv_i_bwtar  TYPE BWTAR_D, "   
lv_i_werks  TYPE WERKS_D. "   

  CALL FUNCTION 'CKMO_SPLIT_ADD'  "
    EXPORTING
         I_AKT_POPER = lv_i_akt_poper
         I_AKT_BDATJ = lv_i_akt_bdatj
         I_BWKEY = lv_i_bwkey
         I_BUKRS = lv_i_bukrs
         I_MATNR = lv_i_matnr
         I_BWTAR = lv_i_bwtar
         I_WERKS = lv_i_werks
    TABLES
         IT_OUTPUTS_CR = lt_it_outputs_cr
         IT_KEPH = lt_it_keph
         ET_KEPH_WEWRT = lt_et_keph_wewrt
         ET_KEPH_REWRT = lt_et_keph_rewrt
         ET_KEPH_AREWR = lt_et_keph_arewr
    EXCEPTIONS
        INVALID_CALL = 1
. " CKMO_SPLIT_ADD




ABAP code using 7.40 inline data declarations to call FM CKMO_SPLIT_ADD

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.

 
 
 
 
 
 
 
 
 
 
 
 
 


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!