Incorrect asset reports by 'main number' if subnumber '0' is retired

[Former Member]

Hello,

Asset reports displays the different results when executed with the options of list assets and main numbers. For example asset number X has three sub numbers (0,1,2) where sub numbers 0 and 1 are retired and sub-number 2 exists. When asset reports are executed with the option of 'display main number', no assets are shown. When asset reports are executed with list assets, sub-number 2 is selected. e.g. S_ALR_87011990 - Asset History Sheet

Any ideas how to avoid this kind of problem. Please suggest.

Regards,

[Former Member]

Each sub asset is an asset by itself. However Sub asset 0 is considered as main asset. It is the functionality. If you retire this sub asset no values are selected in Main number only option is selected.

To get the values select the Group Totals Only option and double click on the respective asset class you will get full details of assets

[former_member188826]

Refer to note 648307

If you start an Asset Accounting report that uses the logical database ADA and you select the "or main numbers only" option, the system may terminate this with error AB 064 "No data was selected". However, if you change the selection to "List assets" or "or group totals only", the system generates an output list.

Solution

Implement the attached source code corrections.

If the above does not work, then try this note 331799.

Symptom

The system needs an extremely long time to create an acquisition list for example, if the assets have subnumbers, however, the report should be summarized to main asset numbers. If the list is completed at all, it contains far too many transactions. If you select 'List assets' instead of '...or main numbers only', the system displays the list correctly after an appropriate amount of time.

Cause and prerequisites

If there is a table in the view to be read and the subquery, the database returns vast numbers of identical entries.

Solution

Implement the attached program corrections into your system.

[former_member188826]

These are applicable only for release 4.7 or less. None could be traced for ERP5.

[Former Member]

Send a note to OSS and ask if the note is relevant for the new releases.