/INT4/IFTT_BCKND_COM - IFTT Backend Communication user

This section describes authorization roles needed for the Int4 IFTT Backend Communication user on the tested environments only (e.g. DEV,TEST,QUALITY,ACCEPTANCE, but not PROD!).
The role for the productive communication user can be found here.

The role allows to:

• Access into backend tables for DB validation of results

• Trigger output messages (based on NAST)

• Trigger Outbound and Inbound IDocs

• Trigger Inbound AIF messages

• Trigger outbound proxy messages

• Read the list of the IDocs

• Read the list of the messages in the SXMB_MONI

Authorization values:

* The name of the Int4 IFTT RFC module name:

• In the case of a decentralized installation where Int4 IFTT is installed and deployed on each ABAP backend, function modules /INT4/IFTT_F_COLLECT_RESLT_RFC and /INT4/IFTT_F_TRIGGER_MSG must be added in RFC_NAME. 
  
  

• In case of a centralized installation (where Int4 IFTT is installed only on SAP Solution Manager or other SAP ABAP Application server ) - custom function module names must be added in S_RFC . For example,  Z_IFTT_F_COLLECT_RESLT_RFC and Z_IFTT_F_TRIGGER_MSG, depending on the customer’s naming convention and names of the function modules created in tested backend systems.
  These are the function module names used in global parameters: RFC_DB_RES and RFC_MSGOUT.

** S_TABU_NAM is checked by function VIEW_AUTHORITY_CHECK inside of function /INT4/IFTT_F_COLLECT_RESLT_RFC to restrict access to DB tables. Please notice that the template includes no values. Role created for communication user should contain all DB tables validated by Int4 IFTT automation objects.