2085589 - Extending an Amount Key Figure of Currency Type in BW

• You have the business requirement to extend an Amount Key Figure of Currency Type in BW.
• You are using the "Use your own domains" approach as listed in Note 460652.
• The extended Amount Key Figure uses a customer domain in which you have enlarged the number of decimal places
• After this, the currency conversion in a BW query gets wrong results.
• Or a BW query displays wrong decimal places in the query result.
• Or in a planning function, the CURC calculation in a fox formula delivers wrong results.
• Or a query or a planning function hits error as below:
  

  Error during deserialization/When converting the value  xxxx the values
  after the decimal place were lost [XSLT Info: CLASSNAME = CX_SY_CONVERSION_LOST_DECIMALS,
  PARAMNAME = ITAB, COLUMNNA
  Message Number 00 001
  Error Error during deserialization/When converting the value  xxx the
  values after the decimal place were lost [XSLT Info: CLASSNAME = ...
  Error CX_SY_CONVERSION_LOST_DECIMALS, PARAMNAME = ITAB, COLUMNNAME = Z____xxxx_SUM,
  ROWNUMBER = 1]/[Target Field Info: ABAP Type = P, Length = xx, ...
  Message Number DBMAN 099
  Error Decimal = x]/[Request Info: Object Name = xxxxx, FM Name = TREX_DBS_AGGREGATE]
  Message Number DBMAN 099
  Error Error 1.699 has occurred in the BWA/SAP HANA server
  Message Number DBMAN 901
  Error Error reading the data of InfoProvider xxxx
  Error Error while reading data; navigation is possible
  Information CL_RSDRH_TREX_STORAGE >> Row: Inc: 5 Prog: RETURN_TREX_MSG

• BW system
• Release independent

RSKYFAMO, FLTP, TCURX, CURR, 0amount, CX_SY_CONVERSION_LOST_DECIMALS, deserialization, Error during deserialization, converting, DBMAN099, 1699 , KBA , BW-BEX-OT-OLAP , Analyzing Data , BW-PLA-IP-PF , Planning Functions and Planning Sequences , How To