No Message: Write to Fact table.

Hi ALL,
Source: ECC 6
Target: BI 7.3
We are Transferring 2LIS_13_VDITM Datasource---->> 0SD_CO3 Infocube .
After Data Replication ,
1. Data Transferred to PSA .
2. During Transformation Creation Manuel Mapping is performed . Activated .
3. During DTP Creation Only Following Warning Messages Occur , Status s not Transferred to Green .
Data is not coming Cube , No Error Messages. (Totally 29000 Records have to transfer to BI Cube)
Warning Messages are,
1.No Message: Write to Fact table.
2.No Message:Infocube Update Completed .
What is the Problem?

Hi,
Have you set the Industroy sector before uploading the set up tables?
For more information refer the note: 353042
Summary
Symptom
Fields BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG, etc. of DataSources 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_03_BF, 2LIS_03_UM, 2LIS_40_REVAL are not filled.
This may lead to the following:
The system does not perform any update into an InfoCube (for example: 0RT_C*, 0PUR_C01, 0CP_PURC1 and so on), even though data arrives in BW.
This occurs with the following InfoSources:
2LIS_02_SCL, 2LIS_02_ITM
2LIS_03_BF, 2LIS_03_UM
2LIS_40_REVAL
With some restriction, this symptom also occurs with the following InfoSources if they are used in connection with retail or consumer products. (InfoCube: 0RT_* or 0CP_* ).
2LIS_11_VAITM, 2LIS_12_VCITM, 2LIS_13_VDITM
Other terms
0PROCESSKEY, PROCESSKEY, 0RT_C01, 0RT_C02, 0RT_C03, 0RT_C04, BWBRTWR, BWGEO, BWGEOO, BWGVP, BWGVO, BWNETWR, BWMNG
Reason and Prerequisites
The process key (0PROCESSKEY and 0BWAPPLNM) of the InfoSources has not been filled. As a result, no key figures are updated because of the update routine of the participating InfoCube and along with it no records are inserted into the InfoCube. In each update routine, the system checks the content of the PROCESSKEY. If this field has no contents, then no data is written into the InfoCube because of the IF condition in the update rules.
Solution
So that you can work in the above mentioned InfoSources, you MUST activate the determination of the process key. This is done with the help of Transaction MCB_ which you can find in the OLTP IMG for BW (Transaction SBIW) in your attached R/3 source system.
Here you can choose your industry sector. 'Standard' and 'Consumer products' are for R/3 standard customers, whereas 'Retail' is intended for customers with R/3 Retail only.
You can display the characteristics of the process key (R/3 field BWVORG, BW field 0PROCESSKEY) by using Transaction MCB0.
If you have already set up historical data (for example for testing purposes) by using the setup transactions (Statistical Setup Programs) (for example: Purchasing: Tx OLI3BW, material movements: OLI1BW) into the provided setup tables (for example: MC02M_0SCLSETUP, MC03BF0SETUP), you unfortunately have to delete this data (Tx LBWG). After you have chosen the industry sector by using  MCB_, perform the setup again, so that the system fills a valid transaction key for each data record generated. Then load this data into your connected BW by using 'Full update' or 'Initialization of the delta process'. Check, whether the system updates data into the involved InfoCubes now.
If all this is not successful, please see Note 315880, and set the application indicator 'BW' to active using Transaction 'BF11'.
Related notes:
157317 --> You MUST make sure that this note is relevant for you.
352344 -> Process key + reversals in Inventory Management
          (Consulting note).
Regards,
Anil Kumar Sharma .P

Similar Messages

  • Can't load data to cubes - same error for all DTPs  "exception in substep write to fact table"

    Hi Experts,
    This initial DTP error is:
    Data package processing terminated Message no. RSBK229
    Error while updating to target <cubename> (type INFOCUBE) Message no. RSBK241
    If I drill down to the specific package in the process monitor the error is:  "exception in substep write to fact table" .
    No more details for why the error is being generated.
    SAP BW 307 service pack 8.
    I have run the debugger without success, an ABAPer also ran debug mode to get more details on the error without success
    We checked teh termination point and the ABAP stack
    No error stack is available
    No short dumps
    I have reactivated the DTP
    The data looks fine
    The server crashed the day before the DTPs started to fail
    One cube is standard content and the other is a Z version of the same cube.
    Please let me know if anyone has resolved this issue before and what steps were necessary.

    Hello Russell,
    We have got the similar situation and we later found that it was a data issue only.
    We tried to enable the error stack, but as the data issue was due to a lookup which is bringing the invalid data, its not captured in the error stack and throwing short dump with the message u mentioned.
    so my suggestion, just put a break point if there are any lookups and check the data in internal tables if everything is as expected.
    Hope this helps.
    Thanks,
    Venkata Naresh

  • 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

  • Key Figure units in Fact Table - Error

    All -
    When a run a report off of a cube, some row display 0 when there are corresponding values in my cube.  The report doesn't agree with LISTCUBE.  I have ran transaction RSRV on my cube and tested the "Key figure units in fact tables of Infocube" and I get an error saying that 1380 units are missing from fact table.
    <b>Diagnosis
    In the fact table /BIC/FEU_FRCTS records have been found that contain values other than zero for key figures that have units, but that have no value for the unit of the key figure. Since the value of the unit has to correspond to the value of the key figure, this inidicates an error when the data was loaded. The values of the units have not been loaded into BW correctly. Choose Details to display the incorrect records.</b>
    Does anyone know what this error means? How do I solve this problem?
    Thanks,
    Nyrvole

    hi Nyrvole,
    as the message said, you have keyfigures with unit but the unit value not filled, click 'detail' as suggested to check which keyfigure(s) involved, that go to rsd2 type in that keyfigure and see which infoobject unit is used, then check transfer/update rules how this unit infoobject mapped, try correct the values and upload again.
    there is option 'repair' in rsrv but think in this case it can't fix the error, just try.
    hope this helps.

  • Key figure units in fact tables of InfoCube are blank

    I run RSRV - Key figure units in fact tables for my cube and found the following error message. I found one SAP note 941895 - RSRV test fails with unknown error, but our system status is SAPKW70020, so this note is not useful to our case. Pls advise!
    System message:
    The test Unit of key figures in fact tables for InfoCube XXX initial had to be terminated due to an unknown error (RSRV320).
    Many thanks!
    rajatina.

    Hi Raja,
    Check that in your transformation you have mapped Unit from source system to this key figure. If not then you will have to do the mapping and reload the data. If you are not able to get unit from source system then atleast you will have to assign some constant Unit if possible.
    Regards,
    Durgesh.

  • Attribute key not found when there is no data in Fact table

    Hi All,
    I have a Dimension and Fact table,Dimension has data but Fact table is empty. The Dimension is MOLAP & Measure group is ROLAP. the relation is built on Key column and named column is some other attribute.
    When I execute MDX "select { [Measures].[Avg Sales] -- Average type measure} on columns from my_Cube ", this returns a valule with #Error. error message in cell is "The attribute key cannot be found when processing:
    Table: 'FACT, Column: 'ID', Value: '0'. The attribute is 'Name' "
    I have processed the Dimension with Full and then Cube is processed with Full. but still same error. Please suggest .
    Ram MSBI Developer

    Hi Ram ,
    Since you mentioned "Value: '0'. The attribute is 'Name' ""
    I would recommend to have a look at the Key/Name Column's property regarding to the NullProcessing .
    Regards, David .

  • Issue using one 2 Fact tables with one dimension Table.

    Hi,
    I have 1 Dimension table X and 2 Fact tables A and B
    X is joined to Both A and B for Loan Amount ( with A) and for colleatral amount (with B) when I am selecting the X.Product_Name, A.Loan_Amt, B.Collateral Amount, it is giving an error message
    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 EIP Collateral FACT) does not contain mapping for [EIP Reporting FACT.PD ID]. (HY000)
    Any clues???
    Is there a Inner or Outer join which needs to be created or set in the RPD to get the desired results???

    Ok..
    I have one table which is Porfolio Details which has Portfolio name, Product Category , Product Name, Product ID, Product sources code.- This is my Dimension table.
    I have another 2 set of fact tables : EIP Reporting FACT and EIP Collateral FACT..
    These two tables are joined to Portfolio Details table.
    EIP Reprting FACT gives portfolio wise Loan Amount
    and EIP Collateral FACT gives Portfolio wise Collateral Amount details for same set of customer..
    Now, I am selecting Portfolio Name, Product Category, Product Name,SUM( EIP Reporting FACT.LOAN_AMOUNT), SUM(EIP Collaetral FACT.Collateral_Amt) in a report
    Now, on selecting these columns I am getting that error message which is related to mapping.
    If I take any column from Portfolio details table and any column from EIP Reporting FACT- It works.
    If I take any column from Portfolio details table and any column from EIP Colletral FACT- It works.
    But if I take any column from portfolio table and columns from both FACT tables it gives mapping error...
    Hope I am able to explain the issue in a better way now..
    Edited by: help-required on Mar 11, 2010 6:53 PM
    Edited by: help-required on Mar 11, 2010 6:53 PM

  • SQL Server 2k - Pulling from 2 fact tables causes error

    Trying to create a simple RPD as follows:
    1 Dimension with Key Fund_ID
    2 Fact tables, each with a Key Fund_ID
    Created a Physical Layer, connecting Dimension to each Facts based off Fund_ID (One to Many)
    Business Model Layer, connected Dimension to each Fact using complex join.
    In Answers, the following is true:
    Querying Dim and Fact Table A returns Data
    Querying Dim and Fact Table B returns Data
    Querying Dim AND Fact Table A, AND Fact Table B returns the following error message:
    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 A) does not contain mapping for [table B]. (HY000)
    It appears to be complaining that it cannot map the fact tables to each other. I tried mapping the two fact tables together (even though that doesn't make DW sense), and the RPD won't validate.
    I'm wondering if this is a bug connecting to SQL Server. We do the majority of our RPD development against ORACLE, and this is our first attempt at using SQL Server as a source.
    Does anyone have any suggestions on this?
    thanks

    I doubt it very much its DB specific, the error is from the BI Server ([nQSError: 15018]) rather than SS.
    Have you got a dimension hierarchy ? Are your content levels set for all logical tables, do you have 2 logical facts or 1 combined logical fact ? What do your Logical Table sources look like (ie how many per logical table, conent levels ?joins within the LTS?)
    I would guess the problem lies in your BMM layer. But should check, is the conformed dimension joined to both fact tables in the physical layer or have your aliased it ?

  • How to combine multiple fact tables and dimensions in one worksheet?

    Hello Forum,
    I am encountering a reporting problem when trying to create a worksheet that uses more than one cube/fact table and common dimensions. I have used Oracle Warehouse Builder 10Gr2 to design and deploy a pretty simple ROLAP data mart. We are using Discoverer Plus for OLAP as our reporting tool. We have 5 dimension tables using a star schema and 3 fact tables, when I create the worksheet I bring in our sales measure from our sales item table and then Store_Name from my Stores Dimension and then day from my time dimension, everything looks good at the stage, we're just trying to get a sum of all sales for that store on that day. Then I bring in a measure from our advertising cost table and a join window pops up asking which join to use, if I choose either the Store or the Time dimension I get correct data for the first fact table (sales) and grossly incorrect data for the ad cost measure from the second fact table (advertsing costs)...... any help would be appreciated

    You have encountered one of the key limitations of Discoverer... which I complained about to the Discoverer product manager at OpenWorld in 2001....
    Anyhow, to get around this, you are going to have to deal with it either in the database, (views, materialized views, tables), or within the admin tool by creating a custom folder.
    Discoverer also calls this the "fan trap", but never really had a solution to the problem. [The solution only worked is you joined to one and only one dimension!]
    What you want (using Sales_Fact and Inventory_Fact as an example) is to join Sales to Time, Store, and Product, and save that result. Then join Inventory to Time, Store, and Product, save that result, then do a double outer join between the two intermediate temporary tables in order to calculate something useful like inventory turns by store and product line.
    This is also known a "multipass SQL", and is supported by some (but not many) other tools.
    So, to accomplish this with Discoverer, you'll either need to create a view, or table, or materialized view that has already put Sales and Inventory into a single (virtual?) fact table. Alternatively you can write the SQL for how to do this linkage (don't forget to handle missing data), and use the Discoverer admin tool to create a custom folder that uses your SQL.
    Hope this helps!

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

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

  • Fact tables in Infocube

    How many tables Exact Contain in Info cube?
    Please search the forum
    Edited by: Pravender on Sep 16, 2011 12:31 AM

    Hi Mahesh,
    For Basis InfoCubes in SAP BW, there are two fact tables for
    including transaction data: The F and the E fact table.
    Unlike the E fact table, the F fact table contains the information
    about the request from where the transaction data originates
    When loading data (when receiving requests), the system writes data
    into the F fact table.
    During "compression", the system summarizes data from different
    requests and writes it to the E fact table.
    To ensure good reporting performance, it is important that you only
    keep data from a few requests in the F fact table, which means that you
    should compress requests as soon as possible.
    Also bear in mind that deleting transaction data according to the
    request is only possible from the F fact table, as only this table
    contains the information regarding which data belongs to which
    request.
    You should therefore compress a request as soon as you are certain
    that the data loaded is correct. When you install BW on an ORACLE database, BITMAP indexes are created on the fact tables to improve the reporting performance of the system
    And yes try to search on help.sap, there is plenty of information.
    Regards
    Sunny

  • Fact Table with a metric repeated in several rows

    Hi!!
    I've got a little problem and I don't know how to face it.
    I'm using OBIEE and I've got this case:
    One fact table like this:
    Order_Number - Q.Received - Supplier - Invoice_Number - Q.Inv.
    1 - 10 - S1 - I1 - 2
    1 - 10 - S1 - I2 - 8
    2 - 10 - S1 - I3 - 10
    So, for an order Number, I can have more than one Invoice Number, but the quantity Received is always 10, because is a metric refered to the Orden, not to de Invoice, but this quantity (10) I find it in two rows, not in one row. It's like having two fact tables mixed (invoices and orders).
    My problem is:
    If in the logical field Q.Received I don't aggregate de column, when in Answers I try to know the Quantity of units received by supplier S1, the report says 10, that is incorrect. It should be 20.
    If in the logical field Q.Received I aggregate de column, when in Answers I try to know the Quantity of units received by supplier S1, the report says 30, that is incorrect too.
    I've tried to separate it in two fact tables by views like this:
    Fact1: Orders
    Order_Number - Q.Received - Supplier
    1 - 10 - S1
    2 - 10 - S1
    Fact2: Invoices
    Order_Number - Invoice_Number - Q.Inv.
    1 - I1 - 2
    1 - I2 - 8
    2 - I3 - 10
    ...and I've created a dimension with Order_Number, but the report:
    Order_Number - Q.Received - Q.Inv.
    ...doesn't work.
    -If I try without jerarquies, OBIEE goes only to the first one and if I select a field from Fact2 says that there isn't a mapping for this field.
    -If I try with jerarquies for the only dimension I have, with a grand total level and a child level, selecting the lowest level for all tables, error is: "None of the fact tables are compatible with the query request "
    Can anybody help me? I'm having nightmares with this issue.
    Thanks a lot in advance.

    Hi,
    Okay. I assume you have the 2 facts:
    Fact1: Orders
    Order_Number - Q.Received - Supplier
    1 - 10 - S1
    2 - 10 - S1
    Fact2: Invoices
    Order_Number - Invoice_Number - Q.Inv.
    1 - I1 - 2
    1 - I2 - 8
    2 - I3 - 10
    create a business model with the following logical tables:
    Order Dim,
    QTY Received,
    QTY Invoiced
    drag/drop Order_number from Fact1 to the logical table Order Dim (this will create a logical column Order_number).
    drag/drop Order_number from Fact2 to the logical COLUMN Order_number. (This will give you a second Logical Table Soruce with 1 logical table column.)
    drag/drop Q.Received from Fact1 to logical table QTY Received
    drag/drop Q.Inv. from Fact2 to logical table QTY Invoiced
    Assign key to LT Order Dim
    and draw Business Model Diagram.
    This should give you the possibility to report the quantity received and invoiced per order number
    Regards
    Message was edited by:
    wobiee1

  • No fact table exists at the requested level of detail Error.

    Hi Everybody,
    Facing a issue on the using  Fact less Fact tables.
    Scenario:
    ========
    Using two subject areas to develop a report.OBIEE 11g
    Fact1 --> Compensation Plan Assignments Real Time
    Fact2 --> Participant Detail Real Time"."Participant Details
    On both facts we created dummy metrics on respective table id's and aggregated to ROWCOUNT.
    As i said in earlier we are using the above 2 subject areas to develop reports.
    Logical SQL:
    ===========
    SELECT
    0 s_0, "Incentive Compensation - Compensation Plan Assignments Real Time"."Role"."Role Name" s_1,
    "Incentive Compensation - Participant Detail Real Time"."Participant Details"."Cost Center" s_2,
    "Incentive Compensation - Participant Detail Real Time"."Participant Details"."Country Code" s_3,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Participant First Name" s_4,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Participant Last Name" s_5,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Party Number" s_6
    FROM "Incentive Compensation - Earnings Real Time" FETCH FIRST 65001 ROWS ONLY
    Error Message:
    ==============
    Expression 'RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]' converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]..
    [2013-10-21T12:18:45.000-05:00] [OracleBIServerComponent] [TRACE:2] [USER-34] [] [ecid: 004uJx90aHO9lZ73VJJNB80007eh000gl_,0:2:1:9:5] [tid: 457c2940] [requestid: f2e001b] [sessionid: f2e0000] [username: [email protected]] -------------------- Query Status: [nQSError: 14025] No fact table exists at the requested level of detail:
    Please share some ideas on this or any guidelines will be very much helpfull.

    Govardhan,
    Did u configured any Dimension Hierarchy please set the levels in that particular Fact LTS.
    For more info,check the below thread
    https://forums.oracle.com/thread/2134934
    Thanks,

  • No fact table exists at the requested level of detail

    We have two fact tables F1,F2 and D1, D2, D3, D4, D5 dimensions.
    They are connected line this.
    F1 to D1, D2, D3 and self dimension D_of_F1
    F2 to D2, D3 and self dimension D_of_F2
    Means D2 and D3 are common dimensions between two facts.
      D_of_F1
             |
             |
    D1--F1--D2
             |      |
             |      |
            D3   |
            |       |
            |       |
            |-F2-|
            |
            |
            |
       D_of_F2
    Hierarchies
    H1 for D1
    H2 for D2
    H3 for D3
    H_of_F1 for D_of_F1
    H_of_F2 for D_of_F2
    and pinned LTS of F1 --> H1 detail, H2 Detail,H3 Detail, H_of_F1 Detail
    and pinned LTS of F2 --> H2 Detail,H3 Detail, H_of_F2 Detail
    We are selecting these columns
    D1.C1, D1.C2, D2.C1, D2.C2,D3.C1 and report works perfactly.
    But when I add D_of_F2.C1 then report gives this error
    Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail
    Please help me to solve this error....
    I m new in OBIEE concepts so not able to trubleshoot...
    Thank you.

    i'm try to do an analysis between two tables (that have a relatinship), we had inclued first the FACTURA.FACTURA_COD, then columns from COBRANCAS and it work's. When we inclued the FACTURA.COMISSIONISTA_ID it return the fowlling error :check the level set in content tab in fact table.it can happen that FACTURA.COMISSIONISTA_ID is at a lower level than specified in fact table.
    Regards,
    Sandeep

Maybe you are looking for

  • 2 ISP link failover in ASA 5505

    Hi, I have ASA 5505, want to configure the 2 ISP link Tata and Airtel with failover. I want to configure the WebVPN with failover, so that user don't need to change the public address when one link goes down. thanks with regards Ashish Kumar

  • HT4367 Apple TV update fail.

    Apple TV was working fine but I kept getting a message prompting me to update, as most would think "what's the harm" I went ahead and did so. I then get to stage two of the update and I get a message saying I need to connect to iTunes via a micro USB

  • Use Of Oracle DRM

    Hi Can anyone tell me  the use of DRM i had gone through DRM Guides and Other blogs also but i did n't understand about this clearly . can you tell me with few examples why DRM and how it is useful to Hyperion Thanks,

  • SRM table for backend PO & PR no. in Classic scenario

    Hi All, We are in classic scenario. I need the table/view name which stores the PR and PO no. created in the backend system. I could find different view names for PO,PR nos. from BBP_PD but is there any single table/view which stores this data ? Any

  • HT201365 How do I stop the running of programs in the background?  The old way of doing it doesn't work now.

    How do I stop the running of programs in the background?  The old way of doing it doesn't work now.