SE16n result not consistent

[Former Member]

Hi All,

When trying to debug the issue, the values in DMBTR are correct and consistent with what's displaying in the alv report. But when I display the entries in SE16n, the values are not correct.

I already tried changing my user settings but still issue still persists.

Do you have idea why the values displayed are incorrect?

Thanks,

Trixa

[Former Member]

Hi All,

When trying to debug the issue, the values in DMBTR are correct and consistent with what's displaying in the alv report. But when I display the entries in SE16n, the values are not correct.

I already tried changing my user settings but still issue still persists.

Do you have idea why the values displayed are incorrect?

Thanks,

Trixa

[ThomasZloch]

Quite likely an issue of internal and external representation. What currency is this? Is it configured as having 3 decimals, by any chance?

Please check value of TCURX-CURRDEC.

Thomas

[Former Member]

Hi Thomas,

No, it has a value 0 in TCURX.

Thanks,

Trixa

[ThomasZloch]

Then it seems like the second screenshot (SE16N?) is correct, as it displays the value "10.185" without decimal comma.

In the first screenshot, obviously your ALV list, the value does not seem to reference the correct currency (T001-WAERS), so it displays in the internal format "101,85" (internally it's always 2 decimals for DMBTR).

What is the expected, correct value for your example, tenthousandonehundredeightyfive or onehundredandonepointeightyfive?

Thomas

[Former Member]

It should be onehundredandonepointeightyfive.

[ThomasZloch]

How does this compare to a currency with 0 decimals notation? Which currency are we talking about? What value does FBL5N show for the same document, as Raymond suggested to check?

Thomas

[Former Member]

when using SE16N the currency key is not used for displaying the amounts, the default of 2 decimals is used then, so the amounts will be in your situation 100 times to small.

SE16N is only a view on a database table and there is no intelligence in the display as would be when you use normal trasactions, where the number of decimals is 0 for your currency.

[Former Member]

As of my knowledge se16n does care of reference fields, but they have to be mapped to the specified record via SE11 (in other words, they simply can not reference another "dynamic" structure, that is not known / filled when se16n is shown).

[PankajJain777]

Hi Trixa,

In field catalog did you check attributes for the the currency field DMBTR e.g.

t_fieldcat-datatype = 'CURR'.

t_fieldcat-currency = fu_curr.(eg USD or INR)

[RaymondGiuseppi]

Look at BSID with SE11 -> field DMBTR is referencing currency T001-WAERS, as SE16N does not read data in other database table for such reference field, it displays data ignoring currency code if not in the same structure. You could execute the Consistency Check on SE16N grid, you will notice the warning raised for missing currencies fields.

Better check data consistency with a transaction like FBL5N.

Regards,
Raymond

[former_member585060]

Hi,

Try to check SAP Note 1571782 :– SE16: Currency or quantity conversions in ALV display. See if this can be implemented to your system.

Thanks & Regards

Bala Krishna

[RaymondGiuseppi]

Alas that wont solve the problem on BSID : 1571782 - SE16: Currency or quantity conversions in ALV display

However, a reference field that is not in the same table is not transferred to the ALV (therefore, the currency key field T001-WAERS that is assigned to the currency amount field BSEG-DMBTR is not transferred for example). Only a specific application program can fill such a reference field in time with suitable values; this is impossible for the Data Browser as a generic table display program.

For BSID like BSEG the T001-WAERS field wont be available in generated report.

Regards,
Raymond

[Former Member]

I found the solution. Thanks for all the help guys.

[Former Member]

and how did you solve this?

[Former Member]

I updated the following fields:

fieldcat-datatype = 'CURR'.

fieldcat-currency = currency

[PankajJain777]

same thing i suggested you trixa

[Former Member]

you wrote, that the errorneous value was in the se16n. So how can you change the fieldcatalog there?

[Former Member]

Sorry for the confusion.

As I further investigated with other system, we found out that se16n results are correct based on the accounting document.