Posts tagged SAP
I’m one of the lucky consultants who can ‘play’ with SAP BW7.4 on HANA at a client. Last week they upgraded our SAP BW 7.3 system to a new release –> SAP BW7.4 SP11. Before the upgrade we developed several Composite Providers via the traditional SAP GUI. A Composite Provider is an InfoProvider in which you can combine data from BW InfoProviders such as InfoObjects, DataStore Objects, SPOs and InfoCubes, or SAP HANA views such as Analytical or Calculation Views using join or union operations to make the data available for reporting.
After an upgrade we recognize two different kind of Composite Providers: the “Local Composite Provider” (coming from SAP BW7.3) and the new SAP HANA Composite Provider.
|Local Composite Provider||SAP HANA Composite Provider|
|Develop in:||Create in SAP BW7.3
Can be maintained in SAP BW7.4
|Create in SAP BW7.4|
|Create / edit:||SAP GUI
Modeling Tool in Eclipse
|Modeling Tool in Eclipse|
|Icon in RSA1:|
After the upgrade you’ve the possibility to migrate your Local Composite Provider to the new SAP HANA Composite Provider. With the program (SE38/SA38) “RSO_CONVERT_IPRO_TO_HCPR” you can convert your InfoProviders including the SAP BEx queries you’ve previously built. On OSS we found a SAP Note that gives you more insight in the program.
If you want to create a new SAP HANA Composite Provider, please read the following document from the SAP SDN: First Guidance SAP BW 7.40 on HANA – CompositeProvider.
Good luck with migrating your Composite Providers!!!
When employees in your organization need authorization for SAP BW and SAP BO, assignments of authorizations need to be executed in both tools.
When you have to do this for some users, the work is limited. If you, however, receive a request for many users, it would be nice if this process could be simplified.
This blogpost describes a way of working on how you can easily adapt your SAP BW and SAP BO authorizations.
If you’re interested in how to setup a good and maintainable authorization-structure in SAP BW and SAP BO, please read the how-to document, you can download the document here.
Performance issues with the filter function in SAP BO Analysis…? This solution can help you to speed-up SAP BO Analysis!
This optimizer can be used for the filter function on the right panel in SAP BO Analysis (see image below). When you want to filter on an object that contains a lot of records (i.e. 0MATERIAL, 0PRODORDER, etc.), users can wait a long time.
First all posted values are read from the SAP BW infocube. In the properties of an infoobject the standard setting for “Query Execution Filter Val. Selectn” (tab BusinessExplorer) is set to “Only Posted Values for Navigation”. This is the reason why SAP BO Analysis take much time to read the posted values.
To speed up SAP BO Analysis, you can change the setting “Query Execution Filter Val. Selectn” to “Values in Master Data Table” (see image below).
This is not the full solution!!! Read more… (more…)
All consultants have the experience to make a quick demo in SAP BW, but demodata is sometimes an issue. If you need to create a demo in a short time, use an ABAP program that will generate the data for you. Follow these instructions to fill your InfoCube with generated data:
– Create your InfoCube with all relevant InfoObjects
– Start transaction SE38
– Execute (F8) program “CUBE_SAMPLE_CREATE”
– Choose the InfoCube that need to be filled with demo data
– Select the number of records you want
– Execute the program and the cube will be filled
– Run your report or display the cube data and you’ll see results
Note: The generated data will not be representable to show it to your client(s), the data can be used for internal demo purposes. If your masterdata is up to date and representable, select the option “Vals from Master Data Table”
Since a long time ago I’m back into SAP BW datawarehousing, currently I’m working in a project where SAP BW is a main focus. From datasources to BEx queries…. I need to retrieve my knowlegde from years ago During a transport procedure on the ECC side from development to test I transported some datasources. Normally after every transport with datasources, a manual replication for the datasources on the BW side is necessary. I found a simple solution that you will not need replicate the datasources manually. If you add an object into your transportrequest, the replication can be automatically be done.
Follow the next procedure to replicate your datasources automatically:
- Modify your current transportrequest in SAP BW
- In your BW transport add an extra object “ISFS” with program ID “R3TR”
- Save your transportrequest
- Transport your request to the next environment (be sure that de datasources will exist on the source side, i.e. ECC)
This is not a new solution, but it’s very useful to share :-).