Description This is a control program for maintaining or displaying logical objectsand associated object lists. It edits the tables TLOGO and TLOGOS, anduses views to access them. The following checks or rules apply when maintaining the logical objectdescription:
- The field non-elementary> in TLOGOS is maintained automatically.
An X> means that the sub-object is an active non-elementaryobject.
- The field Client-specific> in TLOGO is maintained automatically.
- In TLOGOS only the following PGMID/OBJECT combinations are allowed as
sub-objects: - R3TR / TABU - R3TR / XPRA - LIMU / any object
- The replacement symbol /&> must occur in at least one of the
fields TLOGOS_TOBJ_NAME> or TLOGOS-TOBJKEY>. R3TR / XPRA> is an exception to this rule.
- The fields TLOGOS-TOBJ_NAME> and TLOGOS-TOBJKEY> must not
contain /*> (generic) before the replacement symbol /&> .
- The placeholder /*> (generic) may only be used at the end of the
TLOGOS-TOBJKEY> field.
- If a generic key is entered in TLOGOS-TOBJKEY>, then the field
Object function> (TLOGOS-TOBJFUNC) is automatically filled withR>.
- The object key may not be longer than the table key. Only character key
fields are taken into consideration.
- If the table key contains a key field that cannot be represented with
characters, the key description must be entered generically.
- In the table key description the placeholder
/L> should be entered for fields of the type "language". A generic entry or theobject name /&> is also allowed. In this case a warning isissued.
- In the table key description the placeholder
/C> should be entered for fields of the type "client".
- In the table key description a field of the type "numeric" may not
contain an alpha character.
- If the table key description is generic, but the generic specification
is not at the beginning of the field, a warning is issued.
- The field TLOGOS-TOBJ_NAME> must not contain single />
characters. // /* /& /C and /L are exceptions to this rule.
- No sub-object in TLOGOS can appear as a logical object in TLOGO and
itself have sub-objects.
- Non-Customizing objects must be disjunct. This means that logical
objects that do not belong to the class C must not have any overlappingsub-object areas. If two Customizing objects overlap, a warning isdisplayed.
- No C programs may be entered as sub-objects.
- All sub-objects (target objects in TLOGOS) must have a header entry
(object in TLOGO).
- All active sub-objects (target objects in TLOGOS) must have an active
header entry (object in TLOGO).(Active means that PROCFLAG = " " hasto be set).
- The mask length fields in TLOGOS are calculated automatically.
- Tables belonging to the delivery class W can only be sub-objects if the
logical object is assigned to the class S.
- The field TLOGO-ELEMFLAG> is maintained automatically.
'X' means that the object is elementary and thus contains nosub-objects ' ' means that sub-objects exist.
- The fields TObjektname> and TObjektkey> can contain each
of the replacement symbols /* /& /C and /L only once.
- The length of the object name (field TLOGO-OBJNAMELEN>) must not
be more than 30 characters long.
- The fields TObjektname> and TObjektkey> in TLOGOS must not
contain the character combinations /// //* //& //C or //L
- For maintenance, an object directory entry with original system is
required. You may be asked to enter the number of a correction.
- If a locking procedure is entered when CHECKID> does not equal
"L" a warning is issued.
- An object may only have either client-specific sub-objects or client-
independent sub-objects.
- When you save, the report RDDTLOBJ is automatically called up for all
saved objects. The report fills the tables OBJT, OBJS and OBJHappropriately. These tables can be viewed with transaction SOBJ.
|