Start of Content Area

Procedure documentation Lowest level entry  Locate the document in its SAP Library structure

For this entry level, the function modules generated for data processing are available.

Call the function module VIEW_MAINTENANCE_LOW_LEVEL. Knowledge of the view or table-specific function module name for the data processing is not necessary, as it is put together by the system and then called.

Pass the name of the table or view and the desired function when calling. You must evaluate the returned user commands.

You must also perform all the activities which the maintenance dialog otherwise performs:

Interface description

Import parameters

Export parameters

You must process the following commands yourself on this entry level:

If this command is returned, you must call the lowest entry level function module again with this command and then with the previous command. You do not have to write your own re-set program.

Example

The lowest entry level was called with the module VIEW_MAINTENANCE_LOW_LEVEL and the function 'EDIT'. The user has called the function 'ORGL'. The module VIEW_MAINTENANCE_LOW_LEVEL has now to be called first with the function 'ORGL'. The module runs in the background. Then the module VIEW_MAINTENANCE_LOW_LEVEL has to be called again with the function 'EDIT'.

see command 'ORGL' for command processing.

The user has made changes which make it necessary to save the data before leaving the maintenance dialog.

Tables

Structure: INCLUDE STRUCTURE E071K

Structure: INCLUDE STRUCTURE VIMSELLIST see function module VIEW_MAINTENANCE _CALL documentation.

All data which are read in for the table processing or are created during maintenance, are stored in the internal table TOTAL at run time.

The table TOTAL has the structure:

See also the function module VIEW_MAINTENANCE_CALL documentation.

Structure and documentation as DBA_SELLIST

The data are stored at run time in the internal table EXTRACT. The table EXTRACT always only contains the table records which have been filtered out of the table TOTAL as a result of a user action.

The table EXTRACT has the same structure as the table TOTAL

See also the documentation of the function module VIEW_MAINTENANCE_CALL

Structure: INCLUDE STRUCTURE VIMEXCLFUN, see function module VIEW_MAINTENANCE_CALL documentation.

Structure:

All data which are read in for the table processing or are created during maintenance are stored at run time in the internal table TOTAL. After the function has been carried out, the table gets a processing flag for each record processed.

Structure as table TOTAL

The data are stored at run time in the internal table EXTRACT. The table EXTRACT always only contains the table records which have been filtered out of the table TOTAL as the result of a user action. After the function has been performed, the table contains all the data found by the last selection for display.

Structure: INCLUDE STRUCTURE VIMDESC

The table contains the Dictionary header information about the table or view, such as sub-set, selection conditions, maintenance status, delivery class. The table also contains the generation information and event time information for the table or view. You can fill this table with the function module VIEW_GET_DDIC_INFO.

Structure: INCLUDE STRUCTURE VIMDESC.

The table contains the field information about the table or view, from the dictionary such as the position of the field in the structure, key information and the maintenance characteristics of the field. You can fill this table with the function module VIEW_GET_DDIC_INFO.

Exceptions