SAP CACS_RULECHAR_SELECT_FROM_DB Function Module for Provision: read condition data from DB (lead by version)

Search SAP Function Modules

CACS_RULECHAR_SELECT_FROM_DB is a standard cacs rulechar select from db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Provision: read condition data from DB (lead by version) processing and below is the pattern details for this FM, 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 cacs rulechar select from db FM, simply by entering the name CACS_RULECHAR_SELECT_FROM_DB into the relevant SAP transaction such as SE37 or SE38.

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

Function CACS_RULECHAR_SELECT_FROM_DB 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 'CACS_RULECHAR_SELECT_FROM_DB'"Provision: read condition data from DB (lead by version)
  EXPORTING
   I_TABNAME =  "
*  LV_REMUN_AGREEMENT =  "Standard Agreement Number
*  LV_REMUN_AGREEMENT_IND =  "Agreement Number
*  I_FLG_MIGRATION =  "Migration
*  I_FLG_CALL_MODE =  "'X' = external Call
   I_STATUS_WORK =  "Editing Status of an Object
*  I_ORIGIN_STDCTRT =  "called from the standard contract maintenance
   I_ACTIVITY =  "Activity Category
   IT_KSCHL =  "Condition type
*  LV_IND_CONTRACT =  "Commission Contract Number
*  LV_STD_CONTRACT =  "Contract identification key
*  LV_TECH_BEGIN =  "Technically Valid from
*  LV_TECH_END =  "Technically Valid to (Time Stamp: YYYY.MM.DD hh:mm:ss)
*  LV_BUSI_BEGIN =  "Effective From
*  LV_BUSI_END =  "Effective Until (Time Stamp: YYYY.MM.DD hh:mm:ss)
*  LV_COND_APPLICATION =  "Application
*  LV_CACS_APPLICATION =  "Commission Application Identification

 IMPORTING
   RELAT_KNUMH =  "Commissions: Performance-Related Remuneration
   T_XSTAFF =  "Commissions: Individual Scale

CHANGING
   T_MASTER =  "Conditions from SD in Context of Standard Contract

.

IMPORTING Parameters details for CACS_RULECHAR_SELECT_FROM_DB

I_TABNAME -

Data type: DCOBJDEF-NAME
Optional: No
Call by Reference: Yes

LV_REMUN_AGREEMENT - Standard Agreement Number

Data type: CACS_S_REMUN_AGREEMENT-STCAGR_ID
Optional: Yes
Call by Reference: Yes

LV_REMUN_AGREEMENT_IND - Agreement Number

Data type: CACS_BUCAGR-BUCAGR_ID
Optional: Yes
Call by Reference: Yes

I_FLG_MIGRATION - Migration

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

I_FLG_CALL_MODE - 'X' = external Call

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

I_STATUS_WORK - Editing Status of an Object

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

I_ORIGIN_STDCTRT - called from the standard contract maintenance

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

I_ACTIVITY - Activity Category

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

IT_KSCHL - Condition type

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

LV_IND_CONTRACT - Commission Contract Number

Data type: CACS_CTRTBU-CTRTBU_ID
Optional: Yes
Call by Reference: Yes

LV_STD_CONTRACT - Contract identification key

Data type: CACS_CONTR-CONTRACT_ID
Optional: Yes
Call by Reference: Yes

LV_TECH_BEGIN - Technically Valid from

Data type: CACS_S_VERS-TECH_BEGIN
Optional: Yes
Call by Reference: Yes

LV_TECH_END - Technically Valid to (Time Stamp: YYYY.MM.DD hh:mm:ss)

Data type: CACS_S_VERS-TECH_END
Optional: Yes
Call by Reference: Yes

LV_BUSI_BEGIN - Effective From

Data type: CACS_S_VERS-BUSI_BEGIN
Optional: Yes
Call by Reference: Yes

LV_BUSI_END - Effective Until (Time Stamp: YYYY.MM.DD hh:mm:ss)

Data type: CACS_S_VERS-BUSI_END
Optional: Yes
Call by Reference: Yes

LV_COND_APPLICATION - Application

Data type: KONH-KAPPL
Optional: Yes
Call by Reference: Yes

LV_CACS_APPLICATION - Commission Application Identification

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

EXPORTING Parameters details for CACS_RULECHAR_SELECT_FROM_DB

RELAT_KNUMH - Commissions: Performance-Related Remuneration

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

T_XSTAFF - Commissions: Individual Scale

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

CHANGING Parameters details for CACS_RULECHAR_SELECT_FROM_DB

T_MASTER - Conditions from SD in Context of Standard Contract

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

Copy and paste ABAP code example for CACS_RULECHAR_SELECT_FROM_DB 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.

ABAP code using 7.40 inline data declarations to call FM CACS_RULECHAR_SELECT_FROM_DB

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