SAP K_SETTLEMENT_GROUP_PROCESS Function Module for









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

Function Group: KO72
Program Name: SAPLKO72
Main Program: SAPLKO72
Appliation area: D
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function K_SETTLEMENT_GROUP_PROCESS 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_SETTLEMENT_GROUP_PROCESS'"
  EXPORTING
   I_AUAK =  "
   I_CONTROL =  "
   IT_REM_OBJ =  "
   IT_TRACE_OBJ =  "
   IT_SETYPTAB =  "
*  I_NO_COMMIT = ' ' "

 IMPORTING
   E_LST =  "

CHANGING
   CT_SET =  "
   CT_LATE_OBJ =  "
   CT_ADD_SDR =  "
   CT_BEL_ALL =  "
   CT_MATNR =  "
   CT_WSUM =  "
   CT_GSUM =  "

TABLES
   IT_OBJTAB =  "
.



IMPORTING Parameters details for K_SETTLEMENT_GROUP_PROCESS

I_AUAK -

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

I_CONTROL -

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

IT_REM_OBJ -

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

IT_TRACE_OBJ -

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

IT_SETYPTAB -

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

I_NO_COMMIT -

Data type: C
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for K_SETTLEMENT_GROUP_PROCESS

E_LST -

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

CHANGING Parameters details for K_SETTLEMENT_GROUP_PROCESS

CT_SET -

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

CT_LATE_OBJ -

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

CT_ADD_SDR -

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

CT_BEL_ALL -

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

CT_MATNR -

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

CT_WSUM -

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

CT_GSUM -

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

TABLES Parameters details for K_SETTLEMENT_GROUP_PROCESS

IT_OBJTAB -

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

Copy and paste ABAP code example for K_SETTLEMENT_GROUP_PROCESS 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_lst  TYPE KABR_LST, "   
lv_ct_set  TYPE KABRT_AUFSEL_TABLE, "   
lv_i_auak  TYPE AUAK, "   
lt_it_objtab  TYPE STANDARD TABLE OF JSTO_PRE, "   
lv_i_control  TYPE KABR_CONTROL, "   
lv_ct_late_obj  TYPE KABRT_OBJTAB_TABLE, "   
lv_ct_add_sdr  TYPE KABRT_OBJTAB_TABLE, "   
lv_it_rem_obj  TYPE KABRT_OBJTAB_TABLE, "   
lv_ct_bel_all  TYPE KABRT_BEL_ALL_TABLE, "   
lv_it_trace_obj  TYPE KABRT_OBJTAB_TABLE, "   
lv_ct_matnr  TYPE KABRT_COSE_SEL_TABLE, "   
lv_it_setyptab  TYPE KABRT_SETYP_TABLE, "   
lv_ct_wsum  TYPE KABRT_WSUM_TABLE, "   
lv_i_no_commit  TYPE C, "   ' '
lv_ct_gsum  TYPE KABRT_GSUM_TABLE. "   

  CALL FUNCTION 'K_SETTLEMENT_GROUP_PROCESS'  "
    EXPORTING
         I_AUAK = lv_i_auak
         I_CONTROL = lv_i_control
         IT_REM_OBJ = lv_it_rem_obj
         IT_TRACE_OBJ = lv_it_trace_obj
         IT_SETYPTAB = lv_it_setyptab
         I_NO_COMMIT = lv_i_no_commit
    IMPORTING
         E_LST = lv_e_lst
    CHANGING
         CT_SET = lv_ct_set
         CT_LATE_OBJ = lv_ct_late_obj
         CT_ADD_SDR = lv_ct_add_sdr
         CT_BEL_ALL = lv_ct_bel_all
         CT_MATNR = lv_ct_matnr
         CT_WSUM = lv_ct_wsum
         CT_GSUM = lv_ct_gsum
    TABLES
         IT_OBJTAB = lt_it_objtab
. " K_SETTLEMENT_GROUP_PROCESS




ABAP code using 7.40 inline data declarations to call FM K_SETTLEMENT_GROUP_PROCESS

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_i_no_commit) = ' '.
 
 


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!