EPMA 11.1.2.1 : A non-desired dimension is created in Planning with EPMA

When a new Hyperion Planning application is deployed with EPMA 11.1.2.1, a 'Cut-off' dimension is created in the newly deployed applications.
'Cut-Off' was a local dimension for an application deployed from EPMA. But we do not know how this dimension is deployed in all new applications even without adding it to the library of the application. ' Cut 'Off' has been removed and the application where it was also presented. But in the EPMA tables, there's elements of the old application where 'Cut'Off' was present.
How to solve this problem?
How to remove problems in EPMA? Thank you for your help.
Cyril

its not.Here is the support matrix:
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&cad=rja&uact=8&ved=0CB4QFjAA&url=http%3A%2F%2Fwww.oracle…
For 2012 its 11.1.2.4
Cheers..!!
Rahul S.

Similar Messages

  • OBIEE 11g 11.1.1.7 NON Confirmed dimensions and facts

    Hi All,
    In OBIEE 10g if we had non-conformed dimensions we used to work with by defining logical level of the conformed dimensions to grand total and confirmed dimensions to detail in the LTS of the fact table
    and also set metrics to grand total level.
    But in OBIEE 11g doing same is throwing error
    [nQSError: 14025] No fact table exists at the requested level of detail
    How do we achieve this?
    Regards,
    deep

    You need to create a complex join with non conformed dimension and the fact with 1=1 and set the logical level of the measure to total for a non conformed dimension.
    You can refer: https://s3.amazonaws.com/rmc_docs/biforum2011/Mcquigg_Metadata.pdf

  • Filter and non-conforming dimensions

    I have a model design which includes three fact tables with non-conforming dimensions. This causes BI to create multiple queries for a report and finally bring the results together using a full outer join at the end. When I attempt to filter on a field from one of the non-conforming dimensions, that filter is not applied at the full outer join step but during an earlier step related to the chosen filter field. This results in more data returning then desired. I need to move the filter to the full outer join step. Here are two sub-optimal methods that I have found to work around the issue.
    1. Build the logical query in answers. Then, wrap that query with an outer query and apply the filter to the outer query.
    2. Build a minus query in answers that removes the records you don't want to see.
    I have seen this issue discussed in other threads, but I haven't found a good solution. Does anyone have any recommendations?
    Thank you,
    Edited by: user10715047 on May 21, 2010 7:13 AM
    Here is a decent description of the problem
    http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3297052
    and this is a better solution than the two I stated above. However, even this solution is not going to be very intuitive for the users
    http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3298529

    i know this is a bit old thread but thought it might be helpful to someone who came across the same issue...
    when using Degener@teDimen$ion ( this is !nner joned to FACT tables in BMM) and if any of the dimensions {other than theDegener@teDimen$ion (Let us say Dim X) } have an ()uter join to any of the fact tables, and you were doing your analysis using Degener@teDimen$ion,  Dim X, Measure value you will face the following issues.
    when filtering the analysis on the ()uter join dimension ( Dim X), the IN filter will not work. Reason is that the filter is getting applied to both the Dimension and FACT tables and the values that exist in Dimension Dim X but not in FACT table wont show up.
         The above issue can be fixed by changing the join between the fact and Degener@teDimen$ion from inner to outer.
              Please mark if you found this helpful.

  • Content Tab: None of the fact tables are compatible with the query request

    Hi All,
    **One thing I am not clear yet of all my years with OBIEE is working with the content tab in BMM.**
    I have made a rpd the joins in physical layer as shown below:
    https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056545119428530
    And the BMM layer as:
    https://picasaweb.google.com/114804305606242416264/OBIEEError#5663056519553812930
    Error I am getting when i run a request from the 3 columns from the selected 3 tables is:
    Dim - Comment Code Details
    Fact - Complaint
    Dim - Service Details
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14020] None of the fact tables are compatible with the query request Sr Num:[DAggr(Fact - Complaint.Sr Num by [ Dim - Service Details.Sr Cat Type Cd, Dim - Comment Code Details.Cmtcode name] )]. (HY000).
    I get no error for consistency.. I read everywhere and I know i need to set the appropriate aggregation levels in the various dims and facts LTS properties to help OBIEE understanding our model, but how to do that.. how do i decide... how should I approach, what should be the aggregation level, what details.
    When i click More button i see different options: Copy, Copy From, Get Levels, Check Level, what do these mean.
    Aggregation Content, group by - Logical Level or Column which one should i choose and how should I decide.
    Can anyone explain the Content Tab in details and from scratch with some example and why we get these errors.... I know many people who are well versed with many other things related to RPD but this. A little efforts of explaining from you guys will really be appreciated.
    Thanks in advance,
    Dev

    Hi Deepak,
    Option 1:
    My tables in physical layer are joined as below:
    D1--> F1 <--D2--> F2 <--D3
    Same way i model it in BMM
    D1--> F1 <-- D2--> F2 <--D3
    Here D1 is non Conformed Dimension for F2 and D3 is non Conformed dim for F1. Later create Dimensional hierarchies, I tried setting up the content levels
    I go Sources>content tab of Fact F1 I set
    Dimensions----------- Logical level
    D1---------------------- D1 Detail
    D2---------------------- D2 Detail
    D3---------------------- D3 Total
    then, I go Sources>content tab of Fact F2 I set
    Dimensions----------- Logical level
    D1---------------------- D1 Total
    D2---------------------- D2 Detail
    D3---------------------- D3 Detail
    Then, I also go in all the dimensions and set their content levels to Details, but it still gives me errors not sure where I am going wrong in setting the content levels.
    I need to know whether the way I have modeled it in BMM is right,
    Option 2:
    I can combine the two facts in a single Logical Fact or the above design should also work.
    (F1&F2)<--D1, D2 , D3 joined separately using complex logical joins.
    what will be the content tab details?
    Thanks,
    Dev

  • Essbase answers - None of the fact tables are compatible with the query request "member"

    Hi,
    I have modelled an Essbase database into the repository.
    If I pull the measure, period and year dimension in and filter on the year (member) and display the year (member) along with the period (alias) and measure it errors with =>
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request Fiscal Year.Fiscal Year Code. (HY000)
    However, all other things being equal if I change the year displayed to the alias then it works.
    Anyone tell me why??
    Is there a limitation that Essbase brings through that you cannot view what you filter on?
    thanks,
    Robert.

    Hi
    i have done the content level setting in each of the table, D1,F1 and F2(LTS), now i am getting the following error..
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Gl Sets Of Books) does not contain mapping for [Code Combinations.Code Combinations.Affiliate, GL Balances.GL Balances.Currency Code, GL Balances.GL Balances.PTD_Balance, Gl Sets Of Books.Gl Sets Of Books .SoB Name]. (HY000)
    Gl Balances : D1
    Code Commbination: F1
    Gl Sets Of Books : F2
    I have checked the joins in physical and BMM layer..all are fine..

  • OBIEE 11g: Non conformed dimension filter

    Hi,
    I have two fact tables and some confromed and non conformed dimensions between the fact tabels.
    The hiearchies being built and proper levels were set for the fact tables. The measures of the fact were set to the total level of the non confromed dimension tables.
    The fact also hold some non aggregated columns (baseline columns), all the base line columns where moved to a logical dim table.
    The report involves both the fact tables, conformed and non conformed dimension columns.
    When we built the report with all these columns the report is showing fine. But when we add the filter with the non conformed dimension the report is throwing some error.
    Error Details
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14023] None of the fact sources for D01 Date.Date are compatible with the detail filter [D05 Non Confrm Dimension.Code = 'AFS']. (HY000)
    The above functionality was working fine with OBIEE 10g and have implemented it many times before.
    There is one patch available for this issue but it is available only for windows 32 bit enironment.
    Patch details
    Patch 14210864: OBIEE 11G: CONFORMING DIMENSION SETTINGS FROM 10G NOT WORKING IN 11G
    Can anyone give some suggestion or workaround? I can't do any change in Datamodel.
    Thanks,
    Vino

    Hi Vinod,
    In OBIEE 10g, we are running into similar error when we add filter from non conformed dimensions in a report, so can you please share patch download details like where to download or if we have to raise a SR for the Patch 14210864.
    Thanks in Advance!!

  • Obiee 11g non-conforming dimensions and nQSError 14025

    Does anyone know how to configure the 11g repository for non-conforming dimensions? This worked fine in 10g. I have upgraded the repository to 11g and it doesn't work anymore. I am receiving the error [nQSError: 14025] No fact table exists at the requested level of detail. I have tried building a simple test subject area and testing different configurations, but I have not had any success.
    Edited by: user10715047 on Jan 27, 2011 12:33 PM

    Ah, I love answering my own questions. :/
    The only way I could make this work was a follows...
    1. Make sure you have a level-based dimension for each of your logical table dimensions (both conforming and non-conforming).
    2. For the fact table measures, set the levels as you did in 10g with the non-conforming dimensions at the Grand Total logical level for each measure.
    3. For the fact table LTSs, set the logical level in the Content tab to the dimension's lowest level for each conforming dimension (leave the non-conforming dimensions level blank).
    Unfortunately, the query generated in 11g will add an additional sub-query to the mix even though it doesn't appear to have any benefit. Therefore in 10g, if you have two logical fact tables with non-conforming dimensions, three sub-queries were required to create the result set. Two queries for the facts and their related dimensions and a final full outer join to stitch the results together. In 11g, you have one query without the measures, two queries with the measures, and the final outer join.
    I am talking to Oracle support about this issue, but I haven't made much progress yet. I asked development to confirm my repository design and they say it checks out. They indicated that the additional query is a design change/enhancement. I am not getting a warm and fuzzy on this one. I'll post back if I make any progress.
    Oh, did I mention that this change has broken queries where I attempt to combine fields from two non-conforming dimensions?!? This worked fine in 10g.

  • Non-conforming dimension filters

    Hi,
    Here how my join looks
    FACT1>>product(dim)<< FACT2>>ledger(dim)>>RPT(dim)
    Here RPT(dim) is non conforming dimension for FACT1 and product(dim) is common for both FACT1 and FACT2
    I have set content level(LTS) only for conformed dim.( to detail)
    When i drag fact1 and RPT(dim) ,my result is fine
    but when i drag only FACT1 and use (USING filter) of RPT(dim) columns
    i get error No fact table exists at the requested level of detail: [,,,,,,,,,,,,,,,,,,,,].
    FYI: Re: obiee 11g non-conforming dimension filters
    can i know how to set content level for nON conformed dim? will tht solve problem
    Regards
    Sabeer
    Edited by: 944346 on Sep 20, 2012 12:54 AM
    Edited by: 944346 on Sep 20, 2012 12:55 AM
    Edited by: 944346 on Sep 20, 2012 12:56 AM

    I resolved this issue a while ago, but I hadn't posted back the results. Here is what happened...
    I talked to Oracle support about my design and issues. They created a patch for me that would re-enable the 10g functionality so that my model/queries would work again. From their perspective, 10g's non-conforming code design was flawed and 11g was fixed to correct the flaw. This flaw was what allowed my model and queries to work in 10g.
    NOTE: I have not tested the patch (bug# 11850704)
    The only way to get things working on 11g without the patch is to find a common fact that all dimensions can join. After some consideration and testing, I decided that it would be possible to join all the dimensions to one fact with some backend design changes. I could have proceeded with the patch, but I doubt that the 10g functionality will be maintained in the coming releases. Therefore, I would only be delaying the inevitable redesign.
    I have to admit that the final results have been positive and I have eliminated many of the 10g issues that I had with the design.

  • Multiple facts with shared/non shared dimensions

    Hello All,
    I have a scenario where we are using multiple facts in OBIEE. Fact1(Inventory Onhand) is joined to all shared dimensions, and Fact2( Forecasting Values) is joined to few shared dimesnions so the joins are like:
    Fact1 with Dim1, Dim2, Dim3, Dim4, Dim5, Dim6..
    Fact2 with Dim1,Dim3, Dim5
    I have given the physical joins in the physical layer, later in the logical layer I pulled the fact2 in to to the fact1(multiple LTS) and then set the aggregattion levels for the non conformed dimensions. This was working fine for me but the customer was not happy with this. He doesnt want to have different levels of data in to a single fact.
    What are the allternate possible solutions to implement this in the busines layer?
    Any ideas/inputs are highly appreciated.
    - Abhi

    Hi,
    I have done the same as explained above. But here the issue is we are getting duplicate data.
    For Ex: if i have one common dimmension attribute and two non confirmed dimension attributes with a measure. For non confirmed dimension have different value and for all these values the common dimension attribute is same. Then the common attribute will repeat for all non confirmed dimensions.so, here automatically the Corresponding measures also repeating.
    Common Attr non-Confirm Attr1 non-Cnfirm Attr2 measure
    123 abc xyz 1000
    123 bac yzx 1000
    123 pqr mno 1000
    If you observe the above exapmple the confirm dime attr is same for both non confirm dime attrs, so the measure values also repeating here. If i see the data base i have measure data only for ABC record. For Remaining two records it is 0, but here the value 1000 is showing for remaining two records as well.
    Please let me know if any one face this issue earlier.
    Regards,
    Aari

  • Multiple facts with non-conforming dimensions

    Hi, I have a question re: using multiple facts in a report, where one of the facts has a non-conforming dimension.
    I have two metrics: "PAYROLL" and "UNRECONCILED DIFFS". The payroll metric is at the employee level, but the "UNRECONCILED DIFFS" is not. Here's what I've done so far:
    1. Set up a single logical fact table in the business layer
    2. Created 2 LTSs. One has "employee" level, one has "all employees" (i.e. the grand total level)
    3. Created metrics for PAYROLL and UNRECONCILED DIFFS, each pointed to the proper LTS
    4. Set the "employee" hierarchy level for "UNRECONCILED DIFFS" to the "all employees" level
    This is working...kind of. If I have three employees with a payroll amount of $1000, and there is a $500 unreconciled diff, the report shows up like:
    Employee Payroll UnrecDiff
    Emp1 $1000 $500
    Emp2 $1000 $500
    Emp3 $1000 $500
    Total          $3000    $500
    Here's what I'm wondering...instead of having the unreconciled difference repeated for each employee...is there any way it can just be $0 or (even better) NULL, but then still show up as $500 in the total line?
    Thanks!
    Scott

    Hi
    The problem you describe is similar to mine (I wrote several threads ago).
    That is, if there is a non-conformed dimension in a report then the column from the fact table which is not connected with those non-conformed dimensions containes zeros or blanks.
    Was this problem solved? I didn't quite catch one of previuos messages... If you can please repeat it more detailed.
    What I tried to do is to set Total level in the Content tab (LTS properties). In this example - I could set Total level to JOBS in the plan type dimension. But it didn't help.
    So if you know what to do then please describe it here...

  • Error: None of the fact tables are compatible with the query request

    Hi experts,
    I have one confirm dimension D1 and other two fact table F1 and F2 (F1 and F2 are connected to D1)
    when i create a report from D1 and F1 the report is running fine. But pull the column from F2 also in this report i am getting the following error
    None of the fact tables are compatible with the query request Code Combinations
    please suggest on the same.
    Regards,
    S

    Hi
    i have done the content level setting in each of the table, D1,F1 and F2(LTS), now i am getting the following error..
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Gl Sets Of Books) does not contain mapping for [Code Combinations.Code Combinations.Affiliate, GL Balances.GL Balances.Currency Code, GL Balances.GL Balances.PTD_Balance, Gl Sets Of Books.Gl Sets Of Books .SoB Name]. (HY000)
    Gl Balances : D1
    Code Commbination: F1
    Gl Sets Of Books : F2
    I have checked the joins in physical and BMM layer..all are fine..

  • "None of the fact tables are compatible with the query request " error

    I've got a situation where I have two facts(Fact_1, Fact_2) and three dimensions(dim_1,dim_2,dim_3) in 1 subject area. I've got dimension hierarchies setup for all the dimension tables.
    Dim_1 is one to many to Fact_1
    Dim_2 is one to many to Fact_2
    Dim_3 is one to many to both Fact_1 and Fact_2
    I've set up the content levels for the LTS for the Facts so that they are the lowest grain for dimensions they join to and the grand total grain for dimensions they do not join to.
    My rpd is consistent. When I run a report using an attribute from Dim_3 and Dim_1 or Dim_3 and Dim_2, the report comes back fine.
    But if I try to run a report using all three Dim tables, I get an error and the message "None of the fact tables are compatible with the query request ".
    First of all, is it possible to make a report using all three dimensions?
    Second, what's the best way to trouble shoot this error? Why are none of the fact tables compatible? I thought as long as the aggregation levels were set to grand total for non-shared dimensions, Answers would be able to create the report properly.
    Any advise would be greatly appreciated.
    Thanks!
    -Joe

    OBIEE is looking for a fact that can link ALL the dimensions together. This is also known as the implicit fact ... you don't have a fact that can relate all the dimensions - you have 2 facts that together they can. Perhaps you need to great a single logical fact that has both LTS for your physical facts and try it that way.
    Then you'd have Dim1, Dim 2, Dim3 all being able to join to Fact1 (which is made of physical facts 1 & 2).

  • I had a "pdf export" plan and upgraded it to "pdf pack" plan and it was charged the full price of the new plan in my credit card. How to get the refund of the non used part of the old plan?

    I had a "pdf export" plan and upgraded it to "pdf pack" plan and it was charged the full price of the new plan in my credit card. How to get the refund of the non used part of the old plan?

    Hi edilsoncf,
    I've seen your question on several forums, and responded there. Did you get your subscription sorted out?
    See: How do I get a refund if I have multiple Acrobat service subscriptions?
    Best,
    Sara

  • Non-conformed dimension [nQSError: 14020]

    Hi,
    I have linked two cubes in a report, which have some conformed and some non-conformed dimensions. I have set the LTS of the non-conformed dimensions to the total level.
    This creates a warning in Administrator when doing the Global Consistency check:
    *[39054] Fact table "ORACLE_BUSINESS_INTELLIGENCE_1"."CubeXXX" is not joined to logical dimension table "ORACLE_BUSINESS_INTELLIGENCE_1"."DIM_XXX". This will cause problems when extracting project(s).*
    What does 'extracting projects' mean here ???
    And when I run a report on the two fact tables I get an error in the logs
    *...converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request*
    Am I missing something or is this related to the rumor that non-conformed dimensions are broken in 11.1.1.3 ?
    Regards,
    Knut

    Below is some useful and related information from oracle about OBIEE 11g warnings during consistency check:
    Warning: [39055] Fact table "HR"."FACT - HC Budget" is not joined to tables in logical dimension "HR"."DIM - HR EmployeeDim". This will cause problems when extracting project(s).
    Description: Even though this fact logical table source has an aggregate grain set in this dimension, no valid physical join was found that connects to any logical table source in this dimension.
    This means that either no join exists at all, or it does exist but is invalid because it connects a higher-level fact source to a lower-level dimensional source. Such joins are invalid and ignored by the Oracle BI Server because, if followed, they would lead to double counting in query answers.
    For example, consider Select year, yearlySales. Even if a join exists between monthTable and yearlySales table on yearId, it cannot be used because such a join would overstate the results by a factor of 12 (the number of months in each year).
    All three of the given validation rules are related to the same issue.
    Please read through the above text to see if it will help with your issue.
    Thanks,
    -Amith.l

  • Prevent Hourly Employees from Ordering Non-stocked Materials and Creating Purchase Reqs in Work Order

    Our SAP plant maintenance system is configured to create a purchase req when a non-stocked material is ordered. We would like to prevent hourly employees from creating a purchase req or ordering non-stocked materials. Only supervisors should be able to order non-stocked materials and create a purchase req. Is there a way to do this via config or system enhancement?

    Hello Rick,
    Clearly there will be 2 ways if not more. One is the Authorization object route and another is Enhancement route. I'm not going to touch the former one. So let's expect answers from other members for that. For the later one, we need to know the answer for the question below:
    'Can we distinguish the hourly employees from regular employees by the user-Id or some other means? If yes, how ?'
    Once we know this, we need to use some user-exit or enhancement spot of the program SAPLCOIH to capture the event of 'N' in the ItemCategory field of Components tab by such UserIds and trigger an error message.  (Suitable user-exit is not striking my mind, so this might go the implicit enhancement way of Order program SAPLCOIH ).
    KJogeswaraRao

Maybe you are looking for