BKK_ACCNT_CHECK_FUNCTION SAP Function module - Checks Whether A Function Is Allowed on Account

BKK_ACCNT_CHECK_FUNCTION is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BKK_ACCNT_CHECK_FUNCTION into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FBK7
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BKK_ACCNT_CHECK_FUNCTION - BKK ACCNT CHECK FUNCTION

CALL FUNCTION 'BKK_ACCNT_CHECK_FUNCTION' "Checks Whether A Function Is Allowed on Account
  EXPORTING
    i_bkkrs =                   " bkk40-bkkrs   Bank Area
    i_acnum_int =               " bkk40-acnum_int  Internal Account Number
*   i_msg_accnt =               " ibkk_item-acnum_ext  Message Account Number
    i_function =                " tbkkg2-function  Function
*   i_message = 'X'             " boole-boole   Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')
*   i_prodint =                 " fipr_prodint  Internal Product ID
*   i_version =                 " fipr_version  Version of a Product
  IMPORTING
    e_return =                  " sy-subrc      0: Medium is Allowed
    .  "  BKK_ACCNT_CHECK_FUNCTION

ABAP code example for Function Module BKK_ACCNT_CHECK_FUNCTION

The ABAP code below is a full code listing to execute function module BKK_ACCNT_CHECK_FUNCTION including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_return  
 
 TYPE SY-SUBRC
.

 

SELECT single BKKRS 
  FROM BKK40 
  INTO @DATA(ld_i_bkkrs).

 

SELECT single ACNUM_INT 
  FROM BKK40 
  INTO @DATA(ld_i_acnum_int).



DATA(ld_i_msg_accnt) = some text here
 

SELECT single FUNCTION 
  FROM TBKKG2 
  INTO @DATA(ld_i_function).



DATA(ld_i_message) = some text here

DATA(ld_i_prodint) = 'Check type of data required'.

DATA(ld_i_version) = 'Check type of data required'.
.

CALL FUNCTION 'BKK_ACCNT_CHECK_FUNCTION'
  EXPORTING
    i_bkkrs =                    ld_i_bkkrs
    i_acnum_int =                ld_i_acnum_int
*   i_msg_accnt =                ld_i_msg_accnt
    i_function =                 ld_i_function
*   i_message =                  ld_i_message
*   i_prodint =                  ld_i_prodint
*   i_version =                  ld_i_version
  IMPORTING
    e_return =                   ld_e_return
    .  "  BKK_ACCNT_CHECK_FUNCTION

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_return
 
 TYPE SY-SUBRC ,
ld_i_bkkrs
 
 TYPE BKK40-BKKRS ,
ld_i_acnum_int
 
 TYPE BKK40-ACNUM_INT ,
ld_i_msg_accnt
 
 TYPE IBKK_ITEM-ACNUM_EXT ,
ld_i_function
 
 TYPE TBKKG2-FUNCTION ,
ld_i_message
 
 TYPE BOOLE-BOOLE ,
ld_i_prodint
 
 TYPE FIPR_PRODINT ,
ld_i_version
 
 TYPE FIPR_VERSION .



SELECT single BKKRS 
  FROM BKK40 
  INTO ld_i_bkkrs.


SELECT single ACNUM_INT 
  FROM BKK40 
  INTO ld_i_acnum_int.


ld_i_msg_accnt = some text here

SELECT single FUNCTION 
  FROM TBKKG2 
  INTO ld_i_function.


ld_i_message = some text here
ld_i_prodint = 'Check type of data required'.
ld_i_version = 'Check type of data required'.