SAP ABAP Message Class Q6 (Archive Information System)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CCM-ADK-AS (Application Component) Archive Information System
⤷ SARCIS_INTERNAL (Package) Archive Information System: Internal Objects
⤷ BC-CCM-ADK-AS (Application Component) Archive Information System
⤷ SARCIS_INTERNAL (Package) Archive Information System: Internal Objects
Attributes
Message class | Q6 | |
Short Description | Archive Information System | |
Changed On | 20140121 | |
Last Changed At | 103744 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | ********* Archive info structure general + maint dialogs **************** | ||
2 | 001 | Enter an existing info structure | ||
3 | 002 | The info structure & is already active | ||
4 | 003 | Delete the structure table(s) first | Space: object requires documentation | |
5 | 004 | The info structure & is not active | ||
6 | 005 | Info structure &1 is not partitioned | The short text describes the object sufficiently | |
7 | 006 | The info structure & already contains data | ||
8 | 007 | Deactivate info structure &1 first | Space: object requires documentation | |
9 | 008 | Deactivate the info structure & first | ||
10 | 009 | Choose a database table or structure | ||
11 | 010 | Table &1 is also used in info structure &2 | The short text describes the object sufficiently | |
12 | 011 | Enter another field catalog (&V1& is inconsistent) | ||
13 | 012 | Enter an info structure first | ||
14 | 013 | Activate the info structure & first | ||
15 | 014 | You are not authorized to change infostructures for &1 | The short text describes the object sufficiently | |
16 | 015 | You are not authorized to display table & | ||
17 | 016 | Info structure & already exists | ||
18 | 017 | Enter an existing field catalog | ||
19 | 018 | Info structure & deleted | ||
20 | 019 | You are not authorized to display infostructures for &1 | The short text describes the object sufficiently | |
21 | 020 | Comply with name space (see long text) | ||
22 | 021 | You are not authorized to make changes to infostructures | The short text describes the object sufficiently | |
23 | 022 | The info structure & is in the customer name space | ||
24 | 023 | The info structure & is in the SAP name space | ||
25 | 024 | Enter an existing archving object | Space: object requires documentation | |
26 | 025 | Enter archiving object and field catalog appropriately | ||
27 | 026 | Enter a field catalog | Space: object requires documentation | |
28 | 027 | Enter the info structure name | ||
29 | 028 | Info structure & activated | ||
30 | 029 | Info structure & is active and can only be displayed | ||
31 | 030 | Call the info structure maintenance with the correct transaction | ||
32 | 031 | Info-structure & does not exist | ||
33 | 032 | Info structure &1 no longer suitable for field catalog &2 | Space: object requires documentation | |
34 | 034 | The field &1-&2 does not exist | Space: object requires documentation | |
35 | 035 | The info structure &1 has been deactivated | Space: object requires documentation | |
36 | 036 | Info structure &1 entered in transport request | Space: object requires documentation | |
37 | 037 | Problems with transport: info structure &1 will not be created | Space: object requires documentation | |
38 | 038 | Problems with transport: info structure &1 will not be deleted | Space: object requires documentation | |
39 | 039 | Field catalog &1 cannot be deleted because it is still being used | Space: object requires documentation | |
40 | 040 | Select a field from the field catalog &1 | Space: object requires documentation | |
41 | 041 | Enter a valid field | Space: object requires documentation | |
42 | 042 | You can only remove valid fields from the info structure | Space: object requires documentation | |
43 | 043 | Select the fields to be removed | Space: object requires documentation | |
44 | 044 | Select the fields to be incorporated | Space: object requires documentation | |
45 | 045 | Transport problems: the info structure &1 cannot be saved | Space: object requires documentation | |
46 | 046 | Place the cursor on a field name | Space: object requires documentation | |
47 | 047 | Info structure &1 cannot be transported | Space: object requires documentation | |
48 | 048 | Enter a valid name for the infostructure | Space: object requires documentation | |
49 | 049 | Enter an existing table or structure | Space: object requires documentation | |
50 | 050 | Table &1 does not belong to archiving object &2 | Space: object requires documentation | |
51 | 051 | Enter a field from table &1 | Space: object requires documentation | |
52 | 052 | The client cannot be included in a field catalog | Space: object requires documentation | |
53 | 053 | It seldom makes sense to use the indicator "mandatory key field" | Space: object requires documentation | |
54 | 054 | &1 could be incompatible with &2 | Space: object requires documentation | |
55 | 055 | &1 could be incompatible with &2 | Space: object requires documentation | |
56 | 056 | Enter a field name | Space: object requires documentation | |
57 | 057 | Enter a field name | Space: object requires documentation | |
58 | 058 | Enter the name of the reference field | Space: object requires documentation | |
59 | 059 | Place all key fields at the beginning of the field catalog | Space: object requires documentation | |
60 | 060 | Field catalog &1 does not have any key fields | Space: object requires documentation | |
61 | 061 | Source field &1-&2 is the reference field | Space: object requires documentation | |
62 | 062 | Table &1 does not exist | The short text describes the object sufficiently | |
63 | 063 | Field &1 is missing in table &2 | The short text describes the object sufficiently | |
64 | 064 | Key field &1 of the infostructure is a data field of table &2 | The short text describes the object sufficiently | |
65 | 065 | Data field &1 of the infostructure is a key field of table &2 | The short text describes the object sufficiently | |
66 | 066 | Reference field &1-&2 does not exist | The short text describes the object sufficiently | |
67 | 067 | The data type of &1-&2 does not match &3-&4 | The short text describes the object sufficiently | |
68 | 068 | Field &1 is not a field of the infostructure | The short text describes the object sufficiently | |
69 | 069 | The position of field &1 in table &2 is different than in infostructure | The short text describes the object sufficiently | |
70 | 070 | Infostructure &1 contains errors | The short text describes the object sufficiently | |
71 | 071 | Table &1 does not match infostructure &2 | The short text describes the object sufficiently | |
72 | 072 | Table &1 has not been generated and cannot be deleted | The short text describes the object sufficiently | |
73 | 073 | Delete the structure table(s) for information structure &1 first | Space: object requires documentation | |
74 | 074 | User interrupted the activation | The short text describes the object sufficiently | |
75 | 075 | User terminated table regeneration | The short text describes the object sufficiently | |
76 | 078 | Fixed tables for infostructure &1 are inconsistent | Space: object requires documentation | |
77 | 079 | Fixed table &1 does not exist | The short text describes the object sufficiently | |
78 | 085 | Infostructure &1 was saved | The short text describes the object sufficiently | |
79 | 100 | * ------------------- Generate/Delete structure tables ------------- * | ||
80 | 101 | A log could not be created for the activation of table & | Space: object requires documentation | |
81 | 102 | A problem occurred when activating table & | ||
82 | 103 | No object catalog entry could be made for table & | The short text describes the object sufficiently | |
83 | 104 | Archiving object & structure table name determination error | ||
84 | 105 | Structure table & could not be created in the ABAP/4 Dictionary | ||
85 | 106 | Internal error: Missing structure table control entry | ||
86 | 107 | Internal error: Missing archiving object | ||
87 | 108 | The object catalog entry for the structure table could not be deleted | Space: object requires documentation | |
88 | 109 | There is no database table for the info structure &1 | Space: object requires documentation | |
89 | 111 | The archive info structure table & could not be deleted | ||
90 | 112 | The structure table & already exists for the customizing data | Space: object requires documentation | |
91 | 113 | The field &1-&2 does not exist | Space: object requires documentation | |
92 | 150 | *------------------------ Generate database index---------------------- * | Space: object requires documentation | |
93 | 151 | An index &1 for table &2 already exists with the same name | Space: object requires documentation | |
94 | 152 | The system could not create the index &1 for table &2 | Space: object requires documentation | |
95 | 153 | Error when activating the index &1 for table &2 | Space: object requires documentation | |
96 | 154 | Information structure &1: the index ID '&2' is not permitted | Space: object requires documentation | |
97 | 155 | A field name (position &3) is missing from the index &2 | Space: object requires documentation | |
98 | 156 | Information structure &1: error in the field selection for index &2 | Space: object requires documentation | |
99 | 157 | Feld &3 does not belong to information structure &1 | Space: object requires documentation | |
100 | 158 | No repository information (nametab) was found for the table & | Space: object requires documentation | |
101 | 159 | An initial index ID is not allowed | Space: object requires documentation | |
102 | 160 | An initial position is not allowed | Space: object requires documentation | |
103 | 161 | Fieldname &1 does not exist in information structure &2 | Space: object requires documentation | |
104 | 162 | An initial field name is not allowed | Space: object requires documentation | |
105 | 163 | Field name &1 already exists for index ID &2 | Space: object requires documentation | |
106 | 164 | The index ID contains a non-alphanumeric character | Space: object requires documentation | |
107 | 218 | Analysis program could not be deleted | Space: object requires documentation | |
108 | 219 | The reporting program for info structure & is currently being edited | Space: object requires documentation | |
109 | 220 | Generation of analysis program not possible | ||
110 | 221 | Table & is not active | ||
111 | 222 | Table field & is not in table & | ||
112 | 223 | Data element & of table field &-& is not active or does not exist | ||
113 | 225 | Info structure & analysis program could not be deleted | ||
114 | 227 | Error in info structure & analysis program in line & | Space: object requires documentation | |
115 | 228 | No reporting program exists for info structure &1 | Space: object requires documentation | |
116 | 229 | No info structure found for selection | ||
117 | 230 | No analyzable info structures for archiving object & | ||
118 | 231 | No active info structures exist for archiving object &1 | Space: object requires documentation | |
119 | 232 | No reportable info structure exists for archiving object | Space: object requires documentation | |
120 | 233 | Info struct. &2 does not exist, is not suitable for object or is inactive | Space: object requires documentation | |
121 | 234 | Info structure &1 is inconsistent | Space: object requires documentation | |
122 | 235 | Info structure & no longer exists | ||
123 | 236 | Info structure & no longer active | ||
124 | 238 | Enter an active info structure | ||
125 | 239 | Info structure &1 does not exist or is inactive | Space: object requires documentation | |
126 | 240 | No archiving object with active info structure exists | Space: object requires documentation | |
127 | 241 | No archiving object with info structures exists | Space: object requires documentation | |
128 | 242 | No archiving objects available for which field catalogs exist | Space: object requires documentation | |
129 | 250 | Database connection &1 does not exist | The short text describes the object sufficiently | |
130 | 251 | Database platform &1 not supported for AS infostructures | The short text describes the object sufficiently | |
131 | 252 | Test of database connection &1 failed | The short text describes the object sufficiently | |
132 | 253 | Database connection &1 tested successfully | The short text describes the object sufficiently | |
133 | 254 | Data locked by user &1 | The short text describes the object sufficiently | |
134 | 255 | No authorization to maintain database connection for SAP AS | Space: object requires documentation | |
135 | 256 | Default connection already exists: &1 | Space: object requires documentation | |
136 | 257 | Database connection &1 saved as default connection | Space: object requires documentation | |
137 | 258 | Database connection &1 not supported by SAP AS | Space: object requires documentation | |
138 | 259 | Select only one database connection as the default connection | The short text describes the object sufficiently | |
139 | 260 | Error while creating table &1 using database connection &2 | The short text describes the object sufficiently | |
140 | 261 | Default connection was removed | The short text describes the object sufficiently | |
141 | 262 | No changes were made | The short text describes the object sufficiently | |
142 | 263 | Error while deleting table &1 using database connection &2 | The short text describes the object sufficiently | |
143 | 264 | Delete the structure table(s) for information structure &1 first | Space: object requires documentation | |
144 | 265 | Database connection &1 was saved | The short text describes the object sufficiently | |
145 | 266 | Selection of the standard database was saved | The short text describes the object sufficiently | |
146 | 267 | Database &1 with user &2 is already being used for system &3 | Space: object requires documentation | |
147 | 268 | Connection to database using &1 failed | The short text describes the object sufficiently | |
148 | 269 | Lock error while making insertion in table &1 for infostructure &2 | The short text describes the object sufficiently | |
149 | 270 | SQL error &1 while making insertion in table &2 for infostructure &3 | The short text describes the object sufficiently | |
150 | 271 | Database connection &1: incorrect format for SYBASE_IQ_LOCKWAIT | Space: object requires documentation | |
151 | 300 | Multiple archiving objects were registered | The short text describes the object sufficiently | |
152 | 309 | The object defined for info structure & does not exist | The short text describes the object sufficiently | |
153 | 310 | Internal error | The short text describes the object sufficiently | |
154 | 311 | No object exists for info structure & | ||
155 | 312 | Operation not possible for selected archive files and info structures | ||
156 | 313 | Mark the info structures which you want to edit | ||
157 | 314 | Inactive info structures cannot be edited | ||
158 | 315 | Info structure status management inconsistency | ||
159 | 316 | New fill for archive for which fill was not completed | Space: object requires documentation | |
160 | 317 | Mark the archive which you want to edit | ||
161 | 318 | Info structure &1 for archive file &2 already constructed | ||
162 | 319 | Info structure &1 for archive file &2 is not completely built | Space: object requires documentation | |
163 | 320 | The info structure fill program cannot be scheduled periodically | ||
164 | 321 | A background job has already been scheduled for some objects | The short text describes the object sufficiently | |
165 | 322 | Invalid job schedule parameter: Error & | ||
166 | 323 | Job cannot currently be scheduled | ||
167 | 325 | There are no analyzable archives | ||
168 | 326 | A new job for editing archive info structures has been scheduled | ||
169 | 327 | Archive & structure construction canceled | ||
170 | 328 | Info structure constructed for archive & | ||
171 | 329 | Internal error: archive key inconsistent: & <-> & | Space: object requires documentation | |
172 | 330 | Records not inserted in info structure & (see long text) | Space: object requires documentation | |
173 | 331 | You have no display authorization for archiving object & | ||
174 | 332 | no authorization for transaction SARI | ||
175 | 334 | Infostructure(s) was (were) removed | Space: object requires documentation | |
176 | 335 | Infostructure(s) was (were) built | Space: object requires documentation | |
177 | 337 | Infostructure &1 is being processed | The short text describes the object sufficiently | |
178 | 338 | No analyzable archive for &1 found for this selection | Space: object requires documentation | |
179 | 339 | Infostructure &1 does not contain any data for the selected period | The short text describes the object sufficiently | |
180 | 400 | **** 400 -499 Report info structures **** | Space: object requires documentation | |
181 | 401 | Place the cursor on the info record | Space: object requires documentation | |
182 | 402 | Display Data Object: Generation Error | Space: object requires documentation | |
183 | 500 | **** 500 - 599 programming interfaces (API) *** | Space: object requires documentation | |
184 | 501 | Field catalog &1 does not exist | Space: object requires documentation | |
185 | 502 | Incorrect type for parameter I_SELECTIONS, function module AS_API_READ | Space: object requires documentation | |
186 | 503 | Field &1 is not in field catalog &2 | Space: object requires documentation | |
187 | 504 | There is no active info structure for field catalog &1 | Space: object requires documentation | |
188 | 505 | No suitable infostructure found | Space: object requires documentation | |
189 | 506 | Enter an existing table | Space: object requires documentation | |
190 | 507 | There is no suitable active info structure | Space: object requires documentation | |
191 | 508 | Enter a suitable archiving object | Space: object requires documentation | |
192 | 509 | Enter a suitable infostructure | Space: object requires documentation | |
193 | 510 | Enter a suitable infostructure for object &1 | Space: object requires documentation | |
194 | 511 | No suitable infostructure found | Space: object requires documentation | |
195 | 512 | The value for selection field &1 is too long | Space: object requires documentation | |
196 | 513 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
197 | 600 | *** 600 to 699: Administration *** | Space: object requires documentation | |
198 | 601 | Infostructure &1 is being built (file &2) | Space: object requires documentation | |
199 | 602 | Infostructure &1 was built for file &2 | Space: object requires documentation | |
200 | 603 | Infostructure &1 was not built correctly for file &2 | Space: object requires documentation | |
201 | 604 | Unknown status &1 for infostructure &2, file &3 | Space: object requires documentation | |
202 | 605 | Infostructure &1 was built for file &2, although delete not complete | Space: object requires documentation | |
203 | 606 | Infostructure &1, file &2: Delete program running | Space: object requires documentation | |
204 | 607 | Infostructure &1 was not built correctly for file &2 | Space: object requires documentation | |
205 | 608 | First, select a node (object, session, file, or infostructure) | Space: object requires documentation | |
206 | 609 | Program error (&1) | Space: object requires documentation | |
207 | 610 | First, select an object or an infostructure | Space: object requires documentation | |
208 | 650 | *** 650 to 699: Move Infostructures *** | The short text describes the object sufficiently | |
209 | 651 | Infostructure &1 is based on a TREX index | The short text describes the object sufficiently | |
210 | 652 | Infostructure &1 is active | The short text describes the object sufficiently | |
211 | 653 | Infostructure &1 is not active | The short text describes the object sufficiently | |
212 | 654 | Infostructure &1, File &2: build status is incorrect | The short text describes the object sufficiently | |
213 | 655 | Infostructures &1 and &2 contain jointly indexed files | The short text describes the object sufficiently | |
214 | 656 | File &1 has been indexed with infostructure &2 and &3 | The short text describes the object sufficiently | |
215 | 657 | Data of infostructure &1 was moved to &2 | The short text describes the object sufficiently | |
216 | 658 | Infostructure &1 could not be activated | The short text describes the object sufficiently | |
217 | 659 | Infostructure &1 has fixed table &2 | Space: object requires documentation | |
218 | 660 | Infostructure &1 cannot be moved to itself | The short text describes the object sufficiently | |
219 | 700 | *** 700 to 706: Generate infostructures and field catalogs *** | Space: object requires documentation | |
220 | 701 | Field catalog &1 already exists and has not been generated | Space: object requires documentation | |
221 | 702 | Infostructure &1 already exists and is not generated | Space: object requires documentation | |
222 | 703 | Field catalog &1 does not exist | Space: object requires documentation | |
223 | 704 | Field &1 is not in field catalog &2 | Space: object requires documentation | |
224 | 705 | Infostructure &1 is not a generated infostructure | Space: object requires documentation | |
225 | 706 | Field catalog &1 is not a generated field catalog | Space: object requires documentation | |
226 | 707 | Infostructure &1 no longer matches changed field catalog &2 | Space: object requires documentation | |
227 | 708 | Delete the structure table(s) for infostructure &1 | Space: object requires documentation | |
228 | 709 | Info structure &1 was adjusted to amended field catalog &2 | Space: object requires documentation | |
229 | 711 | *** 712 to 730: Generate infostructures and field catalogs *** | The short text describes the object sufficiently | |
230 | 712 | Infostructure &1 was not generated | Space: object requires documentation | |
231 | 713 | Package &1 is not local; transfer a transport request | The short text describes the object sufficiently | |
232 | 715 | *** 715 to 720: Messages for ARCIS_DB_RENAME_TABLE | The short text describes the object sufficiently | |
233 | 716 | DB RENAME - Phase & started (parameter: & &) | The short text describes the object sufficiently | |
234 | 717 | DB RENAME - Phase & failed (rc = & ) | The short text describes the object sufficiently | |
235 | 718 | DB RENAME - Phase & completed | The short text describes the object sufficiently |
History
Last changed on/by | 20140121 | SAP | |
SAP Release Created in |