Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
It's that middle role that will make or break you!
-
It's all in tables in DB ... the issue is: making sure you have all the the related data purged and not just the end result record.
-
You are using the pre-built model ... so you need to understand the pre-built model so you know why you aren't getting results when you expect them. You can write SQL and get data back - so that's all good ... now you need to study the joins and conditions in the physical and logical model for the pre-built. You need to…
-
An Admin needs to be able to see it all and do it all ... seems like you've got multiple people in Admin roles for which they really aren't admins. Who are your admins? Why? OOTB there is Admin, Author, Consumer ... 99% of the time I find myself on day one of security planning suggesting an in-between role below Admin and…
-
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=5boade8eq_121&_afrLoop=375000841751885#REF_TEXT
-
Have you run Run netstat -a -n from a command prompt to see what port the Service is actually listening on?
-
Configuration of the apps ELT (BIACM) versus the configuration of the display of data (BIPS) are two different things...
-
1415129 wrote:I am trying to find some way to optimize our biee model, like joins, indexs etc by checking the SQL execution plan.Alvin I get the feeling you are heading in a path that you will think of trying to force hint the use of indexes in the physical layer of the RPD or you have already done so ... this is NOT the…
-
To get the older versions raise an SR with Oracle
-
1 - You need a level-based measure for Revenue pinned at the Opportunity dimensional hierarchy level. 2 - You need a ranking measure so you can select the appropriate delta row Both of the above should be built in the RPD.
-
A quick google search shows multiple blogs and the links to documentation ...
-
Did you check Oracle support for a fix for this? or you could follow the documented approach to customization and add NODE~ to your integration id. Don't just make the change in the base code follow the documented customization paths.
-
You set the mappings with your finance/accounting department ... to start the conversation you can run the following against EBS: SELECT ST.ID_FLEX_STRUCTURE_CODE "Chart of Account Code" ,SG.ID_FLEX_NUM "Chart of Account Num" ,SG.SEGMENT_NAME "Segment Name" ,SG.APPLICATION_COLUMN_NAME "Column Name" ,SG.FLEX_VALUE_SET_ID…
-
You set the mappings with your finance/accounting department ... to start the conversation you can run the following against EBS: SELECT ST.ID_FLEX_STRUCTURE_CODE "Chart of Account Code" ,SG.ID_FLEX_NUM "Chart of Account Num" ,SG.SEGMENT_NAME "Segment Name" ,SG.APPLICATION_COLUMN_NAME "Column Name" ,SG.FLEX_VALUE_SET_ID…
-
each query has it's own connection ... just make sure in BIP admin you have configured both connections ... build both then add the join in the data model window on the columns you want ...
-
The key to understanding HOW to get the information you want is understanding the model. You need to know the functional intent of the model that supports the reports - as the model was built based on real business functional specifications (which have assumptions about the questions being answered). It may be that this…
-
Do you have an understanding of the logical and physical relationships in the data structures? If not, that's where to start. You need to study the logical and physical data models to understand why you are (or aren't) getting the behavior in question.
-
Setting up the agent with your own user credentials or another's?
-
Yes ... there are warehouse specific values that still apply when you only have a single source. Do the mappings first, then run the domain only load plan. Take a look at the internal (_G) tables to make sure what you put in BIACM found its way to the OBAW schema - then you can run a test full run (set your initial extract…
-
DW fundamentals ... Domain values are values sourced outside the warehouse so that integration can happen from various sources. Example: you might source financial transactions from both EBS and PSoft ... your warehouse domain values allow you to map the statuses from each system to a common warehouse value. a closed…