Define granularity of the fact table

Hi BW experts,
Can you explain defining granularity of the fact table when doing data warehousing?
Thanks,
Bill

Data Modeling issue: want example of Define granularity of the fact table
http://help.sap.com/bp_biv335/BI_EN/documentation/Multi-dimensional_modeling_EN.doc

Similar Messages

Mapping the Fact table to different levels of a dimension

Hi,
I have a fact table which stores the data for 4 levels of the dimensions. The aggregation method was taken care by PL/SQL and the fact table will have the data for all the 4 levels. When im trying to map all the levels to a column in the fact table using the OEM, it is generating the F KEY constraints referncing the columns mapped for the various levels of the dimension.
The problem is that im using a denormalised table for maintaing the values of the dimension. So the columns mapped for the levels(Except for the lowest) can't have the unique key defined on it. The cube is not getting created because of the error in creating the F KEY.
Can u please suggest how to map this fact table.
Thnks,
Manohar Vanama

I am not exactly clear on your schema but I believe you are trying to map tables which are not strict star or snowflake. This means that you cannot use CWM1 (and OEM), unless you change the structure of the tables. You might be able to map the tables with CWM2. The document below will assist you:
Oracle9i OLAP User's Guide
Chapter 4. Designing Your Database for OLAP
Chapter 5. Creating OLAP Catalog Metadata

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

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

Display master data without data in the fact table

Characteristic 0PROJECT
Attribute Price
I want to show in the query all the prices including the projects that don't have registers in the fact table.
How do I do this?
Tnks.

I believe you are describing what SAP referes to as the Slow Moving Item scenario. Search SDN using that phrase and you'll get hits on documents and Notes that talk more about this. Here's something from an old How To
Slow Moving Item Scenario
You want to define a query that displays all products that have been purchased only
infrequently or not at all. In other words, the query is also display characteristic values for
which no transaction data or only low values exist for the selected period.
Procedure
In the Administrator Workbench;
1. Create a MultiProvider consisting of a revenue InfoCube, containing the InfoObject
Material (0MATERIAL), and the InfoObject 0MATERIAL. The InfoObject must be set as
an InfoProvider in InfoObject maintenance. In other words, you need to have assigned
the InfoObject to an InfoArea. (also refer to Tab Page: Master Data/texts [Ext.]).
In the BEx Analyzer:
2. Select your MultiProvider in the Query Designer.
3. Define a query that contains the InfoObject 1ROWCOUNT in the columns.
The InfoObject 1ROWCOUNT is contained in all flat InfoProviders, that is, in all
InfoObjects and ODS objects. It counts the number of records in the InfoProvider.
In this scenario, you can see from the row number display whether or nor values
from the InfoProvider InfoObject are really displayed.
4. Save the query and execute it. All values are now displayed, including those for materials
that were not purchased.
If you filter by time (0CALYEAR, for example), values from the InfoProvider
InfoObjects are not displayed since 0CALYEAR is not an attribute of
0MATERIAL. You can see this from the absence of values in the 1ROWCOUNT
column in the query. If you want to restrict by time, you need to proceed as
follows:
Constant Selection for the InfoObject
You need to set the constant selection for the 1ROWCOUNT key figure in order to be able to
set a filter by time in this query.
1. In the Query Designer, via the context menu for 1ROWCOUNT, choose Edit.
2. On the left hand half of the screen, under the data package dimension, select the
characteristic InfoProvider (0INFOPROV) and drag it into the right-hand screen area.
3. From the context menu for the InfoProvider, choose Restrict, and restrict across the
InfoProvider InfoObject.
4. Also from the context menu for the InfoProvider, choose the function Constant Selection.
5. Save the query and execute it. You can now also set a filter for a time characteristic, the
materials display remains as it was.
Displaying Slow Moving Items
SAP Online Help 05.11.02
MultiProviders 3.0B, Support Package 07 10
If you want to display a list of slow moving items, excluding products that are selling well, you
need to proceed as follows:
1. In the Query Designer, via the context menu for 1ROWCOUNT, choose Edit.
2. Via the context menu for InfoProvider, choose the function Display Empty Values. Also
select Constant Selection.
3. Save the query and execute it. The result is that the system displays the materials for
which there was no revenue.
Displaying Products with Small Revenues
If you want to display a list of products that have not been sold or have only been selling
badly, you need to proceed as follows:
1. Set constant selection as described above, but do not select the display empty values
function.
2. In the Query Designer, define a condition for the 0MATERIAL InfoObject. Specify a value
that is to be the upper limit for a bad sale.
3. Save the query and execute it. The result is that the system displays all materials that
have not been sold or have been selling badly.

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

Transaction data can be loaded into the Fact table without loading the

Transaction data can be loaded into the Fact table without loading the corresponding master data (Example : Sales analysis transaction data can be loaded without populating any of its dimensions master data)
a. True
b. False

Hi Kutti,
True - You need to select the option in the infopackage - alwyas load even if no master data exists.
Bye
Dinesh

Error for the fact table while processing the cube - attribute key cannot be found when processing

Please help as I am new to SSAS and this is urgent requirement. This is a MOLAP cube and below is the error that I am receiving when processing the cube. The cube is set to Prrocess Full. Several similar errors are popped up for various dimensions.
"Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'Fact_Table', Column: 'ID', Value: '1'. The attribute is 'Id'. Errors in the OLAP storage engine: The attribute key was converted to an unknown member because
the attribute key was not found. Attribute Id of Dimension: 17 - Ves - PoC Cont from Database: DB, Cube: IPNCube, Measure Group: iSrvy, Partition: Partition1, Record: 1."
Thanks in advance.

Thanks for the recommendations David.
It will be really great if you can clear some of my doubts:
To my information, all the dimensions need to be processed first and then the fact table will be processed.
So if the ID's are not present in the dimension tables, then it should not be present in the Fact table either.
Here we found null values in the dimension table and the ID's were present in the Fact table. What might be the reasons causing such situation?
Also how frequently the cube needs to be processed? Currently the ETL which processes the cube, is scheduled in a SQL Job Agent on hourly basis everyday.
Is there any possibilty that the cube might be under processing state and the SQL job for the next run getting executed trying to access and process the cube while it was still processing?

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

How to skip the fact table /BI0/9AEDFC01 error while import phase in Heterogeneous migration

Hi.
Please find the below issue of the fact table while import phase in OS/DB migration and enclosed the below log for reference.
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: START OF LOG: 20140924185259
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:06:03
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 14248
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: job completed
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140924185259
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: START OF LOG: 20140924185259
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:06:03
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 14265
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(GSI) INFO: dbname = "AQ220140924040917                                                                                                              "
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "VA1WIPRSCM03                                                    "
(GSI) INFO: sysname = "Linux"
(GSI) INFO: nodename = "VA1WIPRSCM03"
(GSI) INFO: release = "2.6.32-358.el6.x86_64"
(GSI) INFO: version = "#1 SMP Tue Jan 29 11:47:41 EST 2013"
(GSI) INFO: machine = "x86_64"
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: found /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: Trying to open /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST opened
(SQL) INFO: Searching for SQL file DFACT.SQL
(SQL) INFO: DFACT.SQL not found
(SQL) INFO: Searching for SQL file /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: found /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: Trying to open /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL opened
(SQL) ERROR: Invalid entry at line 5 in file /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) ERROR: SQL list was not built successfully
(DDL) ERROR: check_sql_list() failed for /BI0/9AEDFC01
(DB) INFO: disconnected from DB
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: job finished with 1 error(s)
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140924185259
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: START OF LOG: 20140925104442
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:06:03
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 23939
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(GSI) INFO: dbname = "AQ220140924040917                                                                                                              "
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "VA1WIPRSCM03                                                    "
(GSI) INFO: sysname = "Linux"
(GSI) INFO: nodename = "VA1WIPRSCM03"
(GSI) INFO: release = "2.6.32-358.el6.x86_64"
(GSI) INFO: version = "#1 SMP Tue Jan 29 11:47:41 EST 2013"
(GSI) INFO: machine = "x86_64"
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: found /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: Trying to open /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST opened
(SQL) INFO: Searching for SQL file DFACT.SQL
(SQL) INFO: DFACT.SQL not found
(SQL) INFO: Searching for SQL file /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: found /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: Trying to open /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL opened
(SQL) ERROR: Invalid entry at line 5 in file /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) ERROR: SQL list was not built successfully
(DDL) ERROR: check_sql_list() failed for /BI0/9AEDFC01
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(SQL) ERROR: SQL list was not built successfully
(DDL) ERROR: check_sql_list() failed for /BI0/9AEDFC01
(DB) INFO: disconnected from DB
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: job finished with 1 error(s)
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140925104442
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: START OF LOG: 20140925124401
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:06:03
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 25323
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(GSI) INFO: dbname = "AQ220140924040917                                                                                                              "
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "VA1WIPRSCM03                                                    "
(GSI) INFO: sysname = "Linux"
(GSI) INFO: nodename = "VA1WIPRSCM03"
(GSI) INFO: release = "2.6.32-358.el6.x86_64"
(GSI) INFO: version = "#1 SMP Tue Jan 29 11:47:41 EST 2013"
(GSI) INFO: machine = "x86_64"
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: found /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: Trying to open /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST
(SQL) INFO: /data1/SCMEXPORT/EXPAQ2/ABAP/DB/SQLFiles.LST opened
(SQL) INFO: Searching for SQL file DFACT.SQL
(SQL) INFO: DFACT.SQL not found
(SQL) INFO: Searching for SQL file /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: found /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: Trying to open /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL
(SQL) INFO: /data1/SCMEXPORT/EXPAQ2/ABAP/DB/ORA/DFACT.SQL opened
------------------ C-STACK ----------------------
R3load[S](LinStackBacktrace+0x8c)[0x48d167]
R3load[S](LinStack+0x35)[0x6ca6c5]
R3load[S](CTrcStack2+0x48)[0x48fba1]
R3load[S](SigIGenAction+0x212)[0x58b4fb]
libpthread.so.0[T][0x397680f710]
R3load[S](check_sql_list+0xab0)[0x61bbb0]
R3load[S](DBDrop+0xbb)[0x60a8fb]
R3load[S](import+0xde6)[0x620986]
R3load[S](main_r3ldmain+0x1cfc)[0x6073bc]
libc.so.6[T](__libc_start_main+0xfd)[0x397601ed5d]
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: START OF LOG: 20140925125540
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:06:03
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 25932
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: job completed
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140925125540
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: START OF LOG: 20140925125540
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:06:03
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 25955
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(GSI) INFO: dbname = "AQ220140924040917                                                                                                              "
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "VA1WIPRSCM03                                                    "
(GSI) INFO: sysname = "Linux"
(GSI) INFO: nodename = "VA1WIPRSCM03"
(GSI) INFO: release = "2.6.32-358.el6.x86_64"
(GSI) INFO: version = "#1 SMP Tue Jan 29 11:47:41 EST 2013"
(GSI) INFO: machine = "x86_64"
(TSK) ERROR: file /tmp/sapinst_instdir/BS2013SR1/SCM703SR1/ORA/COPY/SYSTEM/STD/AS-ABAP/SAPDFACT_1.TSK.bck already seems to exist
            a previous run may not have been finished cleanly
            file /tmp/sapinst_instdir/BS2013SR1/SCM703SR1/ORA/COPY/SYSTEM/STD/AS-ABAP/SAPDFACT_1.TSK possibly corrupted
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: job finished with 1 error(s)
/usr/sap/AQ2/SYS/exe/uc/linuxx86_64/R3load: END OF LOG: 20140925125540

Dear Ram Nath,
It may be late but it will be use full to others.
I faced similar issue and solved it by commenting the 5th line of DFACT.SQL file.
The issue was with the indexes not being generated properly to avoid such issues we must ensure to implement SAP note 1991576 in prior, if not we can comment the 5th line.
Below is the corrected file in my case
# ORACLE : NATIVE SQL EXPORT GENERATED AT 20150426083248
#ind: - commented line (earlier it was just 'ind: ')
ind: /BI0/E0PPM_VC1~0
tab: /BI0/F0PPM_VC1
Please let me know in case of queries if any.
Regards
Baranedharan S.

How map to my particular table to the fact table in obiee 11g...

Hi friends,
I did this simple report in obiee 11g(i.e)
"NATIONALITY COUNT IN DEPARTMENT WISE"
For that i used the following tables:
per_all_assignments_f----->fact table
hr_all_organization_units----->dim table(containing departments)
per_all_people_f---------------->dim table(containing nationality)
I made all the mappings in the physical diagram, as also viewed my report in BI answers
It shows the following results like
NATIONALITY---------------------------------------------------------------------COUNT(NATIONALITY)
AUS------------------------------------------------------------------------------------------------24
AFR------------------------------------------------------------------------------------------------25
PHQ_VB-------------------------------------------------------------------------------------------40
SH_VT----------------------------------------------------------------------------------------------4
The problem is for me it is showing the above results, but the nationality column is of various codes of the country.
Since i doesnt want the code of the nationalitian to display in the results..i need the meaning of each and every nationality..
like,
AUS------------------------Australian
AFR-------------------------African
PHQ_VB----------------------Germanian(assigned)
Since i know that the meaning for the nationalitian is available in "FND_LOOKUP_VALUES"...okay..
I can import "FND_LOOKUP_VALUES" table to the physical layer...but how i can able to give the mapping to the fact table in my physical diagram...
In my report the fact table is "per_all_assignments_f"
As my fact table doesnt contains any matching column corresponding to the dimension table "FND_LOOKUP_VALUES".....
Then how i can give mappings to the fact column???? for viewing the full meaning of the nationalitian in my report.....Help me friends...
Regards,
Harry...

Hi bifact,
I followed the step that U asked me to go but im stuck with later.....
*) I saved the query that i executed in toad with the columns showing country codes and country meaning to the excel sheet...
This is the query that i executed in toad and copied data s in excel sheet..
select z.lookup_code, z.meaning
from per_all_people_f e, per_all_assignments_f f, hr_all_organization_units h, fnd_lookup_values z where
e.person_id = f.person_id and f.organization_id = h.organization_id and e.business_group_id = f.business_group_id
and f.business_group_id = h.business_group_id and f.location_id = h.location_id
AND z.lookup_type(+) = 'NATIONALITY'AND z.lookup_code(+) = e.nationality and sysdate between
e.effective_start_date and e.effective_end_date and e.nationality is not null
*) After that i created a system DSN for the excel drive..
*) After that when i tried to import metadata of the excel data that is saved, it showed me connection failed...
For importing this excel data
what connection details i need to give:--------------------
as well as user name and also password...
Soon after importing this excel you said that to give key connection only to fnd_lookup_tables(dim) and that excel data..
if so, again im not giving key connection to my fact table..
I think again the same error will occur that no logical mapping is not made to fact so again repository is inconsistent...
Hi bifact sorry to ask you, but can you see the steps that i followed is correct and after that wat more steps i need to proceed..Can you tell me in breif manner...Thanks for your help...
Regards,
Harry...

What is the fact table content?

a. Key figure for a combination of char value of dimensions are stored in the fact table
b. Both cumulatiove and also key figure for non cumulative values can be contained in fact table
Choose any one
Thanks
Babu

Hi,
Fact table contains the data (key figs) for a certain combination of characteristic values of the dimension tbls to help a business person evaluate their company & make appropriate decisions.
=> a. from the choice you had.
Rgds,
Colum
Was this information helpful to you Babu?
If so, please award points as appropriate.
thanks
Edited by: Colum Cronin on Apr 7, 2010 10:11 AM

Record count is more in the Fact tables when compared to Cube data!

When i delete request from my cube it is not getting deleted from the fact table. Cube shows around 3.5 million records but when I checked in the fact table it was showing more than 11 million records.

Hi Kingsley,
   You may try this approach.
   1. Use TCode listschema
   2. Select the type of cube abd give the cube name as well.
   3. This will display the table sinvolved in the cube(star schema).
   4. Select the Ftable listed there and see the number of rows in it.
   Inorder to delete the entire data from cube, you may need to delete all the load requests that has happened before as well.
   Hope this helps...
Thanks,
Raj

Define granularity of the fact table

Similar Messages

Maybe you are looking for