FI_PAYMENT_GTS_MAN_AFTER_FAIL SAP Function module

FI_PAYMENT_GTS_MAN_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_MAN_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

Pattern for FM FI_PAYMENT_GTS_MAN_AFTER_FAIL - FI PAYMENT GTS MAN AFTER FAIL

CALL FUNCTION 'FI_PAYMENT_GTS_MAN_AFTER_FAIL' "
  EXPORTING
    iv_msgno =                  " t100c-msgnr
*   iv_show_e_message = 'X'     " boole_d
  IMPORTING
    eb_do_gts_check =           " abap_bool
    eb_process =                " abap_bool
    eb_write_trigger =          " abap_bool
    .  "  FI_PAYMENT_GTS_MAN_AFTER_FAIL

ABAP code example for Function Module FI_PAYMENT_GTS_MAN_AFTER_FAIL

The ABAP code below is a full code listing to execute function module FI_PAYMENT_GTS_MAN_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_eb_do_gts_check  
 
 TYPE ABAP_BOOL
,
ld_eb_process  
 
 TYPE ABAP_BOOL
,
ld_eb_write_trigger  
 
 TYPE ABAP_BOOL
.

 

SELECT single MSGNR 
  FROM T100C 
  INTO @DATA(ld_iv_msgno).


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

CALL FUNCTION 'FI_PAYMENT_GTS_MAN_AFTER_FAIL'
  EXPORTING
    iv_msgno =                   ld_iv_msgno
*   iv_show_e_message =          ld_iv_show_e_message
  IMPORTING
    eb_do_gts_check =            ld_eb_do_gts_check
    eb_process =                 ld_eb_process
    eb_write_trigger =           ld_eb_write_trigger
    .  "  FI_PAYMENT_GTS_MAN_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_eb_do_gts_check
 
 TYPE ABAP_BOOL ,
ld_iv_msgno
 
 TYPE T100C-MSGNR ,
ld_eb_process
 
 TYPE ABAP_BOOL ,
ld_iv_show_e_message
 
 TYPE BOOLE_D ,
ld_eb_write_trigger
 
 TYPE ABAP_BOOL .



SELECT single MSGNR 
  FROM T100C 
  INTO ld_iv_msgno.

ld_iv_show_e_message = 'Check type of data required'.