Ansicht
Dokumentation
SAPLSEUA - Repository Information System
Addresses (Business Address Services) CPI1466 during BackupThis documentation is copyright by SAP AG.
Description
SAPLSEUA is the general control program for the Repository Information
System. It controls the search, where-used list, and environment
determination functions.
The Repository Information System can be called using the following interfaces.
External generic interfaces:
REPOSITORY_INFO_SYSTEM "Search with display
REPOSITORY_INFO_SYSTEM_SET "Find set with F4
REPOSITORY_INFO_SYSTEM_F4 "F4 display/selection
RS_EU_CROSSREF "Usage set 1 without list
RS_EU_CROSSREF_LIST "Display use set 1
RS_EU_CROSS "Use with list
REPOSITORY_ENVIRONMENT_SET "Envrionment set
Extenral object-specific interfaces:
RPY_
Restriction:
to LIST_
this structure as its first included structure.
(Field names are then identical - performance with table copy)
The fields TEXT, DEVCLASS and TEXT2 are standard.
TEXT = 'Text for Obj_name,
TEXT2 = 'Text for encl_object .
Internal interfaces:
Architecture of the Repository Information System
The Repository Information
System consists of a control unit, the program SAPLSEUA, and programs in which the routines for each
object type are stored.
For load reasons, the general routines in SAPLSEUA are not included
in all object programs.
To get references to the object program data objects (Repository), the
Information System (SAPLSEUA) continually calls the object program,
which for its part calls back with data references.
The Information System calls the list output function in the object
program. The object program calls back to pass the data object. The
Information system then displays the list with references. Information
about the data structures is stored in the Dictionary according to the
naming convention (LIST_XXX), or is passed in the status record$ROLL_DATA$.
The object programs are listed in table EUOBJEDIT.
All general functions, such as navigation, controlling routines,
linking, and list construction are performed by SAPLSEUA.
The object programs are used for read access to search, construct a
where-used list or environment list, and to find unused objects.
Object program routines that can be used by application programs have the naming convention REPOSITORY_... -. (generic)
General control routines within the object programs have the naming
convention Object_.. .
Requirements
The object programs must be assigned to the object types in table EUOBJ.
Table EUOBJEDIT lists object programs and object screen numbers.
Trees for where-used lists and find next functions must be maintained
using Transactino SE89. For Find next, you must also store field
references (REPOSITORY_REFERENCE).
The object programs have type F to allow them to have their own screens
and user interfaces.
Lists that you create in the backgorund are stored, and can be recalled
from a worklist.
Lists created in dialog mode can be saved in a worklist.
ENVIRONMENT:
The environment determination function finds external references to an object.
The environment hit list contains all of the external references, that
is, the objects that do not belong to a program,such as function modules
or dialog modules.
The environment includes all Repository objects, including generated
objects with a TADIR entry and objects that are not recognized in the
transport layer.
The environment of a package or component is the sum of
all external references of objects in the package
(TABL, PROG,..), that do not themselves belong to package.
You can generate an environment list for one or more objects.
If you do so for a set of programs, the system returns all external
subroutines that are not part of the defined set.
You can restrict the search area for the environment search by both
package and object name.
UNUSED OBJECTS
This function is under Utilities. Run it in the background, then display
the list using the worklist function.
The not used implementation is flagged in the field EUOBJEDIT-NOT_USED.
WORKLIST:
From the worklist, you can use all functions as though you were on an
original hit list.
USE:
Use refers to the current system. For program objects, the data
is accurate to the last generation. For screens, it is accurate to the
last day.
FIND NEXT:
This function links hit lists with the attribute display for an object.
Example: Data element with attributes, domain, SET/GET paraemters
The find next trees are stored in Transaction SE89.
RESTRICT SEARCH AREA:
Currently implemented for packages in the environment and
where-used functions.
When you restrict by program object, you can also restrict the search
to certain keywords.
Note:
You can unlock variants using RSVARENT.
Output
Example
CL_GUI_FRONTEND_SERVICES - Frontend Services CPI1466 during Backup
This documentation is copyright by SAP AG.
Length: 5683 Date: 20240520 Time: 115857 sap01-206 ( 44 ms )
