SAP ABAP Message Class SRM_ECM_MSG (Message Class for ECM)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-RM (Application Component) SAP Records Management
⤷
SRM_ECM_IMPL (Package) Records Management SPI (ECM) Implementation
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-RM (Application Component) SAP Records Management⤷
SRM_ECM_IMPL (Package) Records Management SPI (ECM) Implementation 
Attributes
| Message class |  |
SRM_ECM_MSG |
| Short Description |  |
Message Class for ECM |
| Changed On |  |
20110908 |
| Last Changed At |  |
153212 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 2 | 001 |
An error occured in program &1 without a message text | The short text describes the object sufficiently | |
| 3 | 002 |
Type of file could not be determined | The short text describes the object sufficiently | |
| 4 | 003 |
File object is not a document | The short text describes the object sufficiently | |
| 5 | 004 |
MIME type and/or size of requested document &1 not found | The short text describes the object sufficiently | |
| 6 | 005 |
Requested file object is initial | The short text describes the object sufficiently | |
| 7 | 006 |
Size of document &1 not found | The short text describes the object sufficiently | |
| 8 | 007 |
Document ID '&1' has no content | The short text describes the object sufficiently | |
| 9 | 008 |
Attribute &1 (document name) is not maintainable | The short text describes the object sufficiently | |
| 10 | 009 |
Error during creation of name for object &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 11 | 010 |
Error in NNT deletion: incomplete key &1 &2 &3 &4 | The short text describes the object sufficiently | |
| 12 | 011 |
Object &1 &2 &3 already locked | The short text describes the object sufficiently | |
| 13 | 012 |
Database UPDATE for &1 &2 &3 &4 in table NNT failed | The short text describes the object sufficiently | |
| 14 | 013 |
Node name not found | The short text describes the object sufficiently | |
| 15 | 014 |
Node ID not found | The short text describes the object sufficiently | |
| 16 | 015 |
Error during locking of object &1 &2 &3 | The short text describes the object sufficiently | |
| 17 | 016 |
Error during unlocking of object | The short text describes the object sufficiently | |
| 18 | 017 |
Path segment is empty | The short text describes the object sufficiently | |
| 19 | 018 |
Path segment &1 contains at least one forward slash '/' | The short text describes the object sufficiently | |
| 20 | 019 |
Path segment &1 contains forbidden characters | The short text describes the object sufficiently | |
| 21 | 020 |
Path segment &1 contains too many parentheses | The short text describes the object sufficiently | |
| 22 | 021 |
Sequence number in path segment &1 is at the start | The short text describes the object sufficiently | |
| 23 | 022 |
Error in path segment conversion &1 | The short text describes the object sufficiently | |
| 24 | 023 |
Error in path segment conversion &1 | The short text describes the object sufficiently | |
| 25 | 024 |
Sequence number in path segment &1 cannot be found because &2 is missing | The short text describes the object sufficiently | |
| 26 | 025 |
Path segment &1 is too long | The short text describes the object sufficiently | |
| 27 | 026 |
Sequence number of path segment &1 exceeds maximum length | The short text describes the object sufficiently | |
| 28 | 027 |
Path segment &1 contains characters after &2 | The short text describes the object sufficiently | |
| 29 | 028 |
Node ID is empty | The short text describes the object sufficiently | |
| 30 | 029 |
Node ID &1 has an incorrect format | The short text describes the object sufficiently | |
| 31 | 030 |
Node id &2 has unknown type &1 | The short text describes the object sufficiently | |
| 32 | 032 |
RMS ID is empty | The short text describes the object sufficiently | |
| 33 | 033 |
AREA ID is empty | The short text describes the object sufficiently | |
| 34 | 035 |
Error during update of SRM_ECM_NNT because of misleading RMS_ID | The short text describes the object sufficiently | |
| 35 | 036 |
Database update for duplicate key &1 &2 &3 &4 ignored | The short text describes the object sufficiently | |
| 36 | 037 |
& datasets of NNT have been deleted | The short text describes the object sufficiently | |
| 37 | 038 |
Error in favorites caused by element &1 | The short text describes the object sufficiently | |
| 38 | 039 |
Error during tree construction of favorites | The short text describes the object sufficiently | |
| 39 | 040 |
Node ID &1 does not exist in backend | The short text describes the object sufficiently | |
| 40 | 041 |
Attribute WEBDAV_NODE_NAME could not be retrieved for SPS_ID = &1 | The short text describes the object sufficiently | |
| 41 | 042 |
Error during tree construction of history | The short text describes the object sufficiently | |
| 42 | 043 |
Error during tree construction of role | The short text describes the object sufficiently | |
| 43 | 044 |
Role could not be found using transaction SRMVIEWGEN | The short text describes the object sufficiently | |
| 44 | 045 |
Service ID &1 in GET_SUBSERVICE of program &2 is unknown | The short text describes the object sufficiently | |
| 45 | 046 |
Error raised by &1 during retrieval of file &2 | The short text describes the object sufficiently | |
| 46 | 048 |
Parameters AREA_ID and RMS_ID are missing | The short text describes the object sufficiently | |
| 47 | 049 |
No authorization for &1 &2 in object &3 | The short text describes the object sufficiently | |
| 48 | 050 |
RMSID &1 is not accessible | The short text describes the object sufficiently | |
| 49 | 051 |
Organizer for area ID &1 and parameter SPS ID &2 not found | The short text describes the object sufficiently | |
| 50 | 052 |
&1 raised in method GET_NODE by program &2 | The short text describes the object sufficiently | |
| 51 | 053 |
Backend framework could not started | The short text describes the object sufficiently | |
| 52 | 054 |
Error in path | The short text describes the object sufficiently | |
| 53 | 055 |
Invalid parent key for node expansion in roles &1 | The short text describes the object sufficiently | |
| 54 | 056 |
&1 raised in method GET_PROPERTY by program &2 | The short text describes the object sufficiently | |
| 55 | 057 |
Unsupported operation &1 called by ECM | The short text describes the object sufficiently | |
| 56 | 058 |
No child found for the current node | The short text describes the object sufficiently | |
| 57 | 059 |
Current node does not exist | The short text describes the object sufficiently | |
| 58 | 060 |
Could not create record element for ID: &1 SPS: &2 RMS: &3 | The short text describes the object sufficiently | |
| 59 | 061 |
Child ID did not match the node ID | The short text describes the object sufficiently | |
| 60 | 062 |
Child POID did not match the node POID | The short text describes the object sufficiently | |
| 61 | 063 |
POID not found in the node | The short text describes the object sufficiently | |
| 62 | 064 |
Mapped SRM attribute could not be found for ECM attribute &1 | The short text describes the object sufficiently | |
| 63 | 065 |
Error relating to description of a SRM attribute | The short text describes the object sufficiently | |
| 64 | 066 |
SRM attribute description does not exist | The short text describes the object sufficiently | |
| 65 | 067 |
SRM attribute value not defined | The short text describes the object sufficiently | |
| 66 | 068 |
Initialization error in property repository | The short text describes the object sufficiently | |
| 67 | 069 |
POID error during property unification | The short text describes the object sufficiently | |
| 68 | 070 |
Error during property unification configuration | The short text describes the object sufficiently | |
| 69 | 071 |
Unable to retrieve value reference for the SRM property &1 | The short text describes the object sufficiently | |
| 70 | 072 |
Unable to retrieve the requested element from the record | The short text describes the object sufficiently | |
| 71 | 073 |
Unable to retrieve the structure node attributes of a record | The short text describes the object sufficiently | |
| 72 | 074 |
Error getting the case reference | The short text describes the object sufficiently | |
| 73 | 075 |
Error during accessing the case record backend | The short text describes the object sufficiently | |
| 74 | 076 |
The requested attribute &1 is not under ECM namespace. | The short text describes the object sufficiently | |
| 75 | 077 |
Property value could not be created for the attribute &1 | The short text describes the object sufficiently | |
| 76 | 078 |
RM attributes could not be retrieved for the node type &1 | The short text describes the object sufficiently | |
| 77 | 079 |
Repository connection error raised in method GET_RM_ATTR_FOR_CASE | The short text describes the object sufficiently | |
| 78 | 080 |
General exception of Case Management | The short text describes the object sufficiently | |
| 79 | 081 |
Error during retrieval of data from POID | The short text describes the object sufficiently | |
| 80 | 082 |
Error while opening record or record iterator | The short text describes the object sufficiently | |
| 81 | 083 |
Error while opening case &1 | The short text describes the object sufficiently | |
| 82 | 084 |
Error while getting record API reference | The short text describes the object sufficiently | |
| 83 | 085 |
The short text describes the object sufficiently | ||
| 84 | 086 |
Error while fetching value of ECM display attribute &1 | The short text describes the object sufficiently | |
| 85 | 087 |
User &1 cannot access the elements of other users | The short text describes the object sufficiently | |
| 86 | 088 |
Casting error during file extension determination (ID:&1) | The short text describes the object sufficiently | |
| 87 | 089 |
Classrole ambiguously during file ID &1 extension determination | The short text describes the object sufficiently | |
| 88 | 090 |
Document object &1 for detecting file extension not investigatable | The short text describes the object sufficiently | |
| 89 | 091 |
Document &1 contains more than one component, the first one is selected | The short text describes the object sufficiently | |
| 90 | 092 |
File extension of &1 could not be identified | The short text describes the object sufficiently | |
| 91 | 093 |
File &1: extension &2 and mime type &3 do not match | The short text describes the object sufficiently | |
| 92 | 094 |
Component ID of TOADD for MIMETYPE &1 and Document ID &2 does not exist | The short text describes the object sufficiently | |
| 93 | 095 |
AREA-ID &1 does not exist in customizing table SRM_ECM_NNT_AREA | The short text describes the object sufficiently | |
| 94 | 096 |
RMS-ID &1 does not exist in customizing table SRM_ECM_NNT_RMS | The short text describes the object sufficiently | |
| 95 | 097 |
&1 is a "MULTICOMPONENT" file | The short text describes the object sufficiently | |
| 96 | 098 |
Multi-component files can be displayed properly only in the RM backend | The short text describes the object sufficiently | |
| 97 | 099 |
Type of document &1 not determinable | The short text describes the object sufficiently | |
| 98 | 100 |
PropertyService Error for node name "&1" and its attribute "&2" | The short text describes the object sufficiently | |
| 99 | 101 |
Internal error, required parameter is initial | The short text describes the object sufficiently | |
| 100 | 102 |
Unexpected error during closing document in locking processing | The short text describes the object sufficiently | |
| 101 | 103 |
Status of document couldn't be detected | The short text describes the object sufficiently | |
| 102 | 104 |
Document &1 is frozen and therefore it can't be locked | The short text describes the object sufficiently | |
| 103 | 105 |
Document &1 already changed by user &2 | The short text describes the object sufficiently | |
| 104 | 106 |
Checkout failed for user &1 | The short text describes the object sufficiently | |
| 105 | 107 |
DocumentID of requested file not determined | The short text describes the object sufficiently | |
| 106 | 108 |
Multiple implementation for same filter not allowed | The short text describes the object sufficiently | |
| 107 | 109 |
Error in Path: "&1" | The short text describes the object sufficiently | |
| 108 | 110 |
DocumentID inconsistent, here: "&1" <> "&2" | The short text describes the object sufficiently | |
| 109 | 111 |
Backend error while internal copy for document &1 | The short text describes the object sufficiently | |
| 110 | 112 |
No model node found that can accept document: &1 of type: &2 | The short text describes the object sufficiently | |
| 111 | 113 |
Multiple model nodes found that can accept document of type: &1 | The short text describes the object sufficiently | |
| 112 | 114 |
Document might be already checked in | The short text describes the object sufficiently | |
| 113 | 115 |
Document checked out by user "&1" -> Checkin by user "&2" not possible | The short text describes the object sufficiently | |
| 114 | 116 |
Update for document not possible, because of optimistical locking | The short text describes the object sufficiently | |
| 115 | 117 |
Source node not of type File | The short text describes the object sufficiently | |
| 116 | 118 |
Target folder not of type RM object | The short text describes the object sufficiently | |
| 117 | 119 |
Invalid Target Folder | The short text describes the object sufficiently | |
| 118 | 120 |
Cannot copy as target and source are both Favorites | The short text describes the object sufficiently | |
| 119 | 121 |
MOVE not allowed from "&1" | The short text describes the object sufficiently | |
| 120 | 122 |
Move not allowed as multiple links of document '&1' under the folder '&2' | The short text describes the object sufficiently | |
| 121 | 123 |
Document "&1" checked already out by another user "&2" | The short text describes the object sufficiently | |
| 122 | 124 |
Check In failed | The short text describes the object sufficiently | |
| 123 | 125 |
Document "&1" might be frozen during unlocking (checkin processing) | The short text describes the object sufficiently | |
| 124 | 126 |
Backend locking error/warning of file "&1" | The short text describes the object sufficiently | |
| 125 | 127 |
Backend unlocking error/warning of file "&1" | The short text describes the object sufficiently | |
| 126 | 128 |
Exception during Get-Token in LockingService raised | The short text describes the object sufficiently | |
| 127 | 129 |
Exception during Get-SessionLocks in LockingService raised | The short text describes the object sufficiently | |
| 128 | 130 |
Exception during Remove-SessionLocks in LockingService raised | The short text describes the object sufficiently | |
| 129 | 131 |
Exception during Add-Token in LockingService raised | The short text describes the object sufficiently | |
| 130 | 132 |
Error during Update Document | The short text describes the object sufficiently | |
| 131 | 133 |
Authorization Failed for Attribute "&1" of Case "&2" | The short text describes the object sufficiently | |
| 132 | 134 |
Error while connecting to SP backend : &1 | The short text describes the object sufficiently | |
| 133 | 135 |
User &1 is not authorized to create new documents | The short text describes the object sufficiently | |
| 134 | 136 |
Error while adding document &1 to history | The short text describes the object sufficiently | |
| 135 | 137 |
Error while getting POID for doc id : &1 | The short text describes the object sufficiently | |
| 136 | 138 |
Delete not allowed under "&1" | The short text describes the object sufficiently | |
| 137 | 139 |
Multiple link of the document POID Dir ID "&1" under Fav node key "&2" | The short text describes the object sufficiently | |
| 138 | 140 |
Error while adding document Poid Dir id "&1" into Fav node key "&2" | The short text describes the object sufficiently | |
| 139 | 141 |
Move Failed as unable to remove link Poid Dir Id "&1" from Favorite | The short text describes the object sufficiently | |
| 140 | 142 |
Move Failed Unable to create the parent folder for the source node | The short text describes the object sufficiently | |
| 141 | 143 |
Node id for a Structure node doesnt have runtime id | The short text describes the object sufficiently | |
| 142 | 144 |
Unable to remove document link | The short text describes the object sufficiently | |
| 143 | 145 |
Error while saving the record | The short text describes the object sufficiently | |
| 144 | 146 |
Error in Session Info | The short text describes the object sufficiently | |
| 145 | 147 |
Move Failed multiple links of same document "&1" exists under the source | The short text describes the object sufficiently | |
| 146 | 148 |
Creation of document &1 failed : Mime type not provided | The short text describes the object sufficiently | |
| 147 | 149 |
Delete Node Failed . | The short text describes the object sufficiently | |
| 148 | 150 |
Delete Failed as multiple links of doc Poid Dirid "&1"exists under source | The short text describes the object sufficiently | |
| 149 | 151 |
Documents can only be created within a record or case folder | The short text describes the object sufficiently | |
| 150 | 152 |
Error while creating new document | The short text describes the object sufficiently | |
| 151 | 153 |
Authorization failed for case &1 | The short text describes the object sufficiently | |
| 152 | 154 |
Problem occured during creation of Navigation Folder instance | The short text describes the object sufficiently | |
| 153 | 155 |
Creation of generation rule failed | The short text describes the object sufficiently | |
| 154 | 156 |
Error creating path | The short text describes the object sufficiently | |
| 155 | 157 |
Unexpected error in method &1; processing cannot be continued | The short text describes the object sufficiently | |
| 156 | 158 |
Document &1: state unknown or 'frozen', changes not permitted | The short text describes the object sufficiently | |
| 157 | 159 |
Connection parameter &1 not found for SPS ID = &2 | The short text describes the object sufficiently | |
| 158 | 160 |
Multiple generation rules are provided in the registry. | The short text describes the object sufficiently | |
| 159 | 161 |
Document &1 has been checkedout another user from SAPGUI | The short text describes the object sufficiently | |
| 160 | 162 |
Target NNT not found | The short text describes the object sufficiently | |
| 161 | 163 |
Access to node id &1 denied | The short text describes the object sufficiently | |
| 162 | 164 |
Rename &1 to &2: error when inserting new name &3 into NNT | The short text describes the object sufficiently | |
| 163 | 165 |
Rename &1 to &2: value of attribute &3 could not be changed | The short text describes the object sufficiently | |
| 164 | 166 |
No Authorisation for Display of Document &1 | The short text describes the object sufficiently | |
| 165 | 167 |
Exception during UpdateContent in RepositoryService raised | The short text describes the object sufficiently | |
| 166 | 168 |
Not authorised to display Element Type &1 | The short text describes the object sufficiently | |
| 167 | 169 |
No Authorisation for Change of Document &1 | The short text describes the object sufficiently | |
| 168 | 170 |
Not authorised to change Element Type &1 | The short text describes the object sufficiently | |
| 169 | 171 |
Exception during GetBytes in File_Info prime method raised | The short text describes the object sufficiently | |
| 170 | 172 |
Document &1 has already been checkedin | The short text describes the object sufficiently | |
| 171 | 173 |
Doc creation is possible only via template for SPS &1 | The short text describes the object sufficiently | |
| 172 | 174 |
Error while fetching model poid for sps &1 | The short text describes the object sufficiently | |
| 173 | 175 |
Error during HASH calculation (optimistic locking) | The short text describes the object sufficiently | |
| 174 | 176 |
Error during CHECK_OUT processing for DocID &1 | The short text describes the object sufficiently | |
| 175 | 177 |
Insufficient data to retrieve data from CSO table | The short text describes the object sufficiently | |
| 176 | 178 |
Unique identification of document with name '&1' from CSO failed | The short text describes the object sufficiently | |
| 177 | 179 |
Error while opening record iterator | The short text describes the object sufficiently | |
| 178 | 180 |
Multiple instance if &1 exists in the backend | The short text describes the object sufficiently | |
| 179 | 181 |
Creation of folders is not supported | The short text describes the object sufficiently | |
| 180 | 182 |
Rename &1 to &2: new name could not be read from RM backend again | The short text describes the object sufficiently | |
| 181 | 183 |
Generation Rule Reference creation Failed | The short text describes the object sufficiently | |
| 182 | 184 |
Error during opening of Record for Update | The short text describes the object sufficiently | |
| 183 | 185 |
Item exists in the target node | The short text describes the object sufficiently | |
| 184 | 186 |
Document "&1" is locked by another user | The short text describes the object sufficiently | |
| 185 | 187 |
Overwriting document link not supported | The short text describes the object sufficiently | |
| 186 | 188 |
Multicomponent document "&1" cannot be displayed in a file system | The short text describes the object sufficiently | |
| 187 | 189 |
MOVE not allowed to "&1" | The short text describes the object sufficiently | |
| 188 | 190 |
MOVE outside FAVORITE not allowed | The short text describes the object sufficiently | |
| 189 | 191 |
Document &1 is not locked and therefore cannot be updated | The short text describes the object sufficiently | |
| 190 | 192 |
HashValue not exist! | The short text describes the object sufficiently | |
| 191 | 193 |
No read by CL_SRM_ECM_FILE_INFO->IF_NWECM_BINARY~GET_BYTES passed first? | The short text describes the object sufficiently | |
| 192 | 194 |
Delete Failed as multiple links of document "&1" exists under the source | The short text describes the object sufficiently | |
| 193 | 195 |
Delete Failed Unable to create the parent folder for the source node | The short text describes the object sufficiently | |
| 194 | 196 |
Error while updating the Record. | The short text describes the object sufficiently | |
| 195 | 197 |
Renaming of folder &1 denied: action is only supported for files | The short text describes the object sufficiently | |
| 196 | 198 |
Renaming "&1" to "&2": WebDAV output name changed to "&3" | The short text describes the object sufficiently | |
| 197 | 199 |
Renaming "&1": output name may differ (WebDAV name attributes differ) | The short text describes the object sufficiently | |
| 198 | 200 |
Creation of file &1 failed, because user &2 locked a file with same name | The short text describes the object sufficiently | |
| 199 | 201 |
Creation of file '&1' failed -> there are some identical locked files | The short text describes the object sufficiently | |
| 200 | 202 |
File '&1' must first locked via CSO for its creation | The short text describes the object sufficiently | |
| 201 | 203 |
Error in locking table SRM_ECM_CSO for new file '&1' and user '&2' | The short text describes the object sufficiently | |
| 202 | 204 |
Error in creation of file &1 | The short text describes the object sufficiently | |
| 203 | 205 |
File can only be created within a record or case | The short text describes the object sufficiently | |
| 204 | 206 |
Error while accessing or evaluating the record model | The short text describes the object sufficiently | |
| 205 | 207 |
Create file: No unique model node and SPS ID in record model | The short text describes the object sufficiently | |
| 206 | 208 |
Error while checking interfaces supported by SPS ID &1 | The short text describes the object sufficiently | |
| 207 | 209 |
Create file: Selected folder does not accept documents | The short text describes the object sufficiently | |
| 208 | 210 |
Create file: Inconsistent context attribute in target folder | The short text describes the object sufficiently | |
| 209 | 211 |
Creation of file in folder &1 failed | The short text describes the object sufficiently | |
| 210 | 212 |
Creation of file '&1' failed. Empty file creation is prohibited | The short text describes the object sufficiently |
History
| Last changed on/by | |
20110908 | SAP |
| SAP Release Created in | 720 |
