1/3/13

Welcome, Guest Login Register Getting Started Newsletters Store

SAP Community Network Wiki - Contributor Corner - Issues in BI BW Implementation

Solutions Services & Support About SCN Downloads Industries Training & Education Partnership Developer Center Lines of Business University Alliances Events & Webinars Innovation

Issues in BI BW Implementation
Added by Shilpa Vinayak, last edited by Shilpa Vinayak on Aug 27, 2010
This article caters to one of the most frequently asked questions; What are the difficulties faced in implementation projects in BI and how to resolve the issues? Below are a few issues that I am facing in the implementation, and I w ill keep posting the new issues that I face as I progress on to the various phases of the implementation project. 1) First Login to RSA1. When the basis team hand over the system to the BW consultant, the first t-code that any consultant w ould try w ould be RSA1. In that, I got error message "BI system has no logical name". This reflects, that the configuration setting for maintaining logical system name is missing. " Click on create, or to avoid this error, you may go to SPRO SAP Customizing Implementation Guide -> SAP NetWeaver -> Business Intelligence -> Links to Other Source Systems -> Define Logical System

Once that is resolved, and you login to RSA1 again, you w ill get a message to "Activate and Replicate the Metadata". You may select "replicate as w ell" to avoid redoing the task again. This action w ill install and replicate the technical content in the system. It w ill also start a background job in the system for the above action.

You may check the logs in slg1, and correct the errors (if any), also, check the job in sm37 for its completion. 2 )Error: Segment E1RSSH does not exist The most basic setting in a BW system is its connectivity w ith the R/3 system (w hich is a basis team activity, but BI consultant can alw ays help). Issue: While creating source system, I am getting an error "Segment E1RSSH does not exist". Diagnosis Segment E1RSSH is in the syntax description, but it does not exist. The issue w as that some of the entries in the table EDISEGMENT w ere missing. As this a standard table, it is recommended to restore the table from Backup or from another BI system. (Please ask your basis team to do it.) Now , the significance of the segments: We all know that w e require 3 message types in total to communicate w ith R/3 system. RSRQST, RSSEND and RSINFO. Now each of the message types has some segments w hich help in communication. You can see this segment types in the t-code w e30. Just enter the basic idoc type and click on display. This error is not a common error, but can be useful if at any stage of implementation or support, the table gets disturbed and you have issues w ith source system connectivity. (Thanks to my team-mates to help me identify this issue.) 3) Error w hen scheduling job (JOB_SUBMIT) The RFC User used for communication and background jobs in the BW system should be maintained as a System User. If it is not maintained as a system user, there might be some problems or errors on various stages. For example, in my system the User Type for the background user w as mentioned as Communication Data. And due to this setting, w hile creating a process chain for the master data, the process type attribute change run could not be added. It w as giving error message. "Program RSPROCESS is to be scheduled as job BI_PROCESS_ATTRIBCHAN under user <background user name>" Sy-SUBRC=8 w as generated for the above error w hich meant "Error w hen scheduling job (JOB_SUBMIT)".

wiki.sdn.sap.com/wiki/display/Community/Issues+in+BI+BW+Implementation

1/2

1/3/13

SAP Community Network Wiki - Contributor Corner - Issues in BI BW Implementation

The user type of background user w as changed to System and the error w as resolved. 4) Error : no allow ed in compounding While activating the InfoObject 0Material the follow ing error w as encountered "Characteristic 0CM_CTAR: Unit 0UNIT_DIM no allow ed in compounding". "Characteristic 0CM_SHAR: Unit 0AREA_UNIT no allow ed in compounding" This can be resolved by SAP NOTE 1139547: Correction Instruction: 608295 5) Dependency error w hile creating Process Chain When you create a process chain, sometimes the follow ing processes are not identified correctly by the system. For example, create and delete index etc. This error w as rectified by applying note: 1122289 6) Error: Characteristic 0REQUID: Status of number range BIM9999998 is too small by 00000000000000001 Getting a short dump on loading an InfoCube. Also, the request Id w as not getting generated. Check the SAP note 615389, and do the RSRV test for the parameter 0REQUID. One checking that w e found the below error. "Characteristic 0REQUID: Status of number range BIM9999998 is too small by 0000000000000000 1". You can check the number range in t-code SNRO. Click on Correct error in RSRV and then check the number range object again. Now the current number of the object in SNRO, w ill be the SID of request generated, w hen you load the infocube, and this number keeps on increasing as and w hen new Requests are created. 7) The RFC destination for ECC system dialog connection does not w ork When trying to install the Business Content involving transfer rules, DataSource etc, w hich needs a check for dialog logon to the source system, w e w ere getting the error "RFC connection for destination XXX_DIALOG does not w ork. While installing BC DataSource, a prompt has to come for checking if the user has authorization for source system. The navigation dialog w as not w orking, even w hen trying to install the Business Content involving transfer rules, DataSource etc, w hich needs a check for dialog logon to the source system; w e w ere getting the error "RFC connection for destination XXX_DIALOG does not w ork. It w as using the RFC user for this activity, and RFC user w as not set as dialogue user. The user type of RFC user changed to as Dialogue user and thus fixed. Please take help of basis team as RFC destination and related settings should not be changed w ithout basis concern.

Follow SCN Contact Us SAP Help Portal Privacy Terms of Use Legal Disclosure Copyright

wiki.sdn.sap.com/wiki/display/Community/Issues+in+BI+BW+Implementation

2/2