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..

Similar Messages

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

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).

Fact tables are compatible with the query request

Hi,
i am using 11g.In 10g working fine without any error.After migrate 10g into 11g below error will returning. What is the problem and How we will fix.Could you pls let me know.Thanks
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: 14020] None of the fact tables are compatible with the query request FACT_AGENT_TIME_STATISTICS.FKEY. (HY000)
SQL Issued: SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6, s_7, s_8, s_9, s_10 FROM ( SELECT 0 s_0, "Team Performance"."DIMENSION - LOCATION"."COUNTRY CODE" s_1, "Team Performance"."DIMENSION - TIME"."BUSINESS DATE" s_2, CASE WHEN "Team Performance"."DIMENSION - TEAM"."ROLE" ='TEAM LEADER' THEN 'Team Leader' ELSE "Team Performance"."DIMENSION - TEAM"."TEAM" END s_3, CASE WHEN '30 Mins Interval' ='15 Mins Interval' THEN "Team Performance"."DIMENSION - TIME"."15 Mins Interval" ELSE "Team Performance"."DIMENSION - TIME"."30 Mins Interval" END s_4, ((SUM("Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - ACD CALL HANDLING"+"Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - AFTER CALL WORK (ACW)")+SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AVAILABLE TIME"))/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_5, (SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AUX3 - TRAINING"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX4 - MEETING"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX5 - PROJECT"+"Team Performance"."FACT - AGENT TIME STATISTICS"."AUX6 - COACHING")/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_6, (SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."STAFFED TIME")/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") s_7, COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE" s_8, MIN("Team Performance"."DIMENSION - TIME"."FULL DATE TIME") s_9, REPORT_AGGREGATE(((SUM("Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - ACD CALL HANDLING"+"Team Performance"."FACT - AGENT CALL STATISTICS"."TIME - AFTER CALL WORK (ACW)")+SUM("Team Performance"."FACT - AGENT TIME STATISTICS"."AVAILABLE TIME"))/60)/(COUNT(DISTINCT "Team Performance"."FACT - AGENT TIME STATISTICS"."DATE ID")*"Team Performance"."FACT - AGENT TIME STATISTICS"."INTERVAL TYPE") BY CASE WHEN '30 Mins Interval' ='15 Mins Interval' THEN "Team Performance"."DIMENSION - TIME"."15 Mins Interval" ELSE "Team Performance"."DIMENSION - TIME"."30 Mins Interval" END, CASE WHEN "Team Performance"."DIMENSION - TEAM"."ROLE" ='TEAM LEADER' THEN 'Team Leader' ELSE "Team Performance"."DIMENSION - TEAM"."TEAM" END) s_10 FROM "Team Performance" WHERE (("DIMENSION - TIME"."BUSINESS DATE" BETWEEN timestamp '2012-11-23 00:00:00' AND timestamp '2012-11-23 00:00:00') AND ("DIMENSION - LOCATION"."COUNTRY CODE" = 'US') AND ("DIMENSION - LOCATION".DEPARTMENT = 'CSG')) ) djm FETCH FIRST 65001 ROWS ONLY

Back up your repository before following these steps:
1 Reduce the problem report to minimum number of columns required to generate the error. This will usually identify which dimension and which fact are incompatible.
2 Open the repository in the Administration tool and verify that the dimension and fact table join at the physical layer of the repository
3 Verify that there is a complex join between the dimension and the fact in the business layer.
4 Check the logical table sources for the fact table. At least one of them must have the Content tab set to a level in the hierarchy that represents the problem dimension. This is usually the detailed level.
5 Check the logical table source Content tab for the dimension table. Unless there is a valid reason, this should be set to blank.
6. Save any changes to the repository.

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

Hi guys,
I have a weird issue. Previously fine working Subject area started to give this error after migration. The issue is happening when I select a column from dimension and try to display it. Also, I can't get to the list of values in filter I get "Error retrieving choices" error. One dimension is working fine though, and when a column from it is selected, it displays other column just fine. I checked physical layer, primary keys, mappings in the BMM, LTS sources, Connection Pool settings. Everything looks legit. For few hours it was working fine, and now it's giving this issue. Anyone knows what the cause could be. The search I've conducted revealed that this is a data mapping issue - however, all my layers seem to be in check. Thanks

hi user582149,
It is difficult to answer you question with such a little amount of details. Could you specify:
- how many facts/dimensions are you using in the query?
- what is the structure of your Business Model?
- which version of OBI are you using?
- what does your log say?
I hope to tell you more having the information above
Cheers

None of the fact tables are compatible

hi,
am developing report from two fact table columns and one dimension table in obiee 11.1.1.5.0.
am getting error
Error
View Display Error
Odbc driver returned an error (SQLExecDirectW).
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: 14020] None of the fact tables are compatible with the query request Fact - Retail.Retail. (HY000)
SQL Issued: SELECT 0 s_0, "TM Vehicle Sales"."- Offtake Facts"."Offtake" s_1, "TM Vehicle Sales"."- Retail Facts"."Retail" s_2, "TM Vehicle Sales"."Distributor"."Country" s_3 FROM "TM Vehicle Sales"
regards
vcm

need to see your design, dim is shared between the facts?
I think you can assume the physical query based on your columns selection..
Now pick one column from 1st fact and 2nd column from dim run a report, get physcial query and verify the joins with obiee and your own query.
then add column from 2nd query see how it works
Edited by: svee on Jun 29, 2012 6:21 AM

None of the fact tables are compatible error

Hi All,
I do see this error (none of the compatible fact table) after setting the content level aggregation on the dimension tables and the fact table. This error i get only when i try to pull the calculated item which is based on a attribute in the fact table. I have an attribute like year in the fact table i need to display like 'CY'||'2013' in a calculated logical column and when i pull this into answers i get this error -
1) joins are ok ; only one fact table and 3 dimension tables
2). content level on the fact table are specified at the detail level and also for the dimensions
any suggestions - thanks for your time

can anyone please provide some suggestions -
> i looked at the fact table LTS and specified the logical level for each dimension as the detail
> specified the LTS for each dimension table
> I have a column in my fact table which is calendar year and i want to have a derived column like rep_cal_year with 'CY'||cal_year - so when i pull this derived column in my answers i get the error - none of the fact tables are compatibile with the query;
what could be missign?

None of the dimension tables are compatible with the query request

Hi,
i am experiencing the below error while querying columns alone from employee dimension (w_employee_d) in workforce profile SA. There is only one column in my report which is employee number coming from employee dimension. when i query other information like job, region, location etc i am not getting any error. the below error appears only when querying columns from employee dimension. the content tab level for the LTS of employee dimension is set to employee detail.
View Display Error
Odbc driver returned an error (SQLExecDirectW).
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: 14077] None of the dimension tables are compatible with the query request Dim - Employee.Employee Number. (HY000)
SQL Issued: SELECT 0 s_0, "Human Resources - Workforce Profile"."Employee Attributes"."Employee Number" s_1 FROM "Human Resources - Workforce Profile" FETCH FIRST 65001 ROWS ONLY.
couldn't able to know the exact reason. Any suggestions would be highly appreciated.
Regards.

hi user582149,
It is difficult to answer you question with such a little amount of details. Could you specify:
- how many facts/dimensions are you using in the query?
- what is the structure of your Business Model?
- which version of OBI are you using?
- what does your log say?
I hope to tell you more having the information above
Cheers

None of fact sources are compatible with detail filter

Hello
We have 2 facts and 7 dimensions defined in physical layer and below are the relationships between them
D1, D2, D3, D4, D5 are conformed dimensions and all joined to F1 and F2
D6 is joined to F1
D7 is joined to F2.
In BMM layer, I combined two facts(F1 and F2 ) into one fact with two logical sources. And even set the aggregation content level for LTS of F1 to "total level of D7" and
LTS of F2 to "total level of D6".
Whenever I create a report with D6 attributes and D7 attributes without any filter D6 or D7 attribute filters., the report is generating fine. But if the report is using any of the D6 or D7 attributes in filter, I am getting the error *"None of fact sources are compatible with detail filter... "*
Am I missing something. Can someone please help how to resolve this.
BTW..We are on version 11.1.1.5
Thanks,

I am confused here..could you please explain why do you have to set the "Total" Level to Dimension D7 for F1 and "Total" Level for Dimension D6 on F2?
Lets talk about F1 first:
In your case F1 is joined to D1 through D6. Then in the logical layer, on the fact, have you set the levels for the dimensions D1 through D6 to all Detail or lowest level (ROW_WID/KEY)? (Assuming no hierarchies and all are at detail level)
Similarly check the levels on the fact F2. My guess is that it is something to do with your logical level settings. Make sure the logical level are set correctly on the correct dimensions.
Hope this helps.

Non cisco/Third party phones are compatible with CCX 9 or not?

Dear Guys,
I have a CCX 9 server integrated with CUCM 9 and also non cisco based/Third party phones (SNOM IP Phones) as agent for CCX server. when i try to log in to CAD software with User ID and password that assigned to SNOM phone i got JTAPI error but with CIPC(Cisco IP Communicator) works fine and i could log on without any issue. i checked RMuser controlled device and also allow controlled CTI port,all configured. i checked all documents about this issue but it is not mentioned anything about SNOM phone used as agent. any idea for that? any documents for compatibility list between CCX and agent platform...
i have checked below links
http://www.cisco.com/en/US/prod/collateral/voicesw/custcosw/ps5693/ps1844/prod_qas0900aecd80422e66.pdf
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_compatibility/matrix/crscomtx.pdf
Special thanks in advance for your help
Sara

Hi Sara,
If you do not see it in the UCCX comp matirx, than please remember that you will not get support from Cisco TAC incase if you hit any issues with this deployment.
http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_compatibility/matrix/crscomtx.pdf
Thanks,
Anand

None of the fact sources for [column] are compatible with the detail filter

Hi Experts,
I am using obiee 11.1.1.7.
Getting below error when i add a filter of non conformed dimension column.
Below is the 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 [column] are compatible with the detail filter
Please help in solving an issue.
Regards,
NN

Hi NN
You need to follow steps in below link to model your BMM layer for the report to work with non confirmed dimensions.
http://obibb.wordpress.com/2010/05/31/multiple-fact-reporting-on-non-conforming-dimensions/
Once you have followed these steps you can use the non confirmed dimension in the reports.When you see the logs to see the query generated by obiee,it generated 2 queries 1 with confirmed dimension and other with non conformed dimension.When you filter using non confirmed dimension you will now not notice any error but the results will not be filtering out because the filter will be applied only in 1 query which is valid
Now for this to work what you can do is ,instead of using the filter drag the column you like to filter as a prompt in your view.default it to the value you need using the case statement and hide it.This is one of the work around.
There may be many other work arounds for this but you need to understand that for you requirment to work you need to tweek OBIEE to generate 1 query instead of 2 queries.

Fact tables are resulting in error message

hello experts;
I am trying to create a mock-up report in OBI Answers and somehow Im having a problem with metric columns. When I pick any metric column then I get the: *(No Results: The specified criteria didn’t result in any data)*
I have doubled checked the rpd; the schemas btn the dimension and fact tables looks ok to me. I have tried union with another subject area, I get the same error. Anyone with an idea why fact tables are not collaborating with dimension tables?
will appreciate your help

In case if you are not able to see the logs,
follow this
Saving SET VARIABLE LOGLEVEL=2,DISABLE_CACHE_HIT=1; in a report
Mark correct or helpful if it helps,
Regards,
Veeresh Rayan

Which Fact tables are part of OBIA Financial Analytics v796?

Does anyone know which fact tables (Star schemas) are associated with Financial Analytic license?
As of now, I am going thru the document: OracleBusinessAnalyticsWarehouseDMR_V796.pdf and i am trying to identify which Star Schema's are associated with the Financial Analytics and I was wondering if there was a more productive means of finding out this information.
thanks

Ir-respective of what Fact tables are used in Finacial Analytics, the Target DW will have these fact tables when used with EBS source. This is true even if you run ETL only for Financial analytics. This in general is true for EBS also, even though you may only Financial module of EBS, the data model of EBS will have most of the tables as often there are shared tables from other modules.
179 rows selected
TABLE_NAME
W_ABSENCE_EVENT_F
W_ACCT_BUDGET_F
W_ACD_EVENT_F
W_ACTIVITY_F
W_AGREEITEM_F
W_AGREE_F
W_APPL_ACC_SNP_F
W_APPL_EVENT_F
W_AP_BALANCE_F
W_AP_INV_DIST_F
W_AP_XACT_F
W_AR_BALANCE_F
W_AR_XACT_F
W_ASSESS_F
W_ASSET_F
W_BALHSTRY_F
W_BENEFIT_F
W_BOM_ITEM_F
W_CALL_ACCNT_F
W_CALL_ATTND_F
W_CALL_CON_F
W_CAMP_HIST_F
W_CAMP_OPTY_F
W_CASE_F
W_CASE_KPI_F
W_CASE_SNP_F
W_CASE_STG_F
W_CNTCT_CNTR_BNCHMRK_TGT_F
W_CNTCT_CNTR_PERF_F
W_CUSTOMER_COST_LINE_F
W_CUSTOMER_STATUS_HIST_F
W_DTL_FCST_F
W_EMPLOYEE_DAILY_SNP_F
W_EMPLOYEE_EVENT_F
W_EMPLOYEE_MONTHLY_SNP_F
W_EXPENSE_F
W_FN_HOLDING_F
W_FUND_F
W_GL_BALANCE_F
W_GL_COGS_F
W_GL_OTHER_F
W_GL_REVN_F
W_HOUSEHOLD_F
W_INCDNT_KPI_F
W_INCDNT_SNP_F
W_INCIDENT_F
W_INS_CLAIM_F
W_INVENTORY_DAILY_BAL_F
W_INVENTORY_MONTHLY_BAL_F
W_INVOICE_F
W_IVR_NAV_HIST_F
W_JOB_RQSTN_ACC_SNP_F
W_JOB_RQSTN_EVENT_F
W_KPI_F
W_LEAD_F
W_LEAD_KPI_F
W_LEAD_SNP_F
W_LM_ENROLLMENT_ACC_SNP_F
W_LM_ENROLLMENT_EVENT_F
W_LOY_ACCRUAL_ITEM_F
W_LOY_ACTIVITY_F
W_LOY_COST_F
W_LOY_MEMBER_MARKETING_F
W_LOY_MEMBER_STATUS_HIST_F
W_LOY_MEMBER_TIER_HIST_F
W_LOY_PARTNER_POINT_BLOCK_F
W_LOY_PROMOTION_ENROLLEE_F
W_LOY_PROMOTION_MEMBER_F
W_LOY_PROMOTION_PRODUCT_F
W_LOY_REDEMPTION_ITEM_F
W_LOY_REVENUE_F
W_LOY_STATEMENT_F
W_MED_ED_F
W_MKTG_COST_F
W_MKTG_GOAL_F
W_MKTG_LEAD_F
W_OBJECTIVE_F
W_OFR_PROD_F
W_OPTY_CMPT_F
W_OPTY_CON_F
W_OPTY_STG_F
W_ORDERITEM_F
W_ORDER_F
W_ORDIT_WTR_LOG_F
W_PAYROLL_F
W_PERFORMANCE_F
W_PERSON_F
W_PER_RANK_F
W_PIPELINE_F
W_PRODUCT_COST_LINE_F
W_PRODUCT_XACT_F
W_PROJ_BUDGET_F
W_PROJ_COST_LINE_F
W_PROJ_EXP_LINE_F
W_PROJ_FORECAST_F
W_PROJ_FUNDING_HDR_F
W_PROJ_FUNDING_LINE_F
W_PROJ_INVOICE_LINE_F
W_PROJ_RETENTION_F
W_PROJ_REVENUE_HDR_F
W_PROJ_REVENUE_LINE_F
W_PROMOTION_F
W_PURCH_COST_F
W_PURCH_CYCLE_LINE_F
W_PURCH_ORDER_F
W_PURCH_RCPT_F
W_PURCH_RQSTN_LINE_F
W_PURCH_RQSTN_STATUS_F
W_PURCH_SCHEDULE_LINE_F
W_QTEIT_WTR_LOG_F
W_QUOTEITEM_F
W_QUOTE_F
W_RCRTMNT_EVENT_F
W_REP_ACTIVITY_F
W_RESPONSE_F
W_RESP_PROD_F
W_REVN_F
W_RQSTN_LINE_COST_F
W_RTLAUDIT_F
W_SALES_BACKLOG_HISTORY_F
W_SALES_BACKLOG_LINE_F
W_SALES_BOOKING_LINE_F
W_SALES_CYCLE_LINE_F
W_SALES_INVOICE_LINE_F
W_SALES_ORDER_LINE_F
W_SALES_PICK_LINE_F
W_SALES_SCHEDULE_LINE_F
W_SRVREQ_F
W_SUM_FCST_F
W_SURVEY_F
W_SYNDD_DS_F
W_SYNDD_IDS_F
W_SYNDD_PT_F
W_SYNDD_RX_F
W_SYNDD_W_F
W_SYNDD_XPT_F
W_SYNDM_DS_F
W_SYNDM_IDS_F
W_SYNDM_PT_F
W_SYNDM_RX_F
W_SYNDM_W_F
W_SYNDM_XPT_F
W_SYND_DS_T_F
W_SYND_IDS_D_F
W_SYND_IDS_T_F
W_SYND_PT_T_F
W_SYND_RX_T_F
W_SYND_W_T_F
W_SYND_XPT_D_F
W_SYND_XPT_T_F
W_SYNM_DS_T_F
W_SYNM_IDS_D_F
W_SYNM_IDS_T_F
W_SYNM_PT_T_F
W_SYNM_RX_T_F
W_SYNM_W_T_F
W_SYNM_XPT_D_F
W_SYNM_XPT_T_F
W_UA_ACCAPLN_F
W_UA_ACCSUM_F
W_UA_ACCUSG_F
W_UA_ACTUSG_F
W_UA_ADOPT_F
W_UA_ASTAPLN_F
W_UA_ASTSUM_F
W_UA_ASTUSG_F
W_UA_CONAPLN_F
W_UA_CONSUM_F
W_UA_CONUSG_F
W_UA_OPTAPLN_F
W_UA_OPTYSUM_F
W_UA_OPTYUSG_F
W_UA_QOTUSG_F
W_VEHICLE_F
W_WRKFC_EVT_AGE_F
W_WRKFC_EVT_F
W_WRKFC_EVT_MERGE_F
W_WRKFC_EVT_MONTH_F
W_WRKFC_EVT_POW_F
Edited by: shyamvaran on Jul 22, 2009 2:55 PM

I can't restore my data from my iphone5s or ipad to my new iphone6, because it woulkd seem that none of the available backups from icloud are compatible with iOS 8.0.2, which is what the new iphone is running. (or so it seems).

Just received my iphone6, as my iphone5s gave up the ghost. Completely. I now want to restore everything that I had on my old phone to my new new one using icloud. However, when I arrive at the screen that asks you to select a backup version, it shows me a list, but then at the bottom of the screen there is a message that says that 'no icloud backups are compatible with the version of (8.0.2) on this iphone.' I also have an ipad, and both the 5 and the ipad were updated to 8.1. I did try to back up via itunes, but only got some of my photos's back and none of my messages, some of which had essential information on them. Anybody have any idea's? Any help gratefully recieved!

Your iPhone's iOS must be same or newer than the one in backups. In your case it is older so you need to update your iPhone and then recover it with backup.

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

Similar Messages

Maybe you are looking for