In reporting, the line item breakdown for a report line displays a total which does not correspond to the value in the report line. A value field was added to the operating concern before this happened.
The value field was added in Release 2.1, but Table CE3xxxx (xxxx=operating concern) was not converted following this using the database utility.
The new field is created in the database with an undefined value (zero). When you update actual line items, this undefined value is included in the calculation (total). The result of this calculation is consequently also undefined, and the undefined value remains at the segment level.
The data at the segment level CE3xxxx is now no longer compatible with the corresponding data in line item table CE1xxxx. Reporting reads the undefined value as 0,0 when it builds up the report. The line item breakdown, however, contains the correct values.
The error may be reproduced in several cells, lines or columns of different reports where formulas are calculated.
An upgrade to a later release or a higher maintenance level does not correct the error.
To restore the consistency, you can use note 93051.
- In order to correct inconsistencies, you need to execute Program ZKEREO31 for each fiscal year in which data was posted. The distinction between actual and plan data is technical in nature. You should always reorganize both.
- Note that any summarization data you have for reports is not actualized! It is therefore necessary to rebuild these. It is not enough to simply actualize them online. You can rebuild the summarization data using Program RKEBATCH.
- Any existing summarization levels are not updated. Here too you have to rebuild the levels, i.e. fill them with data again.
KE11, KE23, KE30, drill-down reporting, line item
No comments:
Post a Comment