technical information of ABAP workbench

nInactive objects are collected in database table DWINACTIV (from release 7.20: DWINACTIV_A)
nThe following function modules represent the API to the database:
nRS_INSERT_INTO_WORKING_AREA
nRS_DELETE_FROM_WORKING_AREA
nRS_OBJECT_IN_WORKING_AREA
nIn general, function module RS_WORKING_OBJECT_ACTIVATE triggers the check, the activation, and the object generation

nMany Workbench settings are stored in a common database table RSEUMOD
nAPI to table RSEUMOD is function module RS_WORKBENCH_CUSTOMIZING
For any object type processed by the Workbench, there is a relation between the Workbench object type and the transport object type (see table EUOBJEDIT).
There are two kinds of transport object types:
n R3TR objects have an entry in the main object catalog (table TADIR).
‘Logical’ transport object types (R3TR without sub-objects) can be created via transaction SOBJ
n LIMU objects are subordinate objects of R3TR objects.
Transport object types with sub-objects (LIMU) must be created by the Lifecycle Management (LM) colleagues
n
nThe editor type in database table EUOBJEDIT determines the function module to be called in function group SEAP (subroutine VERSION_OVERVIEW)
nThe standard function module is SVRS_DISPLAY_DIRECTORY_NEW
(responsible: BC-CTS-ORG)

要获取更多Jerry的原创文章，请关注公众号"汪子熙":