Deployment scenarios

FLM can be hosted on the same SAP system as the back-end form data (typically a SAP ERP system) or it can be separately hosted on a SAP Netweaver system.  If FLM is to be hosted separately then several considerations should be taken into account.

 Defining remote systems

Use the system-specific settings to define up to 4 remote systems.

Main Ext RFC

This stores the 'main' back-end system that FLM connects to.


This defines the back-end system in which user authorisations are defined

Alt Ext RFC 1 / Alt Ext RFC 2

These define other back-end systems if required. If Alt Ext RFC 1 is filled this will be used by the FLM for HR framework by default to read HR data. This must be setup with a user of type system, service or communication (no login possible). A password should be provided in the RFC setup and the user assigned high level authorizations, customers often create a copy of an existing user that BASIS team use for processing HR/Payroll jobs.


Calling BAPIs in user-exits

In order to call functions in a remote destination, return the 'DESTINATION' programatically using:

g_rfcdest = /flm/core=>get_rfc_dest( ).

This returns the Main Ext RFC connection.

Calling BAPIs in Posting Adapters

In order to call functions in a remote destination, define the destination in the Posting Adapter configuration table as '<Dynamic Dest from FLM Config>'.     


This will then pass the value of the Main Ext RFC connection into the posting adapter function, using import parameter IM_RFC_DEST.

Managing authorisation checks in a remote system

 If a remote system is configured in the UME Ext RFC then FLM will automatically call that system to conduct all authorisation checks.

If more complicated logic is required (for example, to sometimes perform the authorisation check on a different system) then this can be achieved using the Authorisation user-exit.

Note that the standard authorisation check is always made before calling the authorisation user-exit.