Hi Markus,
the first effect indicates that the locked cells were not transfered to the back-end; that should happen automatically via the lock command (context menu).You may check this by explicitely trigger a server roundtrip via 'Refresh'. If you now see the locked cells on the second tab the locked cells were not transferred via the 'lock cell' command. You can open a ticket for that.
AO has not yet implement the back-end cell locking functionality. Because of special 'customer logic' in AO, e.g. planning function triggered by AO events, an adjustment of the workbook might be necessary since planning functions reset the locked cells.
The last effect seems to come from missing data for disaggregation: input of 20 would lead to a disaggregation in the lower part of the result set and the locked grand totall 60 would lead to a disaggregation of 60 - 20 to the upper part of the result set. The lower part seems to have no data yet, so disaggregation does not work (010 seems to have no data). Observe that empty cells might be generated by other non-empty cells in the grid. In order to use disaggregation you have to ensure that 'reference' data are available, cf. also the access type for result values settings in the query).
The above messages have long texts, but unfortunately web templates trigger a full server round trip to display the long text; but this again will trigger the error, so the long text will not be displayed. You can put this information also in OSS ticket.
Regards,
Gregor