FND – 45 – Configure SAP system alias for applications

Let the world know ...Tweet about this on TwitterShare on Google+0Share on Facebook0Email this to someoneShare on LinkedIn0

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help. The steps are for the OData Channel Service for backend system.

  1. Basic configuration activities: SAP Help
    • Set profile parameters to support SSO2 SAP Help
    • Activate ICF Services SAP Help
  2. User & Authorization SAP Help
  3. SAP Gateway to Consumer (FND to SMP3) SAP Help
    1. Creating a bgRFC destination for outbound queues SAP Help
    2. Registering bgRFC destination for the oubound queue SAP Help
    3. Creating bgRFC supervisor destination SAP Help
  4. SAP Gateway to SAP Backend (FND to BEP) SAP Help
    1. Create RFC on SAP Gateway (FND) to SAP backend (BEP) SAP Help
    2. Define trust between SAP Gateway and SAP backend (FND <-> BEP) SAP Help
    3. Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway SAP Help
    4. Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP) SAP Help
    5. Configure SAP system alias for applications SAP Help
  5. Activate SAP NetWeaver Gateway SAP Help

This document explains how to execute step 4.5.

Incoming OData request can be handled locally by the Gateway system or redirected to an SAP Backend. In a HUB installation, the OData service backend is a diferente SAP system (BEP), therefore an alias is needed to define to which backend a OData service should be redirected to.
SAP Help

The alias defined here will be used in the maintain odata services transaction to assign a backend to a service.

SPRO: SAP Reference IMG and navigate to:  SAP NetWeaver Gateway OData Channel Configuration Connection Settings SAP NetWeaver Gateway to SAP System Manage SAP System Aliases


The program to manage SAP system alises opens.


  1. Create a new entry

  1. Enter the corresponding data for the SAP backend
  • SAP System Alias: ECC
  • Description: BEP backend
  • Local GW: No
  • For Local App: No
  • RFC Destination: ECCCLNT001
  • Software Version: DEFAULT
  • System ID: ECC
  • Client: 001
  • WS Provider system: empty

  1. Save
Let the world know ...Tweet about this on TwitterShare on Google+0Share on Facebook0Email this to someoneShare on LinkedIn0

One thought on “FND – 45 – Configure SAP system alias for applications

  1. Pingback: FND – 5 – Activate SAP NetWeaver Gateway | It`s full of stars!

Leave a Reply

Your email address will not be published. Required fields are marked *