SAP FI_PAYMENT_GTS_DELETE_TRIGGER Function Module for









FI_PAYMENT_GTS_DELETE_TRIGGER is a standard fi payment gts delete trigger 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 gts delete trigger FM, simply by entering the name FI_PAYMENT_GTS_DELETE_TRIGGER into the relevant SAP transaction such as SE37 or SE38.

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



Function FI_PAYMENT_GTS_DELETE_TRIGGER 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_GTS_DELETE_TRIGGER'"
EXPORTING
* IS_REGUV = "
* IS_REGUP = "
* IB_FORCED_DELETE_ALL = "
.



IMPORTING Parameters details for FI_PAYMENT_GTS_DELETE_TRIGGER

IS_REGUV -

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

IS_REGUP -

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

IB_FORCED_DELETE_ALL -

Data type: BOOLE-BOOLE
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for FI_PAYMENT_GTS_DELETE_TRIGGER 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_is_reguv  TYPE REGUV, "   
lv_is_regup  TYPE REGUP, "   
lv_ib_forced_delete_all  TYPE BOOLE-BOOLE. "   

  CALL FUNCTION 'FI_PAYMENT_GTS_DELETE_TRIGGER'  "
    EXPORTING
         IS_REGUV = lv_is_reguv
         IS_REGUP = lv_is_regup
         IB_FORCED_DELETE_ALL = lv_ib_forced_delete_all
. " FI_PAYMENT_GTS_DELETE_TRIGGER




ABAP code using 7.40 inline data declarations to call FM FI_PAYMENT_GTS_DELETE_TRIGGER

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 BOOLE FROM BOOLE INTO @DATA(ld_ib_forced_delete_all).
 


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!