Invalid Dimension Entity in lookup

Hi All,
When try to validate the script logics from BPC Admin, I am getting the message "Invalid Dimension Entity in lookup".
Can you please let me how to fix this.
Thank you,
Raju

With the suggestions from this link -
ExecuteBaseLogic : Invalid Dimension:CATEGORY
"I have modified "Constants.lgl file" located into Webfolders\<appset>\AdminApp\<application name> if the categorydim is properly assigned to your category dimension" - I am not getting the above error more But I am getting another Error --
"Enforced *Destination cannot be empty" from ICElim.lgf and here is the code:
//=============================================
// Default Intercompany Eliminations
//=============================================
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB ICELIMWITHCURR.LGL
// append custom elimination rules here
//=============================================
// Elimination logic for two organization(H1, H2)
//=============================================
INITIALIZE_ELIM()
ELIMINATE_ORG(H1)
ELIMINATE_ORG(H2)
*COMMIT

Similar Messages

ExecuteBaseLogic::Invalid dimension BUDGET in lookup

Hello there
Just a quick question.
I am doing a lookup to take the rates in the rate cube
I want the lookup to look at the category budget if my evdre is in budget and actual otherwise...
i did this but it is not working i get the error
ExecuteBaseLogic::Invalid dimension BUDGET in lookup
*LOOKUP RATE
*DIM LCCUR:INPUTCURRENCY=ENTITY.CURRENCY
*DIM TCCUR:INPUTCURRENCY=TRANSACTIONCURRENCY.ID
*DIM RATE="AVG"
*DIM RATEENTITY="GLOBAL"
*DIM CATEGORY=%SET%
*ENDLOOKUP
*WHEN TIME
*IS 2010.JAN
*REC(FACTOR=LOOKUP(TCCUR)*(1/LOOKUP(LCCUR)),RPTCURRENCY="LC",CATEGORY=%SET%)
*ENDWHEN
*COMMIT
What I am doing wrong?

Marcel here is below my logic.
I also would like to tell you that the logics is working in a way that it is giving me results but with the ACTUAL rates not with the BUDGET rates...
Nic
*LOOKUP RATE
*DIM LCCUR:INPUTCURRENCY=ENTITY.CURRENCY
*DIM TCCUR:INPUTCURRENCY=TRANSACTIONCURRENCY.ID
*DIM RATE="AVG"
*DIM RATEENTITY="GLOBAL"
*ENDLOOKUP
*WHEN TIME
*IS 2010.JAN
*REC(FACTOR=LOOKUP(TCCUR)*(1/LOOKUP(LCCUR)),RPTCURRENCY="LC")
*ENDWHEN
*COMMIT

Invalid Dimension SALESACCOUNT in Lookup rule

Hi all,
I craeted a New logic Sales_to_PL and provided the below script. But while validating it I get the message as
"Invalid Dimension SALESACCOUNT in Lookup rule"
Please advice.
// LOGIC FOR BEST PRACTICES - BP_SALES APPLICATION
*INCLUDE SYSTEM_CONSTANTS.lgl
// SEND THE RESULTS to THE PROFIT AND LOSS APPLICATION
*DESTINATION_APP=PROFIT_AND_LOSS
*SKIPDIM=PRODUCT
*RENAME_DIM SALESACCOUNT = Account
*XDIM_MEMBERSET Category <> ACTUAL
*XDIM_MEMBERSET PRODUCT = <ALL>
*WHEN SALESAccount.TRANSFER
*IS "Y"
*WHEN SALESAccount.PROFITLOSSACCT
*IS <> ""
*REC(EXPRESSION=%VALUE%,SALESACCOUNT=SALESACCOUNT.PROFITLOSSACCT,DataSrc="BP_SALESApp")
*ENDWHEN
*ENDWHEN
*COMMIT
// Calculate the FX in the P&L Application after Sales data is Transferred
*RUNLOGIC
*APP = BP_Profit_Loss
*LOGIC = FXTRANS
*ENDRUNLOGIC
Thanks
LAK

As my Dimension name is SalesAccount, I even tried changing the constantsllgl file in server and also the script with same SalesAccount instaed of SALESACCOUNT as shown below. Still it did not work.
// LOGIC FOR BEST PRACTICES - BP_SALES APPLICATION
*INCLUDE SYSTEM_CONSTANTS.lgl
// SEND THE RESULTS to THE PROFIT AND LOSS APPLICATION
*DESTINATION_APP=BP_Profit_Loss
*SKIPDIM=PRODUCT
*RENAME_DIM SalesAccount = Account
*XDIM_MEMBERSET Category <> ACTUAL
*XDIM_MEMBERSET PRODUCT = <ALL>
*WHEN SalesAccount.TRANSFER
*IS "Y"
*WHEN SalesAccount.PROFITLOSSACCT
*IS <> ""
*REC(EXPRESSION=%VALUE%,SalesAccount=SalesAccount.PROFITLOSSACCT,DataSrc="BP_SALESApp")
*ENDWHEN
*ENDWHEN
*COMMIT
// Calculate the FX in the P&L Application after Sales data is Transferred
*RUNLOGIC
*APP = BP_Profit_Loss
*LOGIC = FXTRANS
*ENDRUNLOGIC

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

Validation Rule Error :Invalid Member Name In Lookup ({|0|}) value

We defined fdm validation rule as follows.
|Actual, April, 2010, YTD, ENTITY CURRENCY, Mumbai, TotalAssets, [NONE], [NONE], [NONE], [NONE], [NONE]|-|Actual, April, 2010, YTD, ENTITY CURRENCY, Mumbai, TotalLiabilities, [NONE], [NONE], [NONE], [NONE], [NONE]|= 0
After testing the above rule definition, it gives below error message.
Err = Invalid Member Name In Lookup ({|0|}) value in ID indicates invalid member)
Scenario: ACTUAL [1]
Year: 2010 [2010]
Period: APRIL [83886080]
View: YTD [2]
Entity: MUMBAI [7]
Parent Entity: MUMBAI [7]
Value: ENTITY CURRENCY [-1]
Account: TOTALASSETS [150]
ICP: [NONE] [-1]
C1: [MISSING_VALUE] [-1]
C2: [NONE] [0]
C3: [NONE] [0]
C4: [NONE] [0]
Lookup Error (2)
Err = Invalid Member Name In Lookup ({|0|}) value in ID indicates invalid member)
Scenario: ACTUAL [1]
Year: 2010 [2010]
Period: APRIL [83886080]
View: YTD [2]
Entity: MUMBAI [7]
Parent Entity: MUMBAI [7]
Value: ENTITY CURRENCY [-1]
Account: TOTALLIABILITIES [-1]
ICP: [NONE] [-1]
C1: [MISSING_VALUE] [-1]
C2: [NONE] [0]
C3: [NONE] [0]
C4: [NONE] [0]
Also we could see in the Expression after lookup substitution (scratch pad): we are getting 0-0=0.
Please provide you inputs.

I have not looked closely, but C1 is showing as "Missing Value". Have you checked to see if [None] is a valid member for the account you have selected (TotalLiabilities)?

ExecuteBaseLogic : Invalid Dimension:CATEGORY

Hello SAP Guru,
I have design input schedules using EVDRE() with Time dimension in column and Entity dimension in row. When I send data to database I am getting the following message
Book Name : Test_Comparasion2.xlsx
Application           : ABS_FMCG_PLAN
Status                  : Success
Submitted Count : 1
Accept Count      : 1
Rejected Coount : 0
-Error Message-
ExecuteBaseLOgic : Invalid Dimension:CATEGORY
Please let me know how to rectify the above error message.
Thanks.
With regards,
Anand Kumar

Hi,
It looks like there is a problem with your category dimension. Please try to process the dimension again selecting your application and full process. You ave to check also into Constants.lgl file located into Webfolders\<appset>\AdminApp\<application name> if the cstegorydim is properly assigned to your category dimension.
You acn also have a look into the logic log file located into Webfolders\<appset>\<application name>\Private publications\<user name>\Temp Files, maybe you can find more details about your error.
However, the error is related to default logic (you can retry to validate and save it) and application structure(you can try to modify your application), not to evdre. You will receive the same error trying to send data even using other methods.
Best regards,
Mihaela

Dimension Entity doesn't save allow us to change Reference Dimension

Hello everyone,
My name is Gustavo and I'm working in SAP BPC 7.5 Implementation. The problem that we have is next one:
We create our Dimension Entity and it's got the reference Dimension InputCurrency as default. However we try to change it, because we create our own dimension for Currency.
It allow us to change the Reference Dimension, because it shows us the Dimension we Create, BPC save the changes the result its ok, despite that when we look at the Reference Dimension for Entity and it still shows InputCurrency dimension as default, it doesn't apply the changes we made and BPC doesn't send us any error message.
Has this happen to you?, I hope you can help me.
Thanks for your attention, =)

Hello everyone,
I have already found the solution, the problem i had at the moment of changing the reference dimension, was because I copy from Entity, and in this case I had to create my Entity Dimension since the beginnign without copying it. So in this way I could reference my Entity Dimension to my Currency Dimension.
Thanks everyone.

Dimension Entity - Invalid Parent (error message)

Hi friends,
when we tried to create a new Entity dimension we got a error message, please can you help us in solving this.
Below is the data, we fed into the system (under "MAINTAIN DIMENSION MEMBERS")
ID                evdescription                                                                   parenth1
a1                a1                                                                                AAA
a2               a2                                                                                AAA
The error message was
Dimension 'ZENTITY1's member A1 has a invalid hierarchy parent 'AAA'
why this error message, please can you help us.
and in the property Name,we do not have a property for "PARENTH1", WHEN we tried to create e new property "PARENTH1"
the system was throwing error message
"Attribute name 'PARENTH1' is invalid, please choose another one!"
Thank you and kindest Regards
Srikaanth
Edited by: E.S.Srikaanth Srikaanth on May 1, 2011 11:43 PM
Edited by: E.S.Srikaanth Srikaanth on May 1, 2011 11:45 PM

Hi My Dear Friend,
what I have understood from you explanation is,
Point No. 1)     Hierarchy can be created, by directly adding a column in excel.
                                       and
Point No. 2)     It is not at all possible to add a "PARENTHn" in property name directly. If I try to do so I will be
                           getting an error message.
Please let me know whether above two points are correct, if not please correct us.
Point No. 3) In your point 2, you speak about valid member id, please can you educate us about the prerequisites of a valid member ID. please
Thank You and Kindest Regards
Srikaanth

Using dimension properties in LOOKUP

Hi,
I'm trying to use dimension properties in a LOOKUP, but when I execute the script the log tells me that COMPANY, SALESORG, PRODUCT and TRANSCURRENCY is not defined and therefore create a lookup on all members.
THe usage of properties in LOOKUP is described in the documentation, but somehow it doesn't seem to work for me. Can anyone help me?
*LOOKUP ACTIVITYPLAN
*DIM FCIC:ACCOUNT= "FULLCOST"
*DIM FCIC:PARTNER="I_NONE"
*DIM FCIC:COMPANY=PARTNER.ENTITY
*DIM FCIC:SALESORG=PARTNER.ENTITY
*DIM FCIC:PRODUCT=PRODUCT.PRODREF
*DIM FCIC:TRANSCURRENCY=PARTNER.CURRENCY
*DIM COUNTRY = "CO_NONE"
*DIM DATASOURCE = "INPUT"
*DIM PROFITCENTER = "YB99"
*DIM RPTCURRENCY = "LC"
*ENDLOOKUP
Regards,
Lars
Edited by: Lars Johansen on Nov 4, 2011 10:41 AM
Edited by: Lars Johansen on Nov 4, 2011 10:41 AM

Hi Gersh,
I'm getting closer. I have now tried to use the FOR/NEXT logic on 1 property and it works. I know want to include another. In this case it seems as if the LOOKUP works fine, but the WHEN/REC/ENDWHEN is not. It doesn't recognize my LOOKUP(%LOOP_CU%%LOOP_CO%).
Any suggestions have to solve this problem?
*LOOKUP ACTIVITYPLAN
*FOR %LOOP_CO% = %P_COMP%
    *FOR %LOOP_CU% = %P_CURR%
        *DIM %LOOP_CU%%LOOP_CO%:TRANSCURRENCY=%LOOP_CU%
        *DIM %LOOP_CU%%LOOP_CO%:ACCOUNT= "FULLCOST"
        *DIM %LOOP_CU%%LOOP_CO%:PARTNER="I_NONE"
        *DIM %LOOP_CU%%LOOP_CO%:COMPANY=%LOOP_CO%
        *DIM %LOOP_CU%%LOOP_CO%:SALESORG=%LOOP_CO%
        *DIM %LOOP_CU%%LOOP_CO%:PRODUCT=PRODUCT.PRODREF
    *NEXT
*NEXT
*ENDLOOKUP
*WHEN ACCOUNT
   *IS "QPURC"
               *FOR %LOOP_CU%=%P_CURR%
                   *REC(EXPRESSION=(%VALUE%*LOOKUP(%LOOP_CU%%LOOP_CO%)),ACCOUNT="529996")
                   *END
               *NEXT
*ENDWHEN

Error: Invalid dimension member with special character / in BPC NW 7.5 SP7

Hi experts,
We are encountering the following problem in our Financial Planning application.
We are migrating our existing BPC solution from one server to another through backup and restore. The existing solution was on BPC NW 7.5 SP 5. The profit_centre dimension in the existing solutions has several member ids with special character '/' (forward slash). The dimension never threw an error when processed in the existing solution and there is planning transactional data against these member ids.
While the entire configration , appset , files were successfully restored through UJBR on the new system (BPC 7.5 SP7) through UJBR (backup and restore), the masterdata could not be restored only for this Profit_centre (masterdata for other dimensions were processed successfullu). All the member ids with / are rejected for this dimension. The same error is thrown if processed through the admin client from the member sheet.
Error: Dimension member PC_FF/WS/NT is an invalid member ID
Error in Admin module
Is there any setting which need to be made to allow / character in member ids? Any suggestion to get around this problem would be much appreciated.
Thanks
Abhiman

Hi Abhiman,
Yes, you need to maintain the transformation file to correct all dimension member IDs. Can you please refer to the following link with a similar issue:
conversion file formula not working
Hope this helps.
Rgds,
Poonam

Zeros in invalid dimension intersections

Hi all,
I'm perplexed with a case, when a method writes zeros to invalid intersections, and I can see them in a data grid. The method is like this:
Sub Consolidate()
If HS.Value.Member = "[Parent Total]" Then Call Cons_1
End Sub
Sub Cons_1()
Set objDataUnit = HS.OpenDataUnit("V#[Elimination].A{Accs.[Base]}")
lNumItems = objDataUnit.GetNumItems
For i = 0 to lNumItems-1
Call objDataUnit.GetItem(i, nmAcc, nmICP, nmC1, nmC2, nmC3, nmC4, dtData)
If nmC2 <> "xxx" Then Call HS.Con ("V#[Elimination].C1#" & HS.Custom1.UD1(nmC1) ,-1,"...")
Next
End Sub
Do you have any idea why this method gives 0 on V#[Elimination] for E#Entity, but this intersection is invalid because Elimination value should use nodes instead of entities? I output to log file that this procedure writes 0 to such intersection. And I see it in a grid.
Thank you in advance.

Hi Mary,
Regarding my example, it was a copy paste mistake.
I believe that the reason of the extra zeros is the string: HS.Custom1.UD1(nmC1). If I have understood correct your rule, my way of writing the rule would be similar to:
If HS.Custom1.UD1(nmC1) = "nmC1" and nmC2 = "xxx" Then
Call HS.Con ("V#[Elimination]" ,-1,"...")
End If
In other words, you must remove the UD1 from the Con command.
Regards
Thanos

Programmatic Invalidation of Entity Bean Cache

Hi,
I wonder if there is a way to trigger the invalidation of the WASs Entity Bean cache from a Java program.
Does anybody know anything regarding this issue?
Regards,
Heiko

Hi Heiko,
the SAP EJB container does not support such kind of caching. We support a kind of "read only" entity beans, but you can mark a bean as "read only" only if it will never be updated. Any attempt for update will produce an exception. As a comparison, the JBoss "read only" options can be set for beans that are rarely updated.
This explains why there is no invalidation command in SAP Web AS as well.
We plan the implementation of a similar entity beans cache for the next releases.
I hope this is not a showstopper for your porting project. This kind of caching is usually used with performance reasons, so the fall-back variant would be to define the entity beans as "regular" instead of "read only".
HTH
Regards,
Svetoslav

Error Invalid Dimension - RUNLOGIC

Hello,
I have one application A with account dimension called AAcc and an application B with account dimension called BAcc.
I run a logic from application A calling an B script logic, for example:
At application A:
*RUNLOGIC
*APP = B
*LOGIC = CALC_1
*ENDRUNLOGIC
When I run at the logic debugger, I receive the following error message:
u201CInvalid dimension: AAccu201D
I have to run Calc_1 at the default.lgf as an addition to other calculations I make in application A, but I have to use BAcc accounts for that.
I use BPC 7.0 MS.
Any suggestions?
Thanks in advance.
Best regards,
Sue

Hi Kyle, Kranthi, nilanjan,
Thank you for your reply.
Please see what worked:
*RUNLOGIC
   *APP = B
   *DIMENSION AAcc =
   *LOGIC = CALC_1
*ENDRUNLOGIC
Best regards,
Sue

.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

Recognizing Changes in System_Constants.lgl

I've made changes in the System_Constants.lgl file whereby I've changed the:
*FUNCTION ACCOUNTDIM=ACCOUNT_FS (from the default ACCOUNT)
However when I try to load DATA via the IMPORT Package, the error message I receive is: Invalid dimension ACCOUNT in lookup.
What we're seeing is that any changes in the System_Constraint isn't being reflected (this has happened when we change the Entity Dimension to something else). Our default "Finance" Application is able to load data however, so the issue is for any dimensions we've created and renamed as ENTITY or ACCOUNT, the error seems to occur.
We've done a full process as well, and still receive this error.
Thanks,
Pras

Pras,
After you change the system contants file, you have to recompile all the logic in both the logic file (like fxtrans) and default (if the logic is called from default). That should fix the issue. If it does not, then copy the fx_restatement package in the edata --> and run the logic file individually - that will tell you whether or not the logic is fixed or if there is other logic that is causing the problem. Let me know if you need any other help.
Thanks,
Bart

Invalid Dimension Entity in lookup

Similar Messages

Maybe you are looking for