FND – 6 – Subscription and Notification Flow

The configuration steps to be executed on the HUB system (FND) are detailed at SAP Help.

  1. Maintaining Inbound bgRFC Queue on the Hub System Blog SAP Help
  2. Create outbound destination for content publisher Blog SAP Help

FND – 44 – Configure SAP Gateway (FND) to accept assertion ticket from SAP backend (BEP)

Yes, this item should be under BEP and not HUB, but I am following SAP Help here, so sorry for the confusion!

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.4.

Allow SAP backend (BEP) to logon via SSO to SAP Gateway HUB (FND).
SAP Help

No SPRO activity.

System: BEP

Transaction SSO2

To configure SSO by installing the system certificates, go to transaction SSO2

  • Destination: Give RFC destination: ECCCLNT001

  • Host name: DNS name of backend (BEP): nwecc.tobias.de
  • Instance Number: Instance number of backend (BEP): 01

Run the program. In case the tool finds some problems, it allows you to let it solve them for you.

Result when everything is OK:

FND – 43 – Configure SAP backend system (BEP) to accept assertion ticket from SAP Gateway

Yes, this item should be under BEP and not HUB, but I am following SAP Help here, so sorry for the confusion!

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.3.

Allow SAP Gateway HUB (IWNFD) to logon via SSO to SAP backend (BEP).
SAP Help

No SPRO activity.

System: BEP

Transaction SSO2

  1. To configure SSO by installing the system certificates, go to transaction SSO2

  • Destination: Give RFC destination: GWDCLNT001 (IMPORTANT: must have been created earlier on the BEP system)

  • Host name: DNS name of SAP Gateway HUB: nwgw74.tobias.de
  • Instance Number: Instance number of SAP Gateway HUB: 01

Run the program. In case the tool finds some problems, it allows you to let it solve them for you.

Result when everything is OK:

FND – 42 – Define trust between SAP Gateway and SAP backend

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.2.

A trust relationship between IWFND and BEP is needed to allow for SSO.
SAP Help

No SPRO activity.

Transaction SMT1


Trust relationship wizard opens


Inform a RFC destination: ECCCLNT001 (created in previous step)


Click continue. Basic connection checks are done

Continue

Continue

Complete

FND – 41 -Create RFC on SAP Gateway (FND) to SAP backend (BEP)

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.1.

A RFC connection between SAP Gateway HUB and SAP backend is needed so that the HUB system can communicate with BEP. Without this, the OData services exposed at Gateway won’t work, as they cannot map the services (BAPIs) to a backend.
SAP Help

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

This open transaction SM59

  • Create

  • Give a name for the RFC destination, like <SID>CLNT<Client>
  • RFC Destination: ECCCLNT001 (example)
  • Connection type: 3
  • Inform a description
  • Go to tab “Technical Settings
    • Load balancing: Yes or No, depending on landscape
    • Target host: host name of SAP backend (BEP) system
    • System number: system number of SAP backend (BEP) system

  • Go to tab “Logon & Security
    • Client: cliente of BEP system
    • Current User: Yes
    • Trust Relationship: Yes


  • Go to tab “Special Options
    • Transfer Protocol: Classic with tRFC


  • Save

BEP – 2 – Defining a Remote Function Call to SAP NetWeaver Gateway

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

  1. Settings for Idempotent services Blog SAP Help
  2. Defining a remote function call to SAP Gateway SAP Help
  3. Connection settings to SAP Gateway Blog SAP Help
  4. Configure bgRFC supervisor destination Blog SAP Help

This document explains how to execute step 2.

“You create or define a background remote function call (bgRFC) destination, which is used for communications in an outbound queue, and an inbound queue among SAP systems.”
SAP Help

Important: “If you are using push from an SAP Business Suite backend system to an SAP NetWeaver Gateway hub system, it is important not to have a trusted RFC connection.”

SPRO: SAP Reference IMG and navigate to  SAP NetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver Gateway Create RFC Destination for Outbound Queues

This open transaction SM59.

  1. Click Create.


  1. Give a name for the RFC destination, like BEP_BGRFC_DEST
  • Connection type: 3
  • Inform a description
  1. Go to tab “Technical Settings
  • Target host: host name of SAP Gateway system
  • System number: system number of SAP Gateway system


  1. Go to tab “Logon & Security
  • Enter the logon data for the technical user
  • Trust Relationship: No


  1. Go to tab “Special Options
  • Transfer Protocol: Classic with bgRFC


  1. Save
  2. Test the connection.