SAP FI_PAYMENT_BANK_POST_INIT Function Module for









FI_PAYMENT_BANK_POST_INIT is a standard fi payment bank post init 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 payment bank post init FM, simply by entering the name FI_PAYMENT_BANK_POST_INIT into the relevant SAP transaction such as SE37 or SE38.

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



Function FI_PAYMENT_BANK_POST_INIT 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_PAYMENT_BANK_POST_INIT'"
EXPORTING
I_HBKID = "
I_BUKRS = "
I_WAERS = "
I_ZLSCH = "

IMPORTING
E_T042I = "

EXCEPTIONS
BANKDATA_NOT_FOUND = 1
.



IMPORTING Parameters details for FI_PAYMENT_BANK_POST_INIT

I_HBKID -

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

I_BUKRS -

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

I_WAERS -

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

I_ZLSCH -

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

EXPORTING Parameters details for FI_PAYMENT_BANK_POST_INIT

E_T042I -

Data type: T042I
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

BANKDATA_NOT_FOUND -

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

Copy and paste ABAP code example for FI_PAYMENT_BANK_POST_INIT 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_t042i  TYPE T042I, "   
lv_i_hbkid  TYPE ZHLG1-HBKID, "   
lv_bankdata_not_found  TYPE ZHLG1, "   
lv_i_bukrs  TYPE ZHLG1-ZBUKR, "   
lv_i_waers  TYPE ZHLG1-WAERS, "   
lv_i_zlsch  TYPE ZHLG1-ZLSCH. "   

  CALL FUNCTION 'FI_PAYMENT_BANK_POST_INIT'  "
    EXPORTING
         I_HBKID = lv_i_hbkid
         I_BUKRS = lv_i_bukrs
         I_WAERS = lv_i_waers
         I_ZLSCH = lv_i_zlsch
    IMPORTING
         E_T042I = lv_e_t042i
    EXCEPTIONS
        BANKDATA_NOT_FOUND = 1
. " FI_PAYMENT_BANK_POST_INIT




ABAP code using 7.40 inline data declarations to call FM FI_PAYMENT_BANK_POST_INIT

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 HBKID FROM ZHLG1 INTO @DATA(ld_i_hbkid).
 
 
"SELECT single ZBUKR FROM ZHLG1 INTO @DATA(ld_i_bukrs).
 
"SELECT single WAERS FROM ZHLG1 INTO @DATA(ld_i_waers).
 
"SELECT single ZLSCH FROM ZHLG1 INTO @DATA(ld_i_zlsch).
 


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!