Universe Designer Error - parse failed Invalid definition UNV0023

[Former Member]

Hi,

We are using SAP Business Objects Enterprise XI 3.1 SP3 along SAP Integration Kit XI 3.1 SP3 on the server and SAP Business Objects Client Tools XI 3.1 SP3 along SAP Integration Kit XI 3.1 SP3 on the client machines.

We have created a Universe based on an existing BW query.

When we execute the Integrity check, the parsing check fails for the condition.

Condition : <OPERATOR VALUE="AND"><FILTER KEY="[!V000015]"><CONDITION OPERATORCONDITION="Equal"><CONSTANT TECH_NAME="@Prompt('Currency Type','A','Indicator\LovCurrency TypeBase',mono,primary_key,,{'B0':'[0CURTYPE].[B0]'})"/></CONDITION></FILTER><OPERATOR VALUE="AND"><OPTIONAL><FILTER KEY="[!V000014]"><CONDITION OPERATORCONDITION="Equal"><CONSTANT TECH_NAME="@Prompt('Unit of Measure','A','Indicator\LovUnit of MeasureBase',mono,primary_key)"/></CONDITION></FILTER></OPTIONAL><OPERATOR VALUE="AND"><OPTIONAL><FILTER KEY="[!V000012]"><CONDITION OPERATORCONDITION="InList"><CONSTANT TECH_NAME="@Prompt('Profit Center','A','Indicator\LovProfit CenterBase',multi,primary_key,,{'1000/1040':'[0PROFIT_CTR].[10000000001040]'})"/></CONDITION></FILTER></OPTIONAL><FILTER KEY="[0P_VERS]"><CONDITION OPERATORCONDITION="Equal"><CONSTANT TECH_NAME="@Prompt('Plan Version','A','Indicator\LovPlan VersionBase',mono,primary_key,,{'0':'[0VERSION].[000]'})"/></CONDITION></FILTER></OPERATOR></OPERATOR></OPERATOR>

Error : parse failed Invalid definition UNV0023

Has anyone encountered this error? Different SDN forum posts indicate the same error for Client tools SP2 and in some case it is mentioned that the problem will be resolved in Client tools SP3.

We are already on SP3, but are encountering the issue.

Is there a solution available?

Any help will be appretiated.

Thansk and Regards

[Former Member]

Hi,

Since there are no response, we just moved on and created the report, which works fine.

Thanks

[Former Member]

In @Prompt syntax, after Mono/Multi , one has to give Free/Constrained , if don't want to give just leave (lov,mono,,) --lov,mono,<F/Con>,

Just a guess. See how it works for you.

Thank You!!

[Former Member]

Hi,

Thanks for your suggestion. I will try ot out.

Regards

[Former Member]

Hi, just so you know, primary_key takes the place of mono or constrained in this case. It is a valid option that makes use of the Index Awareness feature or - in this case - the structured nature of the cube data.