ILM_STOR -
The following messages are stored in message class ILM_STOR: .
It is part of development package S_ILM_STOR_TYPES in software component BC-ILM-STO. This development package consists of objects that can be grouped under "ILM DB Store: Basis Types and Elementary Functions".
It is part of development package S_ILM_STOR_TYPES in software component BC-ILM-STO. This development package consists of objects that can be grouped under "ILM DB Store: Basis Types and Elementary Functions".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Invalid program state |
002 | Business function for activation of ILM DB Store is not active |
003 | Function was replaced by an adequate function in Customizing |
004 | This function will no longer be supported as of &1 |
005 | This function is obsolete; use &1 instead |
006 | HTTP connection &1 does not exist |
011 | Interface &1 implemented with &2 instead of &3 |
012 | Property &1 changed to &3 for URI &2 |
013 | Propterty &1 deleted from URI &2 |
014 | & |
015 | E-mail was sent |
069 | Please edit the Customizing for the mandatory property &1 |
100 | *** CX_ILM_STRG_EXEPTION *** |
101 | Handle [&1] does not exist |
102 | No processing data sent with URL &1 |
103 | Runtime information &1 does not exist for handle &2 |
104 | System cannot add runtime information &1 for handle &2 |
105 | URL was not transferred or is empty |
106 | URI &1 is invalid |
107 | System cannot determine handle for URL &1/origin &2 |
108 | Runtime error in method &1 |
109 | Runtime information for handle &2 is inconsistent (keyword &1) |
110 | Command &1 is valid only for &2 |
111 | URI &1 is invalid; it must begin with this separator / |
112 | No URI found for handle &1 |
113 | Legal hold for URI &1 cannot be changed; the path is already locked |
114 | Legal hold for URI &1 cannot be deleted; the path is already locked |
115 | Expiration date for URI &1 cannot be deleted |
116 | Expiration date &1 for URI &2 has an invalid format |
117 | Cannot change expiration date for URI &1 from date to <unknown> |
118 | Expiration date &1 for URI &2 was shortened with &3 |
119 | Expiration date &1 for URI &2 cannot be changed to &3 |
120 | Expiration date &1 for URI &2 is in the past and therefore invalid |
121 | URI &1 cannot be deleted because the element has expiration date &2 |
122 | Cannot delete URI &1 because there is a legal hold on the element |
123 | Process BAdI could not be determined for &1 |
124 | Exception occurred during processing (&1) |
125 | Delete URI &1 from store |
126 | Resource &1 cannot be changed |
127 | Cannot use handle &1: Object is not a resource |
128 | Property &1 not found for URI &2 |
129 | Collection &1 cannot be generated under another resource |
130 | Resource &1 cannot be created below another resource |
131 | Cannot delete URI &1; status &2 is invalid |
132 | Exception occurred when creating attribute &1 |
133 | You have not entered an ORIGIN |
134 | Process step &1 stops processing |
135 | Exception occurred in process step &1 |
200 | *** BEGIN CX_ILM_STRG_TRANSFER *** |
201 | Error while opening file &1: &2 |
202 | Error while writing in file &1: &2 |
203 | Shared file &1 does not exist |
204 | File name was not copied |
205 | File &1 is read only |
206 | No authorization for opening file &1 for &2 |
207 | Error while deleting file &1: &2 |
208 | Error while reading file &1: &2 |
209 | System caanot determine file name for a temporary file |
210 | Security risk in &1 because of value &2 |
211 | File &1 does not exist |
212 | File name already assigned for this data sink |
213 | Memory sink does not recognize file name |
214 | Error during creation / opening ILM DB Store |
215 | Data sink opened in read access, no write access possible |
216 | Data sink open in write access, no attribute changes possible |
217 | Security breach while accessing file &1 |
218 | Logical file name was not transferred |
219 | External handle &1 already exists and cannot be used |
220 | Reopening the memory: Entry (&1) not found |
221 | File cannot be copied to itself |
222 | *** END CX_ILM_STRG_TRANSFER *** |
250 | *** BEGIN CX_ILM_STRG_TRANSFER /Background Transfer *** |
251 | Job could not be scheduled for &1 (reason: &2) |
252 | Job could not be copied for &1 (reason: &2) |
253 | Job scheduling could not be completed for &1 (reason: &2) |
254 | Element &1.&2 selected to be moved |
255 | Prepare processing of &1.&2 |
256 | Lock element &1.&2 |
257 | Unlock element &1.&2 |
258 | Process element &1.&2 |
259 | Close processing of element &1.&2 |
260 | Processing is completed in the background |
261 | Could not lock element &1.&2 |
262 | Terminating processing of element &1.&2 due to process errors |
263 | Background processing of element &1.&2 completed |
264 | Element &1.&2 stays in the buffer as defined in Customizing |
299 | *** END CX_ILM_STRG_TRANSFER /Background Transfer *** |
300 | *** BEGIN CX_ILM_STRG_CUST *** |
301 | Value &1 is not a Boolean value |
302 | Value &1 is not a number |
303 | &2.&3 not found for origin &1 |
304 | Property &1.&2 is read-only |
305 | Namespace &1 not found |
306 | Origin &1 not found |
307 | Type &1 is not a known data type |
308 | Property &1.&2 for origin &3 already exists |
309 | Database connection &1 not found |
311 | No data connection entered for table &1 |
312 | System command &1 for OS &2 is incorrect or not defined |
313 | Logical path or file &1 not found |
314 | Cannot expand logical path or file &1 (message: &2) |
315 | Administrative ORIGIN cannot be changed in the current context (&1.&2) |
316 | Administrative origin not found for origin &1 |
317 | Connection &1 to origin &2 doesn't have a type assigned, DBCO unknown |
318 | Check possible only in the context of an origin |
319 | Value &1 not within the permitted area (&2) |
400 | *** BEGIN CMS INTEGRATION *** |
401 | Runtime error: &1 |
402 | You need to transfer the repository ID |
403 | You need to transfer the document ID |
404 | No ORIGIN assigned to repository &1 |
405 | DOC_ID &1 was changed to &2 |
406 | Error while transferring data: &1 |
407 | Error while adding data: &1 |
408 | Error in attributes: &1 |
409 | Error while mapping data: &1 |
410 | Access information is missing |
411 | Error during export of physical document (&1.&2.&3) to the store |
412 | Incorrect parameter during document (&1.&2.&3) in the store |
413 | Error while opening the store for document (&1.&2.&3), ORIGIN missing |
414 | Unknown error during operation &4 for document (&1.&2.&3) |
415 | Map for document (&1.&2.&3) could not be updated |
416 | Component ID must be transferred |
417 | Document (&1.&2.&3) not found |
418 | Cannot instantiate HTTP client for connection &1; cause &2 |
419 | Store not reached: destination &1, reason &2 |
420 | Document larger than Customizing settings made for maximum data size |
421 | Received return code &1 while reading from &2: &3 |
422 | Received return code &1 while writing from &2: &3 |
423 | Received return code &1 when readng document IDs from &2: &3 |
424 | Execution of the LIST command has started |
425 | Execution of the LIST command is complete |
426 | Execution of the READ command has started |
427 | Execution of the READ command is complete |
428 | Reading not possible; the document ID is missing |
429 | Unknown command &1 in mode &2 |
430 | You cannot use repository type &1 here; only the ILM Store is possible |
431 | Unknown request mode &1 |
449 | *** END CMS INTEGRATION *** |
600 | *** START OF EMAIL RUNTIME ERRORS *** |
601 | E-mail type &1 is unknown |
602 | E-mail was not sent |
650 | *** BEGIN RUNTIME ERRORS *** |
651 | You can only specify one of the optional parameters |
652 | At least one parameter from list of optional parameters is missing |
653 | Transfer already taking place, a second call is not possible |
654 | Calling method &1 is not valid in the current context |
655 | Parameter &1, value [&2] is not within the expected value range |
656 | Unexpected exception &1 when calling &2 |
657 | System cannot validate file name &1 |
658 | Logical file name &1 does not exist |
659 | File name is empty |
660 | No dictionary support for multiple instances (key &1) |
661 | No class name available for interface &1, version &2, parameter &3 |
662 | Parameter &1 was not provided |
663 | DBCON is not available for access to table &1 |
664 | Context not initialized before calling method &1 |
665 | System cannot determine a table for &1 because of an exception |
666 | Unexpected value &1 found for &2 |
667 | Handles must be the same for &1 and &2 |
668 | &1 is not a valid date adhering to format yyyy-mm-dd |
669 | &1 is not a valid date |
670 | BLOB size of &1 may not be 0 |
671 | ORIGIN must be specified if a URI is transferred |
672 | Double initialization not possible (&1) |
673 | Method cannot be called here, use &1 instead |
674 | Context origin already set, duplicate use not possible |
675 | Area &1 cannot be calculated and excluded at the same time |
676 | Status &1 invalid for HANDLE &2, &3 is expected |
677 | BAdI implementation &1 not permitted in productive systems |
678 | Default BAdI implementation &1 has to be re-implemented |
679 | Error during system command &1: &2 |
680 | No authorization to execute an operating system command (&1) |
681 | Virus scan error: &1 |
682 | System command &1 supplied return code &2 |
683 | Parameter check of system command &1 failed |
684 | Cannot end processing; origin &1 is not equal to origin &2 |
685 | You cannot edit data in administrative mode |
686 | Set an origin for system [&1:&2], resource type [&3] |
687 | Parameter &1 needs a value |
688 | Return value cannot be interpreted uniquely |
689 | Specify connection type in the form <DBCON>@<CONN_SYS> |
690 | Method &1 was not initialized after call (&2) |
691 | This function is obsolete and can no longer be used. |
698 | Needs to be done in the near future |
699 | This function has not yet been implemented |
700 | *** BEGIN ADMIN ERRORS *** |
701 | No authorization to select a data source |
702 | Data source &1 has already been selected |
703 | Use the customer namespace for the data source |
704 | &1 selected as data source to be used |
705 | No authorization to generate administration tables |
706 | No authorization to execute test reports |
707 | No authorization to change Customizing |
708 | You are not authorized to execute this function |
709 | No authorization to use the ILM DB store in production mode |
710 | Enter the connection and select the table to be created |
711 | Origin &1 is already being used elsewhere as an administrative origin |
712 | Data inconsistency: Origin &1 is used more than once |
713 | Origin &1 is already productive; do not use as an administrative origin |
714 | You cannot use origin &1 because it already contains Customizing |
715 | Could not lock origin &1 |
716 | Client ID &1 already exists; changing it is possible, creation is not |
717 | Client ID &1 does not exist yet; update not possible |
718 | An error occurred during DB operation &1 |
719 | Could not lock CLIENT_ID &1 |
720 | Content Repository &1 does not exist |
721 | Origin &1 does not exist |
722 | Origin &1 cannot be assigned to a content repository; it has no parent |
724 | Could not lock mapping for content repository &1 - origin &2 |
725 | Origin &1 has already been assigned to another content repository |
726 | Content repository &1 has already been assigned to another origin |
727 | Content repository &1 has not yet been assigned to an orgin |
800 | *** BEGIN DB ERRORS *** |
801 | Key &1 not found in table &2 |
802 | Master entry missing in root table for &1.&2 |
803 | System could not update entry &1.&2 |
804 | Entry with key &1.&2 already exists |
805 | Exception in streaming API for &1 to table &2 |
806 | SQL exception when accessing table &1 |
807 | Access to table &1 only possible with INSERT or UPDATE |
808 | Security breach when accessing table &1 |
809 | Error &1 while attempting to lock table &2 for key &3 |
810 | System could not generate new data table for origin &1 |
811 | NULL handle / emplty handle cannot be used in method &1 |
812 | Name & invalid for data table; name must start with Y, Y, or Z |
813 | Copying not possible, original table &1 is not active |
814 | Copying not possible: &1 already exists |
815 | You are not authorized to delete &1 |
816 | Transport request cannot be created: &1 |
817 | Pooled table cannot be created: &1 |
818 | Pooled table cannot be activated: &1 |
819 | Proxy table &1 cannot be created |
820 | Copying not possible: original table &1 does not exist |
821 | Generating data table &1 for connection &2 failed |
822 | Security breach for SQL &1 |
823 | Deleting connection &2 from database table &1 failed |
824 | Pooled table &3 was selected for origin &1, URI &2 |
825 | New pooled table &3 was generated for origin &1, URI &2 |
826 | Property &1 changed for handle &2 = &3 |
827 | Property &1 added for handle &2 = &3 |
828 | Pooled table &1 reached its size limit; do not add more data |
829 | Generating table &1 for connection &2 failed |
830 | Table &1 already exists on Sybase IQ |
831 | Value &1 already exists in &3 for &2 but it is unique |
832 | CHILD_ORIGIN &1 is already being used as an ADMIN_ORIGIN |
833 | ADMIN_ORIGIN &1 has already been used as a CHILD_ORIGIN |
834 | Origin &1 has already been assigned to another ADMIN_ORIGIN |
835 | An association between origin &1 and ADMIN_ORIGIN &2 is not possible |
836 | Exception while writing data to &1 (&2) |
837 | Exception while reading data from &1 (&2) |
838 | Exception while deleting data from &1 (&2) |
839 | Exception while opening &1 (&2) |
840 | SELECT returns multiple results (only one entry permitted) |
841 | Invalid: Administrative <- operative ORIGIN &1 not unique |
842 | OAuth client configuration &1 does not exist |
843 | OAuth client profile &1 does not exist |