SAP BKK_ACCNT_GET_DATE_STATUS Function Module for Find Administrative Data for Account
BKK_ACCNT_GET_DATE_STATUS is a standard bkk accnt get date status SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Find Administrative Data for Account 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 accnt get date status FM, simply by entering the name BKK_ACCNT_GET_DATE_STATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBK4
Program Name: SAPLFBK4
Main Program: SAPLFBK4
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_ACCNT_GET_DATE_STATUS 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_ACCNT_GET_DATE_STATUS'"Find Administrative Data for Account.
EXPORTING
I_BKKRS = "Bank Area
I_ACNUM_INT = "Internal Account Number
IMPORTING
E_OPENDATE = "Opening Date
E_DELDATE = "Closure Date
E_BALDATE = "
E_PRODDATE = "
E_STATUS = "Status
E_STATUS_ADD = "Completion of Status
E_PLANNED_CLS_DATE = "Planned Account Closure Date
EXCEPTIONS
NOT_FOUND = 1 IMPARA_ERROR = 2
IMPORTING Parameters details for BKK_ACCNT_GET_DATE_STATUS
I_BKKRS - Bank Area
Data type: IBKK40-BKKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_ACNUM_INT - Internal Account Number
Data type: IBKK40-ACNUM_INTOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BKK_ACCNT_GET_DATE_STATUS
E_OPENDATE - Opening Date
Data type: IBKK40-OPENDATEOptional: No
Call by Reference: No ( called with pass by value option)
E_DELDATE - Closure Date
Data type: IBKK40-DELDATEOptional: No
Call by Reference: No ( called with pass by value option)
E_BALDATE -
Data type: IBKK40-BALDATEOptional: No
Call by Reference: No ( called with pass by value option)
E_PRODDATE -
Data type: IBKK40-PRODDATEOptional: No
Call by Reference: No ( called with pass by value option)
E_STATUS - Status
Data type: IBKK40-STATUSOptional: No
Call by Reference: No ( called with pass by value option)
E_STATUS_ADD - Completion of Status
Data type: IBKK40-STATUS_ADDOptional: No
Call by Reference: No ( called with pass by value option)
E_PLANNED_CLS_DATE - Planned Account Closure Date
Data type: IBKK40-PLANNED_CL_DATEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_FOUND - No Data Record Found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
IMPARA_ERROR - Import Parameter is Not Filled
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_ACCNT_GET_DATE_STATUS 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_bkkrs | TYPE IBKK40-BKKRS, " | |||
| lv_not_found | TYPE IBKK40, " | |||
| lv_e_opendate | TYPE IBKK40-OPENDATE, " | |||
| lv_e_deldate | TYPE IBKK40-DELDATE, " | |||
| lv_i_acnum_int | TYPE IBKK40-ACNUM_INT, " | |||
| lv_impara_error | TYPE IBKK40, " | |||
| lv_e_baldate | TYPE IBKK40-BALDATE, " | |||
| lv_e_proddate | TYPE IBKK40-PRODDATE, " | |||
| lv_e_status | TYPE IBKK40-STATUS, " | |||
| lv_e_status_add | TYPE IBKK40-STATUS_ADD, " | |||
| lv_e_planned_cls_date | TYPE IBKK40-PLANNED_CL_DATE. " |
|   CALL FUNCTION 'BKK_ACCNT_GET_DATE_STATUS' "Find Administrative Data for Account |
| EXPORTING | ||
| I_BKKRS | = lv_i_bkkrs | |
| I_ACNUM_INT | = lv_i_acnum_int | |
| IMPORTING | ||
| E_OPENDATE | = lv_e_opendate | |
| E_DELDATE | = lv_e_deldate | |
| E_BALDATE | = lv_e_baldate | |
| E_PRODDATE | = lv_e_proddate | |
| E_STATUS | = lv_e_status | |
| E_STATUS_ADD | = lv_e_status_add | |
| E_PLANNED_CLS_DATE | = lv_e_planned_cls_date | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| IMPARA_ERROR = 2 | ||
| . " BKK_ACCNT_GET_DATE_STATUS | ||
ABAP code using 7.40 inline data declarations to call FM BKK_ACCNT_GET_DATE_STATUS
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 BKKRS FROM IBKK40 INTO @DATA(ld_i_bkkrs). | ||||
| "SELECT single OPENDATE FROM IBKK40 INTO @DATA(ld_e_opendate). | ||||
| "SELECT single DELDATE FROM IBKK40 INTO @DATA(ld_e_deldate). | ||||
| "SELECT single ACNUM_INT FROM IBKK40 INTO @DATA(ld_i_acnum_int). | ||||
| "SELECT single BALDATE FROM IBKK40 INTO @DATA(ld_e_baldate). | ||||
| "SELECT single PRODDATE FROM IBKK40 INTO @DATA(ld_e_proddate). | ||||
| "SELECT single STATUS FROM IBKK40 INTO @DATA(ld_e_status). | ||||
| "SELECT single STATUS_ADD FROM IBKK40 INTO @DATA(ld_e_status_add). | ||||
| "SELECT single PLANNED_CL_DATE FROM IBKK40 INTO @DATA(ld_e_planned_cls_date). | ||||
Search for further information about these or an SAP related objects