SAP Knowledge Base Article - Preview

2517111 - BPC Parameter reading dump 'cannot be interpreted as a number'

Symptom

You fail to create a BPC Embedded environment with the following dump (The number may be different):

Category ABAP programming error
Runtime Errors CONVT_NO_NUMBER
ABAP Program CL_RSBPC0_PARAM===============CP
Application Component BW-PLA-BPC-INF
Date and Time 09.08.2017 19:49:00

Short Text
"500##" cannot be interpreted as a number

Note: CL_RSBPC0_PARAM is the class of reading BPC Embedded Parameters. You may see similar dump in class CL_UJ0_PARAM, which is for reading BPC standard parameters.


Read more...

Environment

  • SAP BusinessObjects Planning and Consolidation 10.0, version for SAP NetWeaver
  • SAP BusinessObjects Planning and Consolidation 10.1, version for SAP NetWeaver

Product

SAP Business Planning and Consolidation 10.0, version for SAP NetWeaver ; SAP Business Planning and Consolidation 10.1, version for SAP NetWeaver

Keywords

BPC, environment, parameter, cannot be interpreted as a number, CONVT_NO_NUMBER, CL_RSBPC0_PARAM, CL_UJ0_PARAM , KBA , EPM-BPC-NW , NetWeaver Version , BW-PLA-BPC , BPC 'embedded model' , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.