SAP ISU_PARTNER_BANK_CARD_DELETE Function Module for INTERNAL: Change Business Partner









ISU_PARTNER_BANK_CARD_DELETE is a standard isu partner bank card delete SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: Change Business Partner 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 isu partner bank card delete FM, simply by entering the name ISU_PARTNER_BANK_CARD_DELETE into the relevant SAP transaction such as SE37 or SE38.

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



Function ISU_PARTNER_BANK_CARD_DELETE 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 'ISU_PARTNER_BANK_CARD_DELETE'"INTERNAL: Change Business Partner
EXPORTING
X_PARTNER = "
* X_BANK_DEL = "BP: Bank details (Read)
* X_CARD_DEL = "BP: Payment Cards (Direct Input)

EXCEPTIONS
NOT_FOUND = 1 FOREIGN_LOCK = 2 NOT_AUTHORIZED = 3 GENERAL_FAULT = 4 NO_SIMPLE_CASE = 5 INPUT_ERROR = 6 BANK_NOT_FOUND = 7
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLES01_001 Duplicate Check: Business Partner
EXIT_SAPLES01_030 Before PBO Customer Subscreen
EXIT_SAPLES01_031 After PAI Customer Subscreen

IMPORTING Parameters details for ISU_PARTNER_BANK_CARD_DELETE

X_PARTNER -

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

X_BANK_DEL - BP: Bank details (Read)

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

X_CARD_DEL - BP: Payment Cards (Direct Input)

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

EXCEPTIONS details

NOT_FOUND - Object does not exist

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

FOREIGN_LOCK - Object Currently Locked

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

NOT_AUTHORIZED -

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

GENERAL_FAULT - Other

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

NO_SIMPLE_CASE -

Data type:
Optional: No
Call by Reference: Yes

INPUT_ERROR - Data incorrect

Data type:
Optional: No
Call by Reference: Yes

BANK_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISU_PARTNER_BANK_CARD_DELETE 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_not_found  TYPE STRING, "   
lv_x_partner  TYPE BUT000-PARTNER, "   
lv_x_bank_del  TYPE BUS0BK, "   
lv_foreign_lock  TYPE BUS0BK, "   
lv_x_card_del  TYPE BUS0CC_DI, "   
lv_not_authorized  TYPE BUS0CC_DI, "   
lv_general_fault  TYPE BUS0CC_DI, "   
lv_no_simple_case  TYPE BUS0CC_DI, "   
lv_input_error  TYPE BUS0CC_DI, "   
lv_bank_not_found  TYPE BUS0CC_DI. "   

  CALL FUNCTION 'ISU_PARTNER_BANK_CARD_DELETE'  "INTERNAL: Change Business Partner
    EXPORTING
         X_PARTNER = lv_x_partner
         X_BANK_DEL = lv_x_bank_del
         X_CARD_DEL = lv_x_card_del
    EXCEPTIONS
        NOT_FOUND = 1
        FOREIGN_LOCK = 2
        NOT_AUTHORIZED = 3
        GENERAL_FAULT = 4
        NO_SIMPLE_CASE = 5
        INPUT_ERROR = 6
        BANK_NOT_FOUND = 7
. " ISU_PARTNER_BANK_CARD_DELETE




ABAP code using 7.40 inline data declarations to call FM ISU_PARTNER_BANK_CARD_DELETE

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 PARTNER FROM BUT000 INTO @DATA(ld_x_partner).
 
 
 
 
 
 
 
 
 


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!