Technical background
Maintenance dialog flow
When a maintenance dialog is called, the table/view entries are read from the database into an internal buffer and are then presented on the screen for maintenance. The read range can be restricted.
The use of internal tables means that field content changes do not immediately result in database changes. The changes are copied from the internal buffer to the database when saving.
Depending on the recording routine of table or view, delivery class, maintenance object description, and, for client-dependent objects, on the client setting, the system logs the changes in a change task when saving them.
Components of a dialog
A table maintenance dialog has view/table-specific and independent program components. The view/table-independent parts are:
The view/table-specific parts of a maintenance dialog are:
Transport changes
Maintenance dialog changes
The generation environment is connected to the transport system, i.e. all maintenance dialog generation activities are automatically logged in a change request. Thus, you can transport the entire maintenance dialog into other systems or clients.
Table/View contents changes
There are two conditions for the automatic recording and transport of table/view contents changes:
The changes are only put in a transport request and can be transported if both conditions are fulfilled.
Change authorization and recording obligation are affected by 3 parameters:
Dialogs:
are not transported and are not considered further.
Change authorization
Table/view contents with the following settings must not be changed (and are not put in a request):
1. |
Parameter |
Value |
|
Client |
no changes allowed | |
|
maintenance objects |
CUSY or CUST |
2. |
Parameter |
Value |
|
Client |
no Repository changes allowed | |
|
maintenance objects |
SYST |
3. |
Parameter |
Value |
|
Client |
no client-independent customizing changes allowed | |
|
maintenance objects |
CUSY |
The following combination of settings is a special case:
Parameter |
Value |
Client |
|
maintenance objects |
|
Changes are allowed, but they are not transported. This combination of settings is chosen when changes are to be made directly in the productive client.
Recording obligation
The following changes must be recorded:
Call the maintenance dialog
You can call the generated maintenance dialogs in various ways:
Enter the name of the table or view. Choose Maintain to go to the generated maintenance dialog. This call is possible immediately after generation.
A parameter transaction must be defined before the call. This is useful e.g. if the table/view and the action (maintain or display) are known.
You can use this call, e.g. if a special context-dependent selection is required. You can enter the dialog at various levels. Depending on the entry level, you may have to program certain activities yourself which are usually performed automatically by table maintenance.
The maintenance dialog performs the following activities:
See also:
Extended function library applications - Extended table maintenance