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

Similar Messages

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

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

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

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

Jabber for IPhone and Directory lookup rules.

At a client I have some problems with getting the Directory lookup rules to work.
I AD the costumer has formatteded the telephoneNumber in this format: +45 4444 XXXX
That is with 2 spaces in the phonenumber.
With Jabber for windows,cups, cucilync etc i have the choice of using "PhoneNumberMasks", so that I avoid the problem with the spaces.
But how do i do it with the directory lookup rules.
I need to make sure that I can do a lookup on 3 different calls.
Full E164 numer:     +454444XXXX
National number:     4444XXXX
Local call:               XXXX
Alt the moment i have those rules in place, but somehow I'm not getting the search for 8 digets national call.
<DialRules>
<DialRule BeginsWith= "4444" NumDigits="8" DigitsToRemove="4" PrefixWith=""/>
<DialRule BeginsWith= "+454444" NumDigits="11" DigitsToRemove="7" PrefixWith=""/>
<DialRule BeginsWith= "" NumDigits="4" DigitsToRemove="0" PrefixWith="+454444"/>
</DialRules>
I'm at a lost to why it's not working with 8 digtes?
Br
Kim Nielsen

Should still work. But would be good to check indial into jabber with the phone unplugged, just for testing purposes.
also, you have checked the partition and configuration on the TAB device is the same as on the deskphone?
Can you attach call manager traces when making a test call and attach to the case. Let us know the extension and device names you have used in the test, and a timestamp of the test.
thanks
=============================
Please remember to rate useful posts, by clicking on the stars below.
=============================

Load Parent-Child dimension with attributes by rule file

Well, I've cracked my head open while banging against this wall.
Task is plain & simple:
How can I load build dimension from such table, using rule file?
Data
ProductParent ProductChild ProductAttribute
Balls Ball_8 Round
I want to load both product dimension and attribute by single rule file (neither of these dimensions exists in database before load), so I do the following:
1) Set dimension build settings, creating dimension Products (marking it P\C generated, sparse), having an attribute dimension AttributeDim
2) Mark the fields as Parent, Child and AttributeDim of dimension Products
After loading rule file a get three types of errors:
a) "Base member (Balls) association level does not match base dimension association level" -- does this mean that I cannot assign attributes in P\C way?
b) "Record #327 - Can not uniquely identify member by Balls (3335)
Balls Ball_8 Round" -- That's strange, I thought member should be identified by Ball_8 (and this column is unique)
c) "\\Record #418 - Error in association transaction [Ball_8] to [Round] (3362)"
I've read all I could find on topic from this forum, network45 board and going to start my way through metalink3, but maybe some kind soul will rescue me from drowning in information ocean?

Hi,
Outline is blank at the start of load and I expect dimensions Product and ProdAttribute to be added.
Generations are unapplicable, since I can't turn this parent-child dimension (it's ragged) into generation one.
And, by the way Integration Services manages to do this somehow, why rule files wouldn't?

Can I pass the selected member at page dimension to form business rule?

I have a business rule which will be executed when the form get loaded, the business rule is very complex, so I want to narrow down the calculation by passing the selected member at page dimension to the business rule.
For example, I have year as page dimension, and I only want to calculate the selected year at one time? How can I do it?
I know runtime prompt, but I don't think it's a good way, since you need to select again.
Thanks
Tony

You can use a variable and a run time prompt.
You can set the business rule options in planning to "Use Members on Form" and "Hide Run time prompt"
This way the page/pov member will be passed into the business and into the variable.
Cheers
John
http://john-goodwin.blogspot.com/

Import varying attribute dimension (with a load rule)

How do I maintain varying attribute dimensions in a model with a large base dimension? It does not make sense to manually maintain all those members in the outline.
Is it possible to import varying attribute dimensions (with a load rule)?

That is true for regular attribute dimensions. Nowhere, I have found instructions how to do this for varying attribute dimensions (aka slowly changing dimensions) that change over time.

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

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

Alternate hierarchy dimension build with load rules

Hi,
I am trying to build a alternate hierarchy dimension using load rules (I feel using EIS is easier to build ASO and multiple hierarchies but we r trying to get rid of EIS member loads). Looking at different posts my understanding is it has to be done using two different rules file first to build the stored hierarchies then use parent-child reference to build the shared hierarchy. Below is the link for the picture how I am trying to build the dimension. I've tried different possibilities but no luck, I am having a tough time to come up with a way to do this using rules file.
http://s24.postimg.org/u5hl4eyqt/basis.jpg

If your file is in a parent/child order, then you can build easily in one rule. make sure the primary (stored Hierarchy) gets built first followed by the alternate hierarchies. I suggest adding a SortID column to the source so you can sort the file to get it into the right order. You can also build the alternate hierarchies using level or generation builds in one load rule, but especially if you have a lot of alternate hierarchies or members, then the parent/child method is easiest.
Read in the DBAG about parent/child files and it will give you more info

Reg: Building Essbase dimension using SQL in rule file

Hi,
We are using Essbase 11.1.2.2. I am trying to build a dimension in a cube using SQL query in the rule file, but i am not able to do it.
I am not able to establish connection to database. Can anyone please give a step by step process to do this.

If you really, really, really want to do this --- and by that I mean really get rid of everything in a dimension, create a dummy file with a single child. That single child should have a name that could never exist in your system. Something like "Forty-seven ginger headed sailors". Then set the Dimension Build Settings Member Update to "Remove Unspecified". Run the dim build -- it will clear out all of the dimension.
Then take your other dim build rule file and use the same Remove Unspecified setting. That will get rid of the silly member. The source can be a file or SQL.
Ta da, you have now cleared out the dim, added a single silly member, cleared out the dim again, and loaded the right members into it.
There may be a better way to do the above, but I have done exactly that and it works.
Regards,
Cameron Lackpour

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

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

Invalid Dimension SALESACCOUNT in Lookup rule

Similar Messages

Maybe you are looking for