1240163 - Amount Too High by Factor of 100 for HUF, JPY Currencies

2017-01-04

Page 1/5

1240163 - Amount too high by factor of 100 for HUF, JPY currencies Version

12

Type

SAP Note

Language

English

Master Language

German

Priority

Recommendations / Additional Info

Category

Consulting

Release Status

Released for Customer

Released On

26.04.2013

Component

BW-BEX (Business Explorer)

Please find the original document at https://launchpad.support.sap.com/#/notes/1240163

Symptom There are problems with the currencies Hungarian Forint (HUF), Japanese Yen (JPY), Korean Won (KRW), Chilean Peso (CLP) among others. An amount is too high or too low by a factor of 100. The decimal place is moved two places.

Other Terms HUF, JPY, decimal place, decimal, comma, currency, TCURX, internal

Reason and Prerequisites If the number of decimal places is not two, misunderstandings frequently occur when the currencies are evaluated. These currencies are defined as exceptions in the table TCURX with their actual number of decimal places. The internal format of the currency values is always displayed with two decimal places, regardless of how many decimal places were defined for the corresponding currency in the table TCURX. The table TCURX is only taken into account during the conversion to the external format. During maintenance in the table TCURX in Customizing (transaction SPRO -> SAP NetWeaver -> General Settings -> Currencies -> Set Decimal Places for Currencies), there is an explanatory example before you can change the table. This often leads to an incorrect interpretation of values for currencies that are defined with a number of decimal places that is not two. The internal format is displayed: In SE16 in the classic format (PSA table, fact table and so on) In the debugger

The external format is displayed: In the query in PSA maintenance (IMPORTANT: PSA table in SE16 see above) In SE16: When using the ALV display If you display the single record using the "Display" function key (F7)

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-01-04

Page 2/5

and the currency value is also contained in the current table. A currency reference in the table definition of the repository may also point to another table. The internal format is always displayed in this case. You can set the internal format display or external format display: In LISTCUBE

Solution The following example shows the behavior of the example currency JPY with 0 decimal places with the "correct" result. 0) Table TCURX Currency: JPY Number of decimal places: 0 1) Source CSV file: my_cur_field: JPY my_amount_field: 100 2) DataSource with PSA (for the BW 3.X data flow, there is a description in Note160467, for the BW7.X data flow and the settings in the DataSource, see Note 1176399) For this example, the 7.X data flow is used and the following settings were made in the DataSource ("Fields" tab page) for our currency key figure (the thousand separator is not relevant in the example and a period is used for the decimal place): Data Type: CURR Format: External Curr/Unit: my_cur_field After the data load, the following values are contained in the PSA. The TCURX settings are already taken into account by the system during the data load. In transaction SE16, you can see the internal format, in the PSA maintenance, you can see the external format: PSA maintenance: my_cur_field: JPY my_amount_field: 100 PSA table in transaction SE16: my_cur_field: JPY my_amount_field: 1.00 or 100 ( note dependencies of SE16 display type )

3) Data target InfoCube The data is written using a 1:1 transformation with DTP directly from the PSA to the InfoCube and the key figure 0AMOUNT with the currency field 0CURRENCY. Transaction LISTCUBE: +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Note the differences between the displays with the checkbox " Do not use any conversion".

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-01-04

Page 3/5

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ a) "Do not use any conversion" = X This setting means that the values are displayed as they are in transaction SE16: 0CURRENCY: JPY 0AMOUNT: 1,00 b) "Do not use any conversion" "blank" This setting means the TCURX is taken into account: 0CURRENCY: JPY 0AMOUNT: 100 c) Fact table in transaction SE16: AMOUNT: 1.00 or 100 ( note dependencies of SE16 display type )

4) Query The query always takes TCURX into account regardless of the front end (BEx, Web, RSRT) during the determination of the amount. However: The settings in transaction RSD1 in the Query Designer or ad hoc in the workbook and/or Web template may lead to more or less decimal places being displayed (this is described in Note 155837). In our example, there is only one setting in transaction RSD1, the query structure element copies this "default". RSD1: 0AMOUNT (Tab page "Additional Properties") Decimal places: 0.00 0,00 Query result: 0AMOUNT: 100.00 JPY

How can unwanted effects occur? The settings described above are very often combined differently, some of these cases are described below: Case 1:The amount in the query is correct, however, it is saved like a currency with two decimal places. TCURX: No entry for JPY (means standard two decimal places) CSV: 100 DataSource: External format Source CSV file: 100 PSA table in SE16: 100.00 LISTCUBE with conversion: 100.00 LISTCUBE without conversion: 100.00 Query with setting "two decimal places": 100.00 Case 2: The amount in the query is too high by 100. TCURX: JPY with 0 CSV 100.00 DataSource: Internal format Source CSV file: 100.00

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-01-04

Page 4/5

PSA table in SE16: 100.00 or 10000 ( note dependencies of SE16 display type ) LISTCUBE with conversion: 10000 LISTCUBE without conversion: 100.00 Query with setting "two decimal places": 10000.00 Case 3: The amount is rounded up, saved and displayed. TCURX: JPY with 0 CSV 123.56 DataSource: External format Source CSV file: 123.56 PSA table in SE16: 1.24 or 124 ( note dependencies of SE16 display type ) LISTCUBE with conversion: 124 LISTCUBE without conversion: 1,24 Query with setting "two decimal places": 124.00

Case 4: The settings regarding the decimal places (SPRO/TCURX) are not made until the relevant data is loaded and therefore the query displays an amount that is too high by a factor of 100. First the data is loaded as in case 1, and the following status is displayed again. TCURX: No entry for JPY (means standard two decimal places) CSV: 100 DataSource: External format Source CSV file: 100 PSA table in SE16: 100.00 LISTCUBE with conversion: 100.00 LISTCUBE without conversion: 100.00 Query with setting "two decimal places": 100.00 Then you add the entry for JPY in TCURX. However, the values saved in the PSA and the fact table do not change. The conversion delivers another result, which is unwanted in most cases. LISTCUBE with conversion: 10000 LISTCUBE without conversion: 100.00 Query with setting "two decimal places": 10000.00 General notes: Most problems of this type occur when the flat file is loaded. If loading is carried out from an SAP source system, it is important that the BW system and the source system have the same settings in the currency tables TCUR*, otherwise similar effects may occur.

Other Components Component

Description

BW-BEX-OT

OLAP Technology

© 2017 SAP SE or an SAP affiliate company. All rights reserved

2017-01-04

Page 5/5

BW-BEX-ET

Enduser Technology

BW-WHM-DST

Data Staging

This document refers to SAP Note/KBA

Title

1591837

How to analyze query results

155837

Tips & tricks with decimal places

153707

Currency translation miscalculates by 100, 1000..

144699

Decimal places of key figures

1176399

Loading amounts to the BW system; decimal places

This document is referenced by SAP Note/KBA

Title

1591837

How to analyze query results

1176399

Loading amounts to the BW system; decimal places

155837

Tips & tricks with decimal places

153707

Currency translation miscalculates by 100, 1000..

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2017 SAP SE or an SAP affiliate company. All rights reserved