SAP Knowledge Base Article - Preview

3559097 - How to find out transaction data which is causing overflow - BPC NW

Symptom

You are using normal key figure(20, 7) for the BPC models, the following errors occurrd during "copy environment" or lite optimization.

SM21/HANA index trace:
numeric overflow: TrexColumnUpdate failed on table 'SAPHANADB:_SYS_SPLIT_/B28/XXXXXXX' with error:
AttributeEngine: overflow in numeric calculation;exception 1000013: cannot convert the value to DECIMAL(20, 7) in
checkDecimalColumn(): got invalid value 11450798830462.26 on pos 52821,column '/B28/S_SDATA', table

For some reasons, you cannot enable large key figure and want to find out the data which is causing overflow.


Read more...

Environment

  • SAP Business Planning and Consolidation 10.1, version for SAP NetWeaver
  • SAP Business Planning and Consolidation 11.0, version for SAP BW/4HANA
  • SAP Business Planning and Consolidation 11.1, version for SAP BW/4HANA
  • SAP Business Planning and Consolidation 2021, version for SAP BW/4HANA

Product

SAP Business Planning and Consolidation 10.1, version for SAP NetWeaver ; SAP Business Planning and Consolidation 11.0, version for SAP BW/4HANA ; SAP Business Planning and Consolidation 11.1, version for SAP BW/4HANA ; SAP Business Planning and Consolidation 2021, version for SAP BW/4HANA

Keywords

EPM, BPC  NW, Business Planning and Consolidation for NetWeaver, SAP BPC FOR NetWeaver, overflow, large key figure , KBA , EPM-BPC-NW , NetWeaver Version , EPM-BPC-BW4 , BPC/4 , How To

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.