SCTS_AIM - Messages for the AIM meta data repository

The following messages are stored in message class SCTS_AIM: Messages for the AIM meta data repository.
 It is part of development package SCTS_OBJ in software component BC-CTS-ORG. This development package consists of objects that can be grouped under "CTS: Object Editing (Including Transport Objects)".
Message Nr ▲
Message Text
000&1 &2 &3 &4
001You can either reference a class or another object type but not both.
002&2 &3 &4: Class &1 cannot be instantiated.
003Referenced object type &1 &2 doesn't exist.
004Referenced object type &1 &2 doesn't have an after import method.
005AIM &1 not ZDM enabled. Object type &2 &3 has a reference to itself.
006Referenced object type &1 &2 has different after import method assigned.
007Object is referencing another object. Own meta data will be ignored: &1.
008Lock mode is undefined for table &1 in metadata of object &2 type &3.
009API &1 not defined but referenced by API &2.
010Object type &1 &2: No AIM meta data maintained.
011AIM meta data of object type &1 &2 is consistent.
012AIM meta data of object type &1 &2 is not consistent.
013API meta data consistent.
014API metadata inconsistent.
015API &1: no meta data maintained.
016Table &1 not defined in Data Dictionary.
017API &1: no source references maintained.
018API &1: cyclic reference detected with API &2.
019API &1: pre-lock function &2 does not exist.
020Unkown error occurred when starting tool in new task.
021Software Component of object type &1 &2 not found.
022Start release specification for software component &3 is missing
023No start release information provided.
024Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4
025Function only supported in cluster view.
026AIM &1 not ZDM enabled. Reason: Table &2 is not properly classified.
027SL_API &1 not ZDM enabled. Reason: Table &2 is not properly classified.
028AIM &1 not ZDM enabled. Reason: Meta data object type &2 is unknown.
029AIM &1 &2 not ZDM enabled according to implementation of IF_TR_CTS_OBJ.
030AIM &1 &2 &3 not ZDM enabled according to AIM repository.
031AIM &1 &2 &3 not ZDM enabled. No meta data found in AIM repository.
032AIM &1 &2 &3 not ZDM enabled according to function module &4.
033SL_API &1 not ZDM enabled according to SL_API repository.
034SL_API &1 not ZDM enabled. No meta data found in SL_API repository.
035Error when calling function module &1 reading meta data of aim &2 &3 &4
036Calling inactive activation for &1 &2 &3
037Calling inactive deletion for &1 &2 &3
038Calling inactive mass activation for &1 &2 &3
039Calling inactive mass deletion for &1 &2 &3
040Inactive activation for &1 &2 &3: Nametab activation failed.
041Inactive mass activaton: Nametab activation failed.
042AIM &1 &2 &3 not enabled for the current start release.
043AIM not enabled for the current start release. See note &1.
044SL API &1 not ZDM enabled according to implementation of IF_TR_CTS_SLAPI.
045Implementation status of note &1 could not be checked via RFC.
046Implementation status of note &1 could not be checked.
047AIM/API not enabled for current start release &1 &2 SP-level &3.
048AIM/API needs start release &1 &2 SP level &3.
049AIM/API not enabled. No start release defined.
050OBJM &1 can not be deleted. It is currently referenced by &2 &3 &4.
051The following definitions cannot be deleted: &1 &2 &3 &4
052Selected object(s) not referenced by other objects.
053ZDM-enablement exists and must be deleted before the AIM can be removed.
054Could not create SLAPI instance for XPRA &1
055XPRA &1 not enabled for the current start release.
056Table lock modes changed to "completely locked" for this AIM/API.
057SL_API &1 not enabled for the current start release.
058No lock modes adjustment P -> X needed. No tables with lock mode P found.
059Lock mode conflict (&2 <-> &3) for table &1 with SLAPI-entry &4
060Lock mode conflict (&2 <-> &3) for table &1 with AIM of SOBJ-type &4
061Lock mode conflict (&2 <-> &3) for table &1 with SLAPI-entry &4
062Lock mode is undefined for table &1 in metadata of API &2.
063Table &1 in metadata of object &3 type &2 does not exist
064No start release information specified for software component &1.
065&1: overwrite lock_mode for table &2 from &3 to &4 due to upgrade flags
066Lock mode conflict (&2 <-> &3) for table &1 with configuration task &4
067Lock mode warning (&2 <-> &3) for table &1 with AIM of SOBJ-type &4
068Lock mode warning (&2 <-> &3) for table &1 with SLAPI-entry &4
069Table &1 is already declared in SLAPI entry &2 with lock mode &3.
070ZDO meta data for a transport object type that does no longer exist.
071ZDO meta data for an after-import-method that does no longer exist.
072ZDO meta data for &1 &2 to be deleted but still referenced by &3 &4.
073ZDO meta data for transport object type &1 &2 successfully deleted.
074Lock mode warning (&2 <-> &3) for table &1 with configuration task &4
075API &1 is not defined in SLAPI but referenced by object type &2 &3.
076Software Component of API &1 not found.
080Configuration task &1 declares illegal LOCK_MODE &2 for table &3.
081Configuration task &1 doesn't declare a LOCK_MODE for table &2.
082Configuration task &1 declares illegal ACCESS_TYPE &2 for table &3.
083Configuration task &1 declares non existing SL-API &2.
084Configuration task &1 declares non existing sub-task.
085Configuration task &1 declares a sub-task without ID. Will be ignored.
086Configuration task &1 declares start release without software component.
087Configuration task &1 declares empty release for software component &2.
088Configuration task &1: Used object &2 &3 does not belong to any SL-API.
089Configuration task &1 does not declare start release information.
090Configuration task &1 has zdm-status &2 and is therefore not ZDM enabled.
091Configuration task &1: Used object &2 &3 is covered by SLAPI &4.
100Transport object &1 &2 declares illegal LOCK_MODE &3 for table &4.
101Transport object &1 &2 doesn't declare a LOCK_MODE for table &3.
102Transport object &1 &2 declares illegal ACCESS_TYPE &3 for table &4.
103Transport object &1 &2 declares non existing SL-API &3.
105
106Transport object &1 &2 declares start release without software component.
107Transport object &1 &2 declares empty release for software component &3.
108
109Transport object &1 &2 does not declare start release information.
110Transport object &1 &2 has zdm-status &3, hence it is not ZDM enabled.
150Table &1, SLAPI &3: Access type &2 not supported in level C declarations
151Table &1, SLAPI &3: Lock mode &2 is not supported in level C declarations
152SL-API &1 can only include other Level C SL-APIs but not &2.
153SL-API &1, table &2: No access type necessary for current settings
154SL-API &1, table &2: No lock mode necessary for current settings
155SL-API &1 can only include other CURR_SETT_ SL-APIs but not &2.
156SL-API &1 cannot refer to current settings SL-API &2.
157SL-API &1 cannot refer to level C SL-API &2.
160Table &1: Contradicting access types in SLAPI and Tx XPRA. &2 <-> &3
161Table &1 is declared in SLAPI &2 but missing in transaction XPRA.
162Table &1 is declared in transaction XPRA but missing in SLAPI &2.
200The release of the source system does not match with the target system
Privacy Policy