SAP Function Modules

comments icon Comments

BKK_API_PRENOTE_CHANGE SAP Function module - API for Prenote Change







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

Associated Function Group: BKK_PRENOTE_API
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM BKK_API_PRENOTE_CHANGE - BKK API PRENOTE CHANGE 





CALL FUNCTION 'BKK_API_PRENOTE_CHANGE' "API for Prenote Change
  EXPORTING
    i_bank_area =               " bkk_bkkrs     Bank Area
    i_acnum_int =               " bkk_accnt     Internal Account Number for Current Account
    i_prenote_id_int =          " bkk_dte_prenote_id_int  Prenote Internal ID
*   i_valid_to =                " bkk_dte_prenote_valid_to  Valid To
*   i_short_text =              " bkk_dte_prenote_shrt_txt  Short Text
*   i_long_text =               " bkk_dte_prenote_lng_txt  Long Text
*   i_exclude_auth_check =      " bkk_str_prenote_auth  Structure for Prenote Authorization
*   i_x_simulate =              " bkk_xfeld     Run in simulation mode
*   i_no_snd_for_release =      " bkk_xfeld     If set, do not send the prenote for release
  IMPORTING
    e_tab_errors =              " bkk_tab_msg_col_message  Return Code and corresponding Message
    e_flg_changed =             " bkk_xfeld     Flag if Prenote is Changed -'X'
    e_prenote_status =          " bkk_dte_prenote_status  Status of Prenote
  EXCEPTIONS
    NO_AUTHORIZATION = 1        "               No authorization for editing the prenote
    BANK_AREA_NOT_FOUND = 2     "               Bank Area not found
    ACCOUNT_NOT_FOUND = 3       "               Account not found
    PRENOTE_NOT_EXISTING = 4    "               Prenote does not exist
    PRENOTE_EXPIRED = 5         "               Prenote has expired
    INVALID_VALID_TO_DATE = 6   "               Valid To date is before posting date of the Bank Area
    LOCK_FAILURE = 7            "               Failed to lock the prenote
    OTHER_ERRORS = 8            "               Other errors
    .  "  BKK_API_PRENOTE_CHANGE

ABAP code example for Function Module BKK_API_PRENOTE_CHANGE





The ABAP code below is a full code listing to execute function module BKK_API_PRENOTE_CHANGE 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_tab_errors    TYPE BKK_TAB_MSG_COL_MESSAGE
,
ld_e_flg_changed    TYPE BKK_XFELD
,
ld_e_prenote_status    TYPE BKK_DTE_PRENOTE_STATUS
.




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

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

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

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

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

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

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

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

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

CALL FUNCTION 'BKK_API_PRENOTE_CHANGE'
  EXPORTING
    i_bank_area =                ld_i_bank_area
    i_acnum_int =                ld_i_acnum_int
    i_prenote_id_int =           ld_i_prenote_id_int
*   i_valid_to =                 ld_i_valid_to
*   i_short_text =               ld_i_short_text
*   i_long_text =                ld_i_long_text
*   i_exclude_auth_check =       ld_i_exclude_auth_check
*   i_x_simulate =               ld_i_x_simulate
*   i_no_snd_for_release =       ld_i_no_snd_for_release
  IMPORTING
    e_tab_errors =               ld_e_tab_errors
    e_flg_changed =              ld_e_flg_changed
    e_prenote_status =           ld_e_prenote_status
  EXCEPTIONS
    NO_AUTHORIZATION =           1
    BANK_AREA_NOT_FOUND =        2
    ACCOUNT_NOT_FOUND =          3
    PRENOTE_NOT_EXISTING =       4
    PRENOTE_EXPIRED =            5
    INVALID_VALID_TO_DATE =      6
    LOCK_FAILURE =               7
    OTHER_ERRORS =               8
    .  "  BKK_API_PRENOTE_CHANGE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 7. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 8. "Exception
  "Add code for exception here
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_tab_errors  TYPE BKK_TAB_MSG_COL_MESSAGE ,
ld_i_bank_area  TYPE BKK_BKKRS ,
ld_e_flg_changed  TYPE BKK_XFELD ,
ld_i_acnum_int  TYPE BKK_ACCNT ,
ld_e_prenote_status  TYPE BKK_DTE_PRENOTE_STATUS ,
ld_i_prenote_id_int  TYPE BKK_DTE_PRENOTE_ID_INT ,
ld_i_valid_to  TYPE BKK_DTE_PRENOTE_VALID_TO ,
ld_i_short_text  TYPE BKK_DTE_PRENOTE_SHRT_TXT ,
ld_i_long_text  TYPE BKK_DTE_PRENOTE_LNG_TXT ,
ld_i_exclude_auth_check  TYPE BKK_STR_PRENOTE_AUTH ,
ld_i_x_simulate  TYPE BKK_XFELD ,
ld_i_no_snd_for_release  TYPE BKK_XFELD .




ld_i_bank_area = 'Check type of data required'.
ld_i_acnum_int = 'Check type of data required'.
ld_i_prenote_id_int = 'Check type of data required'.
ld_i_valid_to = 'Check type of data required'.
ld_i_short_text = 'Check type of data required'.
ld_i_long_text = 'Check type of data required'.
ld_i_exclude_auth_check = 'Check type of data required'.
ld_i_x_simulate = 'Check type of data required'.
ld_i_no_snd_for_release = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BKK_API_PRENOTE_CHANGE or its description.


   
 

BKK_API_PRENOTE_CHANGE - API for Prenote Change
BKK_API_PRENOTE_BUTTON_CB - Callback fn. for controlling buttons
BKK_API_PAYM_ITEM_GET_LIST - RFC: Output Turnover List
BKK_API_PAYMORD_RET_CB - Callback fn. for return of release object
BKK_API_PAYMORD_RETURN_CB - Callbk fn. fr action to be performed after rel. obj. is returned
BKK_API_PAYMORD_RELEASE_CB - Callback fn. for Release Payment Order