Functionality
An entity described via ENTITY_INF, ALIAS_TAB, ATTRIBUTE_TAB,RELATIONTAB, SPECIALIZATION_TAB, SPECTYPE_TAB, VARIANT_TAB andVIEW_TABLE_TAB is included in the SAP R/3 System.
In ENTITY_INF basic information on the entity type are stored in thefollowing form:
ENTITY_ID Identification of the entity
LANGUAGE Language key
REFAREA_ID Area name (not in use at present)
TIME_DEP Flag for time-dependency
'X'-> entity is time-dependent
' '-> is not time-dependent
TIME_UNIT Unit of time
The units of time allowed are defined in the
domain UDZEITE.
MOD_USER Name of the user making the change
MOD_DATE Date of change
MOD_TIME Time of last change
SHORTTEXT Descriptive short text
GRAFICTEXT Graphics description (not in use at present)
In ALIAS_TAB all alias names for the entity are stored as follows:
LANGUAGE Language key
ENTITY_ID Identification of the entity
POSITION Position of the alias name
sequential number of the alias name (1-99)
ALIAS Alias name
MOD_USER Name of the user making the change
MOD_DATE Date of change
In the ATTRIBUTE_TAB the explicit attributes of an entity are stored(attributes can also be implied via view specified in VIEW_TABLE_TAB).The records of ATTRIBUTE_TAB have the following structure :
ENTITY_ID Identification of the entity
ATTRIB_ID Attribute ID
no more than 10 characters longer than the name
of the attribute
ATTRIB_TYP Attribute type (not in use at present)
FLDCLASS Classification of the entity
FLDCLASS2 Classification of the entity
FLDCLASS/FLDCLASS2 contain up to two
classifications for the attribute. The allowed
classifications can be found in the fixed values
for the domain UDFLDCLASS.
DTELNAME Name of the data element assigned to the
attribute
POSITION Attribute position
sequential number of the attribute (1-99)
MOD_USER Name of the user making the change
MOD_DATE Date of change
MOD_TIME Time of last change
In the table RELATION_TAB, ingoing and outgoing relationships for theentity are stored. Each record of RELATION_TAB has the followingstructure:
ENTID_TO Target entity type
ENTID_FROM Source entity type
ROLE Relationship role
If there is more than one relationship between
two entity types, each relationship must be
identified by a single figure nubmer (its
role).
CAT_VAR Temporary reference
Only appropriate if the relationship category
is 'referential'. (see data element UDRELREST)
CATEGORY Relationship category
This describes the relationship from the point
of view of the target entity. The relationship
category can be one of the following:
H hierarchic
A aggregate
R referential
X external
(see also the documentation for the data
element UDRELTYP)
CARDINAL1 Cardinality of a relationship
CARDINAL2 Cardinality of a relationship
CARDINAL1/CARDINAL2 contains the cardinality of
the relationship between the source and target
entity (see also documentation for the data
element UDCDLEFT or UDCDRIGHT)
MOD_USER Name of the user making the change
MOD_DATE Date of change
MOD_TIME Time of last change
SHTXT_FROM Short documentation for source entity
SHTXT_TO Short documentation for target entity
RELTXT1 Relationship description
Text on the link to a relationhip in the
graphic
RELTXT2 Relationship description (not used at present)
The specializations for the entity are stored in the tableSPEZIALIZATION_TAB in the following form:
ENTID_TO Target entity type
SPEZ_ID Specialization category
four character number for identifying the
specialization category
ENTID_FROM Source entity type
MOD_USER Name of the user making the change
MOD_DATE Date of change
MOD_TIME Time of last change
SHTXT_FROM Short documentation for source entity
SHTXT_TO Short documentation for target entity
The specialization categories for the entity are stored in the tableSPECTYPE_TAB in the following form:
ENTITY_ID Identification of the entity
SPEZ_ID Specialization category
four character number for identifying the
specialization category
LANGUAGE Lanugage key
COMPLETE Flag for completeness of the specialization:
'X'-> specialization is complete
(see also the documentation for UDCOMPLETE)
DISJUNCT Flag for disjunct specialization
'X'-> specialization is disjunct
(see also the documentation for UDDISJUNCT)
MOD_USER Name of the user making the change
MOD_DATE Date of change
MOD_TIME Time of last change
SHORTTEXT Short documentation for specialization
category
The view assigned to the entity is given in the table VIEW_TABLE_TAB inthe following form:
ENTITY_ID Identification of the entity
VIEWNAME Name of an SAP table view assigned to the
entity
TABLNAME Table assigned to the entity
MOD_USER Name of the user making the change
MOD_DATE Date of change
MOD_TIME Time of last change
All variants for the entity are given in the table VARIANT_TAB in thefollowing form:
ENTITY_ID Identification of the entiy
VARIANT Number of the variants of an entity
MOD_USER Name of the user making the change
MOD_DATE Date of change
MOD_TIME Time of last change
CALL FUNCTION 'RPY_ENTITY_INSERT'
EXPORTING
ENTITY_INF = ENTITYINF
ENTITY_NAME = 'WEC1000000'
DEVELOPMENT_CLASS = 'STST'
LANGUAGE = SY-LANGU
TRANSPORT_NUMBER = 'B20K000011'
WITH_DOCU = 'X'
DOCUTYPE = 'T'
TABLES
ALIAS_TAB = ALIASTAB
ATTRIBUTE_TAB = ATTRIBUTETAB
RELATION_TAB = RELATIONTAB
SPECIALIZATION_TAB = SPECIALIZATIONTAB
SPECTYPE_TAB = SPECTYPETAB
VIEW_TABLE_TAB = VIEW_TABLE_TAB
VARIANT_TAB = VARIANTTAB
DOCU_TABLE_TECH = DOCUTABLETECH
EXCEPTIONS
ALREADY_EXIST = 01
CANCELLED = 02
NAME_NOT_ALLOWED = 03
PERMISSION_ERROR = 04
INTERNAL_ERROR = 05.

Further information
Data element documentation for the structures RPY_ENTITY, RPY_ALIAS,
RPY_ATTRIB, RPY_RELAT, RPY_SPECI, RPY_SPTYP, RPY_VIEWAL, RPY_VARINT
Online documentation on data modeling.