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.

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