/SCMTMS/COMMON - Common messages
The following messages are stored in message class /SCMTMS/COMMON: Common messages.
It is part of development package /SCMTMS/CMN_PRG in software component TM-CF. This development package consists of objects that can be grouped under "TM Common Development Objects".
It is part of development package /SCMTMS/CMN_PRG in software component TM-CF. This development package consists of objects that can be grouped under "TM Common Development Objects".
Message Nr ▲ | Message Text |
---|---|
000 | Messages for &1 &2 &3 &4: |
001 | The maximum number of messages was reached |
002 | &1 &2 is still used by &3 &4 |
003 | &1 &2 is still used |
004 | Strategy &1 not available; use standard strategy |
006 | Text "&1" exceeds maximum of &2 lines |
007 | Internal text of type &1 (schema &2) cannot be changed via service |
008 | Line &1 of text "&2" exceeds maximum of &3 characters |
009 | Text "&1" reverted to the value from requirement document |
010 | Automatic test in execution; saving aborted |
012 | Archiving status update failed |
020 | You are not authorized to change the TM STAD trace status |
021 | You are not authorized to change TM STAD trace settings |
022 | TM STAD trace activated |
023 | TM STAD trace deactivated |
024 | Cannot activate TM STAD trace |
025 | Node &1 does not contain a DB table |
026 | A maximum of 10 fields are allowed as App.Info of TM STAD trace |
027 | Node &1 does not belong to BO &2 |
028 | BO &1 is unknown |
029 | Action &1 does not belong to node &2 of BO &3 |
030 | Attribute &3 does not belong to node &2 of BO &1 |
031 | You are not authorized to regenerate the TM STAD Trace function group |
032 | You are not authorized to generate TM STAD Trace display function modules |
033 | TM STAD Trace does not support attribute &1 of node &2 |
040 | DC Profile &1 has an invalid filter attribute &2 defined for step &3 |
050 | Internal error |
051 | No dependent objects are verified; however, &1 is a dependent object |
052 | Business object &1 does not contain dependent objects; this is consistent |
053 | Testing business object &1 |
054 | Business object model is consistent |
055 | Business object model is inconsistent |
056 | Database table /SCMTMS/D_TKEY is inactive and needs to be activated |
057 | Not all relevant document keys could be collected for migration |
058 | Restart the migration report to process remaining documents |
059 | Relevant documents found for migration: &1 |
060 | & is not a valid user |
061 | Purchasing organization &1 is not assigned to a company |
062 | Simulation mode active; no changes persisted in database |
063 | Pass &1 of &2: Collecting relevant document keys for migration |
064 | Pass &1 of &2: &3 documents are processed |
065 | Updated documents: &1 |
066 | Can't save any new normalized quantity; threshold not reached |
067 | Can't cancel any freight order; threshold not reached |
068 | Can't cancel any document; threshold not reached or documents are planned |
072 | Enter a number |
073 | Entry is too long |
074 | Value for &1 exceeds the allowed maximum value of &2 |
075 | Value for &1 is lower than the allowed minimum value of &2 |
076 | Input length for &1 exceeds the allowed maximum length of &2 |
077 | Number of decimals for &1 exceeds the allowed maximum number of &2 |
078 | Entry for &1 does not match the required pattern &2 |
081 | Group &1 is not assigned to organization &2 |
082 | Office &1 is not assigned to organization &2 |
083 | Group &1 is not assigned to office &2 |
084 | Organization &1 does not exist |
085 | Group &1 does not exist |
086 | Office &1 does not exist |
090 | Where-used framework not available for object &1 and subobject &2 |
100 | Number range object not valid |
110 | Maximum length of commodity codes must not exceed 30 characters |
111 | Length of commodity code &1 exceeds maximum length defined for type &2 |
112 | Cannot change maximum length of type &1; conflicts with existing codes |
130 | Business documents have been changed; refresh your personal worklist |
145 | Overwrite file &1? |
146 | Delete &1 selected files from database? |
147 | File &1 could not be uploaded |
148 | &1 files deleted from database |
149 | &1 files saved on database |
150 | Upload aborted; file format not supported |
151 | Upload in background not possible |
152 | Unpacking failed; &1 is not a CSV file |
153 | Unpacking failed; zip archive is empty |
154 | Summed-up value of &1 exceeds the allowed maximum value of &2 |
155 | File &1 not found |
156 | Unpacking file &1 failed |
157 | Log could not be written; maximum number of logs reached |
158 | Column name &1 does not exist |
159 | Column separator not valid |
160 | Technical consistency error exists in business object &1 |
161 | No authorization to open file & |
162 | No authorization to write or delete a status file for file & |
163 | File & could not be accessed |
164 | No more files for processing |
165 | Processing of file & failed; choose 'Repeat' |
166 | ========== Opening file & for processing |
167 | Processing of file & failed |
168 | Processing of file & successful |
169 | File & locked |
170 | & files were processed successfully |
171 | Alert email has been sent |
172 | ========== End of file & |
173 | File & not uploaded |
174 | Log: transaction /SCMTMS/APPLOG; object /SCMTMS/TMS, subobject MD, date & |
175 | Status file & could not be accessed |
176 | File name & too long; enter a file name with max. 1000 characters |
177 | Updating zip file with file &1 failed |
178 | Field value '&1' in the column &2 is too long |
200 | Archiving status will be changed from '&1' to '&2' |
201 | Archiving status will be changed from '&1' to '&2' |
202 | Archiving status will be changed from '&1' to '&2' |
203 | Archiving status will be changed from '&1' to '&2' |
204 | Archiving status will be changed from '&1' to '&2' |
205 | Archiving status will be changed from '&1' to '&2' |
206 | Archiving status will be changed from '&1' to '&2' |
207 | Archiving status will be changed from '&1' to '&2' |
208 | Archiving status will be changed from '&1' to '&2' |
209 | Archiving status will be changed from '&1' to '&2' |
210 | Cannot be archived; '&1'-status is '&2' |
211 | Cannot be archived; '&1'-status is '&2' |
212 | Cannot be archived; '&1'-status is '&2' |
213 | Cannot be archived; '&1'-status is '&2' |
214 | Cannot be archived; '&1'-status is '&2' |
215 | Cannot be archived; '&1'-status is '&2' |
216 | Cannot be archived; '&1'-status is '&2' |
217 | Cannot be archived; '&1'-status is '&2' |
218 | Cannot be archived; '&1'-status is '&2' |
219 | Cannot be archived; '&1'-status is '&2' |
220 | Residence period not elapsed for document &1; archiving not possible |
221 | Residence period not elapsed for document &1; archiving not possible |
222 | Residence period not elapsed for document &1; archiving not possible |
223 | Residence period not elapsed for document &1; archiving not possible |
224 | Residence period not elapsed for document &1; archiving not possible |
225 | Residence period not elapsed for document &1; archiving not possible |
226 | Residence period not elapsed for document &1; archiving not possible |
227 | Residence period not elapsed for document &1; archiving not possible |
228 | Residence period not elapsed for document &1; archiving not possible |
229 | Residence period not elapsed for document &1; archiving not possible |
230 | TM lock trace was activated for user &1 |
231 | TM lock trace was deactivated for user &1 |
250 | The query statement could not be executed |
251 | The query statement became too large; it cannot be answered |
252 | The query statement became too complex; it cannot be answered |
300 | The executed query &1-&2-&3 is obsolete |