Resolving "processDPCommands' API" Error when accessing WebI XI 3.1 report

If you are getting an error "An internal error occurred while calling 'processDPCommands' API. (Error: Err_WIS_30270)" when accessing a SAP WebI XI 3.1 report .

My environment when this error was recreated:

SAP BW: BW 7.0 and above but not BW 7.3
SAP BusinessObjects: SAP BO XI 3.1 SP3 FP6.7
SAP InfoView: Client version XI 3.1 FP6.7
SAP Integration Kit: version XI 3.1 FP 6.7

SAP WebI report is access via SAP InfoView (XI 3.1) version. The source is universe version XI 3.1 on an SAP BW MultiProvider.

If we carefully trace how this happened, it would come to light that migration sequence was not right. You will get this error mostly when the report was migrated before the universe or the universe was migrated before the SAP BW infoproviders were transported in SAP BW.

Solution: Open the Universe in Designer, make the that it is pointing to the right source (if it was not, you would have gotten a different error altogether). Perform an integrity check.

When you do so, you will see probably a result very similar to this:


Parse Joins: 1 Errors
ParseObjects: 4 Errors
Parse Conditions: OK
Check Loop: OK
Check for Context : OK

Check the errors, fix them, save the universe and export to the CMS again.

Now access your SAP WebI report and hopefully you should no see the error. If error persists, you might want to repeat these steps.

Inform me if any more information needs to be added.

*******
******
*****
****
***
**
*

Assignment of Source System ID in SAP BW

If a characteristic ZCUST_ID is coming from multiple source systems and is also defined as Master Data bearing InfoObject in SAP BW and is compounded with Source System ID (0SOURSYSTEM), then it becomes necessary to do Source System Assignment in SAP BW to let the system know which system the value for this characteristic ZCUST_ID is coming from.


This is true for even the delivered InfoObjects and even if that field is mapped to another field in several SAP source systems.

All you have to do is follow these steps to create the Source Systems ID’s and do the assignment.

1)      In the Administrator Workbench, choose Tools  à Assignment Source System to Source System ID.

Fig 01 – Assignment of Source System ID

2)      Choose Create.

Fig 02 – Create Source System ID

3)    Enter the logical system name and a description, and confirm you entries (in this example the name 

       would be BIDCL100 or DEVCL100).

4)   In the Source System ID column enter the ID name that you also entered in BW1 for the corresponding source system. (In this example it would be ID 01 or ID 02).

5)    Save your entries.

Fig 03 – Display Source System IDs

I hope this will be helpful to others.

*******
******
*****
****
***
**
*

Comprehensive List of BI Tools - 2 of 10 Parts

I'm continuing the series with some other BI Tools that I'm aare of in this Part. The Part 1 list is given here

Part 2 list continues here:

Teleview Features: -  Touted as Self Service Enterprise BI -  Comes integrated with a database, data capture and data processing component and an interactive     front end with multiple visualizations -  Data Integration and Data Processing -  Modular Architecture -  Role based security -  Dashboard Creator -  Works with Linux and Windows (64 bit for server and 32/64 bit client) Version: Website: http://abibasystems.com/teleview.htm Developed by: ABIBA Systems Private Limited

Datawatch Features: -  Is referred to as Monarch Report Manager on Demand (Monarch RMOD) -  Monarch RMOD can be integrated with CRM applications, Web Portals -  Can be installed on Windows Server 2008 R2, IBM AIX, Solaris, Linux – Red Hat 5.2 -  Application Servers: JBOSS, IBM WebSphere, Apache Tomcat -  Java-based desktop deployment Version: Website: http://www.datawatch.com/Monarch/Report_Management.php Developed by: Datawatch Corporations

Will continue with the list in other posts ....

*********
********
*******
******
****
***
**
*

Dates in WebI always in the different format 1/1/70

The date always displayed as 1/1/70 in WebI that are built on top of BEx queries.

SAP BusinessObjects 4.0 (Product: 14.0.0) Patch level 2.6

SAP BW: SAP EHP 1 for SAP NetWeaver 7.0 (Patch 08)

The BEx : BI AddOn 7.x on (based on 7.10); SP 10, Patch 1

Java Pug-in: Java version 6 Update 29 (build 1.6.0_29b11)

I’m using the WebI from BI Launch Pad which uses Java plug-in to work. I’m not using SAP Web Intelligence Rich Client (this one needs local client installation).

For e.g.:

Fig 01 – Wrong WebI dates

While it suppose to display

Fig 02 – Corrected WebI dates

The solution for this is given in this SAP Note. You will need an OSS ID to access the SAP service marketplace to see this note.


1648578 - date values displayed wrong

The issue is fixed in Patch 2.7 and has adapted as ADAPT01585086.

I hope this will help others. Please leave comments or suggest a coorection.

********
******
****
***
**
*

Some Options are disabled / not funtional in WebI 4.0 on top of SAP BW BEx Query

 SAP BusinessObjects introduced a new functionality where now WebI documents can be created on top of BEx query using BICS.


SAP BusinessObjects 4.0 (Product: 14.0.0) Patch level 10.0

SAP BW: SAP EHP 1 for SAP NetWeaver 7.0 (Patch 08)

The BEx : BI AddOn 7.x on (based on 7.10); SP 10, Patch 1

Java Pug-in: Java version 6 Update 29 (build 1.6.0_29b11)

I’m using the WebI from BI Launch Pad which uses Java plug-in to work. I’m not using SAP Web Intelligence Rich Client (this one needs local client installation).

1) The Scope of Analysis and View Script (previously View SQL) option in the Design mode of the Query
     Panel are not available if you use BEx queries as a source. You will see those disabled.

                    FIG 01 – The Scope of Analysis and View Script options disabled

 
2) In the Filter area in WebI on BEx, the AND operand does not change to OR
 
 

    Fig 02 – Query Filters using AND operand

 
If you try to double-click on this operand AND to try change it to OR, this will not work.
 
3) The search operands underscore (“_”) and percentage (“%”) doesn’t seems to work in WebI on
    top of BEx queries. Only operand “*” works. The obvious reason is the List of Values are not save
    on server.
 
 

 Fig 03 – Search Operand for List of Values

 
 

   Fig 04 – Search in Keys option

 
 
4) The Use Query drill also doesn’t work. Although you can check it in the Document Properties but it
    doesn’t work
 
 

         Fig 05 – Use Query Drill option in Document properties

 
At this time I could only find these options not to work. There could be other’s which I could not yet test.


Please update and let me know if anything here needs to be corrected or needs to be added here.


*******
******
*****
****
***
**
*



Installing SAP Data Services 4.0: Part 3 - Integrating with SAP BusinessObjects BI Platform

I came across a blog where the expert author Stuart Wallace provides details on installing SAP BusinessObjects Data Services. An excellent read.

Installing SAP Data Services 4.0: Part 3 - Integrating with SAP BusinessObjects BI Platform


I hope you will like it.
 
*****
****
***
**
*

How to fix Error 09 ...

Issue:

While activating the DataSource or even when executing an InfoPackage, you might come up with a “Caller 09 …” error message.

While trying to preview data from DataSource, you might come up with this type of error

“S:RSSDK:300 Field DATE not a member of /BIC/CAZDS_TEST_0 00040000001”

FIG 01: Error message in Monitor

 
This error message has the same roots as the error message in the inset box.

This might happen even if you are loading data from a DSO into an InfoCube.

Cause:

It is a memory dump; load got failed due to memory space unavailable.

Troubleshooting:

If you look at details, you will see this message

Error message from the source system

Diagnosis
An error occurred in the source system.

System Response
Caller 09 contains an error message.

Further analysis:
The error occurred in Extractor .
Refer to the error message.

Procedure
How you remove the error depends on the error message.

Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.

Check transaction code ST22 to see if there are short dumps.

Check transaction code SM12 to see if there are any locks.

Check transaction code SM21 to check system logs

Check transaction code SM37 to check status of the Job (finished or terminated).

Resolution:

Nevertheless, these points might help:

• If this is happening at the while loading that Data from DSO into the InfoCube, then drop the indexes and try reloading data in several ‘smaller’ request by slitting the data with an appropriate filter on an InfoObject for e.g. 0CALYEAR

• If the source is SAP systems and also if you are in Production environment, it would be necessary to activate the DataSource

1. Go to transaction code SE38
2. Run the program RSDS_DATASOURCE_ACTIVATE_ALL (If you are on SAP BW 3.5, then use this RS_TRANSTRU_ACTIVATE_ALL)
3. Select the Source System and select the DataSource name and click execute. Check box for "Only Inactive objects"

• If this error happens in dev environment and the Source Systems are non-SAP, I would recommend deleting the DataSource and creating a new one. This will surely fix the problem.

The messages in here might be helpful in getting this resolved.

I hope this will be helpful.

*****
****
***
**
*