SAP BKK_CLOSING_UPDATE_NEXT_DATE Function Module for Update Next Date and Insert Change Document With New Due Date









BKK_CLOSING_UPDATE_NEXT_DATE is a standard bkk closing update next date SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update Next Date and Insert Change Document With New Due Date 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 closing update next date FM, simply by entering the name BKK_CLOSING_UPDATE_NEXT_DATE into the relevant SAP transaction such as SE37 or SE38.

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



Function BKK_CLOSING_UPDATE_NEXT_DATE 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_CLOSING_UPDATE_NEXT_DATE'"Update Next Date and Insert Change Document With New Due Date
  EXPORTING
   I_BKKRS =  "Bank Area
   I_ACNUM_INT =  "Internal Account Number
*  I_CLOS_TYP = '0001' "Balancing Type
   I_NEW_NEXT_DATE =  "New Date
*  I_FLG_NO_COMMIT = ' ' "COMMIT Indicator
*  I_FLG_IN_UPDATE_TASK = ' ' "
*  I_FLG_ONLY_WHEN_END_OF_TERM = ' ' "

 IMPORTING
   E_RC =  "0: All OK, <>0: Error
.



IMPORTING Parameters details for BKK_CLOSING_UPDATE_NEXT_DATE

I_BKKRS - Bank Area

Data type: BKKM2-BKKRS
Optional: No
Call by Reference: No ( called with pass by value option)

I_ACNUM_INT - Internal Account Number

Data type: BKKM2-ACNUM_INT
Optional: No
Call by Reference: No ( called with pass by value option)

I_CLOS_TYP - Balancing Type

Data type: BKKM2-CLOS_TYP
Default: '0001'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_NEW_NEXT_DATE - New Date

Data type: BKKM2-NEXT_DATE
Optional: No
Call by Reference: No ( called with pass by value option)

I_FLG_NO_COMMIT - COMMIT Indicator

Data type: BOOLE-BOOLE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_IN_UPDATE_TASK -

Data type: BOOLE-BOOLE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_FLG_ONLY_WHEN_END_OF_TERM -

Data type: BOOLE-BOOLE
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BKK_CLOSING_UPDATE_NEXT_DATE

E_RC - 0: All OK, <>0: Error

Data type: SY-SUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BKK_CLOSING_UPDATE_NEXT_DATE 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_rc  TYPE SY-SUBRC, "   
lv_i_bkkrs  TYPE BKKM2-BKKRS, "   
lv_i_acnum_int  TYPE BKKM2-ACNUM_INT, "   
lv_i_clos_typ  TYPE BKKM2-CLOS_TYP, "   '0001'
lv_i_new_next_date  TYPE BKKM2-NEXT_DATE, "   
lv_i_flg_no_commit  TYPE BOOLE-BOOLE, "   ' '
lv_i_flg_in_update_task  TYPE BOOLE-BOOLE, "   ' '
lv_i_flg_only_when_end_of_term  TYPE BOOLE-BOOLE. "   ' '

  CALL FUNCTION 'BKK_CLOSING_UPDATE_NEXT_DATE'  "Update Next Date and Insert Change Document With New Due Date
    EXPORTING
         I_BKKRS = lv_i_bkkrs
         I_ACNUM_INT = lv_i_acnum_int
         I_CLOS_TYP = lv_i_clos_typ
         I_NEW_NEXT_DATE = lv_i_new_next_date
         I_FLG_NO_COMMIT = lv_i_flg_no_commit
         I_FLG_IN_UPDATE_TASK = lv_i_flg_in_update_task
         I_FLG_ONLY_WHEN_END_OF_TERM = lv_i_flg_only_when_end_of_term
    IMPORTING
         E_RC = lv_e_rc
. " BKK_CLOSING_UPDATE_NEXT_DATE




ABAP code using 7.40 inline data declarations to call FM BKK_CLOSING_UPDATE_NEXT_DATE

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 SUBRC FROM SY INTO @DATA(ld_e_rc).
 
"SELECT single BKKRS FROM BKKM2 INTO @DATA(ld_i_bkkrs).
 
"SELECT single ACNUM_INT FROM BKKM2 INTO @DATA(ld_i_acnum_int).
 
"SELECT single CLOS_TYP FROM BKKM2 INTO @DATA(ld_i_clos_typ).
DATA(ld_i_clos_typ) = '0001'.
 
"SELECT single NEXT_DATE FROM BKKM2 INTO @DATA(ld_i_new_next_date).
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_no_commit).
DATA(ld_i_flg_no_commit) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_in_update_task).
DATA(ld_i_flg_in_update_task) = ' '.
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_flg_only_when_end_of_term).
DATA(ld_i_flg_only_when_end_of_term) = ' '.
 


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!