SAP Reports / Programs | Financial Accounting | Accounts Payable | Payment Transactions(FI-AP-AP-PT) SAP FI
RFBREAKDOWNGTS SAP ABAP Report - Subsequent Check Made in SAP GTS for FI
RFBREAKDOWNGTS is a standard Executable ABAP Report available within your SAP system (depending on your version and release level). It is used for This program is used for a subsequent sanctioned party list screening or embargo check of an FI payment if: The connection to the SAP GTS (
If you would like to execute this report or see the full code listing simply enter RFBREAKDOWNGTS into the relevant SAP transactions such as SE38 or SE80
Transaction Code(s):
Below is a list of transaction codes which are relevant to this SAP report
FIPAY_BDGTS01 - Subsequent SPL Screening
ABAP code to call this SAP report using the submit statement
This report can be called from another progam/report simply by using the ABAP SUBMIT statement, see below for example ABAP code snipts of how to do this.
SUBMIT RFBREAKDOWNGTS. "Basic submit
SUBMIT RFBREAKDOWNGTS AND RETURN. "Return to original report after report execution complete
SUBMIT RFBREAKDOWNGTS VIA SELECTION-SCREEN. "Display selection screen of submitted report to user
See more syntax options for the ABAP SUBMIT statement
Text pool values
Selection Text: P_ECHT = Update Run (with SAP GTS Call)
Selection Text: P_TEST = Test Run (No SAP GTS Call)
Selection Text: P_TESTSI = Test Run (with SAP GTS Call
Selection Text: SO_LAUFD = Run date
Selection Text: SO_LAUFI = Identification
Title: Subsequent Check Made in SAP GTS for FI
Text Symbol: 001 = Update Run:
Text Symbol: 002 = Test Run
Text Symbol: 003 = Subsequent Sanctioned Party List Screening
Text Symbol: 004 = SAP GTS Error Message
Text Symbol: P01 = Other Parameters
INCLUDES used within this REPORT RFBREAKDOWNGTS
INCLUDE RFBREAKDOWNGTSTOP.
TABLES used within REPORT and the associated SELECT statement:
No SAP DATABASE tables are accessed within this REPORT code!
Function Modules used within report and the associated call statement:
FI_PAYMENT_USE_OF_GTS_CHECK CALL FUNCTION 'FI_PAYMENT_USE_OF_GTS_CHECK' IMPORTING e_xspl_active_gts = gv_xspl_active_gts.
FI_PAYMENT_TRIGGER_GTS_READ CALL FUNCTION 'FI_PAYMENT_TRIGGER_GTS_READ' EXPORTING it_laufi_sel = so_laufi it_laufd_sel = so_laufd IMPORTING et_trigger_table = lt_trigger_table.
FI_PAYMENT_INTERFACE_TO_GTS CALL FUNCTION 'FI_PAYMENT_INTERFACE_TO_GTS' EXPORTING is_reguh = ls_reguh it_regup = lt_regup iv_runmode_gts = ls_trigger_table-runmode ib_return_messages = 'X' IMPORTING eb_technical_error = lb_technical_error eb_communication_error = lb_communication_error et_failed_regup_key = lt_failed_regup_key et_result_legal_control = lt_result_legal_control et_return = lt_messages.
FI_PAYMENT_INTERFACE_TO_GTS CALL FUNCTION 'FI_PAYMENT_INTERFACE_TO_GTS' EXPORTING is_reguh = ls_reguh it_regup = lt_regup iv_runmode_gts = ls_trigger_table-runmode ib_simulate = 'X' ib_return_messages = 'X' IMPORTING eb_technical_error = lb_technical_error eb_communication_error = lb_communication_error et_failed_regup_key = lt_failed_regup_key et_result_legal_control = lt_result_legal_control et_return = lt_messages.
FI_PAYMENT_GTS_DELETE_TRIGGER CALL FUNCTION 'FI_PAYMENT_GTS_DELETE_TRIGGER' EXPORTING is_reguv = ls_reguv ib_forced_delete_all = 'X'.
Contribute (Add Comments)
Although this basic information may have limited use it does provide an easy to find location to store any knowledge about this program/report.
The contribute/comments section below therefore offer's an opportunity for anyone to add additional information. This can be anything from useful hints, tips and screen shots to relevant SAP notes or anything else you feel is relevant to this report.
This will then be available for everyone to easily find by simply searching on the report name RFBREAKDOWNGTS or its description.