Skip to Content
author's profile photo Former Member
Former Member

Error when validating LGF files

We created a new application within an appset. This application shares a couple of dimensions with another application, but the Category dimension is unique to this application. We have changed the System_Constants.LGL file to associate the new category dimension.

*FUNCTION CATEGORYDIM=MSR_CATEGORY

For whatever reason, when we validate our default logic file or any file calling this system_cosntants.lgl file, we get the following error message.

"No match defined for lookup dimension CATEGORY"

Does anyone have any idea what I may be doing wrong and how to fix it.

Thank you in advance for your assistance.

Mark

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 30, 2008 at 10:35 PM

    Are you able to do a FULL Process of all the dimensions in the application?

    Run a report in the application; does it see the correct members?

    You can not use an underscore, ("_") in a member name and I don't usualy trust them in a dimension name.

    I would not recommend duplicate member names in the dimensions.

    Chang the System_Constants.LGL file to read as follows;

    *FUNCTION MSR_CATEGORYDIM =%CATEGORY_DIM%

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thank you for the reply, I don't think there is a restriction on using underscores for dimension names. I am going to try the other suggestions first, and if all else fails, I will change the dimension name to not have an underscore.

      Thanks again, I will let you know how it goes.

      Mark

  • author's profile photo Former Member
    Former Member
    Posted on Jul 30, 2008 at 10:35 PM

    Mark

    I hoped you changed the systemconstants.lgl of the app you really need.

    Did you check if the dimension MSR_CATEGORY is stored as a dimention type C.

    Could you check smtg for me: try not to use an underscore for your dimension... and try like this. (not sure, but worth trying...)

    Nic

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 30, 2008 at 11:41 PM

    The change you made to the new applications systemconstants file is correct as stated in your message. The issue is with the running of default logic at the time of the data send. If you enter the logic and "//" comment out the logic and re-run or resend data the process should not show an error. The reason is most likely tied to the running of the FX logic, where a Category set using a select statement is requested. Either the statement or the select statement uses "CAtegory" instead of the new name or a statement such as %CAtegory_Dim%.

    BTW, the use of an underbar in a dimension name should not have any impact on your cubes or design.

    Hope this helps.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 31, 2008 at 06:17 PM

    Hi Mark,

    As Petar clarified, you can have an underscore in the dimension name, I'm just not real trusting.

    The syntax of the function is what I found in the documentation. After Petars responce, I'm not sure which is correct but would trust Petar.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Everyone,

      I believe I found the issue. It does relate to what Peter mentioned about the FX. Although it wasn't a select statement. The issue was that our Rate application uses the same category as our consolidations application. Our new MSR application was trying to use this rate application, so the categories were not in line. Different Category dimension make it diffictult to find which rate you want to use.....

      So we are going to copy the rate application and have it use the same category dimension as the MSR application. And all should be good from that point forward.

      Thank you all for your assistance,,, it is very much appreciated.

      Mark

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.