CMS - KPro: Content Management Service
The following messages are stored in message class CMS: KPro: Content Management Service.
It is part of development package SCMS in software component BC-SRV-KPR-CMS. This development package consists of objects that can be grouped under "KPRO: Content Management Service".
It is part of development package SCMS in software component BC-SRV-KPR-CMS. This development package consists of objects that can be grouped under "KPRO: Content Management Service".
Message Nr ▲ | Message Text |
---|---|
000 | No content repository defined |
001 | No content repository defined for storage type &1 |
002 | Content repository &1 does not exist |
003 | No long text exists in language &2 for content repository &1 |
004 | Function canceled by user |
005 | An entry with the same key already exists |
006 | SAP ArchiveLink only allows 2-character keys |
007 | No navigation is possible for field &1 &2(&3) |
008 | Select an entry before executing the function |
009 | Another long text (&3/&4) in language &2 already exists for &1 |
010 | Multiple content repositories reference storage system &1 |
011 | Content repository &1 has an invalid type (&2) |
012 | Content repository &1 is not completely defined |
013 | Content repository &1 already exists |
014 | Content category &1: &2 changed to &3 |
015 | Content repository &1 was moved |
016 | Content repository &1 was moved to &2 |
017 | Content repository &1 uses invalid interface version &2 |
018 | You are not allowed to change cross-client Customizing |
019 | You do not have authorization to change the data (only display) |
020 | No maintenance authorization for cross-client tables |
021 | Table &1 does not exist |
022 | Table &1 is not appropriate |
023 | No authorization to display the data |
024 | Content repository &1 is not an HTTP content server |
025 | HTTP error: &1 &2 &3&4 |
026 | Description file does not contain any information for attribute searches |
027 | Attribute search: Template was not found |
028 | Attribute search: No template |
029 | Free search: No template |
030 | Free search: Template was not found |
031 | Before executing the function select one entry |
032 | Error in RFC communication |
033 | Error in RFC communication - & |
034 | Error in RFC communication - & |
035 | Unknown return code &1 from storage system &2 |
036 | Content repository & is not an RFC storage system |
037 | Command '&1' is invalid for version '&2' |
038 | Table &1 is already used for content repository &2 |
039 | Structure &1 is already used for content repository &2 |
040 | Invalid function or parameter &1 &2 &3 &4 |
041 | Overflow in calculation of URI |
042 | Content repository & does not have storage type R/3 database |
043 | The key selected is reserved for the customer |
044 | The selected key is reserved for SAP |
045 | RFC and RPC storage systems allow storage system IDs with max. 10 chars |
046 | No basic path is defined for content repository &1 |
047 | No archive path is defined for content repository &1 |
048 | Error in opening file &1 for reading (&2) |
049 | Error in opening file &1 for writing (&2) |
050 | Doc. with path &1 cannot be accessed from the front end or the back end |
051 | Path is too long for frontend functions (&1) |
052 | Internal error, buffer is too small |
053 | Connection test for content repository &1 was successful |
054 | Component does not exist (DocId: &1, CompId &2) |
055 | Hierarchy type (&3 <> &4) is not appropriate (Contrep &1 DocId &2) |
056 | Component &1 does not exist (Contrep &2 DocId &3) |
057 | RFC server &1 cannot be started - &2: &3&4 |
058 | HTTP storage allows only binary data |
059 | Document does not contain any components |
060 | 1 component must be specified for structure storage- &1 not permitted |
061 | Structure storage does not allow binary data |
062 | Error in creating - the document (&1, &2) already exists |
063 | Category &1 does not exist |
064 | RFC server &1 cannot be stopped - &2: &3&4 |
065 | No SAP GUI: &1 |
066 | Repository &1 cannot be addressed from the frontend |
067 | HTTP command &1 (operation &2) is not possible for &3 (only as of &4) |
068 | Parameter errors &1 &2 &3 &4 |
069 | Repository &1 already exists |
070 | File &1 in directory &2 is not accessible |
071 | Error in DB select in table &1: &2 &3 &4 |
072 | Error in DB insert in table &1: &2 &3 &4 |
073 | Error when uploading file: &1 (&2) |
074 | Error when downloading file: &1 (&2) |
075 | Repository &1 is already used for document area &2 (&3) |
076 | Repository &1 is used for document area &2(&3) |
077 | Repository &1 does not have an explicit document area |
078 | Document being overwritten (ContRep: &1, DocId &2) |
079 | Inconsistent parameters: doc_id &1, phio_id &2 for content table &3 |
080 | HTTP content server (monitor context) |
081 | Name of monitored HTTP content server |
082 | Information on HTTP content server |
083 | Name of monitored repository |
084 | HTTP requests with errors |
085 | Information on repository or content server |
086 | Help nodes |
087 | Standard performance value |
088 | Data collection method active |
089 | Data collection method ends after &1 seconds |
090 | &1 &3 > &2 &3 current value over threshold value |
091 | Data collection method (content server) |
092 | Performance value for specific HTTP command |
093 | Data collection method (repository) |
094 | Statistical information for a Content Server |
095 | No correction proposal for repository document area |
096 | The document area for &1 repositories was corrected |
097 | Error when calling Data Provider: &1 |
098 | SSL port number for &1 not maintained |
099 | TEST: &1 &2 &3 &4 |
100 | Error in RFC call &1 (&2): &3&4 |
101 | COMMUNICATION_FAILURE in RFC call &1 (&2): &3&4 |
102 | SYSTEM_FAILURE in RFC call &1 (&2): &3&4 |
103 | The selected function is already being edited |
104 | RFC info was succesfully sent |
105 | Certificate was sent |
106 | Content repository &1 does not exist |
107 | &1 repositories were included in transport request &2 |
108 | Repository &1 was included in transport request &2 |
109 | Different settings in repositories &1 and on the back end |
110 | KPro Web server (monitor-context) |
111 | Help nodes |
112 | Data collection method (KPro Web server) |
113 | Information on KPro Web server |
114 | KPro web server requests with errors |
115 | Standard performance value |
116 | Information on KPro Web server |
117 | Statistic information for a KPro Web Server |
118 | Time Stamp |
120 | Cache server (monitor context) |
121 | Help nodes |
122 | Data collection method (cache server) |
123 | Information on cache server |
124 | Cache server requests with errors |
125 | Standard performance value |
126 | Information on cache server |
127 | Statistical information for a cache Server |
130 | AutoReaction Pool (Monitor Context) |
131 | Help nodes |
132 | Data Collection Method (AutoReaction Pool) |
133 | Content Server |
134 | Content Server Group |
135 | Cache Server |
136 | Aliases |
137 | Monitoring Inactive |
138 | Service Ready |
139 | Invalid Oauth Profile |
140 | RFC desintation SAPHTTP inaccessible: &1&2&3&4 |
141 | Repository &1 has wrong type &2 - operation cannot be performed |
142 | Repository &1 has wrong sub-type &2 - operation cannot be performed |
143 | Repository &1 is not a structure repository - no entry in CREP_TREE |
144 | Repository &1 not accessible by HTTP |
145 | Cannot copy from repository &1 to &2 - same repository |
146 | Repository &1 is a structure repository - operation cannot be performed |
147 | Repository &1 not accessible using Web Application Server URL |
148 | The RFC destination SAPCMS can no longer be contacted: &1&2&3&4 |
150 | No Server at Location &1 |
151 | Repository &1 (&2) does not have a document area |
152 | Repository &1(&2) is not used in any categories |
153 | Category &1 points to the nonexistent repository &2 |
154 | No repository entered for category &1 |
155 | Wrong document area: category (&1)(&2) using repository &3(&4) |
156 | Cache &1:&2:&3 Is Using an Undefined Host |
157 | CS alias &1:&2:&3 using server location &4 as additional location |
158 | Server &1 on path from &2 to location &3 of content server alias &4 |
159 | Path from &1 to &2 Begins with Index &3 |
160 | Index &3 Missing from Path from &1 to &2 |
161 | Location &3 is passed more than once in path from &1 to &2 |
162 | Location &1 for network mask &2 redundant for network mask &3 |
163 | For &1 users, location is driven using LCA parameters |
164 | LCA Parameter Has Value &2 for &1 |
165 | LCA Parameter for &1 Has Invalid Value &2 |
166 | Error in HTTP Access: &1 &2 &3&4 |
168 | RFC destination &1 has incorrect type (&2 instead of &3) |
169 | RFC Desintation &1 Incorrect (&2 Instead of &3) |
170 | RFC Destination &1: Trace Active |
171 | RFC Destination &1 Inaccessible: &2&3&4 |
172 | RFC Destination &1 OK and Accessible |
173 | RFC destination &1 is using gateway (&2 / &3) |
174 | Trace for RFC request to &1, command &2 |
175 | Trace for RFC request to command &1 |
176 | Inconsistent data with byte access &1 &2 &3 &4 |
181 | Mandatory parameter &2 missing from command &1 |
182 | Access Mode '&1' Insufficient for Command &2 with Access Mode '&3' |
183 | Signature Required: ContRep. &1, DocId &2, DocProt &3, AccessMode &4 |
184 | Validity Period of Signature Expired |
185 | Parameter &1 Has Incorrect Format |
186 | No Certificate with Fingerprint &1 Known |
187 | Internal Error When Checking Signature |
188 | Access denied |
189 | Parameter authId Does Not Correspond to Signature: &1 <> &2 |
190 | PSE &1 Cannot Be Opened |
191 | Repository &1 not suitable for this operation &2 &3 |
192 | Parameter error: Either category (&1) or repository (&2) passed |
193 | Cannot access repository &1 by HTTP |
194 | Cannot access repository &1 by HTTPS |
195 | Error when calling data provider |
196 | Error occurred during character conversion |
197 | Cannot determine a front-end path |
200 | No user defined for service &1 |
201 | HTTP plugin is not active |
202 | No service exists for handler 'CL_HTTP_EXT_CSIF' |
203 | Service &1 is not active |
206 | Please enter your user name or password. |
208 | Operation was successful |
210 | Destination &1, error: &2 (&3&4) |
211 | No RFC destination for archive DLL available for &1 |
212 | Communication failure with RFC call (destination &1): &2&3&4 |
213 | System failure while calling RFC (destination &1): &2&3&4 |
214 | Destination &1, error: &2&3&4 |
215 | Destination &1, error: &2 (&3&4) |
216 | SAP system cannot be modified; update process is active |
220 | Please enter a document number |
221 | Document not available in the repository |
222 | Error has occurred reading the document |
223 | Error updating the document |
224 | Error when retrieving document information from server after update |
225 | Document updated successfully |
230 | Error when downloading file &1 because file size is not permitted. |
231 | Error calling DP for file &1 because DP does not have enough memory. |
232 | Error downloading file &1 because hard disk is full. |
240 | File size &1 cannot be handled by a repository of this type. |
301 | Start of copied package &1 |
302 | Package &1 successfuly copied |
303 | Cancelation of copy package &1 |
304 | The copy package contains &1 documents |
305 | Enter a source repository or a category |
310 | The source repository is empty |
311 | Error while resolving logical file name &1 |