cancel
Showing results for 
Search instead for 
Did you mean: 

SAP HANA LIVE - Calculation View compilation error

0 Kudos

Hi,

My  SAP ECC is 6.0 EHP 7 on SAP HANA (ver. 1.00.096.00.1432206182). I'm installed SAP HANA Live objects - HCOHBAECC10_SP10.

When I've compiled objects i got  error.

In

"sap.hba.ecc::FinacialStatementStructure" - error:

Short Text

  Cannot convert the filter expression to a valid query

Cause

  Invalid syntax used in your filter expression

Recommendations

  Use valid syntax in your filter expression

Error Message

  Internal deployment of object failed;Repository: Encountered an error in repository runtime extension;Internal Error:Create Scenario failed:

  Expression is not valid: Evaluator: type error in expression evaluator;string string(plus(plus(string '$', [here]lpad(fixed8_6 "PARENT", int '6', string '_')), lpad(string "FunctionalArea", constant_integer_2 '20', string '_')))(CalculationNode (BETWEEN_JOIN) -> attributes -> calculatedAttribute (ID) -> expression)

  The following errors occured: Inconsistent calculation model (34011)

  Details (Errors):

  - CalculationNode (BETWEEN_JOIN) -> attributes -> calculatedAttribute (ID) -> expression: Expression is not valid: Evaluator: type error in expression evaluator;string string(plus(plus(string '$', [here]lpad(fixed8_6 "PARENT", int '6', string '_')), lpad(string "FunctionalArea", constant_integer_2 '20', string '_'))).

  - CalculationNode (ALL): Datatype string(27) of ID does not match to datatype fixed6.0(6) of attribute ID in node NormalItem.

  - CalculationNode (ALL): Datatype fixed6.0(6) of PARENT does not match to datatype string(6) of attribute PARENT in node Join_29.

  - CalculationNode (ALL): Datatype string(6) of NEXTN does not match to datatype fixed6.0(6) of attribute NEXTN in node NormalItem.

What's wrong?

Artur

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Artur,

Have you checked all the dependent views of this calculation View sap.hba.ecc::FinacialStatementStructure?

May be the dependent views are inactive?

May be the dependent tables are not in place?

Kindly check and update.

thanks,

adlin