Maintenance view variants for modified dialogs
Modified maintenance dialog view variant creation notes:
Different screen field and maintenance view field names
In maintenance view variant data maintenance, all screen output fields which are excluded or given the maintenance attribute 'H' in the view variant definition, are hidden. This is not automatically the case if a view field is replaced in the generated screen by another field, e.g. when a field is resolved into radio buttons or for fields of type floating point number, or the division of an oversized field. If such a field is not specified, or does not have the maintenance attribute 'H', in the maintenance view variant, it still appears on the generated maintenance screens. To prevent the field being displayed, a module which deactivates the field in variant maintenance must be put in the screen PBO.
This also applies to fields which are on the screen, but not in the view, e.g. if in an entity name is read in a user module und output in a field which is not in the view. Such a field is also not hidden in the maintenance view variant. This must be done in a user module.
Save
When you save in the maintenance dialog, all maintenance view fields (including those which are not in the variant) are saved. This is normally not a problem, as fields which are not in the variant are not changed in the variant maintenance, so the original value is written back.
If fields which are not in the maintenance view variant are filled or changed in the background in a user module, these changed values are also 'incorrectly' written to the DB.
Transport data
Only the fields in the variant are transported. Fields which are changed in user modules and are not in the maintenance view variant are also not transported. Maintenance view transport events apply.