Datasrc dimension

Hi friends,
Can anybody eloborate usage of dimension 'Datasrc'. Is it supports only 3 values(manual,dataainput,total adjustment)?
where exactly we use this and where it is mandatory?
Raju

Hi RAJU K ,
The main use the DataSrc dimension is to segregate the data and to make a trail of data that enters your system. You can have many data sources but you must define each data source type with the 3 values you mentioned above. Data input type(I) are used to store uploaded data usually coming from flat files or trial balances that is uploaded to the system. It may also be used to stored data being inputted in input templates. Manual Adjustments(M) are usually used for adjusting journal entries or any adjustments maid to the data inputs after uploading. On the other hand, Adjustments(A) are used to store data generated by the automatic adjustments business rules.
Hope this helps,
MVS

Similar Messages

OutlookSoft 4.2 SP3: Copy Package on DataSrc dimension

Greetings,
I'm trying to use Copy package to copy previous month's balances for balance sheet accounts into a open balance member of data source dimension. My data source dimension has following members: Total adjustments has two children: input and opening balance.
I am not able to copy total adjustments ( calculated member) into next months opening balance member. I can only copy non calculated data source members. Is there a workaround?
Thanks,
Roman

Here's what i found in Logic help for the CALC_EACH_PERIOD instruction.
Example:
*CALC_EACH_PERIOD
*WHEN ACCOUNT
*IS OPEN_BALANCE, MOVEMENTS
*REC(ACCOUNT=CLOSING_BALANCE)
*REC(ACCOUNT=OPEN_BALANCE,TIME=NEXT)
*ENDWHEN
The above sample logic performs a carry-forward of the closing balance of each period into the opening balance of next period.
I think this is exactly what I need. Is the sample above assumes separate open balance and closing balance account for each GL account? For example, GL account Cash has two children: Cash_open and Cash_closing.

BPC Conversion File - Same External ID for different Dimensions

Hello Experts,
I hope you can help me.
We are running BPC NW V10.0 SP13
I have a Conversion File for External to Internal Mapping on the DATASRC Dimension.
See Image 01
I would now like to use the same 'External ID' to identify the mapping rules for two Dimensions, DATASRC and CATEGORY Member ID
See Image 02
The rules that determine how the External ID is mapped are subjective rather than derived from patterns present in ID. This means I cannot use any conditional logic to determine the mapping rules. For example, I cannot assume that all IDs that start with 99Z19 will need to be mapped the same way.
So the CATGORY Member ID needs to be hard-coded somehow.
Although it is simple enough to copy the entire worksheet and hold the mapping for each Dimension as separate w/sheets, this duplicates the amount of ongoing maintenance and turns 80 rules into 160 (a number which will rise!)
Is there a way of using javascript in the Formula column to identify the Internal Member ID for the CATEGORY Dimension.
If so, how would the Transformation File reference this?
Any help would be much appreciated

Sorry Vadim, I was having problems uploading the actual files.
So I have had to screenshot instead...............
Transformation File
Conversion File
As you can see, the Trans file assumes the CATEGORY is fixed to one Member.
But I want to use the External ID in the the DATASRC Conversion w/sheet and specify different CATEGORY Member IDs.

*ERROR* FX-180 No Datasrc to be converted

Hi all
I am using the currency conversion rules tables.
The following script is being used to call the stored procedure as per the help file.
*RUN_STORED_PROCEDURE=SPRUNCONVERSION(%APP%,%CATEGORY_SET%,'','GLOBAL',%SCOPETABLE%,%LOGTABLE%)
*COMMIT
The following error message is produced:
SPRunConversion Version 7.0.115
ERROR FX-180 No Datasrc to be converted
Regards,
Byron

Hi Byron,
Please check if you have maintained "IS_CONVERTED" property in DATASRC dimension. This has values "Y" or "N". Set it to "Y" for the DATASRC that you want to translate in currency conversion.
Hope this helps.
Regards,
Shoba

Dimension formula error

Hello all,
I have created the following dimension formula in dimension Groups(Currency):
'IIF([DataSrcDim].H1.CurrentMember is [DataSrcDim].H1.[20_ELIM], [GROUPS].MemberX-[GROUPS].MemberY-[GROUPS].MemberZ-[GROUPS].MemberW,NULL),SOLVE_ORDER=50
In short the objective of this formula is to perform a calculation (X-Y-Z-W) on GROUPS dimension members if the DATASRC dimension member is 20_ELIM.
However, I get the following error when I process the GROUPS dimension:
-"[GROUPS].[#ABCD] The dimension '[DATASRCDIM]' was not found in the cube when the string, [DATASRCDIM].[H1], was parsed"
I get this error even though the DATASRC dimension exists in th cube/application.
Would any of you have an idea why this error occurs and if so how can I correct it?
Thank you & regards
Raja

Hi,
Please try the formula as:
IIF([DATASRC].CurrentMember = "20_ELIM", [GROUPS].[MemberX]-[GROUPS].[MemberY]-[GROUPS].[MemberZ]-[GROUPS].[MemberW],NULL);SOLVE_ORDER=50
Hope this helps.

How to group datasrc member in CarryForward Business Rule

Hi Experts,
I want to group few datasrc members to be used as source datasrc in CarryForward Business Rule. Which property of Datasrc Dimension will show the grouping in CarryForward rules ?
For your information - i have DIMLIST, DIMLIST1, COPYOPENING, DATASRC_TYPE, OPENING_DATASRC with some values but none of these properties getting enabled in CARRYFORWARD Business Rule.
Kindly help
Regards,
Samvir

Hi,
You need to define this in the Group property of the Datasource dimension.
The GROUP :It is used to gather datasrc in six groups: example:
INPUT          Input datasrc
STA          Standardization datasrc
ELI          Eliminations datasrc
C          Consolidation datasrc
ICMATCH     Intercompany matching datsrc
IC          Intercompany datasrc
I think, for carry forward , you need not assign this in the group above. in the business rules of carryforward, need assign like this.
Source Account   Source Flow    Destination Account   Destination Flow Datasource Type
BSDIM                     999                                                       100                     ALL
Regards
CSM Reddy

Limit stored procedure (spruncalcaccount) to run on specific datasrcs

We are using the stored procedure spruncalcaccount to accumulate the P&L and then post the total to the Balance sheet. We then add up the Balance sheet and post an Out of Balance value if the BS is not zero.
This works perfectly but it takes a very long time to run. Further, it seems to apply the out of balance logic to all the datasources processed through spicdata IC_Match, Debit1, Debit2, Credit1, Credit2 members).
We therefore want to limit our posting by data sources.
We do not want to use an account property for the rollup. We also do not want to use rolltobs.
Is anyone aware of code that we can use to speed up the process? Any assistance would be much appreciated.

Hello,
   Did you try to use the instruction *XDIM_MAXMEMBERS ? You can add this for DataSrc dimension for example. This will create small queries which can run faster.
   You can have a look to the logic log files to see from where the big time is comming from. If you have big queries which take a lot of time, the *XDIM_MAXMEMBERS vvan help you.
Try something like
*XDIM_MAXMEMBERS DataSrc=2     to see if something is changing.
Regards,
Mihaela

Legal Consol: Received CSD Errors when running SPRUNCONSO

Hi All,
I configured Legal Consol application under BPC 7.0 MS and I've below error message when running SPRUNCONSO:
Warning : Nothing Extract From Ownership for OPENING Period
ERROR CSD-130 Problem Extracting data from the Fact
ERROR CSD-135 Problem Extracting data : C_FINANCE
ERROR CSD-140 Problem extracting Data : C_DATA
ERROR CSD-150 Problem extracting Data : C_REPART
ERROR CSD-160 Problem extracting Data : C_CONSO
20091200 - 0 Rows Calculated
20091200 - 0 Rows Updated
Below are my configuration steps:
1. Account Dimension:
    - Populate TYPELIM Property for account related to interco elimination.
2. Datasrc Dimension:
    - Populate IS_CONSOL Property (value = Y) for source DataSrc (INPUT)
    - Populate DATASRC_TYPE Property (value = A) for destination DataSrc (AJ_ELIM)
3. Entity Dimension:
    Property ELIM = Y for entity related to elimination
4. Groups Dimension:
    Currency_Type = G for Elimination Group
4. Business Rule:
    - Automatic Adjustment:
       Adjustment ID = ELIM01
       Source Data Source = INPUT
       Destination Data Source = AJ_ELIM
       Adjustment Type = Generic
      Adjustment Level = 0
    - Automatic Adjustment Detail:
       Adjustment ID = ELIM01
       Source Account = IC_APAR
       Destination "ALL" Account = IC_APAR (same value under TYPELIM Property for account dimension member)
       Destination Group Account = IC_APAR_CL (same value under TYPELIM Property for account dimension member)
       RuleID = RULE040
4: Business Rule Library:
    - Consolidation Rules:
       RuleID = Rule040
       Rule Type = ALL
    - Consolidation Method: 100
    - Consolidation Rules Formula:
      RuleID: RULE040
      EntityMethod: 100
      IntcoMethod: 100
      "All" Formula: 1
      Group Formula: 1
5. Set Ownership data for 2008.Dec until 2009.Dec (data existed in tblfactownership)
6. Set Foreign Exchange Rate from 2008.Dec until 2009.Dec
7. Stored Procedure:
    *RUN_STORED_PROCEDURE = SPRUNCONVERSION([%APP%], [%CATEGORY_SET%], [], [%GLOBAL], [%SCOPETABLE%], [%LOGTABLE%])
    *RUN_STORED_PROCEDURE = SPRUNCONSO([%APP%], [%CATEGORY_SET%], [%SCOPETABLE%], [%LOGTABLE%])
    *COMMIT
I've been trying to crack it but i still received same error message. Can anyone share what i might have missed?
Thanks a lot for the advice,
Liam

Hi,
I think there is a syntax problem in your SPRUNCONSO call. GROUPS_SET variable is missing. The syntax should be like this:
*RUN_STORED_PROCEDURE = SPRUNCONSO([%APP%],[%CATEGORY_SET%],[%GROUPS_SET%],[%SCOPETABLE%],[%LOGTABLE%])
In addition, not sure if it's a typo problem or not, but it seems that your call for the SPRUNCONVERSION is also wrong. Some variables are also missing:
*RUN_STORED_PROCEDURE=SPRUNCONVERSION([%APP%],[%CATEGORY_SET%],[%CURRENCY_SET%],[GLOBAL],[%SCOPETABLE%],[%LOGTABLE%])
Then, for all the error codes, you can get rid of those one using the ON_ERROR_CONTINUE, at the end of the line.
Normally, those kind of error message are generic, and informed the user that there is actually no records that should be the source of the SPRUNCONSO stored procedure.
Hope this will help you.
Kind Regards,
Patrick

Best way to Import Data from a SQL Server Table?

Hi,
Firstly thanks for looking at this question.
We need to import data into SAP BPC 5.1 on a twice daily basis and have chosen not to export to a .CSV file but instead to hold all data in a SQL table and import it directly from there. As part of the import we wish to run the default logic, however only over the data which is imported as opposed to having to running default logic over the entire database after every import.
We did some research on this topic and the only thing we could find that would work as described above is using the "Import SQL" package. However we keep experiencing problems with it and have not yet been able to run it successfully; the errors it gives are not consistent from run to run which makes it difficult to start a thread, though we are getting help from the helpdesk at the moment.
My question here though is - is there another way that someone knows of to import data into SAP BPC from a SQL table, and being able to run default logic over just the data being imported, or is our only hope getting the "Import SQL" package working?
Any help much appreciated.
Regards,
Iain
Forgot to mention details of our environment:
SAP BPC v5.0.495, 2 server environment -
Server 1 (DB/AS/SSIS/File server) = 64bit Windows 2k3 server with 64bit SQL Server Enterprise Edition
Server 2 (IIS/App server) = 32bit Windows 2k3 server
Edited by: Iain Hambleton on Jun 17, 2008 3:25 PM

Lain,
I recently created SSIS packages that need to work with a staging table that does all kind of manipulations of that data before it is loading into SAP BPC, because it also has to load the data in the drillthrough table within the same package. From one point in my package the data is also in a SQL table so basically the same as in your situation. This also works with an export to CSV within the DTSX file like Alwin said, because in this case you can use the standard transformation and conversion stuff during the load.
I also needed to limit the data region for logic to the data region that is in the load for currency conversion purposes. This is not very much of a problem. I had a situation where I have an Accounts receivable cube containing a daily time dimension for keyduedates and a datasrc dimension containing weeks. Every week has a complete overview of the open AR items in that week and need to be converted for that week (datasrc) only and not for the whole database every time we load. But by default data would be converted based on the Keyduedates dimension while I wanted the Week dimension to be used as the data region. I solved it by using these rows in the logic:
*Scope_by=version,Weeks
*xdim_memberset weeks=%weeks_set%
*xdim_memberset version = %version_set%
I can send you the SSIS package and logic if you want. Just send me your details then.
-Joost
Edited by: Joost Hoppenbrouwers on Jun 17, 2008 4:25 PM

Consolidation Error Documentation (CSD)

Hi all,
I have recently ended upon a consolidation engine error (CSD-070, CSD-080). Searching in the forum I have see some threads talking about some documentation about these errors. Could anyone please send that documentation?
About the CSD-070 (No Time available) & CSD-080 (No Group Available) errors, does anybody know what they can be related to?
Kind Regards,
Rafael
Edited by: Rafael Moreno on Oct 2, 2008 2:00 PM

Please find below a list of all errorcodes per stored procedure.
Alwin
MSG     SPRUNCONVERSION
FX-000     ERROR FX-000 Application not Available !
     Appset maintenance in progress
FX-010     ERROR FX-010 Wrong Application, check your logic
     You may have hardcoded a wrong application in your logic.
FX-020     ERROR FX-020 No Currency in your Appset ! You must have a Dimension with dimension type = u2018Ru2019 in your Application. !
     You must have at least one member with CURRENCY_TYPE = R In your currency dimension.
FX-030     Warning : Application without INTCO dimension
     No INTCO Dimension IN your Application.(Dimtype = I)
FX-040     Warning : Application without Flow Dimension
     No FLOW Dimension IN your Application.(Dimtype = S)
FX-050     Warning : Application without Datasrc Dimension
     No DATASRC Dimension IN your Application.(Dimtype = D)
FX-060     ERROR FX-060 No Local currency, You must have a currency with CURRENCY_TYPE Equal to L
     You must have one member with CURRENCY_TYPE = L (Local currency) In your currency dimension.
FX-070     ERROR FX-070 No Entity available in your Application
     You have to select a parameter which is not a parent.
FX-080     ERROR FX-080 No Time available in your Application
     Check if in the TIME Dimension, you have the property "MONTHNUM"
     Check if in the TIME Dimension, you have filled properly the property "MONTHNUM". The first Period of the Fiscal year must be 1, and then the second 2u2026.
FX-090     ERROR FX-090 Problem IN Category Dimension check properties.
     Your parameter CATEGORY is not valid.
FX-100     ERROR FX-100 Problem IN Category OR Ratedim Dimension check properties.
     Your parameter CATEGORY is not valid OR
     You don' t have the Property FX-SOURCE_CATEGORY In your Exchange Rate Dimension (For Simulation) OR
     The Exchange Rate id you chose doesn't exist.
FX-110     ERROR FX-110 Problem IN Category Or Categhory_for_ope check properties.
     Your parameter CATEGORY is not valid OR
     You don' t have the Property CATEGORY_FOR_OPE In your CATEGORY Dimension OR
     You don' t have the Property RATE_CATEGORY In your CATEGORY Dimension OR
     You don' t have the Property FX-DIFFERENCE_ONLY In your CATEGORY Dimension
FX-120     ERROR FX-120 Problem IN Category Or TIME.
FX-130     ERROR FX-130 No Group available.
     Check if the selected group has the property CURRENCY_TYPE = "G".
FX-140     ERROR FX-140 No Currency avalaible
FX-150     ERROR FX-150 Problem IN Ownership
     Check if you have a base member equal to "METHOD" in the account dimension of the OWNERSHIP cube.
     Check If you have valid information in the OWNERSHIP cube for the selected Category Time.
FX-160     ERROR FX-160 No Entity available
FX-170     ERROR FX-170 No Entity Available
FX-180     ERROR FX-180 No Datasrc to be converted
FX-190     ERROR FX-190 No Rate Application
FX-200     ERROR FX-200 No Rate Extract From FactRate
     No Rate found for the selected category and time.
     Check If the Rateentiy you enter in the parameter is the Same as the one in the Rateentity Dimension
     Check If the Rates in the Rate Cube are in the RATE Dimension with Property Ratetype equal to "FX" OR "FX Rate".
FX-210     Warning : No Rates found in the opening period
FX-220     ERROR FX-220 No Rate for reference currency
     Check If you Pivot currency (The base currency to enter the rate, Rate = 1) is filled.
FX-230     ERROR FX-230 Problem in your Entity Dimension id from your Rate application
     The Rateentity (Dimension from the Rate cube with Evdimtype = E) you chose does not exist
FX-240     ERROR FX-240 : No Rate Extract From MbrRate
     No Rate in the RATE Dimension with Property Ratetype equal to "FX" OR "FX Rate".
FX-250     ERROR FX-250 No Rates found
FX-260     ERROR FX-260 No Rate in Fact corresponding with Rate dimension
     Check If the Rates in the Rate Cube are in the RATE Dimension with Property Ratetype equal to "FX" OR "FX Rate".
FX-270     ERROR FX-270 No Formulas extract from FXTRANS
     No Rate formulas in your Fxtrans Table.
     Check if the application name in the Logic.
FX-280     ERROR FX-280 No values found (T_FIN)
     No values found for the selected Entities . Check if you have values in LC for the selected Entities OR
     Check if the LC values are fro DATASRC with Property IS_CONVERTED not equal to "N"
FX-290     ERROR FX-290 No values found (Entity - T_FINANCETMP)
FX-300     ERROR FX-300 No values found (CLCFXTRANS - T_FINANCE)
     No values found from FACT table for Account / Flow. Check if you have values in LC for the selected Account / Flow OR
     Check our Fxtrans Table.
FX-310     ERROR FX-310 No values found (RATE - T_DATA)
     No account extracted have a corresponding Rate_formula in the Fxtrans table.
FX-320     ERROR FX-320 No values found (ENTITY - GROUPS - T_FINAL2)
     Check your Ownership and your group_currency values.
     SPRUNCONSO
CSD-000     ERROR CSD-000 Application not Available !
     Appset maintenance in progress
CSD-010     ERROR CSD-010 No Subtables. Verify properties FLOW_TYPE, IS_INPUT, SEGNOINV, SUBTABLES_ORIG
     No Flow available, check the flow dimension, you must have the property "FLOW_TYPE"
CSD-011     ERROR CSD-011 No instruction retreived from the ELIM table
     No instruction retreived from ELIM Table.
     Check If the Elim id in ELIM table Exist in the ELIMH Table.
     Check if the Account in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACCOUNT Dimension)
CSD-012     ERROR CSD-012 No instruction retreived from the ELIM Table : GROUP_ACC Problem
     No instruction retreived from ELIM Table. GROUP_ACC Problem
     Check if the GROUP_ACC in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACOUNT Dimension)
CSD-013     ERROR CSD-013 No instruction retreived from the ELIM Table : MINO_ACC Problem
     No instruction retreived from ELIM Table. MINO_ACC Problem
     Check if the MINO_ACC in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACOUNT Dimension)
CSD-014     ERROR CSD-014 No instruction retreived from the ELIM Table : EQUITY_ACC Problem
     No instruction retreived from ELIM Table. EQUITY_ACC Problem
     Check if the EQUITY_ACC in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACOUNT Dimension)
CSD-015     ERROR CSD-015 No instruction retreived from the ELIM Table with FLOW Dimension
     Check if the SUBTABLE_ORIG in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST in the FLOW Dimension)
CSD-020     ERROR CSD-020 No Currency in your Appset ! You must have a Dimension with dimension type = u2018Ru2019 in your Application. !
     No Account extracted from CLCELIM Table, please check the Account from CLCELIM.
     Check if the ACCOUNT in the ELIM Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACOUNT Dimension)
CSD-030     ERROR CSD-030 No Entity Available
     No Entity extracted. Check if you have the Property INTCO and the property CURRENCY in your ENTITY Dimension
CSD-040     ERROR CSD-040 No Account
     No Account Extract from Account Dimension
CSD-050     ERROR CSD-050 No datasrc. Verify Properties DATASRC_TYPE,DATASRC_ORIG, IS_CONSOL
     No Datasrc extracted.
     Check if you have the Property "DATASRC_TYPE" and the property "IS_CONSOL" in your DATASRC Dimension
CSD-060     ERROR CSD-060 No Rules
     No rules in your CLCRULES Table
     Make sure the METHOD from the CLCRULES is not blank.
     Make sure the I_METHOD from the CLCRULES is not blank.
CSD-070     ERROR CSD-070 No Time available
     Check if in the TIME Dimension, you have the property "MONTHNUM"
     Check if in the TIME Dimension, you have filled properly the property "MONTHNUM". The first Period of the Fiscal year must be 1, and then the second 2u2026.
CSD-080     ERROR CSD-080 No Group Available
     Check if the selected group has the property CURRENCY_TYPE = "G".
CSD-090     ERROR CSD-090 Nothing Extracted From Ownership
     Check if You have the property "IS_INPUT" in the Account dimension of the OWNESHIP Cube
     Check if You have some base member from the Account dimension of the OWNESHIP Cube with IS_INPUT = "Y"
     Check If you have valid information in the OWNERSHIP cube for the selected Category Time.
CSD-100     Warning : Nothing Extract From Ownership for OPENING Period
     Nothing extracted from Opening period in the Ownership cube.
CSD-110     ERROR CSD-110 No AccountOwn available
     Check if You have the property "IS_INPUT" in the Account dimension of the OWNESHIP Cube
     Check if You have the property "RATETPE" in the Account dimension of the OWNESHIP Cube
     Check if You have some base member from the Account dimension of the OWNESHIP Cube with IS_INPUT = "Y"
CSD-120     ERROR CSD-120 No Entity - Method available
     No data found in OWNERSHIP Cube for this method.
     Check if you have METHOD in your ownership cube for the selected CATEGORY - TIME - GROUP
CSD-125     ERROR CSD-125 No Entity - Method available
     No data found in OWNERSHIP Cube for this method.
     Check if you have METHOD in your ownership cube for the selected CATEGORY - TIME - GROUP
CSD-130     ERROR CSD-130 Problem Extracting data from the Fact Table
     No Values found
     Check if You have Some Account from the ELIM Table.
     Check if You have some DATASRC with IS_CONSOL = "Y"
CSD-135     ERROR CSD-135 Problem Extracting data - C_FINANCE
     No Values found
     Check the Account in the FACT Tables
CSD-140     ERROR CSD-140 Problem Extracting data - C_DATA
     No Values found
     Check the Entity in the FACT Tables
     Check the INTCO in the FACT Tables
CSD-145     ERROR CSD-145 Problem Extracting data - C_DATA_ALL
     No Values found for those Account And/Or Flow.
     Check the DATASRC in the FACT Linked to the DATASRC_ORIG in the ELIMH Table.
CSD-150     ERROR CSD-150 Problem Extracting data - C_REPART
     No Values found for those rules.
     Check the method between METHOD Table and your ownership Cube.
     Check your Rules between the RULES Table and The ELIM Table.
     Check The INTCO.
CSD-160     ERROR CSD-160 Problem Extracting data - C_CONSO
     SPRUNCALC
CALC-000     ERROR CALC-000 Application not Available !
     Appset maintenance in progress
CALC-010     ERROR CALC-010 Nothing Extract from CALCACCOUNT TABLE
     Nothing Extracted from CALCACCOUNT Table, check the account, The account must be a as Base Member or an Agregat or a Value in property DIMLIST or a value from property TYPELIM in the ACOUNT Dimension)
CALC-020     ERROR CALC-020 Nothing Extract from CALCACCOUNT TABLE   (FLOWS)
     Nothing Extracted from CALCACCOUNT Table, check the Subtables, The Subtables must be a as Base Member or an Agregat or a Value in property DIMLIST in the FLOW Dimension)
CALC-030     ERROR CALC-030 NoTime extract.
     Check your TIME Dimension
CALC-040     ERROR CALC-040 NoTime extract for YTD
     Check your TIME Dimension.
     Check if in the TIME Dimension, you have the property "MONTHNUM"
     Check if in the TIME Dimension, you have filled properly the property "MONTHNUM". The first Period of the Fiscal year must be 1, and then the second 2u2026.
CALC-050     ERROR CALC-050 NoEntity extract
     Check your Parameter Entity, it must be an base member (Or a list of base member) from the ENTITY Dimension
CALC-060     ERROR CALC-060 NoEntity extract
     Check your Parameter Currency, it must be a base member (Or a list of base member) from CURRENCY Dimension
CALC-070     ERROR CALC-070 NoEntity extract
     No values found, check if you have something to calculate for the selected CATEGORY - TIME - CURRENCY
     Check your CALCACCOUNT Table.
     Check : The account must be a as Base Member or an Agregat or a Value in property DIMLIST or a value from property TYPELIM in the ACOUNT Dimension)
CALC-080     ERROR CALC-080 NoEntity extract
     No Values found.
     Check your CALCACCOUNT Table.
     Check : The SUBTABLES must be a as Base Member or an Agregat or a Value in property DIMLIST in the FLOW Dimension)
     SPCOPYCATEGORY
CCAT-000     ERROR CCAT-000 Application not Available !
     Appset maintenance in progress
CCAT-010     ERROR CCAT-010 No Time available in your Application
     Check your Parameter "Time".
CCAT-020     ERROR CCAT-020 Nothing extracted from the Account Dimension
     Check the property in the parameter.
     Check that this property is in the ACCOUNT Dimension
CCAT-030     ERROR CCAT-030 No Entities available
     Check your Parameter "Entity".
CCAT-040     ERROR CCAT-040 No Currency available
     Check your Parameter "Currency".
CCAT-050     ERROR CCAT-050 No data found
     No data found, check if you have data for the selected CATEGORY - TIME - CURRENCY
     SPCOPYOPENING
COPYO-000     ERROR COPYO-000 Application not Available !
     Appset maintenance in progress
COPYO-010     ERROR COPYO-010 No Datasrc Available
     Check if you have Datasrc with DATASRC_TYPE different from "A"
     Check if COPYOPENING Property is equal to Y
COPYO-020     ERROR COPYO-020 Nothing extracted from COPYOPENING TABLE
     Check your COPYOPENING TABLE
COPYO-030     ERROR COPYO-030 No Time available
     Check your Parameter "Time".
COPYO-040     ERROR COPYO-040 No category available
     Your parameter CATEGORY is not valid OR
     You don' t have the Property CATEGORY_FOR_OPE In your CATEGORY Dimension OR
     You don' t have the Property OPENING_YEAR In your CATEGORY Dimension OR
     You don' t have the Property OPENING_PERIOD In your CATEGORY Dimension
COPYO-045     ERROR COPYO-045 No category available
     Your parameter CATEGORY is not valid
COPYO-050     ERROR COPYO-050 Problem in COPYOPENING Properties
     Check Opening_year and / Or Opening period properties in CATEGORY Dimension.
COPYO-060     ERROR COPYO-060 No Entities available
     Check your Parameter "Entity".
COPYO-070     ERROR COPYO-070 No Currency available
     Check your Parameter "Currency".
COPYO-080     ERROR COPYO-080 No Account available
     Check your COPYOPENING Table
     Check if the Account in the COPYOPENING Table Exist. (as Base Member or as Agregat or as Value in property DIMLIST or value from property TYPELIM in the ACCOUNT Dimension)
COPYO-090     ERROR COPYO-090 No Data found
     Check if you have data for the selected CATEGORY - TIME - GROUP
     SPRUNVALID
VALID-000     ERROR VALID-000 Application not Available !
     Appset maintenance in progress
VALID-010     ERROR VALID-020 Nothing extracted from VALIDATION TABLE
     Check your VALIDATION TABLE
VALID-020     ERROR VALID-020 Nothing extracted from VALIDATION_H TABLE
     Check your VALIDATION_H TABLE
VALID-030     ERROR VALID-030 Wrong Application, check your logic
     You may have hardcoded a wrong application in your logic.
VALID-040     ERROR VALID-040 No Datasrc available
     Check your Parameter "DATASRC".
VALID-050     ERROR VALID-050 No Time available
     Check your Parameter "Time".
VALID-060     ERROR VALID-060 Nothing extracted from VALIDATION - VALIDATION_H Table
     Check your VALIDATION TABLE
     Check your VALIDATION_H TABLE
     Check the validation iD in VALIDATION and VALIDATION_H Table.
VALID-070     ERROR VALID-070 No Data found
     Check if you have data for the selected CATEGORY - TIME - GROUP
VALID-080     ERROR VALID-080 No Data found for the selected period
     Check your PERIOD Property in the VALIDATION_H Table

Currency Translation question

When the currency translation is executed..it overwrite the reporting currency by new amount.
Q1>>How to find out additive impact by each each account for currency translation changes.?
For example I have 1000 accounts, which for which currency translation is executed. Can I know the currency translation changes per each account seperately for reporting purpose?
Client wants to do the complete audit trail of amount posted by currency translation. is it possible..
How it is possible. Is it possible thru movement type to track the currency translation by each account?
Q2>>DATASRC dimension has a property IS_CONSOLIDATED? has some one used it before? What it is used for?
Please explain a bit..because the documentation from SAP is very brief..
Apprecaite inputs...

Hi Doodwala,
I'm not sure I'm following your question 1. Do you mean that you want to track the difference between the new and old reporting currency amount when the LC amount changes? Or do you want to track the change in the translated amount if the rate changes (or more likely using a different rate)?
If your audit requirement is to track every record change then it is going to be very arduous to do this in a custom way. I'd recommend looking into the delivered audit trail functionality to see if that meets your requriements. There is a bit of information about this functionality here: [http://help.sap.com/saphelp_bpc70sp02/helpdata/en/e1/8999faf82c4a61acd65683a8cedafe/frameset.htm]
Question 2 was asked and answered in this thread: [IS_CONSOLIDATED in DATASRC;
Ethan

How to create a Cash Flow Statement?

Dear all:
I am trying to create a Cash Flow Statement, and my approach is to use Dimension formula to calculate on the fly. Is my approach the best practice, or should I use script logic instead?
Based on my understanding, if I use Dimension formula, I won't need to create new set Dim members to store the calculated values (such as Increase (Decrease) in A/R = A/R this month - A/R last month). However, I am having problem constructing the formula in FORMULAH1 column.
Given above A/R example, I tried to use [NetAR] - ([NetAR],[Time].[PRIOR]) to get the difference in value between this month and last month, but I received error message saying that "The hierarchy '[PRIOR]' was not found in the cube when the string, [TIME].[PRIOR], was parsed". Is there anyway to retrieve Next or Prior months data in MDX?
If my approach is not correct, please advise correct way.
P.S. I have searched the forum and someone mentioned using Account Transformation logic. I looked up Administration Help file but didn't grasp the concept of Account Transformation logic. Can someone explain in detail for me?
Thank you for your help!
Brian

Try not to use DIMENSION LOGIC, unless it is really simple.
This is a set of ideas from the BPC 5 demo that I often use for Cash Flow Statements. This may be modified for your use, but the idea is consistent. Just remember to prep the customer to understand that 1 time charges and 1 off changes to CF statements are more often added and managed manually since it they would always impact a CF report.
Logic from version 5 BPC Demo- Finance App
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB CONSOLIDATION_LIBRARY.LGL
// MOVE INCOME STATEMENT ITEMS TO CASH FLOW STATEMENT
RUNSUMMARIZE(ThisApp,CF_SUMM,%CATEGORY_SET%,%LC_RPT_CURR%)
//CALCULATE BALANCE SHEET MOVEMENTS AND POST TO CASH FLOW STATEMENT
*SELECT(%FROM_ACCOUNT%, "[ID]", "ACCOUNT", "[CF_TO_ACCT] <> ''")
*XDIM_MEMBERSET ACCOUNT = %FROM_ACCOUNT%
*XDIM_ADDMEMBERSET TIME = PRIOR
*XDIM_MEMBERSET RPTCURRENCY=%LC_RPT_CURR%
*WHEN TIME
      *IS %TIME_SET%
            *REC(ACCOUNT=ACCOUNT.CF_TO_ACCT)
      *IS PRIOR
            *REC(FACTOR=-1,ACCOUNT=ACCOUNT.CF_TO_ACCT,TIME=NEXT)
*ENDWHEN
*COMMIT
Changes to above:
Dependencies (libraries, properties, etc.)
- SYSTEM_CONSTANTS.LGL
- CONSOLIDATION_LIBRARY.LGL u2013 to run the Business Rules section
- The following dimensions, members and properties are assumed
          Account
               CF_TO_ACCT property which is on all base level accounts which are part of the cash flow statement. The value should be the cash flow account that they map to. The dimension values are the IDs so they are all assumed as names
               CF_SUMM property used to move the income statement items to the cash flow statement. Contains the formulas on the destination cash flow accounts that map the Income statement accounts.
          Time u2013 just the dimension name
          RptCurrency
          CURRENCY_TYPE property with a value of L or R
What does it do?
Step 1 - MOVE INCOME STATEMENT ITEMS TO CASH FLOW STATEMENT
Use the formulas in the CF_SUMM accounts to move income statement values to the cash flow statement for all currencies based on the Currency_Type property
Step 2 - CALCULATE BALANCE SHEET MOVEMENTS AND POST TO CASH FLOW STATEMENT
·        Select all accounts that have values in the CF_TO_ACCT property
·        Add the Prior time period to the time memberset
·        Run this process for all currencies based on the Currency_Type property
·        Take the value in the current period and the negative value of the prior period to calculate the periodic cash flow amount and write to the account designated in the CF_TO_ACCT property
IMPORTANT NOTE: this step does have an issue that will be corrected in future versions of the sales demo. The issue is that if you run this logic for 2007.MAR, the negative balance for 2007.MAR will be written to 2007.APR as well as 2007.FEB being written to 2007.MAR. The logic needs to be changed as follows to work
First create two members in the DataSrc dimension that both consolidate to PreAdj member of the DataSrc dimension named CF_Current and CF_Prior
Add the following statement after the *XDIM_MEMBERSET RPTCURRENCY=%LC_RPT_CURR%
*XDIM_MEMBERSET DATASRC=
Change the REC statements as follows
*REC(ACCOUNT=ACCOUNT.CF_TO_ACCT,DATASRC=u201CCF_Currentu201D)
*REC(FACTOR=-1,ACCOUNT=ACCOUNT.CF_TO_ACCT,TIME=NEXT,DATASRC=u201CCF_Prioru201D)
Hope this helps somewhat. It is really hard to send this detailed stuff usingthe FORUM.
Edited by: Petar Daniel on Dec 11, 2008 8:39 PM

How to setup consolidation environment in BPC 7.0MS SP05

Hi I am completely new to the MS version of BPC7.0.
We have to implement the Consolidations for our client. I would like to know how can we setup consolidations environemnt in BPC7.0MS. I have a document on the same for NW7.0. Could you guys have anyinformation on the Consolidations on BPC7.0MS version
What are the considerations to take before working on consolidations using MS7.0BPC.
Thanks in Advance
AK

Hi,
The first step in setting up a legal consolidation application set is to ensure the dimensions are set up properly. Each application must contain some required dimensions, while some other dimensions are optional.
The dimensions discussed here are based on the standards used in the business rules. Other dimensions can co-exist in a reporting application but do not impact the business rule function. All applications must contain the four required ENTITY, CATEGORY, TIME and ACCOUNT dimensions (but can be named as desired). The remaining dimensions have the following rules:
u2022 The CURRENCY/GROUP dimension is required for the consolidation and/or currency business rules
u2022 The INTCO dimension used for matching inter-company activity
u2022 The DATASRC dimension is required for elimination and/or consolidation business rules
u2022 The SUBTABLE (flow) dimension is optional, and based on your requirements
You can also choose to set up the following business rules tables for consolidation:
u2022 Currency conversion
u2022 Account transformation
u2022 Intercompany Bookings
u2022 US Eliminations
u2022 Carry-forward rules
u2022 Validations
u2022 Automatic Adjustments
You will have to look at each of the business rules to undertand their functionalities.
Hope this gives you the basic understanding.

Skip currency translation for certain data source members

I have got percentage data againist some data source members which I do want to translate when the currency translation is executed. Is there a way to achieve this? The business rules for currency translations only have account and flow dimensions and does not include data source dimension so I am not able to filter out datasource dimension members in currency translation business rules.
Any suggestion how it may be possible to filter data source member during currency translation execution?
Thanks in advance.

Hi there,
You can use the *XDIM_MEMBERSET with the DATASRC dimension to limit what data gets translated (7.0 M SP9)
Please see [Note 1522149|https://service.sap.com/sap/support/notes/1522149] - XDIM_MEMBERSET can be used with DataSrc in Business Rule
Also, the IS_CONVERTED property in the DataSrc dimension can also be used:
The IS_CONVERTED property
The members of the DATASRC dimension will be processed according to the value of the property IS_CONVERTED, as per the following rules:
IS_CONVERTED = N: These members are ignored in the conversion
IS_CONVERTED = Y: These members are converted from LC into the desired currency
IS_CONVERTED = G (group): These members are copied from the reporting currency of the GROUP being translated into the currency member corresponding to the given group.
This obviously only applies if the translation is run for a GROUP and not for a reporting currency.
All members of the DATASRC dimension having the property IS_CONVERTED not set to u2018Yu2019 will be skipped.
Thanks,
John

Oracle OLAP cube build question

Hello,
I am trying to build a reasonably large cube (around 100
million rows from the underlying relational fact table). I am using
Oracle 10g Release 2. The cube has 7 dimensions, the largest of which
is TIME (6 years of data with the lowest level day). The cube build
never finishes.
Apparently it collapses while doing "Auto Solve". I'm assuming this
means calculating the aggregations for upper levels of the hierarchy
(although this is not mentioned in any of the documentation I have).
I have two questions related to this:
1. Is there a way to keep these aggregations from being performed at
cube build time on dimensions with a value-based hierarchy? I already
have the one dimension designated as level-based unchecked in the
"Summarize To" tab in AW manager (TIME dimension).
2. Are there any other tips that might help me get this cube built?
Here is the log from the olapsys.xml_load_log table:
RECORD_ID LOG_DATE AW XML_MESSAGE
1. 09-MAR-06 SYS.AWXML 08:18:51 Started Build(Refresh) of APSHELL Analytic Workspace.
2. 09-MAR-06 SPADMIN.APSHELL 08:18:53 Attached AW APSHELL in RW Mode.
3. 09-MAR-06 SPADMIN.APSHELL 08:18:53 Started Loading Dimensions.
4. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members.
5. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for ACCOUNT.DIMENSION (1 out of 9 Dimensions).
6. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Finished Loading Members for ACCOUNT.DIMENSION. Added: 0. No Longer Present: 0.
7. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for CATEGORY.DIMENSION (2 out of 9 Dimensions).
8. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Finished Loading Members for CATEGORY.DIMENSION. Added: 0. No Longer Present: 0.
9. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for DATASRC.DIMENSION (3 out of 9 Dimensions).10. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Finished Loading Members for DATASRC.DIMENSION. Added: 0. No Longer Present: 0.
11. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for ENTITY.DIMENSION (4 out of 9 Dimensions).
12. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Finished Loading Members for ENTITY.DIMENSION. Added: 0. No Longer Present: 0.
13. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for INPT_CURRENCY.DIMENSION (5 out of 9 Dimensions).
14. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Finished Loading Members for INPT_CURRENCY.DIMENSION. Added: 0. No Longer Present: 0.
15. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for INTCO.DIMENSION (6 out of 9 Dimensions).
16. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Finished Loading Members for INTCO.DIMENSION. Added: 0. No Longer Present: 0.
17. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for RATE.DIMENSION (7 out of 9 Dimensions).
18. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Finished Loading Members for RATE.DIMENSION. Added: 0. No Longer Present: 0.
19. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for RPTCURRENCY.DIMENSION (8 out of 9 Dimensions).
20. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Finished Loading Members for RPTCURRENCY.DIMENSION. Added: 0. No Longer Present: 0.
21. 09-MAR-06 SPADMIN.APSHELL 08:18:54 Started Loading Dimension Members for TIME.DIMENSION (9 out of 9 Dimensions).
22. 09-MAR-06 SPADMIN.APSHELL 08:18:55 Finished Loading Members for TIME.DIMENSION. Added: 0. No Longer Present: 0.
23. 09-MAR-06 SPADMIN.APSHELL 08:18:55 Finished Loading Dimension Members.
24. 09-MAR-06 SPADMIN.APSHELL 08:18:55 Started Loading Hierarchies.
25. 09-MAR-06 SPADMIN.APSHELL 08:18:55 Started Loading Hierarchies for ACCOUNT.DIMENSION (1 out of 9 Dimensions).
26. 09-MAR-06 SPADMIN.APSHELL 08:18:55 Finished Loading Hierarchies for ACCOUNT.DIMENSION. 1 hierarchy(s) ACCOUNT_HIERARCHY Processed.
27. 09-MAR-06 SPADMIN.APSHELL 08:18:55 Started Loading Hierarchies for CATEGORY.DIMENSION (2 out of 9 Dimensions).
28. 09-MAR-06 SPADMIN.APSHELL 08:18:56 Finished Loading Hierarchies for CATEGORY.DIMENSION. 1 hierarchy(s) CATEGORY_HIERARCHY Processed.
29. 09-MAR-06 SPADMIN.APSHELL 08:18:56 Started Loading Hierarchies for DATASRC.DIMENSION (3 out of 9 Dimensions).
30. 09-MAR-06 SPADMIN.APSHELL 08:18:56 Finished Loading Hierarchies for DATASRC.DIMENSION. 1 hierarchy(s) DATASRC_HIER Processed.
31. 09-MAR-06 SPADMIN.APSHELL 08:18:56 Started Loading Hierarchies for ENTITY.DIMENSION (4 out of 9 Dimensions).
32. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Hierarchies for ENTITY.DIMENSION. 2 hierarchy(s) ENTITY_HIERARCHY1, ENTITY_HIERARCHY2 Processed.
34. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Hierarchies for INPT_CURRENCY.DIMENSION. No hierarchy(s) Processed.
36. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Hierarchies for INTCO.DIMENSION. 1 hierarchy(s) INTCO_HIERARCHY Processed.
37. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Hierarchies for RATE.DIMENSION (7 out of 9 Dimensions).
38. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Hierarchies for RATE.DIMENSION. No hierarchy(s) Processed.
39. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Hierarchies for RPTCURRENCY.DIMENSION (8 out of 9 Dimensions).
40. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Hierarchies for RPTCURRENCY.DIMENSION. No hierarchy(s) Processed.
41. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Hierarchies for TIME.DIMENSION (9 out of 9 Dimensions).
42. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Hierarchies for TIME.DIMENSION. 2 hierarchy(s) CALENDAR, FISCAL_CALENDAR Processed.
43. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Hierarchies.
44. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Attributes.
45. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Attributes for ACCOUNT.DIMENSION (1 out of 9 Dimensions).
46. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Attributes for ACCOUNT.DIMENSION. 6 attribute(s) ACCTYPE, CALC, FORMAT, LONG_DESCRIPTION, RATETYPE, SCALING Processed.
47. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Attributes for CATEGORY.DIMENSION (2 out of 9 Dimensions).
48. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Attributes for CATEGORY.DIMENSION. 2 attribute(s) CALC, LONG_DESCRIPTION Processed.
49. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Attributes for DATASRC.DIMENSION (3 out of 9 Dimensions). 50. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Attributes for DATASRC.DIMENSION. 3 attribute(s) CURRENCY, INTCO, LONG_DESCRIPTION Processed.
51. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Attributes for ENTITY.DIMENSION (4 out of 9 Dimensions).
52. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Attributes for ENTITY.DIMENSION. 3 attribute(s) CALC, CURRENCY, LONG_DESCRIPTION Processed.
53. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Attributes for INPT_CURRENCY.DIMENSION (5 out of 9 Dimensions).
54. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Attributes for INPT_CURRENCY.DIMENSION. 2 attribute(s) LONG_DESCRIPTION, REPORTING Processed.
55. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Attributes for INTCO.DIMENSION (6 out of 9 Dimensions).
56. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Finished Loading Attributes for INTCO.DIMENSION. 2 attribute(s) ENTITY, LONG_DESCRIPTION Processed.
57. 09-MAR-06 SPADMIN.APSHELL 08:18:57 Started Loading Attributes for RATE.DIMENSION (7 out of 9 Dimensions).
58. 09-MAR-06 SPADMIN.APSHELL 08:18:58 Finished Loading Attributes for RATE.DIMENSION. 1 attribute(s) LONG_DESCRIPTION Processed.
59. 09-MAR-06 SPADMIN.APSHELL 08:18:58 Started Loading Attributes for RPTCURRENCY.DIMENSION (8 out of 9 Dimensions).
60. 09-MAR-06 SPADMIN.APSHELL 08:18:58 Finished Loading Attributes for RPTCURRENCY.DIMENSION. 2 attribute(s) LONG_DESCRIPTION, REPORTING Processed.
61. 09-MAR-06 SPADMIN.APSHELL 08:18:58 Started Loading Attributes for TIME.DIMENSION (9 out of 9 Dimensions).
62. 09-MAR-06 SPADMIN.APSHELL 08:20:26 Finished Loading Attributes for TIME.DIMENSION. 3 attribute(s) END_DATE, LONG_DESCRIPTION, TIME_SPAN Processed.
63. 09-MAR-06 SPADMIN.APSHELL 08:20:26 Finished Loading Attributes.
64. 09-MAR-06 SPADMIN.APSHELL 08:20:26 Finished Loading Dimensions.
65. 09-MAR-06 SPADMIN.APSHELL 08:20:26 Started Updating Partitions.
66. 09-MAR-06 SPADMIN.APSHELL 08:20:26 Finished Updating Partitions.
67. 09-MAR-06 SPADMIN.APSHELL 08:20:40 Started Loading Measures.
68. 09-MAR-06 SPADMIN.APSHELL 08:20:40 Started Load of Measures: SIGNEDDATA from Cube FINANCE.CUBE.
69. 09-MAR-06 SPADMIN.APSHELL 10:54:06 Finished Load of Measures: SIGNEDDATA from Cube FINANCE.CUBE. Processed 100000001 Records. Rejected 0 Records.
70. 09-MAR-06 SPADMIN.APSHELL 10:54:06 Started Auto Solve for Measures: SIGNEDDATA from Cube FINANCE.CUBE.

Hi, I've taken a few minutes to do a quick analysis. I just saw in your post that this isn't "real data", but some type of sample. Here is what I'm seeing. First off, this is the strangest dataset I've ever seen. With the exception of TIME, DATASOURCE, and RPTCURRENCY, every single other dimension is nearly 100% dense. Quite truthfully, in a cube of this many dimensions, I have never seen data be 100% dense like this (usually with this many dimensions its more around the .01% dense max, usually even lower than that). Is it possible that the way you generated the test data would have caused this to happen?
If so, I would strongly encourage you to go back to your "real" data and run the same queries and post results. I think that "real" data will produce a much different profile than what we're seeing here.
If you really do want to try and aggregate this dataset, I'd do the following:
1. Drop any dimension that doesn't add analytic value
Report currency is an obvious choice for this - if every record has exactly the same value, then it adds no additional information (but increases the size of the data)
Also, data source falls into the same category. However, I'd add one more question / comment with data source - even if all 3 values DID show up in the data, does knowing the data source provide any analytical capabilities? I.e. would a business person make a different decision based on whether the data is coming from system A vs. system B vs. system C?
2. Make sure all remaining dimensions except TIME are DENSE, not sparse. I'd probably define the cube with this order:
Account...........dense
Entity..............dense
IntCo...............dense
Category.........dense
Time...............sparse
3. Since time is level based (and sparse), I'd set it to only aggregate at the day and month levels (i.e. let quarter and year be calculated on the fly)
4. Are there really no "levels" in the dimensions like Entity? Usually companies define those with very rigid hierarchies (assuming this means legal entity)
Good luck with loading this cube. Please let us know how "real" this data is. I suspect with that many dimensions that the "real" data will be VERY sparse, not dense like this sample is, in which case some of the sparsity handling functionality would make a huge benefit for you. As is, with the data being nearly 100% dense, turning on sparsity for any dimension other than TIME probably kills your performance.
Let us know what you think!
Thanks,
Scott

Datasrc dimension

Similar Messages

Maybe you are looking for