SAP ISB_CF_PAYMENTS_DELETE Function Module for Zahlungsstromgeschäft: Auszahlung löschen
ISB_CF_PAYMENTS_DELETE is a standard isb cf payments 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 Zahlungsstromgeschäft: Auszahlung löschen 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 isb cf payments delete FM, simply by entering the name ISB_CF_PAYMENTS_DELETE into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBCFTRANSACTION
Program Name: SAPLJBCFTRANSACTION
Main Program: SAPLJBCFTRANSACTION
Appliation area: J
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISB_CF_PAYMENTS_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 'ISB_CF_PAYMENTS_DELETE'"Zahlungsstromgeschäft: Auszahlung löschen.
EXPORTING
I_OBJNR = "Objektnummer
I_STUFE = "Stufennummer
* I_CHECK_ONLY = ' ' "nur Prüfungen durchführen
EXCEPTIONS
OBJNR_NOT_IN_GLOBAL_MEMORY = 1 ENTRY_NOT_IN_GLOBAL_MEMORY = 2 ENTRY_LOCKED = 3 DELETE_NOT_POSSIBLE = 4
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_SAPLJBCFTRANSACTION_001 User Exit: Additional Opportunity Interest Rates from Cashflow
IMPORTING Parameters details for ISB_CF_PAYMENTS_DELETE
I_OBJNR - Objektnummer
Data type: JBTCFINFO-OBJNROptional: No
Call by Reference: No ( called with pass by value option)
I_STUFE - Stufennummer
Data type: JBTCFINFO-STUFEOptional: No
Call by Reference: No ( called with pass by value option)
I_CHECK_ONLY - nur Prüfungen durchführen
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJNR_NOT_IN_GLOBAL_MEMORY - Geschäft nicht im globalen Gedächtnis
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENTRY_NOT_IN_GLOBAL_MEMORY - Eintrag zum Verändern nicht vorhanden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENTRY_LOCKED - Eintrag darf nicht verändert werden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DELETE_NOT_POSSIBLE - Eintrag kann nicht gelöscht werden
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISB_CF_PAYMENTS_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_i_objnr | TYPE JBTCFINFO-OBJNR, " | |||
| lv_objnr_not_in_global_memory | TYPE JBTCFINFO, " | |||
| lv_i_stufe | TYPE JBTCFINFO-STUFE, " | |||
| lv_entry_not_in_global_memory | TYPE JBTCFINFO, " | |||
| lv_entry_locked | TYPE JBTCFINFO, " | |||
| lv_i_check_only | TYPE C, " ' ' | |||
| lv_delete_not_possible | TYPE C. " |
|   CALL FUNCTION 'ISB_CF_PAYMENTS_DELETE' "Zahlungsstromgeschäft: Auszahlung löschen |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| I_STUFE | = lv_i_stufe | |
| I_CHECK_ONLY | = lv_i_check_only | |
| EXCEPTIONS | ||
| OBJNR_NOT_IN_GLOBAL_MEMORY = 1 | ||
| ENTRY_NOT_IN_GLOBAL_MEMORY = 2 | ||
| ENTRY_LOCKED = 3 | ||
| DELETE_NOT_POSSIBLE = 4 | ||
| . " ISB_CF_PAYMENTS_DELETE | ||
ABAP code using 7.40 inline data declarations to call FM ISB_CF_PAYMENTS_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 OBJNR FROM JBTCFINFO INTO @DATA(ld_i_objnr). | ||||
| "SELECT single STUFE FROM JBTCFINFO INTO @DATA(ld_i_stufe). | ||||
| DATA(ld_i_check_only) | = ' '. | |||
Search for further information about these or an SAP related objects