Communication Destinations 

Connection destinations are required in BI in the following areas:

·        BEx Web

RFC destinations in the J2EE Engine

RFC destination for the portal

For more information, see the Implementation Guide (IMG) for SAP NetWeaver and choose  Business Intelligence  → Reporting-relevant Settings → BEx Web → Integration into SAP Enterprise Portal 6.0

·        Use of TREX

RFC destination in the BI system

See the Implementation Guide for SAP NetWeaver  → Business Intelligence  → Connectivity of TREX

·        Connection of data sources to BI system

These destinations are usually not delivered but are created by customers.

If you want to connect SAP systems and non-SAP data sources as source systems to BI, you usually need RFC destinations.

To use UD Connect you need an RFC destination for the J2EE Engine. Communication between the J2EE Engine and the BI server is undertaken by the JCo. See the Implementation Guide for SAP NetWeaver  → Business Intelligence →  UDI Settings by Purpose →  UD Connect Settings.

The destination for a Myself BI is created automatically by the system the first time you open the BI Data Warehousing Workbench.

XML data is sent to the SAP Web AS SOAP service using specific ports, then into BI. For more information, see Sending Data to the SOAP Service.

The communication between BI and source systems is the responsibility of BI background users and the background users in the source system (in the case of the SAP source systems). The BI background user requires the authorization profile S_BI-WHM_RFC. The background user in the SAP source system requires the authorization profile S_BI-BW_RFC. For more information, see Authorization Profiles for Background Users.