error while creating a cube using Cube Builder

[Former Member]

we have installed the Cube builder for SSM 7.0

while creating the cube I am facing a error and the .TRC file contents are as follows :-

LSS>

LSS> set control LINKID SSM_CB_EA

LSS>

LSS> .... capture cube id in a control var to simplify queries on other tables

LSS> access lslink

LSLink> connect SSM_CB_EA

LSLink>

LSLink> SELECT ID FROM CPMS_CB_CUBES WHERE NAME = 'CUBEBUILDER1'

[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'CPMS_CB_CUBES'.

SQLSTATE: S0002

SQL System code: 208

LSLink> lss create code = 'set control CUBEID ' + ID

LSLink> output proc setcubeid;PIPADMINDEFAULT over

LSLink> peek create nohead nonumb

No Fields currently Selected

ACC004:

No Record Has Been Accessed From the Database.

ACC004:

No Record Has Been Accessed From the Database.

CHE FRE

CHE UPD

Kindly help me out........

[Former Member]

Hi,

I have changed the lslink to use the user SAPCE1ADM.

After this, I get following error, when building a new CUBE in cubebuilder.

But the model connections; "CBSYS2_MM" and "CBSYS2_SC" are ceated.

In PAS I can see the SYS2 DB, but no measures are attached.

I am using MsSQL.

LSS> 
LSS> set control LINKID SSM_CB_EA
LSS> 
LSS> .... capture cube id in a control var to simplify queries on other tables
LSS> access lslink
LSLink> connect SSM_CB_EA
LSLink> 
LSLink> SELECT ID FROM CPMS_CB_CUBES WHERE NAME = 'SYS2'
LSLink> lss create code = 'set control CUBEID ' + ID
LSLink> output proc setcubeid;PIPADMINDEFAULT over
LSLink> peek create nohead nonumb
ACC089:
Unable to Find ID for CREATED Field CODE
ACC089:
Unable to Find ID for CREATED Field CODE
LSLink> output off
LSLink> 
LSLink> end
LSS> 
LSS> job setcubeid;PIPADMINDEFAULT
LSS> ACC089:
ACC089:
^
Expected an Application Server Command
CHE FRE
CHE UPD

Please help

Martin Bille

[former_member84747]

Hi Martin,

I believe that the issue you are encountering now is that you're using the wrong set of procedures for accessing MS SQL Server.

In section 5.4.1 (Setting up SAP NetWeaver System database software) in the Strategy Management configuration guide, there is a section which discusses steps that are required depending on whether or not you are using MaxDB or MS SQL Server as your system database behind NetWeaver CE. My guess is that you have not followed the steps described for SQL Server here. This is simple to do thoughm, because all you need to do is copy the files in the "<install-dir>\SAP\SSM\InternetPub\procs\sqlsrvr_procs" into the <install-dir>\SAP\SSM\InternetPub\procs" directory.

This is required because, when using Cube Builder or Entry and Appropval, the PAS component communicates directly with the system database in order to load data from there into PAS. Because MaxDB and SQL Server have different SQL syntax, specifically regarding field concatenation, slightly different SQL is required. So if you copy the SQL Server specific procedures across, you should be able to successfully build your model from Cube Builder.

Of course, having read through your question again I'm not 100% sure that this is what you are hitting. The problem you're seeing seems to be that, when we internally concatenate some selected fields together, we aren't finding a field called ID. However, the SQL select being issued doesn't seem to have returned any error messages, so I'm not sure why there is a problem referencing the field.

The only thing that comes to mind is a problem that I ran into at one point with the type of driver I was using to connect to SQL Server. The PAS component of Strategy Management, even though it runs on Windows 2003 Server 64bit, is still only a 32bit component. This means that, when configuring the System Data Sources within the ODBC applet in Control Panel, it is critical that the 32bit version of that ODBC applet be used - as documented in the note at the end of section 5.4.3 in the configuration guide. The reason this is important is because, if you use an OLEDB connection to SQL Server, for some reason the field names are not returned correctly. It is only when using the ODBC driver that the field names are returned correctly.

So please ensure that you are using the ODBC driver for your Link ID which connects to SQL Server, and not an OLEDB connection.

Hope this helps,

Robert

Edited by: Robert Holland on Dec 19, 2008 3:23 PM