"AP Transactions" Subject Area hitting incorrect Fact table

Hi Gurus,
Requirement/Background:
We have done some customization to "Financials - AP Transactions" subject area i.e. adding 3 new W_DAY_D aliases in physical layer and few custom columns in W_AP_XACT_F.
I did not create any new BMM tables for new W_DAY_D aliases, just added these new tables in LTS (Fact_W_AP_XACT_F) under "Dim - AP Transaction Details", and put all the custom columns under same Logical table i.e."Dim - AP Transaction Details" mapping correctly to W_DAY_D and W_AP_XACT_F.
Problem Statement :
Whenever I add "Purchase Invoice Number" to the query, it hits incorrect fact table i.e.W_AP_AGING_INVOICE_A and gives incorrect results.
Expected Query : (if I select GL Account Number, Purchase Invoice Number & AP Amount)
select sum(T333486.AP_LOC_AMT * -1) as c1,
               sum(T333486.AP_DOC_AMT * T333486.GLOBAL1_EXCHANGE_RATE * -1) as c2,
               T333486.PURCH_INVOICE_NUM as c3,
               T334337.GL_ACCOUNT_NUM as c4
          from
               W_AP_XACT_F T333486 /* Fact_W_AP_XACT_F */ ,
               W_GL_ACCOUNT_D T334337 /* Dim_W_GL_ACCOUNT_D */
          where  ( T333486.GL_ACCOUNT_WID = T334337.ROW_WID and T333486.PURCH_INVOICE_NUM = '1161/13 CH' and T333486.DELETE_FLG = 'N' )
          group by T333486.PURCH_INVOICE_NUM, T334337.GL_ACCOUNT_NUM
Current Query it is firing :
select sum(T333486.AP_LOC_AMT * -1) as c1,
               sum(T333486.AP_DOC_AMT * T333486.GLOBAL1_EXCHANGE_RATE * -1) as c2,
               T348360.PURCH_INVOICE_NUM as c3,
               T334337.GL_ACCOUNT_NUM as c4
          from
               W_AP_XACT_F T333486 /* Fact_W_AP_XACT_F */ ,
               W_GL_ACCOUNT_D T334337 /* Dim_W_GL_ACCOUNT_D */ ,
               W_SUPPLIER_ACCOUNT_D T336997 /* Dim_W_SUPPLIER_ACCOUNT_D */ ,
               W_STATUS_D T338711 /* Dim_W_STATUS_D_Generic */ ,
               W_XACT_TYPE_D T338741 /* Dim_W_XACT_TYPE_D_Financials */ ,
               W_DAY_D T344857 /* Dim_W_DAY_D_Payment_Due_Date */ ,
               W_DAY_D T348434 /* Dim_W_DAY_D_Purchase Invoice Date */ ,
               W_DAY_D T351452 /* Dim_W_DAY_D_Purchase Invoice Cleared_Date */ ,
               W_PAYMENT_METHOD_D T394960 /* Dim_W_PAYMENT_METHOD_D_AP */ ,
               W_XACT_SOURCE_D T394984 /* Dim_W_XACT_SOURCE_D */ ,
               W_AP_AGING_INVOICE_A T348360 /* Fact_W_AP_AGING_INVOICE_A */
          where  ( T333486.GL_ACCOUNT_WID = T334337.ROW_WID and T333486.SPLR_ACCT_WID = T336997.ROW_WID and T333486.DOC_TYPE_WID = T338741.ROW_WID and T333486.DOC_STATUS_WID = T338711.ROW_WID and T333486.INVOICED_ON_DT_WID = T348434.ROW_WID and T333486.PAY_METHOD_WID = T394960.ROW_WID and T333486.CLEARED_ON_DT_WID = T351452.ROW_WID and T333486.PAYMENT_DUE_DT_WID = T344857.ROW_WID and T333486.SOURCE_WID = T394984.ROW_WID and T333486.DELETE_FLG = 'N' and T344857.ROW_WID = T348360.PAYMENT_DUE_DT_WID and T336997.ROW_WID = T348360.SPLR_ACCT_WID and T338711.ROW_WID = T348360.DOC_STATUS_WID and T338741.ROW_WID = T348360.DOC_TYPE_WID and T348360.PURCH_INVOICE_NUM = '1161/13 CH' and T348360.PAYMENT_METHOD_WID = T394960.ROW_WID and T348360.INVOICED_ON_DT_WID = T348434.ROW_WID and T348360.CLEARED_ON_DT_WID = T351452.ROW_WID and T348360.SOURCE_WID = T394984.ROW_WID )
          group by T334337.GL_ACCOUNT_NUM, T348360.PURCH_INVOICE_NUM
"Purchase Invoice Number" is out-of-box present under "Dim - AP Transaction Details" and it is mapped to 4 tables including W_AP_XACT_F & W_AP_AGING_INVOICE_A. It is also set at Detail level in AP Transactions dimension hierarchy.
Additionally, implicit fact column has also been set. So why it is not hitting W_AP_XACT_F ???
Thanks in advance.
Regards,
Ravi Desai

You said that the Logical table Date- dim has 2 LTS (Date_dim, Event_closed_date_dim ).
How you defined this, is it something like
1) Drag table Date_dim
2) Select the column Row_wid of Event_closed_date_dim from Physical layer and drop on Row_wid of Logical tabl Date_dim
With this logical column Row_wid 2 sources. In this case you see 1 logical join between logical table day(with 2 LTS) and fact
If you followed this way should not have any issues.
Joins like:
PL-: Date_dim--->Fact<-- Event_closed_date_dim
BMM: Date->Fact
If you have any doubts, just create a new rpd with these table objects
Check your configuration.

Similar Messages

  • OBIEE Hitting incorrect fact table

    Hi,
    I have two Fact tables joined with 3 Dimensions..
    F1 - D1, D2, D3
    F2 - D1, D2, D3
    Now I added another dimension D4 and joined it with F2.
    While taking D1, D2 D3 while it use to get F1 in the Query now, it started taking F2 and showing incorrect results.. How can this be fixed?

    Dont blame OBIEE!! You haven't configured it correctly.
    Try to set implicit fact column setting on Subject area. That might help you.
    If helps mark

  • Hi, all transactions codes are saved in which table?some transaction codes?

    hi,
    all transactions codes are saved in which table?i want some transaction codes?

    All transaction codes are stored in table TSTC. Their texts are displayed in TSTCT.
    Here are some T-CODE's..
    OSS1      SAP Online Service System
    OY19      Compare Tables
    S001      ABAP Development Workbench
    S002      System Administration.
    SA38      Execute a program.
    SCAT      Computer Aided Test Tool
    SCU0      Compare Tables
    SE01      Old Transport & Corrections screen
    SE09      Workbench Organizer
    SE10      Customizing Organizer
    SE10      Customizing organizer – requests for user (To release for transport – enter user name, press Enter. Select changed object and select ReleaseSE10 New Transport & Correction screen
    SE11      ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary Display SE13 Maintain Technical Settings (Tables)
    SE11      ABAP/4 Dictionary.
    SE12      Dictionary: Initial Screen – enter object name
    SE13      Access tables in ABAP/4 Dictionary.
    SE14      ABAP/4 Dictionary: Database Utility.
    SE14      Utilities for Dictionary Tables
    SE15      ABAP/4 Repository Information System
    SE15      ABAP/4 Repository Information System.
    SE16      Data Browser
    SE16      Data Browser: Initial Screen.
    SE16      Display table contents
    SE17      General Table Display
    SE30      ABAP/4 Runtime Analysis
    SE30      ABAP/4 Runtime Analysis: Initial Screen.
    SE30      Run Time Analysis (press Tips and Tricks button for good stuff)
    SE32      ABAP/4 Text Element Maintenance
    SE35      ABAP/4 Dialog Modules
    SE36      ABAP/4: Logical Databases
    SE37      ABAP/4 Function Library.
    SE37      ABAP/4 Function Modules
    SE38      ABAP Editor
    SE38      ABAP/4 Editor.
    SE38      ABAP/4 Program Development
    SE39      Splitscreen Editor: Program Compare
    SE41      Menu Painter
    SE43      Maintain Area Menu
    SE51      Screen Painter
    SE51      Screen Painter: Initial Screen.
    SE54      Generate View Maintenance Module
    SE61      R/3 Documentation
    SE62      Industry utilities
    SE63      Translate Short/Long Text.
    SE63      Translation
    SE64      Terminology
    SE65      R/3 documents. Short text statistics SE66 R/3 Documentation Statistics (Test!)
    SE68      Translation Administration
    SE71      SAPscript layout set
    SE71      SAPscript Layouts Create/Change
    SE72      SAPscript styles
    SE73      SAPscript font maintenance (revised)
    SE74      SAPscript format conversion
    SE75      SAPscript Settings
    SE76      SAPscript Translation Layout Sets
    SE77      SAPscript Translation Styles
    SE80      ABAP/4 Development Workbench
    SE80      Repository Browser: Initial Screen.
    SE81      SAP Application Hierarchy
    SE82      Customer Application Hierarchy
    SE84      ABAP/4 Repository Information System
    SE85      ABAP/4 Dictionary Information System
    SE86      ABAP/4 Repository Information System
    SE87      Data Modeler Information System
    SE88      Development Coordination Info System
    SE91      Maintain Messages
    SE92      Maintain system log messages
    SE93      Maintain Transaction Codes
    SE93      Maintain Transaction.
    SEU      Object Browser
    SHD0      Transaction variant maintenance
    SM04      Overview of Users (cancel/delete sessions)
    SM04      Overview of Users.
    SM12      Deletion of lock entries (in the event you have you are locked out).
    SM12      Lock table entries (unlock locked tables)
    SM21      View the system log, very useful when you get a short dump. Provides much more info than short dump
    SM30      Maintain Table Views.
    SM31      Table Maintenance
    SM32      Table maintenance
    SM35      View Batch Input Sessions
    SM37      View background jobs
    SM50      Process Overview.
    SM51      Delete jobs from system (BDC)
    SM62      Display/Maintain events in SAP, also use function BP_EVENT_RAISE
    SMEN      Display the menu path to get to a transaction
    SMOD/CMOD      Transactions for processing/editing/activating new customer enhancements.
    SNRO      Object browser for number range maintenance.
    SPRO      Start SAP IMG (Implementation Guide).
    SQ00      ABAP/4 Query: Start Queries
    SQ01      ABAP/4 Query: Maintain Queries
    SQ02      ABAP/4 Query: Maintain Funct. Areas
    SQ03      ABAP/4 Query: Maintain User Groups
    SQ07      ABAP/4 Query: Language Comparison
    ST05      Trace SQL Database Requests.
    SU53      Display Authorization Values for User.
    Human Resources
    PA03      Change Payroll control record
    PA20      Display PA Infotypes
    PA30      Create/Change PA Infotypes
    PP02      Quick Entry for PD object creation
    PU00      Delete PA infotypes for an employee. Will not be able to delete an infotype if there is cluster data assigned to the employee.
    Sales and Distribution (SD)
    OLSD      Config for SD. Use Tools-Data Transfer-Conditions to setup SAP supplied BDC to load pricing data
    VA01      Create Sales/Returns Order Initial Screen
    VB21      Transaction for Volume Lease Purchases (done as a sales deal)
    VK15      Transaction used to enter multiple sales conditions (most will be entered here)
    VL02      Deliveries
    SAP Office
    SO00      send a note through SAP, can be sent to Internet, X400, etc
    Financial Accounting (FI)
    FGRP      Report Writer screen
    FM12      View blocked documents by user
    FST2      Insert language specific name for G/L account.
    FST3      Display G/L account name.
    KEA0      Maintain operating concern.
    KEKE      Activate CO-PA.
    KEKK      Assign operating concern.
    KL04      Delete activity type.
    KS04      Delete a cost centre.
    KSH2      Change cost centre group – delete.
    OBR2      Deletion program for customers, vendors, G/L accounts.
    OKC5      Cost element/cost element group deletion.
    OKE1      Delete transaction data.
    OKE2      Delete a profit centre.
    OKI1      Determine Activity Number: Activity Types (Assignment of material number/service to activity type)
    OMZ1      Definition of partner roles.
    OMZ2      Language dependent key reassignment for partner roles.
    Material Management (MM)
    MM06      Flag material for deletion.
    OLMS      materials management configuration menu, most of the stuff under this menu is not under the implementation guide
    MM configuration transactions
    OLMB      Inventory management/Physical Inventory
    OLMD      MM Consumption-Based Planning
    OLME      MM Purchasing
    OLML      Warehouse Management
    OLMR      Invoice Verification
    OLMS      Material Master data
    OLMW      MM Valuation/Account Assignment
    Configuration related
    OLE      OLE demo transaction
    OLI0      C Plant Maintenance Master Data
    OLI1      Set Up INVCO for Material Movements
    OLI8      Set Up SIS for Deliveries
    OLIA      C Maintenance Processing
    OLIP      C Plant Maintenance Planning
    OLIQ      New set-up of QM info system
    OLIX      Set Up Copying/Deleting of Versions
    OLIY      Set Up Deletion of SIS/Inter.Storage
    OLIZ      Stat Set Up INVCO: Invoice Verify
    OLM2      Customizing: Volume-Based Rebates
    OLMB      C RM-MAT Inventory Management Menu
    OLMD      C RM-MAT MRP Menu
    OLME      C MM Menu: Purchasing
    OLML      C MM Menu for Warehouse Management
    OLMR      C RM-MAT Menu: Invoice Verification
    OLMS      C RM-MAT Master Data Menu
    OLMW      C RM-MAT Valuation/Acct. Asset. Menu
    OLPA      SOP Configuration
    OLPE      Sales order value
    OLPF      SPRO Start SAP IMG (Implementation Guide).
    OLPK      Customizing for capacity planning
    OLPR      Project System Options
    OLPS      Customizing Basic Data
    OLPV      Customizing: Std. Value Calculation
    OLQB      C QM QM in Procurement
    OLQI      Analysis OLVD C SD Shipping Menu
    OLVF      C SD Billing Menu
    OLQM      Customizing QM Quality Notifications
    OLQS      C QM Menu Basic Data
    OLQW      C QM Inspection Management
    OLQZ      Quality Certificates
    OLS1      Customizing for Rebates
    OLSD      Customizing: SD
    OLVA      C SD Sales Menu           
    OLVS      C SD Menu for Master Data
    Regards,
    Pavan

  • In General What is are Dimentional and fact tables

    Hi
    In General What is are Dimentional and fact tables.
    What are the differences between
    Data Warehouse, Data Mart, Data Mining, OLAP
    if possible Pl give definations also for above.
    thanks

    Please refer to www.ralphkimball.com

  • Dimension ids are 0 in fact table of infocube

    Hi ,
    We have cube in which we have have dimension A which has two chars stocktype (non masterdata).
    and stock category(non masterdata).
    When I checked the fact table of the same cube I could see that the DIM ID for A is maintained as 0 for all values.
    In this case how does the DIM IDs get linked to the fact table.
    Please explain.
    Thanks.
    Ramesh

    Hello Ramesh
    DIM ids are combination of SIDs.  Please check whether those two InfoObject have "Attribute Only" option checked in InfoObject maintenance.
    If that is the case , then there will be no SID table generated for these two InfoObjects and if no SID is there, there can not be any DIM id.
    But I was wondering why this if these are Attribute Only then why did system allow you to add them in dimension.
    Another possibility, you did not get any data for these two field in this cube , so it did not check SIDs and generated DIM ids.
    Do you have value for these two fields in the cube?
    Regards
    Anindya

  • Repository Subject Area with mutiple Facts that share a dimension

    Hi,
    I have repository model that has 2 fact tables that share a dimension. I'm trying to pull information from both fact tables and this dimension but get this error:
    Error Code :OPR4ONWY:U9IM8TAC:OI2DL65P
    None of the fact tables are compatible with the query request Club Products.Product Price. (HY000)
    Thanks and Regards

    It stands for Logical Table Source (LTS). See OBI Server Administration Guide manual.

  • Historical Reporting With Multiple Subject Areas

    Hi All,
    I am working on to decide the best way to create repository. I do have a requirement from my client that they need to see both Current and Historical Reporting via OBIEE. I am keeping Type 2 SCD. My model consists of about 30 fact tables - each of them represents a business process/event.
    Following are my options:
    1) One Subejct Area to keep current/historical reporting. Here the joins would be based on PK/FK relationships with Effective Start and Effective End dates. There is a flag in all tables to find the most updated record. Users can use the flag to find the most updated record or use Effective Start and Effective End dates to go point in time.
    2) Create two Subject Areas - Current and Historical reporting. Current one will include the flag logic to get the most updated record in RPD
    3) Create multiple Subject Areas for each Fact table and use Combining Multiple Subject Area approach to join Subject Areas. Additionally, create one Subject Area for Historical Reporting (that will have all the tables in one SA)
    I am thinking of going ahead with option 3) This will have Subject Areas for all logical facts (for Current reporting) and one Subject Area for Historical reporting.
    Is this a standard design? Any inputs?

    You should try both Complex folders as well as custom folders and see which gives you better performance. Discoverer SQL optimizations for example apply only on Complex folders and not on simple folders.
    If you define the joins between the two tables, you can still use items from them in your Discoverer report without having to create a complex folder on them.
    And finally, you can always create a view or materialized view and use that MV in your Discoverer query.
    thanks
    Abhinav
    Oracle Business Intelligence Product Management
    BI - http://www.oracle.com/bi
    BI - http://www.oracle.com/technology/bi
    Blog - http://blogs.oracle.com/
    BI Blog - http://oraclebi.blogspot.com/

  • Two fact tables in one business area

    Hi,
    Would there be problem if two fact tables, one flat, one with hierarchy, in one business area. Both fact tables are joined to same set of dimension tables except one: region_1 to fact_1, region_2 to fact_2. The consistency check is fine. But I get error in Answers. I don't have the exact error with me, but it is complains about fact_1 is not linked region_2.
    Any suggestions ?
    Thanks.

    Thank you, Stijn, Ced for your kind reply.
    I did not explain it clearly.
    The fact_1 (flat) table has data in all levels (detailed and aggregated). For example, it has % sales to planned from city, state to national (we were not provided with numberator and demoninator to aggregate the detailed data). The fact_2 table has only city level data and have a dimension region_2 with city, state and national hierarchy. For data in Fact_1 table, we simply want to show them in reports. For data in Fact_2 table, reports can drill-down.
    In Answers, the error is "Incorrectly defined logical table source ( for fact table Fact_1) does not contain mapping for region_2.state_id".

  • SIDs are written in a Fact Table?

    Hi,
    Some experts told me that SIDs are written in a fact table in extended star schema model . I am not able to understand how SIDs can be written in a fact table. As per my understing fact table contains only keyfigure and Dimids ( foreign key).
    Please explain.
    Thanks.
    Asim

    Hello!
    Basically you are right. Fact table holds only DIM-ID's and key figures. But if you set a dimension to line item (line item flag in cube definition) than no dimension table is created and SID is written directly into the fact table. Therefore a line item dimension can hold only one characteristic.
    Hope that helps.
    kind regards,
    Peter

  • Doc listing all OBIA RPD Projects and related Subject areas and Presentation tables.

    Hi All,
    Can anyone help with the Oracle document ID which gives the RPD Projects and related Subject areas only and Presentation tables.
    I tried using the documentation utlity but it is unable to give me result according to the RPD Projects.
    Thanks,
    Dev

    It is combination of different activities:
    Product guide, check here cool-bi.com
    RPD documentation based on prod guide.
    There might be a project called Project and try to import rpd contents into another then generate rpd doc.
    if helps mark

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

  • Large Fact Tables

    I have some transactional tables that are quite large. Anywhere from 1 to 3 million records. I have been doing my best to find information on the best way to deal with these and I am having some trouble. I am a little tight for time and could use a little help from others who have dealt with large datas sets before. What are some of the best ways to deal with this.
    I have tried creating database level partitions by date which didn't seem to affect the OBI performance much. If I actually create different physical tables through the ETL process for each year it helps but I would like to avoid needing to create and manage that many different mappings.
    Is the best way to do this to use the OBI caching and seed the cache after loading the data? I have even tried a few indexes and not had much luck.
    Any help is greatly appreciated and I thank everyone in advance for their time. :)

    Presuming Oracle backend database.....(you didnt say)
    Partitioning would seem a quick (and expensive $$$$) win, if you partition on date, be sure to use the same date key to perform 'partition pruning' , which is to say give the optimizer a chance to throw away all unrequired partitions before it starts going to disk. When you say 'didnt improve performance much' you need to give a partition wise join for the partitioning to become effective at query time - did you do this ? for example a dashboard prompt with a filter on week / month would help (assuming your week / month time dim column is joined on partition key)
    Is your data model a star schema ? Do you have dimension metadata in your database ? I'd be looking at Materialized views and looking for some sort of aggregate rollup query re-write whereby you queries are re-written at run time to the Mview and does not hit your fact table.
    As for caching, OBIEE caching is the last resort after you exhaust every other alternative, its not there to speed up queries and you would be hiding the problem, what when a user drills down or needs to run an ad-hoc report that is not cached ?
    I would start with understanding Oracle execution plans, review your data model (with the view on speedy data extraction) and look at what Oracle DB gives for data warehousing appliances :
    parallelism is your friend!
    star transformation,
    Mviews (table or Cube based)
    OLAP

  • Relationship between Dimension without linking Fact table

    Hi,
    My question is like I have five dimensions connected to a fact table through primary - foreign key(Composite Key) relationship. Will this referential integrity help if I want some information between two dimension which are not linked directly and I am not
    including any measures from fact table .
    Example: Suppose I have customer, Product and Manufacturer Dimensions all linked to a fact table but  not linked to each other directly  but can I get right result when I want to know what are the manufacturer for each product? or list of
    customers using a particular product. Will the referential integrity work ? since they all are related in fact table.
    regards
    Sanjoy ghosh 

    Hi Sanjoy -
    The answer to your questions depends on your dimensional design and exactly what the fact table represents.  Fact tables naturally capture the intersection of the different dimensions.  This is true whether you physically implement a
    PK - FK relationship in the relational db.  
    In your case, since customer is involved, sounds like a sales transaction fact.  If that's true, you can easily join from customer, through the fact, to the product dimension, to get the list of customers that purchased a particular product.
    For the manufacturer for each product, a sales transaction fact will not necessarily answer this question completely.  Particularly in the case of products that have no sales for a given period, and thus, don't have any fact records to join from manufacturer
    across to product.  If you need to solve this question, you have some other options:
    - flatten the Manufacturer directly into the Product dimension as attribute of the product (probably the simplest approach and allows you to remove a key from the fact)
    - embed the Manufacturer key directly in the Product dimension (if you need the Manufacturer dimension separate for use with other events / facts and more detailed dimensionality - i.e., detailed attributes about the Manufacturer that wouldn't need
    to be flattened onto the product)
    - build a factless fact that captures the products offered by a given manufacturer at a given point in time (perhaps representing various products catalogs and associated dates.  This would allow you to capture rich details about each dimension separately
    and use the factless fact to record)
    Let me know if that helps.
    Brent Greenwood, MS, MCITP, CBIP
    // Please mark correct answers and helpful posts //
    http://brentgreenwood.blogspot.com

  • Result set from two fact tables

    Hi,
    I have two fact tables, fact1, fact2. These two fact tables share common dimension dimension1.
    In RPD I joined dimension1 to fact1, fact2.
    In Answers I pulled the columns from fact1, fact2 and dimension1, I am getting ODBC Error, no fact table exists at the requested level..
    When I pull the columns from fact1, dimension1 i am getting result.
    When I pull the columns from fact2, dimension1 i am getting result.
    Please suggest me how to resolve this.
    Thanks & regards,
    SR

    Whether Fact1 and Fact2 are 2 sperate Logical Fact Tables or part of same logical fact tables.
    If they are separate logical fact tables then check for the Properties of Logical Table Source - Content Tab and set aggregation level for Dimension 1 hierarchy for respective facts.
    Thanks!
    Exa-BI

  • How to update a fact table when a dimension table is reloaded

    We have implemented BI Apps 796. Insertion into W_EMPLOYEE_D table which stores all the employee information had stopped one year back as some company security policy restricted the informatica worklfows to pick up the data. (PER_ALL_PEOPLE_F was a HRMS table and it contained sensitive information line SSN and salary, was inaccessible to the user which informatica uses and the SDE mapping used to return 0 rows).
    Now we have the approval to see those rows and the dimension table is loaded with some 100 new employees who joined in last one year.
    The ROW_WID of W_EMPLOYEE_D is referenced in lot of fact tables and for all those missing employees the WID in the fact table is 0.
    Now that we have all employees, how to make the FACT table point to the correct WID and not store 0. Has anyone faced this problem before?? Writing an update statement will be a tedious task as there are so many fact tables that join to w_employee_d. Also our company uses Sales, Procurement, Finance modules of OB Apps (which constitutes atleast 20 fact tables)
    Any guidance is appreciated. Thanks in advance

    Hello Kostis,
    thank you for your answer. I don't fully understand you. Can you show me short example, please? I create alias table for time dimension on Physical Layer - original table is TimeDayDim and I create aliases TimeDayDim1, TimeDayDim2, TimeDayDim3, TimeDayDim4. Then I create foreign key Fact.Time1 -> TimeDayDim1, Fact.Time2 -> TimeDayDim2, Fact.Time3 -> TimeDayDim3, Fact.Time4 -> TimeDayDim4. And what now? Must I create these table api Bussines Model and create new time dimensions at bussiness model????
    I need in Answers ONE Time dimension. I think I must split my fact table to four tables ... (time1, place1 ...) (time2, place2 ...) (time3 place3...) (time4 place4...) then link those tables to Time dimension (but I dont know where I can split those tables - on Physical Layer or on Bussines Layer).
    I suppose that I will have in Answers one time dimension and four facts tables and I will be able to query them. (for example: Time.Days, Fact1.Place1, Fact3.Speed, Fact4.Count Criteria: Time.Year = 2008)
    Best Regards Vlada

Maybe you are looking for