SAP FTR_BPAR_EVENT_BKDEL Function Module for Business Partner: Delete Bank Details









FTR_BPAR_EVENT_BKDEL is a standard ftr bpar event bkdel SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Business Partner: Delete Bank Details 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 ftr bpar event bkdel FM, simply by entering the name FTR_BPAR_EVENT_BKDEL into the relevant SAP transaction such as SE37 or SE38.

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



Function FTR_BPAR_EVENT_BKDEL 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 'FTR_BPAR_EVENT_BKDEL'"Business Partner: Delete Bank Details
  EXPORTING
*  I_PARTNER =  "Geschäftspartnernummer Regulierer
*  I_PARTNER_GUID =  "Business Partner GUID
   I_BKVID =  "Partner Bank Details
*  I_CALLTP =  "Aufruftyp (1=Dialog; 2=BAPI)
*  I_VALID_FROM = '00000000' "Field of type DATS
*  I_VALID_FROM_OLD = '00000000' "Field of type DATS
*  I_VALID_TO = '00000000' "Field of type DATS
*  I_VALID_TO_OLD = '00000000' "Field of type DATS

 IMPORTING
   E_RESULT =  "Resultat (1=OK ; 3 = Nein;9=Fehler)

TABLES
*  ET_RETURN =  "Return Parameter
.



IMPORTING Parameters details for FTR_BPAR_EVENT_BKDEL

I_PARTNER - Geschäftspartnernummer Regulierer

Data type: BP_PARTNR_NEW
Optional: Yes
Call by Reference: Yes

I_PARTNER_GUID - Business Partner GUID

Data type: BU_PARTNER_GUID
Optional: Yes
Call by Reference: Yes

I_BKVID - Partner Bank Details

Data type: TB_RPBANK
Optional: No
Call by Reference: Yes

I_CALLTP - Aufruftyp (1=Dialog; 2=BAPI)

Data type: BUS000FLDS-CHAR1
Optional: Yes
Call by Reference: Yes

I_VALID_FROM - Field of type DATS

Data type: DATS
Default: '00000000'
Optional: Yes
Call by Reference: Yes

I_VALID_FROM_OLD - Field of type DATS

Data type: DATS
Default: '00000000'
Optional: Yes
Call by Reference: Yes

I_VALID_TO - Field of type DATS

Data type: DATS
Default: '00000000'
Optional: Yes
Call by Reference: Yes

I_VALID_TO_OLD - Field of type DATS

Data type: DATS
Default: '00000000'
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FTR_BPAR_EVENT_BKDEL

E_RESULT - Resultat (1=OK ; 3 = Nein;9=Fehler)

Data type: BUS000FLDS-CHAR1
Optional: No
Call by Reference: Yes

TABLES Parameters details for FTR_BPAR_EVENT_BKDEL

ET_RETURN - Return Parameter

Data type: BAPIRET2
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for FTR_BPAR_EVENT_BKDEL 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_result  TYPE BUS000FLDS-CHAR1, "   
lt_et_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_i_partner  TYPE BP_PARTNR_NEW, "   
lv_i_partner_guid  TYPE BU_PARTNER_GUID, "   
lv_i_bkvid  TYPE TB_RPBANK, "   
lv_i_calltp  TYPE BUS000FLDS-CHAR1, "   
lv_i_valid_from  TYPE DATS, "   '00000000'
lv_i_valid_from_old  TYPE DATS, "   '00000000'
lv_i_valid_to  TYPE DATS, "   '00000000'
lv_i_valid_to_old  TYPE DATS. "   '00000000'

  CALL FUNCTION 'FTR_BPAR_EVENT_BKDEL'  "Business Partner: Delete Bank Details
    EXPORTING
         I_PARTNER = lv_i_partner
         I_PARTNER_GUID = lv_i_partner_guid
         I_BKVID = lv_i_bkvid
         I_CALLTP = lv_i_calltp
         I_VALID_FROM = lv_i_valid_from
         I_VALID_FROM_OLD = lv_i_valid_from_old
         I_VALID_TO = lv_i_valid_to
         I_VALID_TO_OLD = lv_i_valid_to_old
    IMPORTING
         E_RESULT = lv_e_result
    TABLES
         ET_RETURN = lt_et_return
. " FTR_BPAR_EVENT_BKDEL




ABAP code using 7.40 inline data declarations to call FM FTR_BPAR_EVENT_BKDEL

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 CHAR1 FROM BUS000FLDS INTO @DATA(ld_e_result).
 
 
 
 
 
"SELECT single CHAR1 FROM BUS000FLDS INTO @DATA(ld_i_calltp).
 
DATA(ld_i_valid_from) = '00000000'.
 
DATA(ld_i_valid_from_old) = '00000000'.
 
DATA(ld_i_valid_to) = '00000000'.
 
DATA(ld_i_valid_to_old) = '00000000'.
 


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!