Diagnosis
The system determined that values already exist in summarizationversion &V3& for investment program &V1&/&V2&.
Writing values again for investment program &V1&/&V2& to summarizationversion &V3& can lead to inconsistencies. Existing data records arenot deleted, only overwritten. However, an existing data recordis overwritten by a new data record only if all characteristicsare the same in both data records.
If there have been master data changes or Customizing changes in themeantime, then it could mean that existing data records are notoverwritten. This would result in incorrect values in reporting.

Example
A plan value of 100,000 was stored for a measure that is assigned tocost center A in summarization version X. The Customizing settingsspecify that the characteristic 'cost center' should be shown in detaildisplay. If you now change the cost center for the measure to B, andthen write the data to summarization version X again, then the existingdata record with cost center A is not overwritten. Instead, asecond data record with cost center B is entered. As a result, the planvalue for the measure could be shown as 200,000 in reports.

Procedure
Make sure that you do not update the same data for an investmentprogram more than once in a summarization version, when changes tomaster data and/or Customizing settings have taken place. If necessary,delete the existing values for the investment program in thissummarization version, or use a new summarization version. You canchoose to delete only specific values within a certain subtree, ordelete only values in specific "value categories" (such as plan fromprogram positions) or only for certain fiscal years.
Updating various "value categories" (such as plan/budget/assigned/userdefined values) at different times is usually not a concern, sincethese "value categories" do not overlap. For the same reason, updatingvalues from different fiscal years at different times also does notusually pose a problem. In both of these cases, the selection can onlylead to undesired results if the the values for different fiscal yearsor for plan, budget, etc. have been stored with differentcharacteristics (such as cost centers).
You may want to include values from different systems or clients in thesame summarization database. In that case, in order to avoid theinconsistency described above, make certain that only oneindividual sub-tree of the investment program is used operatively ineach system or client (that is, that measures or appropriation requestsare assigned only to this one sub-tree). When you use differentsub-trees, there is no overlapping during updating. In any case, youshould still specify that the characteristic 'positon ID' for theinvestment program position is for detail display.