LCM_COMMON - Messages for Legal Content Management
The following messages are stored in message class LCM_COMMON: Messages for Legal Content Management.
It is part of development package APPL_LCM_COMMON in software component CM-GF. This development package consists of objects that can be grouped under "LCM Common objects".
It is part of development package APPL_LCM_COMMON in software component CM-GF. This development package consists of objects that can be grouped under "LCM Common objects".
Message Nr ▲ | Message Text |
---|---|
000 | Context &1 is used in other objects and cannot be deleted |
001 | Enter a valid context owner |
002 | Enter a context description |
003 | Valid From date should be before Valid To date |
004 | Choose a contact type |
005 | Customer &1 does not exist |
006 | Supplier &1 does not exist |
007 | Company code &1 does not exist |
008 | Purchasing organization &1 does not exist |
009 | Sales organization &1 does not exist |
010 | Context ID &1 does not exist |
011 | User &1 does not exist |
012 | Business partner &1 does not exist |
013 | New version of the context could not be created |
014 | Entity &2 with type &1 already exists |
015 | Choose a relationship type |
016 | Choose a linked object type |
017 | Enter ID for mandatory relationship legal transaction |
018 | Linked object ID &1 does not exist |
019 | Relationship ID &1 already exists for type &2 |
020 | Linked object ID &1 already exists for type &2 |
021 | Legal transaction ID &1 does not exist |
022 | Enter ID for mandatory entity |
023 | Internal contact &2 with type &1 already exists |
024 | External contact &2 with type &1 already exists |
025 | Choose a date type |
026 | Only one contact type Requester allowed for internal contacts |
027 | Enter ID for mandatory contact |
028 | Date with type &1 already exists |
029 | Contact type Requester not allowed in a context |
030 | Linked object with type &1 already exists |
031 | Not possible to save duplicate category |
032 | Not possible to save empty category |
033 | 'Main Entity' indicator can only be set for one entity |
034 | Object is locked by user &1 |
035 | Not possible to lock the table; try again later |
036 | Message to &1 with subject '&2' was successfully sent |
037 | An error occurred while sending email to &1; error text: &2 |
038 | &1 reminders sent successfully |
039 | Error occurred while sending &1 reminder(s) |
040 | No reminder to send for date &1 |
041 | Email ID is not maintained for user &1 |
042 | Type S- is restricted for use by SAP only |
043 | Modification of read-only attribute not possible |
044 | Entity type &1 not valid |
045 | Internal contact type &1 not valid |
046 | External contact type &1 not valid |
047 | Linked object type &1 not valid |
048 | Date type &1 not valid |
049 | No authorization to run report '&1' |
050 | Profile is missing for legal transaction &1 |
051 | Entity type is empty; not possible to create a new entry |
052 | Contact type is empty; not possible to create a new entry |
053 | Linked object type is empty; not possible to create a new entry |
054 | Reminder type is empty; not possible to create new entry |
055 | Stamp name is empty; not possible to create new entry |
056 | Date type is empty; not possible to create new entry |
057 | Profile is empty; not possible to create new entry |
058 | Content type is empty; not possible to create new entry |
059 | Linked Object integration link &1 is invalid |
060 | Package Size: &1; Number of records processed: &2 |
061 | Legal Transaction: &1, Table: &2, Last changed time: &3 |
062 | Number of Legal Transactions with active documents: &1 |
063 | Aged Legal Transactions between &1 and &2 restored to main memory |
064 | Number of Legal Transactions completed: &1 |
065 | Number of Legal Transactions which are in residence period: &1 |
066 | Undo Aging for Legal Transaction: &1, Table: &2, Last changed time: &3 |
067 | Documents: &1, Table: &2, Last changed time: &3 |
068 | Number of active documents: &1 |
069 | Aged Documents between &1 and &2 restored to main memory |
070 | Governing Law &1 does not exist |
071 | Number of Documents which are in residence period :&1 |
072 | Documents older than &1 are aged |
073 | Undo Aging for Documents: &1, Table: &2, Last changed time: &3 |
074 | Legal Transaction cannot be reopened as it has aged: &1 |
075 | Document cannot be reopened as it has aged: &1 |
076 | Active Legal Transaction |
077 | Process completed; Transaction not aged as residency period not reached |
078 | Process completed; Transaction not aged as document not ready for aging |
079 | Process completed; Transaction not aged but can be aged |
080 | Process completed and Transaction aged |
081 | Unsaved changes exist for Legal Transaction ID &1 |
082 | Summary of Legal Transaction Data Aging Analysis |
083 | Total Legal Transactions |
084 | No Data found for processing |
085 | No records found |
086 | Document is Locked for legal transaction &1 ; Email sent to Context Owner |
087 | Process completed; Document not aged as residency period not reached |
088 | Active Legal Document |
089 | Internal error in function modules for archiving |
090 | Process completed; Document not aged but can be aged |
091 | Process completed and Document aged |
092 | Operation not supported |
093 | Block Process, Update failed for &1 : &2 |
094 | Unable to save note due to technical error; please try saving again |
095 | Note field cannot be empty |
096 | An unexpected error occured in step : &1 Error Code : &2 |
097 | &1 is Archived |
098 | No authorization for the selected archiving action |
099 | Snapshot/Destruction is not supported |
100 | '&1' &2 are in final status (except objects where archiving has started) |
101 | &1 '&2' has not reached end of residence period |
102 | &1 '&2' has reached end of residence period |
103 | Error while determining residence period for &1 '&2' |
104 | &1 '&2' &3 is moved to status 'Archivable' |
105 | '&1' &2 are independently archivable |
106 | '&1' cannot be archived, as it's linked to non-archivable '&2' |
107 | &1 '&2' &3 is moved to status 'To be archived' |
108 | '&1' &2 are archivable, including linked objects |
109 | Checking the dependency of archivable objects with other objects |
110 | Total number of '&1' of &2 ready for dependency check |
111 | &1 '&2' &3 can be moved to status 'Archivable' |
112 | Error while updating status of &1 '&2' to 'Archivable' |
113 | Error while updating status of &1 '&2' to 'To Be Archived' |
114 | &1(of &2) &3: &4 |
115 | &1 '&2' &3 can be moved to status 'To Be Archived' |
116 | Error while updating deletion flag in document |
117 | No authorization to change the archiving status |
118 | &1 Deleted |
119 | Please select Created On: From and To date |
120 | Error while updating status of '&1' to 'Archived' |
121 | &1 |
122 | Session termination requested, hence unable to process this object |
123 | Language &1 does not exist |
124 | Execution of report '&1' is not in scope |
125 | No authorization for execution |
131 | No authorization to perform operations on Notes |
132 | Responsibility Function &1 can be used only once |
133 | &1 number of characters, enter a text with a maximum of 5000 character |
134 | Document cannot be reopened as it has archived: &1 |
135 | Document cannot be reopened as it has aged and archived: &1 |
136 | User for at least one Transaction Manager must be maintained |
137 | One internal contact of type Transaction Manager must exist |
138 | Configuration for Transaction Manager with key 0001 is missing |
139 | Main organization type &1 is not valid |
140 | For Clause ID &1, Time must be from &2 to &3 when you select &4 |
141 | Time must be from &1 to &2 when you select &3 |
142 | For Clause ID &1, select Unit for Clause Reference |
143 | Select Unit for Clause Reference |
144 | For Clause ID &1, wrong Unit selected for Clause Reference &2 |
145 | Wrong Unit selected for Clause Reference &1 |
146 | Select Clause Reference |
147 | &1&2&3&4 |
148 | Virtual document &1 couldn't be deleted; contact key user |
149 | Invalid Template for selected Governing Law, Language and Content Type |
150 | Document &1 is updated |
151 | Document &1 couldn't be updated |
152 | Document &1 with virtual document version &2 is created |
153 | Document &1 with virtual document version &2 couldn't be created |
154 | Report &1 aborted; check application log for details |
155 | New version of document &1 couldn't be created |
156 | For attachment files, enter linked object 'LCMDOC' and no Template ID |
157 | For Virtual document, enter Template ID and not linked object |
158 | Enter either linked object or Template ID |
159 | For undefined document, enter linked object 'LCMDOC' or Template ID |
160 | For attachment files, do not fill Template ID's. |
161 | Legal Transaction could not be created |
162 | Invalid Document Type &1 |
163 | File is already attached |
164 | Binary Content, Filename and Mimetype are mandatory |
165 | Virtual Document already exists |
166 | Invalid Document ID &1 |
167 | Template ID is mandatory |
168 | Variable name is empty; not possible to create new entry |
169 | Language is mandatory |
170 | Provide at least one document |
171 | Document &1 cannot be sent for esign as it is in status &2 |
172 | Document &1 cannot be sent for esign as it is in draft |
173 | Document &1 is locked hence cannot be sent for esign |
174 | Document &1 does not have any content |
175 | For VD, do not fill binary content, filename or mimetype |
176 | Error during calculation for variable &1 |
177 | Log for Variable Request &1 for Language &2 was processed on &3 |
178 | Log for Template Variable &1 |
179 | No data provided |
180 | Either authorization access token is not available or expired |
181 | Cannot assign transaction in status Canceled, Terminated, or Expired |
182 | Integr.Link '&1' already selected for LnkObj. Ty &2 |
183 | Error while instantiating the Application log |
184 | Reminder Relevant Scenario '&1' already selected for Reminder Type &2 |
185 | Log for Document &1 with Version &2 in Legal Transaction &3 |
186 | &1 number of characters, enter a text with a maximum of 1000 characters |
187 | Maintain a valid Profile |
188 | Maintain a valid CDS view |
189 | CDS View source is mandatory |
190 | Technical field name is mandatory |
191 | Maintain a valid Integration Type |
192 | Integration Mapping Variable is mandatory |
193 | Set Type is mandatory |
194 | Maintain a Set Technical Type |
195 | &1 does not have a Technical Type |
196 | Maintain a valid Technical Field Name |
197 | Maintain a valid Integration Variant |
198 | Integration Link is mandatory |
199 | Maintain a valid Profile |
200 | Identifying Attribute is mandatory |
201 | Maintain a valid Identifying Attribute |
202 | Maintain a valid Set type Value |
203 | Document &1 cannot be sent for esign as it is not editable |
204 | Identifying attributes not maintained for Integration Variant |
205 | Variables are not mapped to Integration Variant '&1' |
206 | Varibale for Main Enty. Type not mapped to Integration Variant '&1' |
207 | Only one entity must be marked as 'Main Entity' |
208 | Maintain a valid text for Technical Field Name |
209 | System fields have already been imported |
210 | Business Entity &1 is not a valid CDS view |
211 | Maintain a valid Technical Type |
212 | Maintain value of Set Type |
213 | Context determination failed |
214 | Integration variant cannot be blank |
215 | &1 is invalid Integration variant |
216 | Business Object ID cannot be blank |
217 | Context determination failed; more than one context determined |
218 | Context determination failed; no matching context found |
219 | Context determination failed; custom implementation enabled but missing |
220 | Context determination failed; invalid integration variant |
221 | Context determination failed; values for all attributes are mandatory |
222 | Integration variant '&1' of determined context differs from '&2' |
223 | You cannot use a context that belongs to an Integration Variant |
224 | Profile ID is mandatory |
225 | Context ID cannot be blank |
226 | Legal Transaction ID cannot be blank |
227 | Error while instantiating &1 |
228 | Determined context '&1' differs from the earlier context |
229 | Category Model is mandatory |
230 | Maintain Category model as Text CDS view |
231 | Category Model is not master/transactional data |
232 | Document ID cannot be blank |
233 | Maintain the Model key field name |
234 | Maintain the Model key field description |
235 | Maintain a valid key field name |
236 | Maintain a valid description for the field name |
237 | Maintain the long text |
238 | Category Model can have only one key field apart from language |
239 | Category Model should contain Language as key field |
240 | You are not authorized; contact system administrator |
241 | Virtual document &1 will not be set to assembly status 'Final' |
242 | Virtual document &1 will be set to assembly status 'Final' |
243 | Execution of report '&1' started |
244 | Execution of report '&1' completed |
245 | Category model cannot have more than 20k records |
246 | Enter Document Type |
247 | Enter Legal Transaction |
248 | Enter Document Content Type |
249 | Varaible data transfer completed |
251 | Invalid file type for Assembly Automation Level |
252 | New DMS version is created for virtual document &1 |
253 | New DMS version not created for virtual document &1 |
254 | Category model has been used to create Category, hence cannot be deleted |
255 | Error while determining timestamp |
256 | Enter valid Integration Variant |
257 | &1 cannot be active since system mapping variables are not assigned |
258 | Include ECM system variables also as part of the Integration variant |
259 | &1 is part of SAP pre delivered category model |
260 | System table entries cannot be deleted as integ variant is active |
261 | Business feature is not active |
262 | Document Action cannot be blank |
263 | Document Action provided is invalid |
264 | Integration variant cannot be deleted as it is active |
265 | Maintain value of Set Type in 'Map Variables to Integration Variant' |
266 | Maintain a Set Technical Type in 'Map Variables to Integration Variant' |
267 | Controlling parameter is mandatory |
268 | Profile Set &1 already exists |
269 | Choose Linked Object Technical Category for the technical type &1 |
270 | Invalid Contolling parameter |
271 | Config:Default Linked Object type missing for Integration Link &1 |
272 | Only one default linked object type allowed for integration link &1 |
273 | Default a Linked Object Type for Integration Link &1 |
274 | Select a valid Business Partner |
275 | Maintain a Business Partner role for Entity Type &1 |
276 | Delete Business Partner Role(s) |
277 | Maintain required BP Roles for this BP |
278 | Can't maintain BP Role for &1 as you have changed Technical Type |
279 | Value of Set Type in Mapping Variables is not mapped to Profile &1 |
280 | Internal Contact Type &1 is not valid |
281 | Internal Contact Type &1 is not valid for Profile &2 |
282 | External Contact Type &1 is not valid |
283 | External Contact Type &1 is not valid for Profile &2 |
284 | Entity Type &1 is not valid |
285 | Entity Type &1 is not valid for Profile &2 |
286 | Linked Object Type &1 is not valid |
287 | Linked Object Type &1 is not valid for Profile &2 |
288 | Date Type &1 is not valid |
289 | Date Type &1 is not valid for Profile &2 |
290 | Invalid Internal Contact type &1; please contact key user |
291 | Invalid External Contact type &1; please contact key user |
292 | Invalid Entity type &1; please contact key user |
293 | Invalid Linked Object type &1; please contact key user |
294 | Invalid Date Type &1; please contact key user |
295 | BP Role not configured for this Entity Type; please contact key user |