Get Functional Enhancements
Use
Before you start modifying, you must identify all tables with functional enhancements.
You can search for the functional enhancements of a maintenance dialog in a function group with either the program RSVIMT_NON_UC_VIM_AREAS, or the main program of your generated function group.
Get Functional Enhancements from the List of the Program RSVIMT_NON_UC_AREAS
The list contains all maintenance dialogs and view clusters which satisfy the selection, with their maintenance screens and events. You can go from the list to the event form routines and the screens.
The following PBO and PAI modules belong to the standard view maintenance and must not be changed:
|
PBO |
PAI |
|
DETAIL_INIT |
COMPLETE_viewname |
|
FILL_SUBSTFLDS |
CONSISTENCY |
|
LISTE_DEACTIVATE |
DETAIL_EXIT_COMMAND |
|
LISTE_INITIALISIEREN |
DETAIL_PAI |
|
LISTE_SHOW_LISTE |
DETAIL_SET_PFSTATUS |
|
VIM_MODIF_DETAIL |
LISTE_AFTER_LOOP |
|
VIM_SUPPRESS_LISTE |
LISTE_BEFORE_LOOP |
|
LISTE_EXIT_COMMAND |
|
|
LISTE_INIT_WORKAREA |
|
|
LISTE_MARK_CHECKBOX |
|
|
LISTE_UPDATE_LISTE |
|
|
SET_TXT_UPDATE_FLAG |
|
|
SET_UPDATE_FLAG |
|
|
TEMP_DELIMITATION |
|
|
VCL_HELP_VALUES |
All other PBO and PAI modules contai individual coding which you must check.
Get Functional Enhancements with the Main Program of a Generated Function Group
Assuming that the function group SCP4 contains functional enhancements in the form of form routines and its own PAI modules, as well as the generated sources. There can also be user-written function modules which have nothing to do with the view maintenance.
*---------------------------------------------------------------------*
* generated viewmaintenance function pool
* generation date: 16.05.1995 at 13:34:05 by user MITTELSTEIN
*---------------------------------------------------------------------*
********************************************************************
* System-defined Include-files.
*******************************************************************
INCLUDE LSCP4TOP. " Global Data
INCLUDE LSCP4UXX. " Function Modules
*******************************************************************
* include-files generated by view maintenance tool *
*******************************************************************
* view related include-files (never change, please) *
INCLUDE LSCP4F00. " subprograms
INCLUDE LSCP4I00. " PAI modules
* general include-files (never change, please) *
INCLUDE LSVIMFXX. " subprograms
INCLUDE LSVIMOXX. " PBO modules
INCLUDE LSVIMIXX. " PAI modules
*******************************************************************
* User-defined Include-files (if necessary). *
*******************************************************************
* INCLUDE LSCP4F01. " Subprograms
INCLUDE LSCP4O99. " PBO modules
INCLUDE LSCP4I99. " PAI modules
All highlighte Includes contain individual coding: Include LSCPUXX contains Include statements for modules belonging to the function group.
******************************************************************
* THIS FILE IS GENERATED BY THE FUNCTION LIBRARY. *
* NEVER CHANGE IT MANUALLY, PLEASE! *
*****************************************************************
INCLUDE LSCP4U03. "SCP_MAY_EDIT_CODEPAGE
INCLUDE LSCP4U01. "TABLEFRAME_SCP4
INCLUDE LSCP4U02. "TABLEPROC_SCP4
INCLUDE LSCP4U04. "BLENDED_CP_NAME_SCP4
INCLUDE LSCP4U05. "VIEWFRAME_V_CHARLY
INCLUDE LSCP4U06. "VIEWEPROC_V_CHARLY
All Includes highlighted here contain individual coding. The modules TABLEFRAME_fugrname, TABLEROC_fugrname, VIEWFRAME_viewname and VIEWPROC_viewname contain generated coding and must not be changed.
Note the relevant user developments LSCP4U03 and LSCP4U04.
i) Remove errors which you can identify statically.
ii) Display the not statically analyzable positions with the following list of Includes to be displayed:
LSCP4U03
LSCP4U04
LSCP4I99
LSCP4O99
LSCP4F01