Adding Calculation Column in Physical layer

Hi All,
I have oppty fact table and product dimension table.
I have to create calculation columns
credit revenue = ( sum( opptyfact. Revenue where product. productgroup = “credit”))
Debit revenue = (sum( opptyfact. Revenue where product. productgroup = “debit”))
Brokarage Revenue = (sum( opptyfact. Revenue where product. productgroup = “Brokarage”))
How can create this calculation column in meta physical layer ( i don't want create in BMM due to some reasons) using fact and dimension table.
I am creating one phisical table and in Genaral tab i select Table Type as Select.
i am thinking to write Case statment but i could not gey any idea how can i implement.
could you please help me is it correct approch to write CASE statement ? is there any other way ?
Please help me
Thank you for your time

Hi user10441472,
You can use Madan's suggestion. Using it would imply that you change your physical table type to a SELECT. And the you need to emulate the code that he wrote. That is how you get logic implemented in your physical layer from the RPD side of things. Alternatively, you could create a database view to accomplish the business logic (case statements) and reference the view in the RPD physical layer instead of the source table.
That being said, I would highly recommend against that kind of thing. It makes for a bit more confusing RPD.
The natural place to put that is in the BMM layer. You mentioned you did not want to do that for several reasons. Could you list those reasons here?
Best regards,
-Joe

Similar Messages

OBIEE 10g Getting wrong results when adding calculated columns to a report

Hi,
I'm experiencing a possible misbehaviour with OBIEE 10g (10.1.3.4.1).
I have a simple report with a table. Columns are simply selected from dimensions and facts. In this case the generated query is:
WITH
SAWITH0 AS (select sum(T30604.TOTAL_TIME) as c1,
sum(T30604.MATERIALS_QTT_COST) as c2,
sum(T30604.AMNT) as c3,
sum(T30604.QNTY) as c4,
T30622.BRANCH_CODE as c5,
T25064.SRP1_CODE as c6,
T25064.SRP1_DESC as c7,
T25064.SRP2_CODE as c8
from
THK_BRANCHES T30622,
THK_ITEMS T25064,
THK_INVENTORY_TRANSACTIONS T30604
where ( T25064.ITEM_ID = T30604.ITEM_ID and T30604.BRANCH_ID = T30622.BRANCH_ID )
group by T25064.SRP1_CODE, T25064.SRP1_DESC, T25064.SRP2_CODE, T30622.BRANCH_CODE)
select distinct SAWITH0.c5 as c1,
SAWITH0.c6 as c2,
SAWITH0.c7 as c3,
SAWITH0.c8 as c4,
SAWITH0.c4 as c5,
SAWITH0.c3 as c6,
SAWITH0.c2 as c7,
SAWITH0.c1 as c8,
SAWITH0.c4 as c9,
SAWITH0.c3 as c10,
SAWITH0.c2 as c11,
SAWITH0.c1 as c12,
SAWITH0.c4 as c13,
SAWITH0.c3 as c14,
SAWITH0.c2 as c15,
SAWITH0.c1 as c16,
SAWITH0.c4 as c17,
SAWITH0.c3 as c18,
SAWITH0.c2 as c19,
SAWITH0.c1 as c20
from
SAWITH0
Results of this report / query are correct.
I then add a simple calculation (subtraction between two fields). The generated query is:
WITH
SAWITH0 AS (select sum(T30604.MATERIALS_QTT_COST) as c1,
sum(T30604.AMNT) as c2,
T30622.BRANCH_CODE as c3,
T25064.SRP1_CODE as c6,
T25064.SRP1_DESC as c7,
sum(T30604.TOTAL_TIME) as c8,
sum(T30604.QNTY) as c11,
T25064.SRP2_CODE as c12
from
THK_BRANCHES T30622,
THK_ITEMS T25064,
THK_INVENTORY_TRANSACTIONS T30604
where ( T25064.ITEM_ID = T30604.ITEM_ID and T30604.BRANCH_ID = T30622.BRANCH_ID )
group by T25064.SRP1_CODE, T25064.SRP1_DESC, T25064.SRP2_CODE, T30622.BRANCH_CODE),
SAWITH1 AS (select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
D1.c6 as c6,
D1.c7 as c7,
D1.c8 as c8,
D1.c9 as c9,
D1.c10 as c10,
D1.c11 as c11,
D1.c12 as c12
from
(select sum(SAWITH0.c1) over (partition by SAWITH0.c3) as c1,
sum(SAWITH0.c2) over (partition by SAWITH0.c3) as c2,
SAWITH0.c3 as c3,
sum(SAWITH0.c1) over (partition by SAWITH0.c6, SAWITH0.c3) as c4,
sum(SAWITH0.c2) over (partition by SAWITH0.c6, SAWITH0.c3) as c5,
SAWITH0.c6 as c6,
SAWITH0.c7 as c7,
sum(SAWITH0.c8) over (partition by SAWITH0.c6, SAWITH0.c12, SAWITH0.c3) as c8,
sum(SAWITH0.c1) over (partition by SAWITH0.c6, SAWITH0.c12, SAWITH0.c3) as c9,
sum(SAWITH0.c2) over (partition by SAWITH0.c6, SAWITH0.c12, SAWITH0.c3) as c10,
sum(SAWITH0.c11) over (partition by SAWITH0.c6, SAWITH0.c12, SAWITH0.c3) as c11,
SAWITH0.c12 as c12,
ROW_NUMBER() OVER (PARTITION BY SAWITH0.c3, SAWITH0.c12 ORDER BY SAWITH0.c3 ASC, SAWITH0.c12 ASC) as c13
from
SAWITH0
) D1
where ( D1.c13 = 1 ) ),
SAWITH2 AS (select sum(T30604.MATERIALS_QTT_COST) as c1,
sum(T30604.AMNT) as c2
from
THK_INVENTORY_TRANSACTIONS T30604)
select SAWITH1.c3 as c1,
SAWITH1.c6 as c2,
SAWITH1.c7 as c3,
SAWITH1.c12 as c4,
SAWITH1.c11 as c5,
SAWITH1.c10 as c6,
SAWITH1.c9 as c7,
SAWITH1.c8 as c8,
SAWITH1.c10 - SAWITH1.c9 as c9,
SAWITH1.c11 as c10,
SAWITH1.c10 as c11,
SAWITH1.c9 as c12,
SAWITH1.c8 as c13,
SAWITH1.c11 as c15,
SAWITH1.c10 as c16,
SAWITH1.c9 as c17,
SAWITH1.c8 as c18,
SAWITH1.c11 as c20,
SAWITH1.c10 as c21,
SAWITH1.c9 as c22,
SAWITH1.c8 as c23,
SAWITH1.c5 as c26,
SAWITH1.c4 as c27,
SAWITH1.c2 as c28,
SAWITH1.c1 as c29,
SAWITH2.c2 as c30,
SAWITH2.c1 as c31
from
SAWITH1,
SAWITH2
Results of this report / query are wrong: it seems as if some rows "disappear".
If I delete the filter in SAWITH1 query above ( D1.c13 = 1 ) results are correct.
Anyone experiencing the same problem? The strange thing is that I have a number of similar reports (on other subject areas) and everyting is working fine.
Please also note that I don't want to add this kind of calculated items in the RPD (they can be simple calculations that are made on-the-fly).
Any help would be greatly appreciated.
Thanks a lot and regards,
Cristina

I have the same issue, everything OBIEE server generate query using ROW_NUMBER() over () function, it will hardcode Dx.cx = 1, this will cause issue if you have rows of the same distinct value, thus causing missing rows and the final results will be wrong.
I have open a SR with Oracle Support since March 2011, but till today, they have not resolve the issue yet.
Hope they solve the issue soon.
Best Regards
KT

Trouble adding new Essbase dimension to physical layer

I'm using OBIEE 10.1.3.4.2 and have created a repository where I imported an Essbase cube. That's all been fine. I recently added another layer to one of the dimensions in my cube - had Division and Market and then added System below Market. I opened the Admin tool and added the new layer/column to the physical layer. Dragged the cube to the BM&M and then the Presentation layers. When I go into Answers and begin drilling down once I select a Market the System column says organization instead of displaying valid System names.
I also created a new repository and imported the cube and everything drills down just fine. I then compared both repositories and they look identical.
Does anyone have a better approach to updating the physical layer when working with Essbase? I really don't want to create the whole thing from scratch as I am also including other sources.
Thanks,
Brad

Follwoing links will be helpful for the same:-
http://hekatonkheires.blogspot.com/2009/10/obiee-101341-essbase-931-udml-for-cube.html
http://hekatonkheires.blogspot.com/2010/01/obiee-101341-essbase-931-udml-for-cube.html
If interested you also check this link for OBIEE 11g
http://www.rittmanmead.com/2011/06/incremental-essbase-metadata-imports-now-possible-with-obiee-11g/

Refreshing the Physical Layer ( New Columns)?

Hi,
I am new to OBIEE. (11.1.1.5)
I have a physical layer defined and now I have added some additional columns to these tables in the database.
Now, How to get these new columns reflected in the Physical layer.
I tried the Tools -> Utilities -> Update Physical Layer.
But it only checks for the data types of the existing columns already in the Physical layer.
Please help.
Edited by: 937825 on Jul 16, 2012 6:46 PM

Use File->Import Metadata option
The tables and column which are in RPD are grayed out and which are not available are in black.
Pls mark correct or helpful if helps

Problem when creating a calculated column "Item has already been added"

Hi,
I built an a set of lists and custom content types which are made available under http://moss/callcenter. When I want to create a new calculated column for one of my custom content types i get the following error
Item has already been added. Key in
dictionary: 'Strasse_Strasse' Key being added: 'Straße_Straße'
This is rather strange as I don't even get as far as creating that new column. The error occurs right when I select the type calculated column, even before I enter a name for the new column. How ever, when I want to create a calculated column in root site collection (http://moss/) this error does not occur and I can create the new column.
Any ideas anyone?
Thank you,
Christoph

hi,
you can try below thing
http://blogs.msdn.com/b/timquin/archive/2009/02/11/sharepoint-item-has-already-been-added-key-in-dictionary-484-key-being-added-484.aspx
Whenever you see a reply and if you think is helpful,Vote As Helpful! And whenever you see a reply being an answer to the question of the thread, click Mark As Answer

Sorry, something went wrong error when adding a calculated column

Hi I tried add a column via calculation, and it seems to not be correct because I keep getting a syntax error.. Can anyone tell me why or where I went wrong?
This is a dropdown box when a certain CIRCUIT TYPE is selected it would out put a calculation...
56, 56SW, 56FR are using the same calculation
DDS IDSL, ISDN TR, ISDN are using the same calculation
HDSL, HDSL2, HDSL4 are using the same calculation
Thank you... Here is the calculation below...
=IF([Circuit Type]="ISDN",(([F1 Makeup (26)]+[F1 bridge tap (26)]+[F2 Makeup (26)]+[F2 bridge tap (26)])*2.81)+(([F1 Makeup (24)]+[F1 bridge
tap (24)]+[F2 Makeup (24)]+[F2 bridge tap (24)])*2.03)+(([F1 Makeup (22)]+[F1 bridge tap (22)]+[F2 Makeup (22)]+[F2 bridge tap (22)])*1.42)+(([F1 Makeup (19)]+[F1 bridge tap (19)]+[F2 Makeup (19)]+[F2 bridge tap (19)])*0.84),
IF([Circuit Type]="DDS IDSL",(([F1 Makeup (26)]+[F1 bridge tap (26)]+[F2 Makeup (26)]+[F2 bridge tap (26)])*2.81)+(([F1 Makeup (24)]+[F1 bridge tap (24)]+[F2 Makeup (24)]+[F2 bridge tap (24)])*2.03)+(([F1 Makeup (22)]+[F1
bridge tap (22)]+[F2 Makeup (22)]+[F2 bridge tap (22)])*1.42)+(([F1 Makeup (19)]+[F1 bridge tap (19)]+[F2 Makeup (19)]+[F2 bridge tap (19)])*0.84), IF([Circuit Type]="ISDN T.R.",(([F1 Makeup (26)]+[F1 bridge tap (26)]+[F2
Makeup (26)]+[F2 bridge tap (26)])*2.81)+(([F1 Makeup (24)]+[F1 bridge tap (24)]+[F2 Makeup (24)]+[F2 bridge tap (24)])*2.03)+(([F1 Makeup (22)]+[F1 bridge tap (22)]+[F2 Makeup (22)]+[F2 bridge tap (22)])*1.42)+(([F1
Makeup (19)]+[F1 bridge tap (19)]+[F2 Makeup (19)]+[F2 bridge tap (19)])*0.84), IF([Circuit Type]="56",(([F1 Makeup (26)]+[F1 bridge tap (26)]+[F2 Makeup (26)]+[F2 bridge tap (26)])*2.45)+(([F1 Makeup (24)]+[F1 bridge
tap (24)]+[F2 Makeup (24)]+[F2 bridge tap (24)])*1.85)+(([F1 Makeup (22)]+[F1 bridge tap (22)]+[F2 Makeup (22)]+[F2 bridge tap (22)])*1.3)+(([F1 Makeup (19)]+[F1 bridge tap (19)]+[F2 Makeup (19)]+[F2 bridge tap (19)])*0.77),
IF([Circuit Type]="56SW",(([F1 Makeup (26)]+[F1 bridge tap (26)]+[F2 Makeup (26)]+[F2 bridge tap (26)])*2.45)+(([F1 Makeup (24)]+[F1 bridge tap (24)]+[F2 Makeup (24)]+[F2 bridge tap (24)])*1.85)+(([F1 Makeup (22)]+[F1
bridge tap (22)]+[F2 Makeup (22)]+[F2 bridge tap (22)])*1.3)+(([F1 Makeup (19)]+[F1 bridge tap (19)]+[F2 Makeup (19)]+[F2 bridge tap (19)])*0.77), IF([Circuit Type]="56FR",(([F1 Makeup (26)]+[F1 bridge tap (26)]+[F2
Makeup (26)]+[F2 bridge tap (26)])*2.45)+(([F1 Makeup (24)]+[F1 bridge tap (24)]+[F2 Makeup (24)]+[F2 bridge tap (24)])*1.85)+(([F1 Makeup (22)]+[F1 bridge tap (22)]+[F2 Makeup (22)]+[F2 bridge tap (22)])*1.3)+(([F1
Makeup (19)]+[F1 bridge tap (19)]+[F2 Makeup (19)]+[F2 bridge tap (19)])*0.77), IF([Circuit Type]="19.2",(([F1 Makeup (26)]+[F1 bridge tap (26)]+[F2 Makeup (26)]+[F2 bridge tap (26)])*1.73)+(([F1 Makeup (24)]+[F1 bridge
tap (24)]+[F2 Makeup (24)]+[F2 bridge tap (24)])*1.31)+(([F1 Makeup (22)]+[F1 bridge tap (22)]+[F2 Makeup (22)]+[F2 bridge tap (22)])*0.96)+(([F1 Makeup (19)]+[F1 bridge tap (19)]+[F2 Makeup (19)]+[F2 bridge tap (19)])*0.59),IF([Circuit
Type]="DDS T.R.",(([F1 Makeup (26)]+[F1 bridge tap (26)]+[F2 Makeup (26)]+[F2 bridge tap (26)])*1.91)+(([F1 Makeup (24)]+[F1 bridge tap (24)]+[F2 Makeup (24)]+[F2 bridge tap (24)])*1.46)+(([F1 Makeup (22)]+[F1
bridge tap (22)]+[F2 Makeup (22)]+[F2 bridge tap (22)])*1.08)+(([F1 Makeup (19)]+[F1 bridge tap (19)]+[F2 Makeup (19)]+[F2 bridge tap (19)])*0.64),IF([Circuit Type]="HDSL",(([F1 Makeup (26)]+[F2 Makeup (26)])*3.88+(([F1
Makeup (24)]+[F2 Makeup (24)])*2.84)+(([F1 Makeup (22)]+[F2 Makeup (22)])*2.18)+(([F1 Makeup (19)]+[F2 Makeup (19)])*1.5)+(([Num of F1 BTs]+[Num of F2 BTs])*3)+[Num of F1 Guage changes (HDSL)]+[Num of F2 Guage changes (HDSL)]),
IF([Circuit Type]="HDSL2",(([F1 Makeup (26)]+[F2 Makeup (26)])*3.88+(([F1 Makeup (24)]+[F2 Makeup (24)])*2.84)+(([F1 Makeup (22)]+[F2 Makeup (22)])*2.18)+(([F1 Makeup (19)]+[F2 Makeup (19)])*1.5)+(([Num of F1 BTs]+[Num
of F2 BTs])*3)+[Num of F1 Guage changes (HDSL)]+[Num of F2 Guage changes (HDSL)]), IF([Circuit Type]="HDSL4",(([F1 Makeup (26)]+[F2 Makeup (26)])*3.88+(([F1 Makeup (24)]+[F2 Makeup (24)])*2.84)+(([F1 Makeup (22)]+[F2 Makeup
(22)])*2.18)+(([F1 Makeup (19)]+[F2 Makeup (19)])*1.5)+(([Num of F1 BTs]+[Num of F2 BTs])*3)+[Num of F1 Guage changes (HDSL)]+[Num of F2 Guage changes (HDSL)]),0)))))))))))

Two possible issues:
Maximum formula length is 1024 characters, and you have nearly 4000.
Maximum nesting is 7 or 8 levels.
http://blog.pathtosharepoint.com/2010/04/12/maximum-number-of-if-statements-in-a-calculated-column/
Mike Smith TechTrainingNotes.blogspot.com
Books:
SharePoint 2007 2010 Customization for the Site Owner,
SharePoint 2010 Security for the Site Owner

How to improve slow PowerPivot performance when adding/modifying measures, calculated columns or Relationships?

I have been using PowerPivot for a couple of months now and whilst it is extremely quick when pulling in data to populate Pivot Tables, it is extremely slow to make the following kind of changes to the Data Model:
- Add a Measure / Calculated Field
- Add a Calculated Column
- Rename a Calculated Field
- Re-name a Calculated Column
- Modify a relationship
- Change a tables properties
- Update a table
In the status bar of excel I get a very quick 'calculating', then it spends a lot of time 'reading data',
then it 'finalises' after which nothing is in the status bar but it still takes approx. 45 seconds before the program becomes responsive again. This waiting time does not change depending on the action, it is the same if I rename a
column as it is if I add a new measure.
My question is what affects performance of these actions and how do I improve it?
To give you an idea of where my data comes from, I have:
- 7 tables that feed into the Data Model directly from within the workbook which contains the data model itself. These are a combination of static tables and tables that connect to a MySQL database.
- 6 separate workbooks which contain static data that is updated manually periodically (copied and pasted from another source)
- 5 separate workbooks which contain dynamic tables that are linked to our MySQL database and update when opened.
Now I realise that this is probably where my issue is, however I have no idea how to fix it. You do not seem to be able to connect to a MySQL database directly within the PowerPivot window itself so there is no way to generate and update tables without
first creating them either in a worksheet or separate workbook (as far as I know). If I try to create all of the tables directly within the single workbook containing the Data Model I get performance and crashing issues hence why I separate tables into
individual workbooks.
Any advice on how to improve performance would be tremendously appreciated. I'm new and keen to learn, I'm aware this set-up is far from best practice.
Hardware wise I am using:
- Windows 8 64-bit
- Excel 2013 64-bit
- Intel Core i7 processor
- 6 GB Ram
Thanks,
James

Darren,
I think the point I was making is its in memory, geez... BTW what do all applications do when they run out of paged memory, if PowerPivot is using all available memory then wouldn't this force the other applications to use Virtual or essentially write
back and forth to the disks? I think Virtual memory white to disk ??, lol Also, there are parts if the architecture of Excel 2013 that when importing data into PowerPivot require memory and when working in SharePoint the PowerPivot data is cached to disk
unless recently refreshed... But this conversation isn't help the James who asked the question and as much as I would love to continue its become a little boring..
Hi James,
If you download one the ODBC MySQL Connectors
http://dev.mysql.com/downloads/connector/odbc/ and I believe yours is the first one for x64 systems and connect directly to the data you should be able to reduce the number of workbooks your opening and if you notice in the following graphic these
connection are automatically refreshed by default, the parts in red are the differences between PowerPivot 2010 and 2013
You should notice a lot of improvement especially when refreshing data please let us know how it goes...
After registering the ODBC Driver
Click Add. on the User-DSN sheet, choose the “MySQL ODBC 5.x driver”, fill in the credentials, choose a database (from the select menu) and a data source name and you’re done.
Back in Excel you go on the PowerPivot section of the ribbon and open the PowerPivot window (the green icon on the left side). In the ‘Home’ section of that window you will see a small gray cylindrical symbol (the international
symbol for “database”) which will suggest to you different data sources to choose from. Take the one where it says “ODBC”.
In the next dialog you click on create, choose the adapter, and then Ok. Back in the assistant you can check the connection and proceed.
Now you have the choice between importing the data from tables using the import assistant or Query depends on your skillset..
Cheers,
Ivan
Ivan Sanders <a href="http://www.linkedin.com/in/iasanders">My LinkedIn </a> , <a href="http://msmvps.com/blogs/ivansanders">My Blog</a>, <a href="http://twitter.com/iasanders"> @iasanders</a>,
<a href="http://shop.oreilly.com/product/0790145372703.do">BI in SP2013</a>, <a href="http://sharepointdemobuilds.codeplex.com">SP2013 Content Packs</a>.

How to add a stand alone table from Physical layer to Business Model

Hi,
I have tables from 2 different database sources in my Physical Layer.
My Business model currently uses only tables from one database. from my second database in teh physical layer I need only one table and that will be a stand alone table, to my Presentation layer.
1. Does it have to go through my Business layer or can it be directly added to the Presentation layer. What are the steps?
2. Can I restrict the permissions on that stand alone table only to the administrator?
Thank you.

1)create a view with single column using the sql (select 1 from dual) in physical layer and join it with the table using complex join in physical layer (1=1).
Move that to BMM, set the column as key in both physical and bmm layer.
2) You can restrict the access for the table presentation layer
Double click the presentation layer table -> Permission -> there you can restrict the access by user or group
Thanks,
Vino

Physical layer tables

I have a question on the physical layer. When we import the tables to the physical layer and after that there are few changes to the tables like adding or deleting columns. Do those changes reflect in the physical layer tables as well or do we have to import the modified table again to the physical layer and delete the previous table?

Hi,
After importing tables in physcial layer if you modify those tables in database those changes will not be reflected in physical layer.You dont have to import tables again if you add only one or more columns.You can simply create physical column in rpd with the same name and datatype as of database.In the same way if you delete any column in databse table then you can delete that column from RPD.
Thanks
Sandeep

How do I update Physical Layer

How to I update the table in the physical layer in the OBI admin tool when:
1. the data in the underlying database table changes (meaning the records/rows are added or deleted in the database)
2. the fields in the underlying database table change (meaning columns are added or deleted)
3. the size of the field changes (meaning the type or length of the columns change)
4. only the table names/column names in the underlying database change.
In which of the above cases do I have to import again through the connection pool. If I have to import again do I have to create physical joins in the physical layer and complex joins in the BMM layer and mapping to the new table as LTS and any expressions in the column mappings again?
Thanks for your input.

How to I update the table in the physical layer in
the OBI admin tool when:1. the data in the underlying database table changes
(meaning the records/rows are added or deleted in the
database):
You don't need to take any action here unless you are concerned with query caching. In that case use 'event polling table'. Lookup documentation for event polling table.
2. the fields in the underlying database table change
(meaning columns are added or deleted)
You will need to manually add those in physical layer and propogate to business and presentation layer.
3. the size of the field changes (meaning the type or
length of the columns change)
Go to utilities - update physical layer and select the affected presentation layer.
4. only the table names/column names in the
underlying database change.
You will need to manually change those in physical layer. No need to and propogate to business and presentation layer ans its is automatically taken care of.
In which of the above cases do I have to import again
through the connection pool. If I have to import
again do I have to create physical joins in the
physical layer and complex joins in the BMM layer and
mapping to the new table as LTS and any expressions
in the column mappings again?
No need in any case to import manually.
Thanks for your input.

Do we need to give new joins in physical layer

hi all,
due to some back ground problem ,we have deleted the existing table in back end and again we have created the table having different columns names with same table name
let say ,i have deleted table A and it is having columns (no int ,name varchar,...) in the back end... again i have created table A and different columns name(sno number,sname varchar)...
like this i have created .. and whatever the content is there in old table same data i copied in to new table.
so... here my question is do we need to again import that table into physical layer and again we need to give joins... or can we make use of existing table ....???
now i am running the reports with old table .. reports are not coming up... its giving an error....
is it mandatory to import the table again .. and again i have to do all joins..
i did few calculations using that dimension ...... so... any other alternative solution for this ... instead of doing joins.. ..
i have changed the column names in back end... that's it
here can we make use of catalog manager to change the column name in the reporting side....after changing the columns name in physical layer..
i don't knw the process of catalog manager.... please can any one send me the link to change the column names in the reporting side .....using catalog manager
Thanks

Hi,
If you have deleted table in database and you have created a new table with same columns and same structure then you should not face any problem. OBIEE will still have that table intact in physical layer.In your case since you have changed the names of columns in database it is creating problems for you because OBIEE query will use names mentioned in physical layer and those columns are no more in database. SO to resolve the issue go to physical layer and change the names of the columns .That should solve the problem.
Regards,
Sandeep

How to reimport relational table objects into RPD physical layer...

I am new to OBIEE. I am not sure how to reimport relational database tables into physical layer whenever the base database table structure changes.
How do I configure the ODBC or OCI 10G/11G connections on my computer so I can reimport objects into RPD on remote server.
I would appreciate it if you can give step by step instructions
Thanks in advance.

Hello -
You can re-import a table to the Physical Layer the exact same way that you would import the table for the first time:
1) Click File > Import > From Database...
2) Select your data source connections
3) Choose your table you wish to reimport
The system will warn you that you will overwrite the existing table and may lose information. The information you would lose is any discrepencies in the physical layer that are no longer existing in the actual database table. However, logical columns will NOT be overwritten.
Alternately, if it is a minor change to the table (say a column name change, or one additional column added), you can also manually add the column
1) Right Click on the already imported table in the presentation layer and select New Object > Physical Column...
2) Name the column and provide the proper data type
The column now exists in the physical layer and will be properly associated with the new column in the database, assuming the same column name was attributed. You WILL have to drag this new column forward to the logical layer and presentation layer, as this will not be automatically done.
I hope this answers your question. If you found this helpful, please assign points!
Regards,
Jason

Update physical layer - new database schema

Can the physical layer be updated with new database schema? (Has a new table column) If so, how?
userQHN

Hi,
If you import table which has changes you will get it ,if there is any new columns added.
Regards,
Somu

Problem with binding value on the UI from a calculated column in the view

I have calculated field "Readiness" in my db view, which gets calculated based on other columns in the same table. I have added new column to my EO using "Add from table" option and added the same column from to VO using "Add from EO" option. In my application, I will update a particular date field in the UI and this calculated column "Readiness" in the db will be set to yes or no and this logic is working fine, both date date field and calculated field are in same view object. I have added a attribute binding to this "Readiness" column in my view page. The problem is the calculated column value does not reflect the new value in the db, it shows the old value. I have tried different refresh option for the iterator and ppr option for the field binding. Even after reloading the page, the value shown on the UI page is different from the value in db, other bindings on the UI page works fine, not sure any special settings are required for the Calculated columns. any ideas are appreciated.
Thanks for your help,
Surya

I tried to add soms debugging statements in the EO and getters method, the calcaulated column is not picking the value in db view. I'm not any special iterator/field settings are required at BC level. I'm a newbie, any help is appreciated.
Thanks,
Surya

How to define join in physical layer between cube and relational table

Hi
I have a aggregated data in essbase cube. I want to supplement the information in the cube with data from relational source.
I read article http://community.altiusconsulting.com/blogs/altiustechblog/archive/2008/10/24/are-essbase-and-oracle-bi-enterprise-edition-obiee-a-match-made-in-heaven.aspx which describes how to do it.
From this article I gather that I have to define a complex join between the cube imported from essbase to my relational table in physical layer.
But when I use Join Manager I am only able to define jooin between tables from relation source but not with the imported cube.
In My case I am trying to join risk dimension in the cube based on risk_type_code (Gen3 member) with risk_type_code in relation table dt_risk_type.
How can I create this join?
Regards
Dhwaj

Hi
This has worked the BI server has joined the member from the oracle database to cube. So Now for risk type id defined in the cube I can view the risk type code and risk type name from the relational db.
But now if I want to find aggregated risk amount against a risk type id it brings back nothing. If I remove the join in the logical model then I get correct values. Is there a way by which I can combine phsical cube with relational model and still get the aggregated values in the cube?
I have changed the column risk amount to be sum in place of aggr_external both in logical and phsical model.
Regards,
Dhwaj

Adding Calculation Column in Physical layer

Similar Messages

Maybe you are looking for