ERROR BRAIN (449): Formal error in query definition (DIM <-> FROM[NAV])

[Former Member]

Hi,

Whn i run my query, i am getting this error.

ERROR BRAIN (449): Formal error in query definition (DIM <-> FROM[NAV])

MSGV1: 0COMP_CODE

MSGV3: NAV

Please help me out.

[Former Member]

Hi guys,

guess why i hit this thread?

Well, in BEx3.5 query designer i have created a new mandatory query variable on 0CALYEAR and dragged it right into the free characteristics area. then i got confused by the BRAIN449 message. then tried all the awkward things like closing and re-opening my BW-sessions, doing the same for the query designer session. Both didn't help much.

Then i found the details: Having a sharp look at the query definition i have found that the leading and trailing "&"-signs were missing for the variable name which i had dragged to the free chars area. I did a double click on this item, confirmed the assignment by clicking 'OK'. Saved the query definition again.

And the query worked fine!

Hopefully this helps you as well!

Cheers and suxxess!

Harry

[surya_prasad9]

Hi,

Are you able to solve the issue? The issue may be with your Formula with Replacement path, Please check the query definition thouroughly.

I got the similar error, which I resolved.

Please let me know more information, I will try to give you correct solution to your issue.

Regards,

Surya

[Former Member]

Hi,

Did you figure out how to fix this? We are facing the same error with some navigational attributes.

Thanks!

Kathleen

[Former Member]

Hi all,

Finally I figured out that the problem was the filter on the navigational attribute. I removed it and re-added it and the problem is now solved.

Kathleen

[former_member225306]

You have to change the mapping for non-cumulative cubes,

"Time characteristics has to be mapped with time

characteristics only".

[Former Member]

Hi Harsh,

Are you from Delhi, if i am correct. I am Srinivas and we attended trng in Kolkata.

Well, for your problem, check your query definition thoroughly, If you are maintaining a variable, which is not available or if you are maintaing cell definitions. Please let me know along with fields and restrictions and structure.

Best Regards,

Srinivas

[Former Member]

Hi Srinu,

You got me right buddy. M in HCL now.

How are you?

Actually my query shows no error in Devlopment.

But when i transport it to quality, i am facing this error.

I have checked the query definition.

I will again give it a look.

[Former Member]

The reason could be the one Navigation attribute you are using in the query is navigational attribute in Dev and it is included properly in Cube and Multiprovider, but when you transported that to Quality, you may not have that as navigational attribute or may not have included in the cube and multiprovider.

In short, your backend object may be different in Dev and Quality.

Please check it.

- Danny

[Former Member]

hi experts.

i tried all the above options but it is not solved,in my query there is no navigational attributes. if anyone got thesolution plz tell me.thanks in advance.