Introduction
The SAP BPC NetWeaver connector uses SAP .NetConnector NET Connector which creates a direct connection to the SAP BPC NetWeaver cube. The following architecture picture shows the system components:
MDX
This connector generates internally MDX queries to retrieve the data from SAP BPC NetWeaver, which are translated into ABAP function calls. Read more on MDX trouble shooting here: Turn on MDX Logging to investigate data or performance issues
Connectivity
The connection to SAP BPC NetWeaver is managed in the /wiki/spaces/CXO/pages/2806776143 specify the following fields:
- Server/SystemNumberr: the IP address of the NetWeaver serverand server and the open port from the range 3300-3399.
- (Network traffic over specified port needs to be allowed)
- Client: The client number
- Cube: The technical name of the SAP BPC NetWeaver cube (Note, that prior to CXO version 6.3.2, the cube name should not contain leading $-sign).
- Username & Password: Then The name and password of the user on SAP BPC NetWeaver system.
Use the check button to check if the connection can be made.
Configure CXO-CockpitConnectivity to a load balancing server
it is also possible to connect to a BW Message Server. This enables load-balancing of sessions which prevents queuing of MDX-queries in case of a high load of reporting requests.
Configure CXO to run on SAP BPC
In order to successfully run CXO -Cockpit on an SAP BPC NetWeaver application the following additional configuration is required.
- Dimension Mapping: all of the CXO Core Dimensions need to be mapped
- Sometimes it is required to use Dimension Splits in order to get all required dimensions. Specify dimension splits first then map the dimensions.
- Set the Period Frequencies table
- Correct any Dimension Variable errors
- In the configurator settings there are a few SAP BW-specific settings which can be adjusted.
Installation Prerequisites
You can find the Installation Prerequisites file for SAP BPC NetWeaver in this article.
See also
CONTENT
| Table of Contents |
|---|