#SYNTAX error while creating a Webi report

[Former Member]

Hello Everyone,

I am using SAP BI 4.1 support pack 3 (14.1.3.1257). I am creating a Webi report using two BEx query with merge dimension and getting #SYNTAX error. Actually problem is when I create some calculated variable in report everything is working fine but suddenly all calculated variable disappear with #SYNTAX error.

Please see the attachment..

Could you please help me on that issue?

Regards,

[former_member285534]

Hi Ritesh,

#SYNTAX occurs when a formula references an object that no longer exists in the report.  If the cells contains no longer existing objects or formulas referencing no longer existing objects you get this error.

Arijit could be right.   The no longer existing object might be a merged dimension in your formulas (or directly in your cells) that was unmerged later.  If that happened webi would have replaced the object with a dummy text.  Merging back again the dimensions does not bring back the original objects.  You must place the new merged dimensions back in the formulas or cells manually.

[Former Member]

Thank for your prompt reply...but one thing I am unable to understand,how the variable has been disappeared from webi panel. It happen once or twice but I thought it happen accidently..but now again the variable which I created in webi level has disappeared. Can you put some input on this also.

Could you put some input on this also?

Regards,

[arijit_das]

Sometimes, due to poor network connection or some other reason, if the report is not saved properly then such thing is possible. Otherwise, if it is saved properly, then the only way the variables can disappear is if someone deletes them. Anything else would be really weird.

You can try restarting the webi processing servers in CMC, but I am not sure if that will be helpful to you or not.

[former_member285534]

I had never seen variables disappearing by themselves, but I have seen some other weird behaviours (corrupt data and inexplicable # errors within tables), specially when I have lots of calculations (variables) and big data sets.  When those things happen, if I save the "corrupt" report, when I open it back again it stays corrupt and I have no other choice than remaking it or reworking from a previous .wid version.  If your .wid is corrupt maybe your only choice will be to reconstruct it from scratch and back up often your .wid to be prepared if same situation happens again.

[arijit_das]

I can see no variable created in the screenshot. If you are using formula in those cells containing merged dimension, did you by any chance unmerged and merged the dimension after creating the formulas for the measures ?

[former_member285534]

Hi Ritesh,

Is Calendar Year/Month the standard 0CALMONTH for both queries?  If not check data types match exactly at the bw layer.

Is Calendar Year/Month the only dimension in the table?  The second column's header is also showing #SYNTAX... weird !.

If you used the merged dimension in the table's first column, have you tried using Query 1's or Query 2's dimension instead (without unmerging)?  Or viceversa if you're not using the merged dimension...  You can try changing the dimension and see if things work different.

Difficult to give a valuable advice...  looks like there's a problem with that version.  This might be an obvious or a silly advice, but before reporting a bug to sap or looking somewhere else...  have you tried recreating your bics connections and the report?

Check all the parameters of your olap bics connection are OK.  I had a similar experience one occasion I accidentally mixed dev and prd parameters by mistake in a prd connection.  The connection was working but the report had erratic behaviour like #SYNTAX or #UNAVAILABLE.

Regards,

Fernando