Showing results for 
Search instead for 
Did you mean: 

NWBC u2013 are connections to multiple SAP backends possible?

Former Member
0 Kudos

Apologies if this is not the correct Forum group, but I was unable to find a forum specifically for NWBC (Netweaver Business Client).

We are currently trying to build a u201Ccockpitu201D in NWBC for use by Sales Reps to perform their daily tasks.

e.g. Enter Sales Order

View Customer Master

View Price Conditions


Most of the tasks which the Sales Rep will perform will be in an ECC u201Cbackendu201D, however we also have some requirements to link to CRM transactions (e.g. Activity Management) or to run BW reports.

The SAP help for NWBC states that it is only possible to connect to one backend SAP system at a time. If transactions need to be run from other backend systems it is necessary to close the current NWBC connection to ECC and open a new connection to the other system (e.g. CRM or BW).

Has anyone in this forum ever experienced a similar requirement? If so, were any workarounds found?

The current workarounds I am investigating are:

u2022 As in NWBC it is possible to call URLS of external webpages (e.g. google), can URLS of the BW or CRM systems be called? e.g. to see if a BW report can be web-enabled, and to setup the link to a web report in the PFCG role which will be assigned to the Sales Rep.

u2022 PFCG menu options also have the possibility to specify an RFC destination. I was hoping that this may allow us to add an entry in the menu for a CRM transaction and then specify the CRM RFC destination. Unfortunately, this did not work.

u2022 Are there any other options possible for u201Ctunnelingu201D through the open ECC backend to CRM or BW?

Many thanks in advance for any help.

For info, we are on ECC EHP4, and using NWBC version 1 and 3.

Alistair Crawshaw

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Please disregard this question. NWBC to call multiple backends IS possible, but you need to setup Trusted RFCs/SSO tickets to get it to work.

Consider the example below:



We have a NWBC (version 3) connection setup to an ECC backend. This works well.

We have two roles assigned to the user

1st A collection of ECC transactions

2nd A collection of APO (i.e. SCM) transactions (an RFC connection to the relevant APO system is linked to this role)

In order to get the SSO to work for the APO role (and for the logon screen of the APO system not to be shown), perform the following:

RFC + SSO changes required


The system parameters are set as below on both ECC and APO systems (as per note Note 1286549 - SSO logon not possible - While logging through NWBC):

login/accept_sso2_ticket 1

login/create_sso2_ticket 2

The same user ID exists on both systems, and has the authority S_RFC and S_RFCACL on both systems (with wildcards for the system).

The systems and clients of the ECC and APO systems are set as below:

ECC System DSS client 100 DSSCLNT100

APO System DPD client 640 DPDCLNT640

On the ECC system:

In transaction SM59 we have:

ABAP RFC connection DPDCLNT640 set as Trusted, with current user id.

HTTP RFC connection DPDCLNT640_HTTP with same user id.

Remote Logon works for both of these, and the user/password does not have to be reentered upon logging onto APO.

Transaction SSO2 was run against the ABAP connection + activated with all green lights (this was done with the ABAP connection set initially as non-trusted, as it did not work when it was initially set as trusted).

Transaction STRUSTSSO2:

Go to the menu option below:


Specify the RFC destination of the APO system (DPDCLNT640)

Change the application to SSO2.

Then after the certificate has been opened, click on the buttons:

- Add to ACL

- Add to Certificate List

Note: in the Logon ticket section at the bottom of the screen, it is possible to delete the entries as these are recreated by the u201CAdd to ACLu201D button.

On the APO system:

In transaction SM59 we have:

ABAP RFC connection DSSCLNT100 set as non-Trusted, with current user id.

No HTTP connection needed

In transaction SMT1:

The ECC system was setup as trusted system by creating a new entry using the ABAP connection DSSCLNT100.

Transaction STRUSTSSO2

This was also run to import the certificate from the ECC system. The u201CAdd to ACLu201D button worked successfully, but the add to certificate list did not work u2013 however, this did not seem to prevent the functionality.

After applying the changes above, NWBC was able to call the APO system via SSO correctly.

Ali Crawshaw