I have gone through a lot of articles on SCN which speak extensively about integration with BO-BW however, I could not find a document that consolidated and spoke about UNX on Multiprovider SSO manually setup, BICS on BEX issue and the concepts on BW. In case if there are issues how do we troubleshoot to get to the root of the cause.
Concepts on BW:
Before we begin on how we integrate BO with BW, we must be aware of some of the basic concepts of BW.
- Multiprovider: A multi-cube is a union of basic cubes. The multi-cube itself does not contai n any data; rather, data reside in the basic cubes. To a user, the multi-cube is similar to a basic cube. When creating a query, the user can select characteristics and key figures from different basic cubes.
- Infocube: An InfoCube is a fact table and its associated dimension tables in the star schema. The maximum number of characters allowed for the technical name is 30.
- Info Object: In BW, key figures and characteristics are collectively called Info Objects.
- DSO: A Data Store object serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level. This data can be evaluated using a BEx query.
- Bex: Short for Business Explorer. It includes following tools to present the reports to end user: Analyzer, Query Designer, Web Application Designer (WAD), Report Designer and Web Analyzer.
- Key Figure: Key figures are numeric values or quantities, such as Per Unit Sales Price, Quantity Sold, and Sales Revenue. The maximum number of characters allowed for the technical name is 9. Reference Characteristic.
Understanding Connections:
In order to proceed further into development ways we must first understand the mode of connection with the BW system.
- OLAP Universe: before 4.0 had set in the market in 3.1 we connected through the unv universe .This was the traditional way to connect to the BW environment through BW Info cubes or Bex Queries. In this process the MDX parser is used to co nnect to Bex and the output comes in a flat structure. The RFC executes the MDX parser which executes a query.
- Relational Universes through Data Federator: Currently in 4.0 and higher versions we are using the unx universe, the leverage or advantage of this universe is that the data federator allows to create a single as well as multiple connection to connect to a BW source. So for example to can have a multiprovider as one source and one or more DSO's in the same universe.
Note: This connection type too flattens the hierarchy.
This method connects through the SAP JCO/ Java Connector to connect to the BW data source.
Also through this method we cannot connect to the BEX Query.
- BICS Connection: The last connection method is the BICS connection / BI Consumer Services which connects directly to the Bex Query in BW. No universe is needed here and the hierarchies do not come in the flattened structure. Also connecting to BW through this mechanism brings in better performance and faster access to BW data.
Connecting to Multiprovider, Infocube through UNX:
While working on my current project, we connected to the Multiprovider, Info cubes, DSO's through the multisource capability of the under lying Data Federator connecting to the BW environment.
To establish connecti vity to connect through the SAP JCO/Java Connector.
When we speak of JCO it is very important that while setting up of connectivity with the BO and BW we ensure that the JCO connection is setup. This process can be a manual process and an automatic. We explain below the necessary steps to create a JCO connection manually.
- Logon to SAP logon screen. Enter t-code SE37 and click execute.
- This opens the parameter panel. Enter function module RSDRI_DF_CONFIGURE click execute.
Set the parameters as follows.
I_ONLY_CHECK'' (empty)
I_RFC_DESTINATIONDF_J CO_hostnameOfBOEServer_some-sid
I_REMOVE_CONFIGURATION'' (empty)
- Run SM59, check TCP/IP connections and you should be able to see the newly created JCO connection DF_JCO_MYHOST( adaptive processing server)
- This JCO connection should be updated in the parameters of the Relation Connection.
- Login to Data Federator ->Connector Configurations tab->Create Configurations
- In the property programIDMapping, point the JCO connection only use the RFC destination defined in step 4
- In the programIDMapping = MySia.AdaptiveProcessingServer=DF_JCO_MYHOST
- In the property gatewayHostname, type in the FQDN of the BW server.
Note: Create the relational JCO connection to BW using an account that has full authorization on S_RFC_ADM
It is always advisable in an environment where you have multiple adaptive processing servers to create separate JCO connections.
Authorizations to access data through relational connection.
When a user is accessing data from the BO end, to access data at the BW end through relational connection. There are certain authorizations/ rights that are needed to be provided to those group pf users.
The rights or BW roles that required:
S_RFC (Authorization Check for RFC Access)
S_RS_ADMWB (Data Warehousing Workbench - Objects)
S_RS_AUTH (BI Analysis Authorizations in Role)
S_RS_ICUBE (Data Warehousing Workbench - InfoCube)
S_RS_IOBJ (Data Warehousing Workbench - InfoObject)
S_RS_ISET (Data Warehousing Workbench - InfoSet)
S_RS_MPRO (Data Warehousing Workbench - MultiProvider)
S_RS_ODSO (Data Warehousing Workbench - DataStore Object)
The above authorizations are required for end user that run queries against
BW e.g. running Webi reports.
You can keep the connection in the BO end to Single Sign on without the manual user name and password .You might receive an error but there shouldn't be any issue in accessing the data.
Refer to note: SAP Note 1465871
The coding here comes as MSQL and not as XML and we can play around with the tables and the structure as we wish too.
Connecting to BICS –Bex Query:
When we are creating a connection from BO to connect to the Bex Query we are doing the same through SAP BICS client.
Creation of the connection is a simple process however, but in order to use the SSO we must ensure that the certificate you created during the configuration of STS has been added to the SYSTEM PSE section of the STRUSTSSO2 transaction. Else while we access the connection through SSO, the connection will through an error.
No comments:
Post a Comment