S_ARC_LCM_MES - Message Class for Legal Case Management (Subcomponent)
The following messages are stored in message class S_ARC_LCM_MES: Message Class for Legal Case Management (Subcomponent).
It is part of development package S_ARC_LEGAL_CASE in software component BC-ILM-LCM. This development package consists of objects that can be grouped under "Legal Case Management Subcomponent".
It is part of development package S_ARC_LEGAL_CASE in software component BC-ILM-LCM. This development package consists of objects that can be grouped under "Legal Case Management Subcomponent".
Message Nr ▲ | Message Text |
|---|---|
| 000 | &1 &2 &3 &4 |
| 001 | Table SLCM_OBJ_CAT not maintained; Legal Case Management not possible |
| 002 | Could not generate container for object category &1 |
| 003 | No entries selected |
| 004 | Canceled by user |
| 005 | Entry already exists: &1 &2 &3 |
| 006 | An exception was raised in function module &1 |
| 007 | Logical system &1 is unknown |
| 008 | Report &1 is unknown |
| 009 | Variant &1 is unknown |
| 010 | System error (RFC) while calling function module &1 |
| 011 | Communication error (RFC) while calling function module &1 |
| 012 | Exception context: Class &1, method &2 |
| 013 | Exception in CL_GUI_ALV_GRID: Display ended (by export) |
| 014 | Exception in CL_GUI_ALV_GRID: Unknown error |
| 015 | Object added |
| 016 | Object not added |
| 017 | Objects added |
| 018 | Cannot display objects with the origin &1 |
| 019 | Generic display from the archive has not yet been implemented |
| 020 | Cannot determine the status of the case |
| 021 | Cannot save the data for the LCM subcomponent |
| 022 | Could not remove any legal holds (see long text) |
| 023 | Legal hold information saved |
| 024 | Cannot determine the origin of the object &1 &2 &3 |
| 025 | Cannot determine the archive key for object &1 &2 &3 |
| 026 | Key &1 &2 |
| 027 | Key may already exist |
| 028 | Exception &1 was raised in method &2 |
| 029 | An unknown exception was raised in method &1 |
| 030 | No document area found |
| 031 | No documents selected |
| 032 | Cannot find any key values for selected document |
| 033 | Cannot find document type of &1 &2 |
| 034 | Cannot find the document category for document type &1 |
| 035 | Cause: Error from archive system or maximum mode number reached |
| 036 | Inconsistencies in the Archive Table |
| 037 | Error from SAP Kernel |
| 038 | No object type selected |
| 039 | Cannot log the deletion of the data record |
| 040 | Authorization error occurred in method &1 |
| 041 | Parameter error occurred in method &1 |
| 042 | Error while generating a GUID |
| 043 | Insertion of data in database table &1 failed |
| 044 | Deletion of data from database table &1 failed |
| 045 | Object &1 &2 &3 does not have any attachments |
| 046 | Only individual selection is possible (multiple lines were selected) |
| 047 | Object &1 &2 &3 was not archived |
| 048 | &1 &2 &3 Multiple data origins are not yet supported |
| 049 | Parameter for Retention Warehouse indicator does not exist |
| 050 | Logical system &1 is not maintained in Customizing table &2 |
| 051 | No Authorization |
| 052 | No objects could be determined |
| 053 | Object &1 with object key &2 is not part of any archive files |
| 054 | Legal case was saved.Scheduled E-Discovery jobs could not be completed. |
| 055 | You are not authorized to create a case |
| 056 | You are not authorized to display a case |
| 057 | You are not authorized to change a case |
| 058 | You are not authorized to delete a case |
| 059 | Customizing for content repository &1 does not exist in table &2 |
| 060 | Error code &1 in function module &2 (see long text) |
| 061 | Content repository for Retention Warehouse not defined |
| 062 | Customizing incomplete: Content repository not defined |
| 063 | Selection did not produce any hits |
| 064 | Input filter is empty ; Back-end search is aborted |
| 065 | E-Discovery : Background job &V1 is scheduled for this legal case |
| 066 | Insert Failed |
| 067 | Post processing module does not exist |
| 068 | RFC destination not found |
| 069 | Primary BOR objects not fetched |
| 070 | Batch run of e-discovery failed |
| 071 | Communication error happened ( see long text ! ) |
| 072 | System failure at RFC call happen |
| 073 | RFC call to FM &1 resulted in error ( &2 ) |
| 074 | Start of report processing |
| 075 | Primary BOR objects found |
| 076 | Start of Post processing |
| 077 | $1 BOR objects are found |
| 078 | End of Post processing |
| 079 | Start of save method |
| 080 | End of save method |
| 081 | Couldn't execute postproc function |
| 082 | Insertion into table &1 failed |
| 083 | Updation into &1 failed |
| 084 | Error while scheduling E-Discovery in background. |
| 085 | Object key &1 has no origin determined |
| 086 | You are not authorized to edit a legal case |
| 087 | Scheduled E-Discovery operation aborted due to incorrect legal case GUID |
| 088 | Exception occurred during scheduling of E-Discovery for report &1 |
| 089 | E-Discovery for report &1 terminated due to lock issues |
| 090 | Updation to &1 failed for case GUID &2 and archive key &3 |
| 091 | Processing of &1 BOR objects completed |
| 092 | &1 BOR objects processed out of &2 BOR objects returned |
| 093 | &1 BOR objects returned by E-Discovery report &2 for legal case GUID &3 |
| 094 | &1 BOR objects returned by postprocessing module &2 |
| 095 | You are not authorized to edit a legal case |
| 096 | Deletion of legal hold items for case closure scheduled in background |
| 097 | Legal case status cannot be set to closed |
| 098 | &1&2&3&4 |
| 099 | Start of processing of BOR objects for case closure |
| 100 | Legal case GUID &1 with title &2 is set to status Case Closed |
| 101 | Legal case with status Case Closed cannot be created |
| 102 | Legal hold propagation job scheduled in background with Job name &1 |
| 103 | Inconsistencies in tables &1 and &2 |
| 104 | Could not propagate case GUID &1 as case closure job is still running |
| 105 | Could not propagate case GUID &1 as E-Discovery job is still running |
| 106 | Error during processing of BOR key &1 for BOR object &2 |
| 107 | Error in update of user veto information for archive file &1 at offset &2 |
| 108 | Case was not saved due to concurrent access to the BOR object key |