SAP Function Modules

comments icon Comments

FI_PAYMENT_GTS_AUTO_AFTER_FAIL SAP Function module







FI_PAYMENT_GTS_AUTO_AFTER_FAIL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name FI_PAYMENT_GTS_AUTO_AFTER_FAIL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FIPAY_GTS
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM FI_PAYMENT_GTS_AUTO_AFTER_FAIL - FI PAYMENT GTS AUTO AFTER FAIL 





CALL FUNCTION 'FI_PAYMENT_GTS_AUTO_AFTER_FAIL' "
  EXPORTING
    is_reguv =                  " reguv
    iv_proposal_run =           " abap_bool
  IMPORTING
    ev_runmode =                " fipay_runmode_gts
    ev_write_trigger_entries =   " abap_bool
    ev_stop_processing =        " abap_bool
    .  "  FI_PAYMENT_GTS_AUTO_AFTER_FAIL

ABAP code example for Function Module FI_PAYMENT_GTS_AUTO_AFTER_FAIL





The ABAP code below is a full code listing to execute function module FI_PAYMENT_GTS_AUTO_AFTER_FAIL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_runmode    TYPE FIPAY_RUNMODE_GTS
,
ld_ev_write_trigger_entries    TYPE ABAP_BOOL
,
ld_ev_stop_processing    TYPE ABAP_BOOL
.




DATA(ld_is_reguv) = 'Check type of data required'.

DATA(ld_iv_proposal_run) = 'Check type of data required'.
.

CALL FUNCTION 'FI_PAYMENT_GTS_AUTO_AFTER_FAIL'
  EXPORTING
    is_reguv =                   ld_is_reguv
    iv_proposal_run =            ld_iv_proposal_run
  IMPORTING
    ev_runmode =                 ld_ev_runmode
    ev_write_trigger_entries =    ld_ev_write_trigger_entries
    ev_stop_processing =         ld_ev_stop_processing
    .  "  FI_PAYMENT_GTS_AUTO_AFTER_FAIL

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:


ld_ev_runmode  TYPE FIPAY_RUNMODE_GTS ,
ld_is_reguv  TYPE REGUV ,
ld_ev_write_trigger_entries  TYPE ABAP_BOOL ,
ld_iv_proposal_run  TYPE ABAP_BOOL ,
ld_ev_stop_processing  TYPE ABAP_BOOL .




ld_is_reguv = 'Check type of data required'.
ld_iv_proposal_run = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name FI_PAYMENT_GTS_AUTO_AFTER_FAIL or its description.


   
 

FI_PAYMENT_GTS_AUTO_AFTER_FAIL - 
FI_PAYMENT_GLOBAL_CUSTOM_PARAM - 
FI_PAYMENT_FORMAT_INDICATOR - 
FI_PAYMENT_DOCLN_ADDON_READ - 
FI_PAYMENT_DOCLN_ADDON_MODIFY - 
FI_PAYMENT_DETAILS_READ -