FTR_HM_SUBSCREEN_0200 SAP Function module

FTR_HM_SUBSCREEN_0200 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 FTR_HM_SUBSCREEN_0200 into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: FTR_HM
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM FTR_HM_SUBSCREEN_0200 - FTR HM SUBSCREEN 0200

CALL FUNCTION 'FTR_HM_SUBSCREEN_0200' "
  EXPORTING
    pi_proxy_transaction =      " if_open_trtm_proxy_transaction  Proxy for Financial Transaction in Open TR-TM
    pi_proxy_messages =         " if_open_trtm_proxy_message  Proxy for Message Handler for Transaction Management
    pi_proxy_fcode =            " if_open_trtm_proxy_fcode  Proxy for FCODE in Open TR-TM
    pi_proxy_fmod_sap =         " if_open_trtm_proxy_fmod  Field selection control / field modification
  EXCEPTIONS
    FAILED = 1                  "
    .  "  FTR_HM_SUBSCREEN_0200

ABAP code example for Function Module FTR_HM_SUBSCREEN_0200

The ABAP code below is a full code listing to execute function module FTR_HM_SUBSCREEN_0200 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_pi_proxy_transaction) = 'Check type of data required'.

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

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

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

CALL FUNCTION 'FTR_HM_SUBSCREEN_0200'
  EXPORTING
    pi_proxy_transaction =       ld_pi_proxy_transaction
    pi_proxy_messages =          ld_pi_proxy_messages
    pi_proxy_fcode =             ld_pi_proxy_fcode
    pi_proxy_fmod_sap =          ld_pi_proxy_fmod_sap
  EXCEPTIONS
    FAILED =                     1
    .  "  FTR_HM_SUBSCREEN_0200

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_pi_proxy_transaction
 
 TYPE IF_OPEN_TRTM_PROXY_TRANSACTION ,
ld_pi_proxy_messages
 
 TYPE IF_OPEN_TRTM_PROXY_MESSAGE ,
ld_pi_proxy_fcode
 
 TYPE IF_OPEN_TRTM_PROXY_FCODE ,
ld_pi_proxy_fmod_sap
 
 TYPE IF_OPEN_TRTM_PROXY_FMOD .


ld_pi_proxy_transaction = 'Check type of data required'.
ld_pi_proxy_messages = 'Check type of data required'.
ld_pi_proxy_fcode = 'Check type of data required'.
ld_pi_proxy_fmod_sap = 'Check type of data required'.

SAP Documentation for FM FTR_HM_SUBSCREEN_0200