/UIF/LREP_TMS_MSG - LRep transport management messages
The following messages are stored in message class /UIF/LREP_TMS_MSG: LRep transport management messages.
It is part of development package /UIF/LREP_CORE in software component CA-UI5-FL-LRP. This development package consists of objects that can be grouped under "LRep core services".
It is part of development package /UIF/LREP_CORE in software component CA-UI5-FL-LRP. This development package consists of objects that can be grouped under "LRep core services".
Message Nr ▲ | Message Text |
|---|---|
| 000 | System setting sets current client to read-only |
| 001 | File &1/&2 can only be modified in its original language &3 |
| 002 | File already exists with original in system &1 |
| 003 | Do you want to create the file as a copy? |
| 004 | Cannot release transport request/task &1 of owner &2 |
| 005 | There is a non-LRep file (&1/&2/&3) in &4; please release it using SE01 |
| 006 | You need one more transport task of type 'Unclassified' under &1 |
| 007 | System error when reading data in table BAOATTRSYS |
| 008 | Mandatory attribute &1 of &2 must be maintained in backend |
| 009 | Error when updating TADIR |
| 010 | Translation object type &1 is unknown |
| 011 | Package &1 does not exist |
| 012 | Adaptation transport object notification not permitted; return code &1 |
| 013 | Item type &1 not registered for use in adaptation transport organizer |
| 014 | No mixing of ATO- and CTS transport handling for file |
| 015 | Transport object name &1 has to start with package namespace &2 |
| 016 | Transport object name starts with package namespace |
| 017 | No change of the transport object name allowed for existing file (&1) |
| 018 | Transport object name &1 already used by file &2&3&4 |
| 019 | Cross-client file can only be recorded into ATO collection for package &1 |
| 020 | Local object cannot be assigned to a transport |