SAP K_BASICCOSTS_COMMIT Function Module for









K_BASICCOSTS_COMMIT is a standard k basiccosts commit 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 k basiccosts commit FM, simply by entering the name K_BASICCOSTS_COMMIT into the relevant SAP transaction such as SE37 or SE38.

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



Function K_BASICCOSTS_COMMIT 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 'K_BASICCOSTS_COMMIT'"
EXPORTING
* PAR_AWEPS = ' ' "
* PAR_GJAHR2 = "
* PAR_VBMOD = ' ' "
* PAR_AWWTB = '3C' "
PAR_AWVRS = "
PAR_OBJNR = "
PAR_KOKRS = "
PAR_POPER1 = "
* PAR_POPER2 = "
PAR_GJAHR1 = "

TABLES
PTA_KV0123 = "

EXCEPTIONS
NO_INSERT = 1 COSTS_IMPOSSIBLE = 2 SYSTEM_ERROR = 3
.



IMPORTING Parameters details for K_BASICCOSTS_COMMIT

PAR_AWEPS -

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

PAR_GJAHR2 -

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

PAR_VBMOD -

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

PAR_AWWTB -

Data type: TKV09-AWWTB
Default: '3C'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PAR_AWVRS -

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

PAR_OBJNR -

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

PAR_KOKRS -

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

PAR_POPER1 -

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

PAR_POPER2 -

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

PAR_GJAHR1 -

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

TABLES Parameters details for K_BASICCOSTS_COMMIT

PTA_KV0123 -

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

EXCEPTIONS details

NO_INSERT -

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

COSTS_IMPOSSIBLE -

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

SYSTEM_ERROR -

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

Copy and paste ABAP code example for K_BASICCOSTS_COMMIT 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_no_insert  TYPE STRING, "   
lv_par_aweps  TYPE TKV01-AWEPS, "   SPACE
lt_pta_kv0123  TYPE STANDARD TABLE OF KV012, "   
lv_par_gjahr2  TYPE T009B-BDATJ, "   
lv_par_vbmod  TYPE KV042-XFELD, "   SPACE
lv_costs_impossible  TYPE KV042, "   
lv_par_awwtb  TYPE TKV09-AWWTB, "   '3C'
lv_system_error  TYPE TKV09, "   
lv_par_awvrs  TYPE TKV09-AWVRS, "   
lv_par_objnr  TYPE KV012-OBJNR, "   
lv_par_kokrs  TYPE TKV09-KOKRS, "   
lv_par_poper1  TYPE T009B-POPER, "   
lv_par_poper2  TYPE T009B-POPER, "   
lv_par_gjahr1  TYPE T009B-BDATJ. "   

  CALL FUNCTION 'K_BASICCOSTS_COMMIT'  "
    EXPORTING
         PAR_AWEPS = lv_par_aweps
         PAR_GJAHR2 = lv_par_gjahr2
         PAR_VBMOD = lv_par_vbmod
         PAR_AWWTB = lv_par_awwtb
         PAR_AWVRS = lv_par_awvrs
         PAR_OBJNR = lv_par_objnr
         PAR_KOKRS = lv_par_kokrs
         PAR_POPER1 = lv_par_poper1
         PAR_POPER2 = lv_par_poper2
         PAR_GJAHR1 = lv_par_gjahr1
    TABLES
         PTA_KV0123 = lt_pta_kv0123
    EXCEPTIONS
        NO_INSERT = 1
        COSTS_IMPOSSIBLE = 2
        SYSTEM_ERROR = 3
. " K_BASICCOSTS_COMMIT




ABAP code using 7.40 inline data declarations to call FM K_BASICCOSTS_COMMIT

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 AWEPS FROM TKV01 INTO @DATA(ld_par_aweps).
DATA(ld_par_aweps) = ' '.
 
 
"SELECT single BDATJ FROM T009B INTO @DATA(ld_par_gjahr2).
 
"SELECT single XFELD FROM KV042 INTO @DATA(ld_par_vbmod).
DATA(ld_par_vbmod) = ' '.
 
 
"SELECT single AWWTB FROM TKV09 INTO @DATA(ld_par_awwtb).
DATA(ld_par_awwtb) = '3C'.
 
 
"SELECT single AWVRS FROM TKV09 INTO @DATA(ld_par_awvrs).
 
"SELECT single OBJNR FROM KV012 INTO @DATA(ld_par_objnr).
 
"SELECT single KOKRS FROM TKV09 INTO @DATA(ld_par_kokrs).
 
"SELECT single POPER FROM T009B INTO @DATA(ld_par_poper1).
 
"SELECT single POPER FROM T009B INTO @DATA(ld_par_poper2).
 
"SELECT single BDATJ FROM T009B INTO @DATA(ld_par_gjahr1).
 


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!