CRM_DOCUMENTS - Messages on Content Management in CRM
The following messages are stored in message class CRM_DOCUMENTS: Messages on Content Management in CRM.
It is part of development package CRM_KNOWLEDGE in software component CRM-BF-COM. This development package consists of objects that can be grouped under "Content Management in CRM".
It is part of development package CRM_KNOWLEDGE in software component CRM-BF-COM. This development package consists of objects that can be grouped under "Content Management in CRM".
Message Nr ▲ | Message Text |
|---|---|
| 050 | Internal error in Content Management |
| 051 | Could not determine protocol, 'HTTP/HTTPS' for Content Repository: &1 |
| 052 | Could not determine document Storage Category |
| 100 | Error loading file & |
| 101 | Internal error linking a business object with a document |
| 102 | Enter a URL |
| 103 | Action was cancelled |
| 104 | This action is not available for a URL |
| 105 | Where-Used List |
| 106 | New version of document created |
| 107 | For performance reasons enter one more search criterion |
| 108 | The selected document is not of type 'URL' |
| 109 | Select a document type to create an ArchiveLink document |
| 110 | Document(s) cannot be deleted |
| 111 | Reference(s) cannot be deleted |
| 112 | Function is not available for logical documents |
| 113 | No documents found |
| 114 | This function is not available for folder |
| 115 | Type &1 of file does not suit the selected document type &2 |
| 116 | New version created. Name '&1' was not transferred |
| 117 | Document Template Selection |
| 118 | Find a document that already exists in the CRM system |
| 119 | Find a Content Management document or load a new document |
| 120 | The ArchiveLink Document with ID &1 Does Not Exist |
| 121 | Link for the ArchiveLink Document to Object &1 Already Exists |
| 122 | Error When Creating the Link with Document Type &1 to Object &2 |
| 123 | &1&2&3&4 |
| 124 | More than &1 documents were found. |
| 125 | Document locked by user &1; You cannot make changes |
| 126 | Number of results smaller due to additional filter for document type |
| 127 | Document is checked out by user &1 |
| 200 | ******************** Messages Office Integration ******************** |
| 201 | Running Office application not found |
| 202 | Error Saving Office Document |
| 203 | Active office document does not come from Office Integration |
| 204 | Error replacing values in Office document |
| 205 | Office application could not be started |
| 206 | Error opening Office document |
| 207 | Business object data for replacing variables is incorrect |
| 208 | Office application could not be determined using file ending |
| 209 | At least Office 2000 required for Office integration |
| 210 | Alias &1 does not exist |
| 211 | Alias &1 no longer exists |
| 212 | Alias &2 and &1 display the same clients |
| 213 | Document is already open |
| 214 | The selected document does not correspond to the active Office document |
| 215 | The document was cached successfully |
| 216 | The document was transferred |
| 300 | ******************** Messages Document Templates ********************** |
| 301 | Choose a document template |
| 302 | Document still being processed. |
| 303 | BO links successfully entered in table CRMD_CM_TRANS. |
| 304 | BO links successfully imported from table CRMD_CM_TRANS. |
| 305 | No objects found in transport. |
| 306 | Temporary file cannot be deleted |
| 307 | Document Template Selection |
| 308 | Implement SAP Note: 685521 |
| 309 | Document templates were included in the transport request |
| 310 | Verify entered/modified URL. |
| 311 | Could not Read or Find entry in Table SKWG_BREL in Client &1 |
| 312 | BO links NOT entered in Table CRMD_CM_TRANS. |
| 350 | ********************** PLM Integration Messages ************************* |
| 351 | No Customizing maintained for PLM integration |
| 352 | Internal error when creating/deleting link to PLM document |
| 353 | Communication error: &1 |
| 354 | System error: &1 |
| 356 | PLM DMS document statuses could not be determined |
| 357 | RFC error: &1 &2 |