Optimization of rate cube

Hi All,
I have a query like when the BPC system is upgraded to V4.2 SP6, the optimization for rate application is taking less time to process. The database is running to the success but the process is not running. Any guess like on it.
Thanks in Advance.
Raghu.

I am not sure if I understand your issue yet.
if you are trying to process the application with out any processing at all then try to do the following
A. Go to Admin Console.
B. Modify Application
C. Uncheck "Reassign SQL Index" and "Process Application"
D. Choose Modify Application
This should do the trick. Let me know if it works.

Similar Messages

Calc with a rates cube

I have 2 cubes, 1 with a Local Scenario / Scenario and a rates cube that converts the numbers from Local to USD. When have one dept in the Product category that should not be converted. I have tried several things to bypass this dept but I continue to get errors. I used if statement and other statement but I can't seem to get it to work.The set-up:DataCopy Local scenario to ScenarioThenFix ("2004 Act+Dem"); CCONV "2004 Act Type"->"US Dollar";Endfix; Any help would be appreciated

Unless you switch of CCTRACK in the cfg file, you will not be able to complete this task.Set the cfg file with the CCTRACK FALSE command. Your calc script will not validate, but will run correctly once this has been changed.Hope this helpsAndy Kingwww.analitica.co.uk

The Cube with ID = Rate doesn't exist in the collection Error Message

When doing a Full Optimization in the Rate cube I get a "The Cube with ID = Rate doesn't exist in the collection" error message. What is causing this error and how do I fix it?

I have seen this error when reporting services was not properly configured. can you connect to http://servername/reports ?
If not try to fix reporting services first, this solved the problem for me in the past.
But usually in this case all the aplications are giving this error when modifying. Is this also the case in your appset?
Does Apshell work when you modify the application there?
-Joost

Management of rate types

Dear gurus,
I have trouble on currency conversion. There are different kinds of rate types such as AVG, END, historical and so on. I don't know how the system manage each kind of rate type, I mean the calculation of the values per each rate type.
For example, I want to register on the system an historical rate, but I'm not really sure if the system makes the operations automatically through business rules or, it must be done manually by the user out of the system and subsequently registered on the rate cube.
Does anyone knows how it works?
Thanks so much

Hi,
1. These Rate Types are required based upon your business demand. If business want to translate any amount with historical rate, only then you need to maintain this in the dimension.
2. All the calculation will be automatic based on the business rule and dimension property, Just business suppose to maintain the conversion rate for historical rate type.
From the below link, you can find complete detail:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6052a57b-8c64-2c10-b3a5-b0378ff21243?quicklink=index&overridelayout=true
I hope this will help.
Anil

Where to enter conversion rates

Hi,
We are trying to implement a case study in bpc for 1st time and am not aware where I should enter currency conversion rates.I have included all local currency in entity under currency property.
Should all this currencies be members of input currency?
I have included RPTcurrency in the dimensions I used and Inputcurrency in only Rate application.Should I include Inputcurrency any where else?
Awaiting for your response.

The rates are entered into the RATE application, by RATETYPE and INPUTCURRENCY. So, if you have 10 Input currencies defined and ENTITIES that will use one of the 10 defined currencies, then you need to ENTER in the RATE cube 10 currency values, by TIME, by category. The dimension named InputCurrency is limited to the RATE cube in standard designs, based ONLY on its function.
In the core Reporting cube, such as FINANCE, RPTCURRENCY defines the available views of the combined FX results. SO, if you want to see the 10 currencies in EURO and GBP, then you need to define those currencies as members in the RPTCURRENCY dimension. This also requires you to set up the properties correctly by reproting currency. PLus, make certain tha tyou enter the cube's script logic section and open the FXTRANS and defualt logic scriipts, Validate and Process the scripts to account for the changes you have made to the dimensionality.
Hope this helps.

Permanently change default error configuration in Analysis Services 2005

Hi,
Currently, I am working on a BPC 5.1 application. The data for this application is loaded(inserted via SQL statement) right to the FACT table and then a full process is run for that cube via an SSIS package using the Analysis Services Processing Task. Often records are loaded this way where a dimension member for some of the records has not been added to the Account dimension yet. These records after loading are considered 'orphan records' until the accounts are added to the account dimension.
This loading process is used because of the volume of records loaded(over 2 million at a time) and the timing of the company's business process. They will receive data sometimes weeks before the account dimension is updated in BPC with the new dimension members.
If I try and process the application from the BPC Administration area with these orphan records in the FACT table, the processing stops and an error displays. Then when I process the cube from Analysis services, an error is displayed telling me that orphan data was found.
A temporary work-around is to go into the cube properties in Analysis Services 2005, click on Error Configuration, uncheck 'Use default error configuration' and select 'Ignore errors'. Then you can process the application from BPC's Administration page successfully. But, the problem is that after processing the application successfully, the Analysis Services Error Configuration automatically switches back from 'Ignore errors' to 'Use default error configuration'.
Does anyone have any suggestions on how to permanently keep the 'Ignore errors' configuration selected so it does not automatically switch back to 'Use default error configuration'? Prior to BPC 5.0 this was not occurring.
Also, does anyone know why this was changed in BPC 5.0/5.1?
Thanks,
Glenn

Hi Glenn,
I understood the problem but I can say that it was a bad migration of appset from 4.2 to 5.0.
Any way they are using a dts package to import data into our fact table. That's means they have to add another step into that package where they have to do the verfications of records before to insert into fact table. Verfications can be done using the same mechanism from our standard import. Just edit that package and add similar steps into customer package.
Attention you need somebody with experience developing DTS packages with for BPC to avoid other problems.
One of big benefits from 5.X compare with 4.2 was the fact that we are able to use optimization schema and aggregations for cubes.
Heaving that orphan records it is not possible to use optimization schema for cubes and you are not able to create good aggregation into your cube.
So my idea is to provide all these information to customer and to try to modify that package instead to enable that option which can cause many other issues.
Sorin

Error while running FX restatement process for currency translation

Hi Experts,
I am facing errors while trying to run FX_Restatement process to do currency translation.
I am having the error: RUN_LOGIC:Member u201CXXXu201D not exist => where XXX is any currency I am trying to convert.
Below is the script logic (FXTRANS.LGF)used.
*RUN_PROGRAM CURR_CONVERSION
      CATEGORY     = %FX_CATEGORY_SET%
      CURRENCY     = %FX_INPCURRENCY_SET%
      TID_RA = %FX_TIME_SET%
      OTHER = [ENTITY=%FX_ENTITY_SET%]
      RATEENTITY = GLOBAL
      //For More than one other scope parameters: OTHER = [ENTITY=%FX_ENTITY_SET%;INTCO=%INTCO_SET%...]
*ENDRUN_PROGRAM
I am working on BPC 7.5 NW version.
Can you help us with this?

For the currency you are converting to: XXX
INPUTCURRENCY dimension must have XXX as a member with "REPORTING" property set to "Y"
and
RPTCURRENCY dimension must have XXX as a member with "REPORTING" property set to "Y" and "CURRENCY_TYPE" property set to "R"
It needs to be in both dimensions with the right properties. INPUTCURRENCY is the currency dimension in the RATE cube, RPTCURRENCY is the currency dimension in the financial or consolidations cube.

.LGF Modification Error

Hi,
I am using BPC Version 7.0.104 MS
OS: 2003 server edition
I have created one application "Consolidate_1" using new dimension in it "C_Acct" , "C_Datasrc" ,"C_FLOW" and "C_Category"
RATE1 application has been created and successfully imported.
(Validation of Transformation file, Package execution and script logic validated)
Well i am facing problem in the script logic for the consoildate_1 application
I have modified my SYSTEM_CONSTANT.LGF file (from adminapp/consolidate_1) as follows:
// application constants //
*FUNCTION CATEGORYDIM=C_CATEGORY
*FUNCTION TIMEDIM=TIME
*FUNCTION CURRENCYDIM=GROUPS
*FUNCTION ENTITYDIM=ENTITY
*FUNCTION ACCOUNTDIM=C_ACCT
*FUNCTION INTCODIM=INTCO
*FUNCTION DATASRCDIM=C_DATASRC //
This part is needed when a RATE cube
// is associated to the application //
(FX = single or multi currency) //
*FUNCTION THISAPP=CONSOLIDATE_1 -- My consolidation application
*FUNCTION RATEAPP=RATE1 ---New Rate Application consisting of in-built dimension.
*FUNCTION RATEENTITYDIM=RATESRC
*FUNCTION RATEACCOUNTDIM=RATE
*FUNCTION INPUTCURRENCYDIM=INPUTCURRENCY
*FUNCTION RATEENTITYMBR=RATEINPUT
*FUNCTION RATESRCCALCMBR=RATECALC
*FUNCTION AVGRATEID=AVG
*FUNCTION ENDRATEID=END
The modified FXTRANS.LGF (In the application) looks like :
//============================================= //
Currency translation logic //
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB SYSTEM_LIBRARY.LGL
*SYSLIB MULTICURRENCYTRANS.LGL
*RUN_PROGRAM
CURR_CONVERSION CATEGORY=%C_CATEGORY_SET%
CURRENCY=%INPUTCURRENCY_SET%
TID_RA=%TIME_SET%
OTHER=ENTITY=%ENTITY_SET%
RATEENTITY=Global
*ENDRUN_PROGRAM
*COMMIT
I am facing 2 situations where I am getting errors:
1. While executing the package - Error --> Mapping error; the dimension does not exist in the application. CATEGORY
2. While validating the FXtrans.lgf/Default.lgf - Error --> "Invalid line in logic section : category = %C_categoy_set% invalid line in logic section"
I have referred the threads mentioned below but still unable to resolve this issue as this is the first time I am working on SAP BPC so I don't know much about this tool!
Invalid Dimension Entity in lookup
Re: Invalid Dimension SALESACCOUNT in Lookup rule
Can somebody show me the right path..
Thanks
SG

Hi Nilanjan,
yesterday i created new appset, application and new customized dimensions also.
I have replaced RateSrc with R_Entity every where (System constant, in Default.lgf, Datafile and in Transformation file)
Ratesrc -Entity - RptCurrency ( Dimension name- Dim Typ- Ref Dimension)
R_Entity- Entity -InputCurrency ( Dimension name- Dim Typ- Ref Dimension)
The why this RateSrc dimension error is coming up..
My Questions:
1. Do i need to change the default.xls of rate1 application also?
2. Do i need to change the default.xls of other related application like finance which are referred by rate1 application?
3. I have copied system_constant.lgl to my rate application from finance application but scrap this stuff n removed the file from rate1 application and created consolidate1 application and now the logic looks like below.
*INCLUDE ..\consolidate1\system_constants.lgl
*SELECT(%RATEMBRS%,[ID],RATEACCOUNTDIM,"CALC='N'")
*XDIM_MEMBERSET RATEACCOUNTDIM=%RATEMBRS%
*SELECT(%CURRMBRS%,[ID],INPUTCURRENCYDIM,"CALC='N'")
*XDIM_MEMBERSET INPUTCURRENCYDIM=%CURRMBRS%
*XDIM_MEMBER RATEENTITYDIM=RATEINPUT
*WHEN INPUTCURRENCY.MD
*IS "D"
*REC(EXPRESSION=ROUND(1/%VALUE%,6),RATEENTITYDIM="RATECALC")
*ELSE
*REC(R_Entity="RATECALC")
*ENDWHEN
*CLEAR_DESTINATION
*DESTINATION R_Entity=RATECALC
also the system_constant.lgl look like:
// application constants //
*FUNCTION CATEGORYDIM=C_CATEGORY
*FUNCTION TIMEDIM=TIME
*FUNCTION CURRENCYDIM=INPUTCURRENCY
*FUNCTION ENTITYDIM=R_ENTITY
*FUNCTION ACCOUNTDIM=R_ACCT
This part is needed when a RATE cube
// is associated to the application //
(FX = single or multi currency) //
*FUNCTION THISAPP=CONSOLIDATE1 -- My consolidation application
*FUNCTION RATEAPP=RATE1 ---New Rate Application consisting of in-built dimension.
*FUNCTION RATEENTITYDIM=R_ENTITY
*FUNCTION RATEACCOUNTDIM=R_ACCT
*FUNCTION INPUTCURRENCYDIM=INPUTCURRENCY
*FUNCTION RATEENTITYMBR=RATEINPUT
*FUNCTION RATESRCCALCMBR=RATECALC
*FUNCTION AVGRATEID=AVG
*FUNCTION ENDRATEID=END
Can you make out where i am missing??
Thanks for the help till now..
Saurabh

Best practice for number of result objects in webi

Hello all,
I am just wondering if SAP has any recommendation or best practice document regarding number of fields in Result Objects area for webi. We are currently running on XI 3.1 SP3...one of the end user is running a webi with close to 20 objects/dimensions and 2 measure in result objects. The report is running for 45-60 mins and sometimes timing out. The cube which stores data has around 250K records and the report would return pretty much all the records from the cube.
Any recommendations/ best practices?
On similar issue - our production system is around 250GB what would be the memory on your server typically...currently we have 8GB memory on the sap instance server.
Thanks in advance.

Hi,
You mention Cubes so i suspect BW or MS AS . Yes, OLAP data access (ODA) to OLAP DataSets is a struggle for WebIntelligence which is best at consuming Relational RowSets.
Inefficient MDX queries can easily be generated by the webi tool, primeraly due to substandard (or excessive) query and document design. Mandatory filters and focused navigation (i.e. targetted BI questions) are the best for success.
Here's an intersting article about "when is a webi doc too big" https://weblogs.sdn.sap.com/pub/wlg/18706
Here's a best practice doc about webi report design and tuning ontop of BW MDX : https://service.sap.com/~sapidb/011000358700000750762010E
Optimization of the cube itself, including aggregates and cache warming is important. But especially use of Suppress Unassigned nodes in the BW hierarchy, and "query stripping" in the webi document.
finally, patch level of the BW (BW-BEX-OT-MDX) component is critical. i.e. anything lower than 7.01 SP09 is trouble. (memory management, mdx optimization, functional correctness)
Regards,
H

An error in Script Logic

Hi Experts,
I have a problem with one of the FXTranslation logicu2019s in one of my report can u please help me on that.
The logic works fine for 2 reports out of 3, for the 3rd report I donu2019t know why itu2019s not doing the translation to USD. As far as the design of the report goes the 2 reports for which translation works fine comprises of 2 logics one for percentage allocation and other for translation from LC to USD, whereas the 3rd report needs only translation but doesnu2019t need the allocation logic to be run.
The conversion for the 3rd report happens if I comment out the allocation logic. Both these logics are mapped to Default.LGF file. I am unable to figure out what could be the error.
Below is the Script Logic for Aloocation and Translation:
//Budget Allocation
*SELECT(%CURR%,"[ID]","RPTCURRENCY","[CURRENCY_TYPE]='L' OR [CURRENCY_TYPE]='R'")
*XDIM_MEMBERSET RPTCURRENCY=%CURR%
*RUNALLOCATION
*FACTOR=USING/1
*DIM ACCOUNTB WHAT=[IS_ALLOC]='Y'; WHERE=<<<; USING=ALLOCPER
*DIM PRODUCTM WHAT=NOPRODUCT; WHERE<>NOPRODUCT; USING=<<<
*ENDALLOCATION
*COMMIT
// Currency Translation
*SELECT(%REPORTING_CURRENCIES%, "[ID]", "RPTCURRENCY", "[REPORTING] = 'Y'")
*SELECT(%FX_RATES%, "[ID]", "RATE", "[GROUP] = 'FX RATE'")
// Load the rates from the RATE cube
*LOOKUP RATE
            *DIM CATEGORY="BUDGET"
     *DIM RATEENTITY="GLOBAL"
     *DIM RATE=ACCOUNTB.RATETYPE
     *DIM SOURCECURR:INPUTCURRENCY=LEGALENTITY.CURRENCY
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *DIM %CURR%:INPUTCURRENCY="%CURR%"
     *NEXT
*ENDLOOKUP
// define the translation rule
*WHEN ACCOUNTB.RATETYPE
*IS "NOTRANS"
     // skip
*IS %FX_RATES%
           // translate
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *REC(FACTOR=LOOKUP(%CURR%)/LOOKUP(SOURCECURR),RPTCURRENCY="%CURR%")
     *NEXT
*IS "COPYLC"
     // take as is
     *FOR %CURR%=%REPORTING_CURRENCIES%
          *REC(RPTCURRENCY="%CURR%")
     *NEXT
*ENDWHEN
*COMMIT
// Default
// FX Translation
*include FXTranslation.lgf
// Budget Allocation
*include BudgetAllocation.lgf

Hi Naresh,
One thing that helped me solve the problem was I needed to use different set of Dimension members/property in the Logic i.e What, Where and Using to trigger off the Curency Translation.
But please make sure that you use try to understand a unique dimension (member/property) used and use that to trigger off the translation or anything for that matter. My other two translations were working fine as the parameters i used were unique for them whereas the remaining one needed alteration in the logic only in the parameters used in What, Where and Using, so had to add one more set of Translation Logic for this exclusively.
Another point you need to check in your Rate Application is whether you have your Reporting Currency as value 1, say for eg USD is your reporting currency then the value in Rate Application for USD must be 1, if u by mistake cleared of this value when using the Clear Data Manager Package so the multiplication with 0 results in no conversion.
These were the two points that helped me solve my issue. I hope it helps.
Rgds,
Rizwan
Edited by: Rizwan Mustaffa on Jul 13, 2009 12:09 PM

SAP BPC 10 NW - component used by admin module

Hello Gurus,
We are on BPC 10NW - SP04
We were trying all the features using some test data. Now, we have received actual data from the business. We are trying to delete the previously created master data and create the new one give by the business.
It gives an error while processing the dimension (ENTITY Dimension)
To get processed we had done following activities too -
1. Deleted the transaction data from Consolidation, Ownership and Rate cubes
2. Deleted the BPFs
3. Deleted the inout forms and/or changed the references wherever we had used the hardcoded values.
4. Deleted the data from the referencial dimension (INPUTCURRENCY)
5. Tried to delete the ENTITY data from the backend (From BW)
Still it gives the error while processing the ENTITY dimension as "Error in admin module, Component used by admin moduile"
Only remaining part I can think of is of JOURNALS. We had created few data using journals. However, I am not sure how to delete the journal data. (if that is the root cause of the issue)
Can anyone suggest the remedy for this issue.
Let us know if you need more information.
Regards,
Rashmi

Hi Rashmi,
Please check if there is journal data. The journal data would be in a generated table. Please check for the journal generated table using the program UJ0_GET_GEN_TABNAME. You can check the entries in the table. The tables start with /1CPMB.....
- If you simply want to clear, then in BPC 7.5 there would be seprate task profile 'Admin Journal' which would enable the option of clearing the journals in admin console.
Thanks,
Sreeni

Currency Translation not producing any results

Hello Everyone,
I have ran into a very strange problem with the out of the box currency conversion. I have a finance app and am using the Fxtrans script logic to execute my currency translation. The problem I am having is when I run the FX Restatement package I not getting any results. LC has the correct amount that was input but my other reporting currencies show zero. My Entity dimension (which is named Company) has the correct currencies in the currency column for each company, and the InputCurrency dimension has all of my currencies listed. Everything else is the same as the AppShell app set. One last note is I do have some additional dimensions in the finance application but I don't think that would cause any issue.
My Rate cube is built the exactly the same as the rate cube in appshell app set. The only difference is my category dimension is named scenario.
I have updated all the system constants files and the script logic to reflect the dimension name changes. Everything works as expected in the Appshell application, but I just can't seem to figure out why it won't work in my appset.
I am sure I have left out some details that are needed so please just ask and I will provide whatever I can. I really appreciate any help anyone can provide.
Thanks in advance!
Nick

So I figured out the issue. For some reason the data that was in the WriteBack table for any currency other than LC was not showing up in the report. Once I optimized the application the currency conversion showed up as expected.
Has anyone had this problem before. Any known solution?
Thanks,
Nick

Currency conversion not working for foreign entity

I am having an issue with currency conversion not generating the correct values for foreign entities. For entities where the currency is USD, I am able to see the LC amount being written to USD. However, for entites that have currencies other than USD, I just see zeros. I have double-checked to make sure that rates exist for the given currencies. Below is the logic script I am using which is a modificatio nof the multicurrency.lgl. Any help would be greatly appreciated.
// filter the appropriate currencies and rates
*SELECT(%REPORTING_CURRENCIES%, "[ID]", "RptCurrency", "[REPORTING] = 'Y'")
*SELECT(%FX_RATES%,"[ID]","RATE","[GROUP]='FX RATE'")
// set the appropriate region to clear
//(all reporting currencies)
*CLEAR_DESTINATION
*DESTINATION RPTCURRENCY=%REPORTING_CURRENCIES%
// load the rates from the RATE cube
*LOOKUP RATE
*DIM RATESRC="RATECALC"
*DIM Rate=ARFIELD.RATETYPE
*DIM SOURCECURR: INPUTCURRENCY=LOC_MILLOTH.CURRENCY
*FOR %CURR%=%REPORTING_CURRENCIES%
*DIM %CURR%:INPUTCURRENCY="%CURR%"
*NEXT
*ENDLOOKUP
// define the translation rule
*WHEN ARFIELD.RATETYPE
*IS "NOTRANS"
// translate
*IS %FX_RATES%
       *FOR %CURR%=%REPORTING_CURRENCIES%
           *REC(FACTOR=LOOKUP(SOURCECURR)/LOOKUP(%CURR%),RptCurrency="%CURR%")
       *NEXT
*ELSE
       *FOR %CURR%=%REPORTING_CURRENCIES%
           *REC(RptCurrency="%CURR%")
       *NEXT
*ENDWHEN
*FOR %CURR%=%REPORTING_CURRENCIES%
         [RptCurrency].[#%CURR%]=null
*NEXT
*COMMIT
Regards,
Karen

Hi Karen,
I'm no script logic expert so I won't comment on your code. If it's working for USD then the code is probably fine.
There are a few other things you could check (these are based on investigation using the standard multicurrency script). They should line up with the standard Finance application from AppSet
In the InputCurrency dimension for the currencies you want to convert into :
   Check property Reporting is equal to "Y"
   Check property Group is set to "Report"
   Check propoerty MD has a value of "M" or "D"
In the RptCurrency dimension you need to have entries for the the currencies you want to convert into (AppSet only has USD and EUR to start). Also for each of the currencies :
   Check property Reporting is equal to "Y"
   Check property Group is equal to "Report"
   Check property Transfer is equal to "Y"
I'm not convinced that the Transfer value is required but from my testing if you get the above set up and use the standard multicurrency script it will work.
The testing I did was translating into USD, EUR, GBP, CHF, AUD etc
Hope this helps.
Thanks.
Bradley Newcombe.
Edited by: Bradley Newcombe on Apr 28, 2009 1:30 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

Test script logic file - Errror "Invalid Dimension Account"

Hi BPC Experts,
I am a new bee in BPC and have developed HCM applicaton in BPC 5.1. The Appset contains Finance, Rate & HCM applications.
I am working on HCM and wants to write a script logic file for HCM and it is giving an ERROR "Invalid Dimensin Account".
I have following dimensions in HCM Application:
account_hc --> type A
category_hc --> type C
company_hc --> type E
time_hc       --> time t
costcenter_hc --> type u
datasrc_hc      --> type d
employerole_hc --> type u
geography_hc --> type u
rptcurrency_hc --> type r.
I had defined Dimensions in system_cnstants file as mentioned below.
// application constants
*FUNCTION CATEGORYDIM         =CATEGORY_HC
*FUNCTION TIMEDIM =TIME_HC
*FUNCTION CURRENCYDIM =RPTCURRENCY_HC
*FUNCTION ENTITYDIM =COMPANY_HC
*FUNCTION ACCOUNTDIM =ACCOUNT_HC
*FUNCTION INTCODIM =INTCO
*FUNCTION CATEGORYDIM         =CATEGORY
*FUNCTION TIMEDIM =TIME
*FUNCTION CURRENCYDIM =RPTCURRENCY
*FUNCTION ENTITYDIM =ENTITY
*FUNCTION ACCOUNTDIM =ACCOUNT
// This part is needed when a RATE cube
// is associated to the application
// (FX = single or multi currency)
*FUNCTION THISAPP =HCM
*FUNCTION RATEAPP =RATE
*FUNCTION RATEENTITYDIM =RATESRC
*FUNCTION RATEACCOUNTDIM =RATE
*FUNCTION INPUTCURRENCYDIM =INPUTCURRENCY
*FUNCTION RATEENTITYMBR =RATEINPUT
*FUNCTION RATESRCCALCMBR =RATECALC
*FUNCTION AVGRATEID=AVG
*FUNCTION ENDRATEID=END
I tried to validate and save standard default script logic. But it gives me an error " NO match defined for lookup dimension Category"
So I could not use default logic file to write my script logic. Hence I have created HCM logic file. and Given the following script logic.
*XDIM_MEMBERSET ACCOUNT = XYZ_INC_RetPlan
*WHEN ACCOUNT
*IS XYZ_INC_RetPlan
*REC(FACTOR = 1.1, ACCOUNT)
*ENDWHEN
*COMMIT
While validat & save, I get an error "Invalid Dimension Account".
I do not understand why these errors occuring.
I have checked Category & Account dimensions checked. Every thing is ok. I have created Input schedules and they are working ok. It means the dimensions are fine.
Then why the error ?
Can you guys please guide me.
Appreciate your kind help.

Eswara,
try to close down BPC for ExCEl in case your IS/Reports are trying to access the APPlication.And also any other BPC ADmin screens accessing the same Application/Dimension.
1)try to only do a "process " on the account dimension without including the processing for Applications...
2)then try to do a process on the application.
Now your script should be able to recognize Account dimension and validate fine..
hope this helps...

Optimization of rate cube

Similar Messages

Maybe you are looking for