SAP K_SETTLEMENT_RULE_CHECK Function Module for









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

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



Function K_SETTLEMENT_RULE_CHECK 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_RULE_CHECK'"
EXPORTING
* ADD_PARA = ' ' "Additional info on settlement sender
* XFUNCSAVE = ' ' "
* APROF = ' ' "Settlement profile
OBJNR = "Object number of the settlement rule
* TEST_BUKRS = ' ' "Company code (for validation)
* TEST_KOKRS = ' ' "Controlling area (for validation)
* RWIN_AUFRUF = 'X' "Access RWIN to check receiver
* I_PFLEGE = ' ' "'X' -> You can change the rules
* IVPRO = ' ' "Investment Profile
* XREVENUE = ' ' "Flag: sender with revenues

IMPORTING
XSAVE = "Flag: Rules were changed

EXCEPTIONS
ERROR_OCCURRED = 1 NO_RULE_FOR_OBJNR = 2 WARNING_OCCURRED = 3 INTERNAL_PROBLEMS = 4
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLKOBS_001 Creation of Settlement Rules: Strategies

IMPORTING Parameters details for K_SETTLEMENT_RULE_CHECK

ADD_PARA - Additional info on settlement sender

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

XFUNCSAVE -

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

APROF - Settlement profile

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

OBJNR - Object number of the settlement rule

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

TEST_BUKRS - Company code (for validation)

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

TEST_KOKRS - Controlling area (for validation)

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

RWIN_AUFRUF - Access RWIN to check receiver

Data type: DKOBR-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_PFLEGE - 'X' -> You can change the rules

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

IVPRO - Investment Profile

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

XREVENUE - Flag: sender with revenues

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

EXPORTING Parameters details for K_SETTLEMENT_RULE_CHECK

XSAVE - Flag: Rules were changed

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

EXCEPTIONS details

ERROR_OCCURRED - Error occurred

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

NO_RULE_FOR_OBJNR - No rule is available for the object number

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

WARNING_OCCURRED - Warning message occurred

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

INTERNAL_PROBLEMS - Internal Program Error

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

Copy and paste ABAP code example for K_SETTLEMENT_RULE_CHECK 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_xsave  TYPE C, "   
lv_add_para  TYPE COBR_INFO, "   SPACE
lv_error_occurred  TYPE COBR_INFO, "   
lv_xfuncsave  TYPE DKOBR-XFELD, "   SPACE
lv_aprof  TYPE COBRA-APROF, "   SPACE
lv_no_rule_for_objnr  TYPE COBRA, "   
lv_objnr  TYPE COBRA-OBJNR, "   
lv_warning_occurred  TYPE COBRA, "   
lv_test_bukrs  TYPE COBRB-BUKRS, "   SPACE
lv_internal_problems  TYPE COBRB, "   
lv_test_kokrs  TYPE COBRB-KOKRS, "   SPACE
lv_rwin_aufruf  TYPE DKOBR-XFELD, "   'X'
lv_i_pflege  TYPE C, "   SPACE
lv_ivpro  TYPE TAPRF-IVPRO, "   SPACE
lv_xrevenue  TYPE DKOBR-XFELD. "   SPACE

  CALL FUNCTION 'K_SETTLEMENT_RULE_CHECK'  "
    EXPORTING
         ADD_PARA = lv_add_para
         XFUNCSAVE = lv_xfuncsave
         APROF = lv_aprof
         OBJNR = lv_objnr
         TEST_BUKRS = lv_test_bukrs
         TEST_KOKRS = lv_test_kokrs
         RWIN_AUFRUF = lv_rwin_aufruf
         I_PFLEGE = lv_i_pflege
         IVPRO = lv_ivpro
         XREVENUE = lv_xrevenue
    IMPORTING
         XSAVE = lv_xsave
    EXCEPTIONS
        ERROR_OCCURRED = 1
        NO_RULE_FOR_OBJNR = 2
        WARNING_OCCURRED = 3
        INTERNAL_PROBLEMS = 4
. " K_SETTLEMENT_RULE_CHECK




ABAP code using 7.40 inline data declarations to call FM K_SETTLEMENT_RULE_CHECK

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_add_para) = ' '.
 
 
"SELECT single XFELD FROM DKOBR INTO @DATA(ld_xfuncsave).
DATA(ld_xfuncsave) = ' '.
 
"SELECT single APROF FROM COBRA INTO @DATA(ld_aprof).
DATA(ld_aprof) = ' '.
 
 
"SELECT single OBJNR FROM COBRA INTO @DATA(ld_objnr).
 
 
"SELECT single BUKRS FROM COBRB INTO @DATA(ld_test_bukrs).
DATA(ld_test_bukrs) = ' '.
 
 
"SELECT single KOKRS FROM COBRB INTO @DATA(ld_test_kokrs).
DATA(ld_test_kokrs) = ' '.
 
"SELECT single XFELD FROM DKOBR INTO @DATA(ld_rwin_aufruf).
DATA(ld_rwin_aufruf) = 'X'.
 
DATA(ld_i_pflege) = ' '.
 
"SELECT single IVPRO FROM TAPRF INTO @DATA(ld_ivpro).
DATA(ld_ivpro) = ' '.
 
"SELECT single XFELD FROM DKOBR INTO @DATA(ld_xrevenue).
DATA(ld_xrevenue) = ' '.
 


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!