SAP CACS_DEC_GET_SAVE_FLAG Function Module for FDT: Save dec table









CACS_DEC_GET_SAVE_FLAG is a standard cacs dec get save flag SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for FDT: Save dec table 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 dec get save flag FM, simply by entering the name CACS_DEC_GET_SAVE_FLAG into the relevant SAP transaction such as SE37 or SE38.

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



Function CACS_DEC_GET_SAVE_FLAG 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_DEC_GET_SAVE_FLAG'"FDT: Save dec table
EXPORTING
* I_IND_CONTRACT = "Contract identification key
* I_COND_APPLICATION = "Application
* I_ACTIVITY = "Activity Category
* I_CONTRACT_CURRENCY = "Contract Currency Key
* I_FLG_CURR_CHANGED = "General Flag
* I_FLG_CTRT_LONGER = "General Flag
* I_FLG_CTRT_SHORTER = "General Flag
* I_FLG_CTRT_EARLIER = "General Flag
* I_FLG_CTRT_ACTIVE = "General Flag
* I_FLG_VERS_BRING_FWD = "General Flag
* I_FLG_DELIMIT = "General Flag
* I_STD_CONTRACT = "Contract identification key
* I_FLG_AGR_ONLY_CURRENT = "General Flag
* I_BUSI_BEGIN_TEMPLATE = "Effective from
* I_TECH_BEGIN_TEMPLATE = "Technically Valid From
* I_BUSI_BEGIN_ACTIV = "Effective from
* I_TECH_BEGIN_ACTIV = "Technically Valid From
* I_STATUS_WORK = "Object Version Processing Status
* I_BUCAGR = "Agreement Number
* I_STCAGR = "Standard Agreement Number
* I_VERSION = "Version of Master Data or Customizing Object
* I_CREA_W_TEMPL = "General Flag
* I_BUSI_BEGIN = "Effective from
* I_BUSI_END = "Effective Until (Time Stamp: YYYY.MM.DD hh:mm:ss)
* I_OLD_BUSI_BEGIN = "Effective from
* I_OLD_BUSI_END = "Effective Until (Time Stamp: YYYY.MM.DD hh:mm:ss)
* I_TECH_BEGIN = "Technically Valid From
* I_TECH_END = "Technically Valid To (Time Stamp: JJJJ.MM.TT hh:mm:ss)
* I_CACS_APPLICATION = "Commission Application (ICM)

IMPORTING
E_SAVE_FLAG = "General Flag
.



IMPORTING Parameters details for CACS_DEC_GET_SAVE_FLAG

I_IND_CONTRACT - Contract identification key

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

I_COND_APPLICATION - Application

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

I_ACTIVITY - Activity Category

Data type: TBZ0K-AKTYP
Optional: Yes
Call by Reference: Yes

I_CONTRACT_CURRENCY - Contract Currency Key

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

I_FLG_CURR_CHANGED - General Flag

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

I_FLG_CTRT_LONGER - General Flag

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

I_FLG_CTRT_SHORTER - General Flag

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

I_FLG_CTRT_EARLIER - General Flag

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

I_FLG_CTRT_ACTIVE - General Flag

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

I_FLG_VERS_BRING_FWD - General Flag

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

I_FLG_DELIMIT - General Flag

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

I_STD_CONTRACT - Contract identification key

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

I_FLG_AGR_ONLY_CURRENT - General Flag

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

I_BUSI_BEGIN_TEMPLATE - Effective from

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

I_TECH_BEGIN_TEMPLATE - Technically Valid From

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

I_BUSI_BEGIN_ACTIV - Effective from

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

I_TECH_BEGIN_ACTIV - Technically Valid From

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

I_STATUS_WORK - Object Version Processing Status

Data type: CACS_S_VERS1-STATUS_WORK
Optional: Yes
Call by Reference: Yes

I_BUCAGR - Agreement Number

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

I_STCAGR - Standard Agreement Number

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

I_VERSION - Version of Master Data or Customizing Object

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

I_CREA_W_TEMPL - General Flag

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

I_BUSI_BEGIN - Effective from

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

I_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

I_OLD_BUSI_BEGIN - Effective from

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

I_OLD_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

I_TECH_BEGIN - Technically Valid From

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

I_TECH_END - Technically Valid To (Time Stamp: JJJJ.MM.TT hh:mm:ss)

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

I_CACS_APPLICATION - Commission Application (ICM)

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

EXPORTING Parameters details for CACS_DEC_GET_SAVE_FLAG

E_SAVE_FLAG - General Flag

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

Copy and paste ABAP code example for CACS_DEC_GET_SAVE_FLAG 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_save_flag  TYPE FLAG, "   
lv_i_ind_contract  TYPE CACS_CONTR-CONTRACT_ID, "   
lv_i_cond_application  TYPE CACS_BR_KAPPL, "   
lv_i_activity  TYPE TBZ0K-AKTYP, "   
lv_i_contract_currency  TYPE CACSCONCURR, "   
lv_i_flg_curr_changed  TYPE FLAG, "   
lv_i_flg_ctrt_longer  TYPE FLAG, "   
lv_i_flg_ctrt_shorter  TYPE FLAG, "   
lv_i_flg_ctrt_earlier  TYPE FLAG, "   
lv_i_flg_ctrt_active  TYPE FLAG, "   
lv_i_flg_vers_bring_fwd  TYPE FLAG, "   
lv_i_flg_delimit  TYPE FLAG, "   
lv_i_std_contract  TYPE CACS_CONTR-CONTRACT_ID, "   
lv_i_flg_agr_only_current  TYPE FLAG, "   
lv_i_busi_begin_template  TYPE CACS_S_VERS-BUSI_BEGIN, "   
lv_i_tech_begin_template  TYPE CACS_S_VERS-TECH_BEGIN, "   
lv_i_busi_begin_activ  TYPE CACS_S_VERS-BUSI_BEGIN, "   
lv_i_tech_begin_activ  TYPE CACS_S_VERS-TECH_BEGIN, "   
lv_i_status_work  TYPE CACS_S_VERS1-STATUS_WORK, "   
lv_i_bucagr  TYPE CACS_BUCAGR_ID, "   
lv_i_stcagr  TYPE CACS_STCAGR_ID, "   
lv_i_version  TYPE CACSVERSION, "   
lv_i_crea_w_templ  TYPE FLAG, "   
lv_i_busi_begin  TYPE CACS_S_VERS-BUSI_BEGIN, "   
lv_i_busi_end  TYPE CACS_S_VERS-BUSI_END, "   
lv_i_old_busi_begin  TYPE CACS_S_VERS-BUSI_BEGIN, "   
lv_i_old_busi_end  TYPE CACS_S_VERS-BUSI_END, "   
lv_i_tech_begin  TYPE CACS_S_VERS-TECH_BEGIN, "   
lv_i_tech_end  TYPE CACS_S_VERS-TECH_END, "   
lv_i_cacs_application  TYPE CACSAPPL. "   

  CALL FUNCTION 'CACS_DEC_GET_SAVE_FLAG'  "FDT: Save dec table
    EXPORTING
         I_IND_CONTRACT = lv_i_ind_contract
         I_COND_APPLICATION = lv_i_cond_application
         I_ACTIVITY = lv_i_activity
         I_CONTRACT_CURRENCY = lv_i_contract_currency
         I_FLG_CURR_CHANGED = lv_i_flg_curr_changed
         I_FLG_CTRT_LONGER = lv_i_flg_ctrt_longer
         I_FLG_CTRT_SHORTER = lv_i_flg_ctrt_shorter
         I_FLG_CTRT_EARLIER = lv_i_flg_ctrt_earlier
         I_FLG_CTRT_ACTIVE = lv_i_flg_ctrt_active
         I_FLG_VERS_BRING_FWD = lv_i_flg_vers_bring_fwd
         I_FLG_DELIMIT = lv_i_flg_delimit
         I_STD_CONTRACT = lv_i_std_contract
         I_FLG_AGR_ONLY_CURRENT = lv_i_flg_agr_only_current
         I_BUSI_BEGIN_TEMPLATE = lv_i_busi_begin_template
         I_TECH_BEGIN_TEMPLATE = lv_i_tech_begin_template
         I_BUSI_BEGIN_ACTIV = lv_i_busi_begin_activ
         I_TECH_BEGIN_ACTIV = lv_i_tech_begin_activ
         I_STATUS_WORK = lv_i_status_work
         I_BUCAGR = lv_i_bucagr
         I_STCAGR = lv_i_stcagr
         I_VERSION = lv_i_version
         I_CREA_W_TEMPL = lv_i_crea_w_templ
         I_BUSI_BEGIN = lv_i_busi_begin
         I_BUSI_END = lv_i_busi_end
         I_OLD_BUSI_BEGIN = lv_i_old_busi_begin
         I_OLD_BUSI_END = lv_i_old_busi_end
         I_TECH_BEGIN = lv_i_tech_begin
         I_TECH_END = lv_i_tech_end
         I_CACS_APPLICATION = lv_i_cacs_application
    IMPORTING
         E_SAVE_FLAG = lv_e_save_flag
. " CACS_DEC_GET_SAVE_FLAG




ABAP code using 7.40 inline data declarations to call FM CACS_DEC_GET_SAVE_FLAG

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 CONTRACT_ID FROM CACS_CONTR INTO @DATA(ld_i_ind_contract).
 
 
"SELECT single AKTYP FROM TBZ0K INTO @DATA(ld_i_activity).
 
 
 
 
 
 
 
 
 
"SELECT single CONTRACT_ID FROM CACS_CONTR INTO @DATA(ld_i_std_contract).
 
 
"SELECT single BUSI_BEGIN FROM CACS_S_VERS INTO @DATA(ld_i_busi_begin_template).
 
"SELECT single TECH_BEGIN FROM CACS_S_VERS INTO @DATA(ld_i_tech_begin_template).
 
"SELECT single BUSI_BEGIN FROM CACS_S_VERS INTO @DATA(ld_i_busi_begin_activ).
 
"SELECT single TECH_BEGIN FROM CACS_S_VERS INTO @DATA(ld_i_tech_begin_activ).
 
"SELECT single STATUS_WORK FROM CACS_S_VERS1 INTO @DATA(ld_i_status_work).
 
 
 
 
 
"SELECT single BUSI_BEGIN FROM CACS_S_VERS INTO @DATA(ld_i_busi_begin).
 
"SELECT single BUSI_END FROM CACS_S_VERS INTO @DATA(ld_i_busi_end).
 
"SELECT single BUSI_BEGIN FROM CACS_S_VERS INTO @DATA(ld_i_old_busi_begin).
 
"SELECT single BUSI_END FROM CACS_S_VERS INTO @DATA(ld_i_old_busi_end).
 
"SELECT single TECH_BEGIN FROM CACS_S_VERS INTO @DATA(ld_i_tech_begin).
 
"SELECT single TECH_END FROM CACS_S_VERS INTO @DATA(ld_i_tech_end).
 
 


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!