SAP FI_HOUSEBANK_READ Function Module for
FI_HOUSEBANK_READ is a standard fi housebank read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fi housebank read FM, simply by entering the name FI_HOUSEBANK_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: FK00
Program Name: SAPLFK00
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FI_HOUSEBANK_READ 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 'FI_HOUSEBANK_READ'".
EXPORTING
IC_BUKRS = "
IC_HBKID = "
IMPORTING
ES_T012 = "
ES_T012D = "
IMPORTING Parameters details for FI_HOUSEBANK_READ
IC_BUKRS -
Data type: T001-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
IC_HBKID -
Data type: T012-HBKIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FI_HOUSEBANK_READ
ES_T012 -
Data type: T012Optional: No
Call by Reference: Yes
ES_T012D -
Data type: T012DOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FI_HOUSEBANK_READ 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_es_t012 | TYPE T012, " | |||
lv_ic_bukrs | TYPE T001-BUKRS, " | |||
lv_es_t012d | TYPE T012D, " | |||
lv_ic_hbkid | TYPE T012-HBKID. " |
  CALL FUNCTION 'FI_HOUSEBANK_READ' " |
EXPORTING | ||
IC_BUKRS | = lv_ic_bukrs | |
IC_HBKID | = lv_ic_hbkid | |
IMPORTING | ||
ES_T012 | = lv_es_t012 | |
ES_T012D | = lv_es_t012d | |
. " FI_HOUSEBANK_READ |
ABAP code using 7.40 inline data declarations to call FM FI_HOUSEBANK_READ
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 BUKRS FROM T001 INTO @DATA(ld_ic_bukrs). | ||||
"SELECT single HBKID FROM T012 INTO @DATA(ld_ic_hbkid). | ||||
Search for further information about these or an SAP related objects