BNK_API_CHECK_EXIST_RELEASE SAP Function module - Release tool: Check if the object is in release

BNK_API_CHECK_EXIST_RELEASE 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 BNK_API_CHECK_EXIST_RELEASE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM BNK_API_CHECK_EXIST_RELEASE - BNK API CHECK EXIST RELEASE

CALL FUNCTION 'BNK_API_CHECK_EXIST_RELEASE' "Release tool: Check if the object is in release
  EXPORTING
*   i_rel_obj_cat = 'BNK_COM'   " bca_dte_object_cat  Release Object
    i_batch_guid =              " bnk_com_btch_guid  GUID to identify the batch
    i_batch_id =                " bnk_com_btch_no  Batch Identification Number
*   i_item_no =                 " bnk_com_btch_cnt  Item Count Number
  IMPORTING
    e_flg_exists =              " bnk_com_boolean  Boolean Variable
    .  "  BNK_API_CHECK_EXIST_RELEASE

ABAP code example for Function Module BNK_API_CHECK_EXIST_RELEASE

The ABAP code below is a full code listing to execute function module BNK_API_CHECK_EXIST_RELEASE 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_flg_exists  
 
 TYPE BNK_COM_BOOLEAN
.


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

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

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

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

CALL FUNCTION 'BNK_API_CHECK_EXIST_RELEASE'
  EXPORTING
*   i_rel_obj_cat =              ld_i_rel_obj_cat
    i_batch_guid =               ld_i_batch_guid
    i_batch_id =                 ld_i_batch_id
*   i_item_no =                  ld_i_item_no
  IMPORTING
    e_flg_exists =               ld_e_flg_exists
    .  "  BNK_API_CHECK_EXIST_RELEASE

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_flg_exists
 
 TYPE BNK_COM_BOOLEAN ,
ld_i_rel_obj_cat
 
 TYPE BCA_DTE_OBJECT_CAT ,
ld_i_batch_guid
 
 TYPE BNK_COM_BTCH_GUID ,
ld_i_batch_id
 
 TYPE BNK_COM_BTCH_NO ,
ld_i_item_no
 
 TYPE BNK_COM_BTCH_CNT .


ld_i_rel_obj_cat = 'Check type of data required'.
ld_i_batch_guid = 'Check type of data required'.
ld_i_batch_id = 'Check type of data required'.
ld_i_item_no = 'Check type of data required'.