SAP BKK_CHNGDOC_COND_TABEVENT Function Module for Table Event for Change Documents-Limits









BKK_CHNGDOC_COND_TABEVENT is a standard bkk chngdoc cond tabevent SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Table Event for Change Documents-Limits 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 bkk chngdoc cond tabevent FM, simply by entering the name BKK_CHNGDOC_COND_TABEVENT into the relevant SAP transaction such as SE37 or SE38.

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



Function BKK_CHNGDOC_COND_TABEVENT 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 'BKK_CHNGDOC_COND_TABEVENT'"Table Event for Change Documents-Limits
  EXPORTING
   I_OBJECTCLAS =  "Object Class
   I_TABNAME =  "Table Name
   I_TABKEY =  "Changed table record key
*  I_TABKEY_LONG =  "Table Key for CDPOS in Character 254
   I_CREATEDATE =  "Creation date of the change document
   I_CREATETIME =  "Time changed

 IMPORTING
   E_NO_TABLEKEYTEXT =  "Do Not Format Table Key
   E_TABKEYTEXT =  "
   E_NO_TABLEKEYGROUP =  "No Table Group for 'Multiple Case'
   E_TABKEYGROUP =  "Changed table record key
   E_TABKEYGROUP_LONG =  "Table Key for CDPOS in Character 254
   E_TABKEYGROUPTEXT =  "
.



IMPORTING Parameters details for BKK_CHNGDOC_COND_TABEVENT

I_OBJECTCLAS - Object Class

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

I_TABNAME - Table Name

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

I_TABKEY - Changed table record key

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

I_TABKEY_LONG - Table Key for CDPOS in Character 254

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

I_CREATEDATE - Creation date of the change document

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

I_CREATETIME - Time changed

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

EXPORTING Parameters details for BKK_CHNGDOC_COND_TABEVENT

E_NO_TABLEKEYTEXT - Do Not Format Table Key

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

E_TABKEYTEXT -

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

E_NO_TABLEKEYGROUP - No Table Group for 'Multiple Case'

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

E_TABKEYGROUP - Changed table record key

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

E_TABKEYGROUP_LONG - Table Key for CDPOS in Character 254

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

E_TABKEYGROUPTEXT -

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

Copy and paste ABAP code example for BKK_CHNGDOC_COND_TABEVENT 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_i_objectclas  TYPE CDOBJECTCL, "   
lv_e_no_tablekeytext  TYPE BANK_DTE_CD_NOTABLEKEYTEXT, "   
lv_i_tabname  TYPE TABNAME, "   
lv_e_tabkeytext  TYPE BANK_DTE_CD_TABLEKEYTEXT, "   
lv_i_tabkey  TYPE CDTABKEY, "   
lv_e_no_tablekeygroup  TYPE BANK_DTE_CD_NOTABLEKEYGROUP, "   
lv_e_tabkeygroup  TYPE CDTABKEY, "   
lv_i_tabkey_long  TYPE CDTABKEYLO, "   
lv_i_createdate  TYPE CDDATUM, "   
lv_e_tabkeygroup_long  TYPE CDTABKEYLO, "   
lv_i_createtime  TYPE CDUZEIT, "   
lv_e_tabkeygrouptext  TYPE BANK_DTE_CD_TABLEKEYTEXT. "   

  CALL FUNCTION 'BKK_CHNGDOC_COND_TABEVENT'  "Table Event for Change Documents-Limits
    EXPORTING
         I_OBJECTCLAS = lv_i_objectclas
         I_TABNAME = lv_i_tabname
         I_TABKEY = lv_i_tabkey
         I_TABKEY_LONG = lv_i_tabkey_long
         I_CREATEDATE = lv_i_createdate
         I_CREATETIME = lv_i_createtime
    IMPORTING
         E_NO_TABLEKEYTEXT = lv_e_no_tablekeytext
         E_TABKEYTEXT = lv_e_tabkeytext
         E_NO_TABLEKEYGROUP = lv_e_no_tablekeygroup
         E_TABKEYGROUP = lv_e_tabkeygroup
         E_TABKEYGROUP_LONG = lv_e_tabkeygroup_long
         E_TABKEYGROUPTEXT = lv_e_tabkeygrouptext
. " BKK_CHNGDOC_COND_TABEVENT




ABAP code using 7.40 inline data declarations to call FM BKK_CHNGDOC_COND_TABEVENT

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



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!