SSM Data Model

Hi,
Can anyone tell me where I can find the data model for the relational tables on SSM?
Thanks in advance
Cliff Stinson

Cliff,
Did you just want to know where the data resides in SSM or were you looking to pull that data for other uses?
You can open up PAS, select a data model and use the DataView tab to see the data loaded within that model. Consulting the PAS help section, in the IDQL tab you can enter commands to show the structure of the model, dimensions, variables, etc.
Consider SSM a data consumer rather than a data provider. Loading data into SSM means creating a data model and a file layout that will match the external source. Although there is a connector available to bring data in from SAP BW, it's one-way.
With SSM 7.5, there is the ability to use web services to make SSM data available primarily to other BusinessObjects applications like Xcelsius for dashboarding purposes.
It is not recommended that you change or modify tables in SSM since that can serious affect the performance and usage of the application.
Regards,
Bob

Similar Messages

Excel Workbook with Excel Data Model stored on SharePoint - daily refresh

I'm not sure if this is exactly the right forum but I'm hoping that someone here can either answer or point me in the right direction.
I have an Excel Workbook with an Excel Data Model.
The Excel Data Model uses SQL to contact our data warehouse and pull through data into tables.
We are storing the Workbook on a SharePoint site and viewing it using Excel Services.
The data in our data warehouse is updated daily and so I would like to refresh the workbook daily and remove the option to refresh the data in the browser.
Is this possible with a workbook that has an Excel Data Model (I've seen lots of posts that relate to workbooks with connections to tabular models).
Thanks
Paul

Hi Paul,
I have answered this issue in this thread that you posted in SQL Server PowerPivot for SharePoint forum, please see:
http://social.msdn.microsoft.com/Forums/en-US/9627939c-e9f1-48ae-a6ed-0c238d8f2d69/excel-workbook-with-excel-data-model-stored-on-sharepoint-daily-refresh?forum=sqlkjpowerpointforsharepoint
Furthermore, this issue is more related to PowerPivot for SharePoint. If you have any more questions about PowerPivot for SharePoint, I would sugget you open a new thread in the forum below for better support:
http://social.msdn.microsoft.com/Forums/en-US/home?forum=sqlkjpowerpointforsharepoint
Thanks for your understanding.
Regards,
Elvis Long
TechNet Community Support

Issue while creating Data Model in BI Publisher and logging into xmlpserver

Hi All,
We are facing an issue in OBIEE 11.1.1.5.
If we are logging with Non Admin Id (other than weblogic) and select New Data Model, a blank screen is coming. Where as, if we use Admin Id, we are getting screen as usual for creating data model. There were some blogs mentioning to change Priviledges for SOAP access, but that approach is also not working.
Further, we are also not able to open xmlpserver with Non Admin Id.
Any help or pointers would be great.
Regards,

how about pasting the content of your data template here, so that forum members can see what could be the problem.

Data Modeler : Modifying the Table Report layout

Hi ,
I'm using SQL Data Modeler (DM) 4.0 EA .
I used the File -> reports option to generate the reports on Table and in the report
1) I couldn't see the column data type ? (Refer below table ) , Is there any options to bring on the Data Type in the Report ?
No
Column Name
PK
FK
M
Data Type
DT
kind
Domain Name
Formula
(Default Value)
Security
Abbreviation
1
ID1
P
Y
(10)
LT
2
ID2
F
Y
(10)
LT
3
ID3
Y
(1)
LT
4
ID4
Y
(10)
LT
5
ID5
F
(20,4)
LT
2) In options to manage the Table report (Reports -> Manage). Currently I can only remove a heading (like Descriptions Notes ,columns,column comments.). Is there is any way to customize the report in such a way that I can remove some columns (mostly the empty ones) from the report and add the column comments along with the column table than a new column comments table.
Please let me know ,is there is an option to customize the report .
Note: I even tried generating the report using the search then report , but it doesn't give a complete report (i was only able to generate a report on column or table name or constraints , not all together.)
Thanks,
Srinivasan.K

Thanks for the immediate reply.
I checked on the DM again, the report comes good for the one which has the data type . But now all my data type changed to UNKNOWN and lokks like ,due to this my table report is coming without the "Data Type".
Can you please help me in fixing this unknown data type issue ?
Table report for the ones with proper Data type:
Columns
No
Column Name
PK
FK
M
Data Type
DT
kind
Domain Name
Formula
(Default Value)
Security
Abbreviation
1
ID1
Y
NUMERIC (10)
LT
2
SCRIPT
Y
VARCHAR (1024)
LT
3
UPGRADE_S
Y
VARCHAR (10)
LT
4
UPGRADE_D
Y
VARCHAR (250)
LT
5
UPGRADING_F
Y
VARCHAR (20)
LT
6
TIMESTAMP2
Y
Timestamp
LT

Can "trigger" management be addressed in the data modeler?

Please add an easier way to add/modify triggers.
I reverse-engineered my model into the data modeler and my triggers all migrated correctly to the model but, for the life of me, had no idea how to view, modify or create triggers. After extensive research, I found that they can be accessed in the left-hand Browser by drilling some 8 levels to view the triggers for each table - why? Why can't this functionality be added to properties context menu for the table. I'm not a big advocate for triggers but if I need to work on one, the current methodology is tedious at best.
Of course, if there's some other way to do this, please inform...
Accessing Triggers via the Browser
Design -> Relational Model -> APEX_DEMO -> Physical Model -> Oracle Database 11g -> Tables -> ACTIVITY_LOG -> Triggers

Thanks Joop and Phillip...
While I occasionally use SQL Developer, I currently use PL/SQL Developer (Allround Automations) as my development tool of choice and bringing a 3rd tool as SQL Developer into the mix, makes no sense to me.
I completely agree that managing a trigger via a development tool is much easier but one occasionally wants to quickly add a trigger either manually or via a template and this is not easy currently.
While functions, procedures, package, etc. are all important to a data model, the existence of most triggers are completely dependent on a table and are a critical component in any model that uses them. The ability to access and modify them easily in Data Modeler is important and shouldn't be an afterthought as is perceived here. If trigger access cannot be added to the Table Properties (as noted in the image below), at the very least, please provide a shortcut methodology to do so.

Not able to save a newly created Data Model in BI Publisher.

Hello everyone,
I was trying to create a new Report (my very first report) in BI Publisher. I created a new Data Model and a Data Set. But I am not able to save the Data Model and thus not able to proceed to the report. There's no error shown. Same happens with reports too.
Kindly provide me with a solution.
Regards
Ash
Edited by: 902739 on 28-Dec-2011 01:02

You should have a group called 'XMLP_ADMIN' in your repository and administrator or the user you are using should be part of that group. Look into paint.rpd for all these.

Table or view does not exist - Data Dictionary Import Wizard(Data Modeler)

Hi All,
In Data Modeler, Data Dictionary Import Wizard, I'm able to connect to database.But while going to the second stage (Select Schema/Database), I'm getting an error "ORA-00942: table or view does not exist".
I am able to select the table with select * from all_tables and I can open many tables as well.
Could anyone tell me, whether I'm missing any privilege, that causing this error.
Thanks in advance for you support.
Thanks.

Hi,
Thanks for your response, sorry for my late reply as I was away from my place.
Yes, it is showing "Connection established successfully".
log file as below-
2012-08-02 10:37:26,471 [main] INFO ApplicationView - Oracle SQL Developer Data Modeler 3.1.1.703
2012-08-02 10:39:42,889 [AWT-EventQueue-0] ERROR AbstractDBMExtractionWizardImpl - java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist
Pls see oracle version details-
Oracle Database 11g Enterprise Edition
11.1.0.6.0
64bit Production
Thanks again and waiting for reply.

Copy data models and reports from BW 3.1 to NW 2004s

Hi experts,
Our client has two BW servers: BW 3.1 and BI 7. BW 3.1 contains lots of data models and reports. And the BI 7 server is newly installed.
Now we want to copy these data models and reports from BW 3.1 to the new BI 7 server. Are there any solutions for this?
Thank you very much in advance.

Hi Frank,
Sounds like a cross version transport is needed.
This is a solution we have used to do what you want to do:-
Create and release a transport as per normal.
Copy and transport the files from the source system (BW 3.1) e.g /usr/sap/trans/data & /usr/sap/trans/cofiles to the same folders on the target system.
Basis help is needed here.
From here onwards using stms_import should help you in the normal manner.
Works a treat.
Have transported the following all correctly appearing as 3.x data models in NW2004s.
DSO objects.
Cubes
Transfer/Update rules
Reports.
Cheers,
Pom

Some observations on my first use of Data Modeler Beta

First of all, I can see this tool has a lot of promise.
I hope Oracle keeps at it, it could turn into a real winner if all the features I see being worked on mature.
Thanks!
Here are a few observations on things that I found non-obvious or tedious to do.
1. When designing an entity, I want to give it a name, a definition, attributes and keys. I want that process to be quick and require the minimum amount of mouse-clicking/navigation fiddling as possible. The current way of defining the attribute's datatype and size is painfully slow. I have to click to get a pop-up. Then I have to click to choose from a set of categories. Then I have to click on a dropdown list. If I try to use the down-arrow on the dropdown list, it works, but not if I go past the one I want. The up-arrow won't take me backwards in the list, so more clicking. It's just a nasty, slow interface to do a simple task that I have to do a thousand times in a data model. If I need to change the size of something, back I go thru the entire process all over again.
That makes it doubly slow to work in the most natural way, which is to list the attributes and the datatypes, then come back and refine the sizes once the model is maturing and relatively stable.
2. Adding an additional attribute requires a mouse click instead of a down-arrow. That means I have to take my hands off the keyboard to add a new attribute. Maybe there is some short-cut key that does that, but I have better things to do than memorize non-standard keyboard mappings. Make the down/up arrows works as they should.
3. Adding the comment that describes the attributes is not quite as slow, but still requires more keystrokes/mouse movements than it should. It's hard enough to get developers to document their attributes, don't discourage them.
4. I can't see the list of attributes, data types, sizes, key/mandatory settings, and the comment at one time while editing the entity. Makes it harder to grasp what all the attributes mean at a glance, which slows down the modeling and the comprehension of an existing model.
5. All the entities I created had primary keys with columns in them. But when I tried to have it build a physical model, it complained that some relationships had no columns in them. For the life of me, I couldn't figure out how to fix that. Never had that problem in any other case tool.
6. Getting it to generate DDL was awkward to find. Make it something obvious, like a button on the toolbar that says "Generate DDL".
7. Apostrophes in the Comments in RDBMS are not escaped, so the generated DDL won't run.
8. For the ease of use/speed of use testing on high-volume key tasks, make the developers do the task 1000 times in a row. Make them use long names that require typing, not table A with columns c1, c2 and c3. Long before they get to iteration 1000 they will have many ideas on how to make that task easier and faster to do.
9. Make developers use names of things that are the maximum length allowed. For example, for a table name in oracle, the max length of the name is 30 characters. The name of one testing table should be AMMMMMMMMMMMMMMMMMMMMMMMMMMMMZ. That's a capital A followed by 28 capital M's and a capital Z. For numbers, use the pattern 1555559. If the developers can't see the A and Z or 1 and 9 in the display area for the name in the default layout for the window, they did the display layout wrong. For places where the text can be really long, choose a "supported visible length" for that field and enter data in the pattern AMMMMMMMMMMMMMMMQMMMMMMMMZ, where Q is placed at the supported visible length. if the A and Q don't show, the layout is wrong.
10. SQL Developer has quite a few truly gooberish UI interaction designs and I can see some of that carrying over to the Data Modeler tool. I really recommend getting a windows UI expert to design the ui interface, not a java expert. I've seen a lot of very productive windows user interfaces and extremely few java interfaces suitable for high-speed data entry. Give the UI expert the authority to tell the java programmers "I don't want to hear about java coding internals - make the user interface perform this way." I think the technical limitations in java UIs are much less than the mindset limitations I've seen in all to many programmers. That, and making the developers use their code 1000 times in a row to perform key tasks will cause the UI to get streamlined considerably.
Thanks, and keep up the good work!

Dear David,
Again thank you for your valuable and highly appreciated feedback. Find included a more elaborated answer to your observations:
*1. When designing an entity, I want to give it a name, a definition, attributes and keys.*
In the new Early Adopter Release, a "SQL developer like" property window has been added for Entities and Tables. For each attribute/column you will have the ability to add name, datatype, Primary Key, Mandatory and comment from one and the same screen
*2. Adding an additional attribute requires a mouse click instead of a down-arrow.*
An enhancement request has been created
*3. Adding the comment that describes the attributes is not quite as slow, but still requires more keystrokes/mouse movements than it should.*
In the new Early Adopter Release, a "SQL developer like" property window has been added for Entities and Tables. For each attribute/column you will have the ability to add name, datatype, PK, M and comment from one and the same screen
*4. I can't see the list of attributes, data types, sizes, key/mandatory settings, and the comment at one time while editing the entity. Makes it harder to grasp what all the attributes mean at a glance, which slows down the modeling and the comprehension of an existing model.*
See former answers. For meaning of attributes you can also use the Glossary and Naming Standardization facilities: see Tools Option menu, Glossary and General Options for naming standards
*5. All the entities I created had primary keys with columns in them. But when I tried to have it build a physical model, it complained that some relationships had no columns in them. For the life of me, I couldn't figure out how to fix that. Never had that problem in any other case tool.*
A Bug report has been created. Issue will most probably be solved in the nexr Early Adopter release
*6. Getting it to generate DDL was awkward to find. Make it something obvious, like a button on the toolbar that says "Generate DDL".*
An enhancement request has been created.
*7. Apostrophes in the Comments in RDBMS are not escaped, so the generated DDL won't run.*
A bug report has been created
*8. For the ease of use/speed of use testing on high-volume key tasks, make the developers do the task 1000 times in a row. Make them use long names that require typing, not table A with columns c1, c2 and c3. Long before they get to iteration 1000 they will have many ideas on how to make that task easier and faster to do.*
I aplogize, but I don't understand clearly what you want to say with the use/speed of use here.
*9. Make developers use names of things that are the maximum length allowed.*
Our relational model is for use for not just Oracle, but also DB2, SQL Server and in the future maybe other database systems. Whicjh means that we can't taylor it to just one of these database systems. However you can set maxinum name lenghts by clicking right on the diagram and select Model Properties and here you can set naming Options. Here you can also use the Glossary and Naming Standardization facilities: see Tools Option menu, Glossary and General Options for naming standards
*10. SQL Developer has quite a few truly gooberish UI interaction designs and I can see some of that carrying over to the Data Modeler tool.*
Fully agree. As you will see in our next Early Adopter release we have started to use SQL Developer like UI objects.
Edited by: René De Vleeschauwer on 17-nov-2008 1:58

Can we use session variables in BI publisher's Data Model SQL Query?

Hi Experts,
We need to implement Data level security in BI Publisher 11g.
In OBIEE we do so by using session variables, so just wanted to ask if we can use the same session variables in BI Publisher as well
ie can we include the where clause in the Data Models SQL Query like
Where ORG_ID = @{biServer.variables['NQ_SESSION.INV_ORG']}
Let me know your views on this.
PS: We are implementing EBS r12 security in BI Publisher.
Thanks

Read this -> OBIEE 11g: Error: "[nQSError: 23006] The session variable, NQ_SESSION.LAN_INT, has no value definition." when Creating a SQL Query using the session variable NQ_SESSION.LAN_INT in BI Publisher [ID 1511676.1]
Follow the ER - BUG:13607750 - NEED TO BE ABLE TO SET A SESSION VARIABLE IN OBIEE AND USE IT IN BI PUBLISHER
HTH,
SVS

ORACLE reports Build 10g - Data Model - query - If statement in Alias ?

I have the following select statement. It has the alias Survivors, Deaths and "All
With the ORACLE reports Build 10g - Data Model - I have the following query statement. I require the alias to change. Can the following be done.
Cases". Is it posible to use :P_LANGUAGE variable to say that -- IF :P_LANGUAGE = FRENCH THEN alias are Survivants for survivors, Décès for Deaths, Tous_les_cas for All Cases. Please advise
SELECT ALL T_NTR_MULTIBAR.CAT, T_NTR_MULTIBAR.NUM_CASES_LEFTBAR AS Survivors,
T_NTR_MULTIBAR.NUM_CASES_MIDDLEBAR AS Deaths, T_NTR_MULTIBAR.NUM_CASES_RIGHTBAR AS "All Cases"
FROM T_NTR_MULTIBAR
WHERE INSTANCE_NUM = :P_INSTANCENUM
order by ORDERS

It is no problem, you can automatically change the complete query before the report is running, which delivers you different kind of values. But the alias names does not change in the group of the data-model, although two query are running with different alias names at different times. In the data model you see the alias names of the first implemented select statement, which are the column fields in the layout.

APEX application development with an existing data model

Dear all,
We - as a company - are trying to build an application in ApEx with an existing data model. The idea is that the data model that has all sorts of TAPIs and business rules defined is going to be re-used in an ApEx environment. I am actually wondering whether this is possible, wise, feasible. When I am building some simple pages on one specific table, which has approx. 35 fields, sometimes the triggers around that table fail. Before I am actually going to dive in to try and sort these problems I am wondering whether this use of a data model in an ApEx environment is wise.
I mean, when you build an ApEx application there are usually no triggers and TAPIs available. My logic is that the ApEx application can look after validation and stuff.
Does anybody experienced have anything smart and useful to say about this. Any feedback is appreciated.
Kind regards,
-victorbax
-leiderdorp, the netherlands

Hey vik,
At my company we rarely use the standard APEX wizards because of multi-linguility (on data level) and error management issues.
We always create an API in PL/SQL and call the procedures for APEX making APEX the 'view' layer in a kind of model-view-controller architecture.
The main thing to keep in mind is maintainability, if you're working with an existing datamodel with an API that works it's probably best to just created forms and reports through APEX and then calling the appropriate pl/sql (packaged) procedure manually. We believe that this kind of architecture has the downside of being a little more work initially but it's much easier to maintain large projects through a self written API and take care of issues like error handling, logging and multi-linguility through a self written API.
Kind Regards,
Geert Guldentops

CM14 BI Publisher - modifying an existing Data Model, the Graphic View in Query Builder does not display

I am trying to edit the default forms/reports that come with CM14, trying to edit the data model, data set, (to get to the old Infomaker style graphic view) , the Query model does not display (error the list of tables is too long..) Oracle tell me the limit is 60, there are not 60 tables referenced in any CM report.
Does this Query builder view work at all on any report?
(bigger question, we are moving from CM12, should we move to CM13 which works with infomaker?)
Thanks,
Paul L

Kurt, thanks for your replies.
A couple of notes/clarifications.
1. You are correct that BI works better in Firefox--I have observed issues with the BI display when using IE. I would recommend using Firefox too.
2. You are correct about the way to get to the Query Builder to see a graphical view of data tables. There are basically two issues with this that I mentioned, but will re-iterate:
a. If you have an EXISTING query in the data set, then click the "Query Builder" button, this will remove the existing query that's there, it will NOT display the existing query in the query builder. Query Builder works only to create a NEW query from scratch.
b. Query builder is limited to selecting 60 fields max in your query. If you are creating a large report with many tables, you may find that 60 fields is not enough. For that you will have to work in the SQL edit screen rather than using the query builder.
I would impress on anyone developing CM14 reports that they become familiar with the database schema and relationships to avoid problems when developing your BI reports. You should be able to find the tables and joins documentation in the knowledgebase.

Data model that takes part of data to DSO and part to cube

Hello experts,
I have a question about the data model I am currently working on. This model is about a reservation agency, where a customer contacts the agency through a sales representative and makes a reservation for a certain event. He later has the option of confirming or cancelling the reservation. We will be receiving data for future reservations every day, with the updated status of future and recently past reservations, sales representative in charge of the reservations, income that will be perceived from each reservation (if the reservation is confirmed) or that was perceived if the event already took place, and more.
I have found the need to use a DSO to update the reservation status of incoming reservations, as well as other fields. I am loading from a flat file with 20 fields, and the destination is a cube, after the data gets cleansed in the DSO, where there are 2 key fields (reservation code and reservation date). However, not all the remaining data from the flat file needs to get updated. Out of the other 18 fields, only around 9 may change on an update, while the others will never change (for example, the customer name, confirmation date and event name will not change, while the sales representative, reservation status and income perceived can change from one day to another).
I was designing a model in which the DSO contained all 18 non-key fields as data fields, so that everything got updated and passed to the cube, but then I thought that perhaps since many fields will not change, it would be better if the DSO only updated those fields that could actually change, while the other fields "jumped" directly to the cube. After the DSO updates the changing fields, the others will already be in the cube. This way, the DSO would receive and have to process less amount of data, making the DSO tables smaller and the process more efficient. But I cannot find a proper way to do this from a single data source, since the data has to pass from the data source to the DSO and then through a transformation from the DSO to the cube.
Is there a way to accomplish this, or should I just have all fields go through the DSO and from there to the cube?

Hi, thanks for the suggestion. The reservation code, as of right now, is not master data, and it is unique almost always, except for rare occurences where the same customer makes several reservations, each one for a different date (that is why for the DSO I am using as key fields both reservation date and reservation code). Because of that and the fact that there are lots of reservations made each day, we had defined that object without master data (since the master data table would be huge in a short amount of time). Perhaps I should change it to become master data? Or what should we do?

PowerPivot removed table replicated into the data model on refresh

Hey
I am facing the following problem which is absolutely persistent and annoying in nature. I am using a data model created with PowerPivot with connections to three different SQL servers and 25 tables. The bug is that every time I refresh my data, a table
that was initially added to the data model (and later removed) is replicated in equivalent number of tables that use this connection, which is currently around 12 tables, so I get 12 duplicates of the same unnecessary table on every refresh, named with the
name of the schema on the SQL server that is followed by a running number. Removing these from the data model on every refresh simply takes too much time on a daily basis. The additional undesired table which is created is what is defined in the SQL query
of the connection string of this connection.
I tried to solve this problem by zipping the Excel file and modifying this SQL statement present in the connection string in the connections.xml file in a way that it would not return anything, but this always leads into a corrupted workbook.
After encountering this I have managed to avoid this problem by making sure that the initial table I'm adding to the data model will remain in the model, but I really don't want to rebuild this current model. Is there any fix for this issue without
rebuilding the data model?
Thanks for all the help in advance!

I am using 64-bit Office 2013 with the recent SP1 upgrade and the included PowerPivot plug-in on a Windows 8.1 machine.
I always create the connection by using "From SQL server" then fill in the server and log in details and use a ready SQL statement that I have written by using SQL Server Management Studio to import the initial table. For all the preceding tables
using the same server and schema, I always select it from existing connections and just paste the SQL queries required for any additional tables to the "Write a query that will specify the data to import", rather than using the table import tool.
I am not sure if it could have any effect that I've been using the type connection "From SQL server" although the database is really running on Azure (there is a possibility to select From Other sources > Microsoft SQL Azure, but the functionality
seems the same).
I don't really understand what I should edit from the existing connections section. Just to clarify, apparently the Connection String parameters can be edited from PowerPivot, but not the Command Text which can be viewed from Excel Data > Connections
> Properties, but is shown in gray with a message "Some properties cannot be changed because this connection was modified using the PowerPivot add-in."
In the data model I am using two sets of identical tables, but connected to two different servers that are running a database 1:1 in structure. Initially the problem considered only the other of these, but I accidentally reproduced it by, again, editing
the SQL query in the table that was initially imported when that connection was created (PowerPivot > Design > Table Properties). Now when refreshing I get tables that are structured as in what the "Connection Text" part of the connection would
produce, which replicated for the equivalent amount of additional tables using the same connection, so now I'm getting 12 tables (the number of tables using the same connection) each named "*schemaname1* Query", "*schemaname1* Query2",
"*schemaname1* Query3" "*schemaname2* Query" and so on.
Personally I can definitely see a pattern here. If there isn't a table matching what has been specified in the "Command Text" that was described when the connection was created, then it for some reason runs this query anyway on every table that
is using the connection.

SSM Data Model

Similar Messages

Maybe you are looking for