SAP CACS_DEC_DOUBLECLICKED_BDT Function Module for Commns: BDT Condition Maintenance









CACS_DEC_DOUBLECLICKED_BDT is a standard cacs dec doubleclicked bdt SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Commns: BDT Condition Maintenance 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 doubleclicked bdt FM, simply by entering the name CACS_DEC_DOUBLECLICKED_BDT 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_DOUBLECLICKED_BDT 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_DOUBLECLICKED_BDT'"Commns: BDT Condition Maintenance
EXPORTING
I_NODE_ID = "Tree Control: Node Key
I_COND_APPLICATION = "Application

IMPORTING
E_MSG_ID = "Message Class
E_MSG_TY = "Message Type
E_MSG_NO = "Message Number
E_FLG_EXIT = "
.



IMPORTING Parameters details for CACS_DEC_DOUBLECLICKED_BDT

I_NODE_ID - Tree Control: Node Key

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

I_COND_APPLICATION - Application

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

EXPORTING Parameters details for CACS_DEC_DOUBLECLICKED_BDT

E_MSG_ID - Message Class

Data type: SY-MSGID
Optional: No
Call by Reference: Yes

E_MSG_TY - Message Type

Data type: SY-MSGTY
Optional: No
Call by Reference: Yes

E_MSG_NO - Message Number

Data type: SY-MSGNO
Optional: No
Call by Reference: Yes

E_FLG_EXIT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CACS_DEC_DOUBLECLICKED_BDT 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_msg_id  TYPE SY-MSGID, "   
lv_i_node_id  TYPE TV_NODEKEY, "   
lv_e_msg_ty  TYPE SY-MSGTY, "   
lv_i_cond_application  TYPE CACS_BR_KAPPL, "   
lv_e_msg_no  TYPE SY-MSGNO, "   
lv_e_flg_exit  TYPE SY. "   

  CALL FUNCTION 'CACS_DEC_DOUBLECLICKED_BDT'  "Commns: BDT Condition Maintenance
    EXPORTING
         I_NODE_ID = lv_i_node_id
         I_COND_APPLICATION = lv_i_cond_application
    IMPORTING
         E_MSG_ID = lv_e_msg_id
         E_MSG_TY = lv_e_msg_ty
         E_MSG_NO = lv_e_msg_no
         E_FLG_EXIT = lv_e_flg_exit
. " CACS_DEC_DOUBLECLICKED_BDT




ABAP code using 7.40 inline data declarations to call FM CACS_DEC_DOUBLECLICKED_BDT

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 MSGID FROM SY INTO @DATA(ld_e_msg_id).
 
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_e_msg_ty).
 
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_e_msg_no).
 
 


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!