SAP ABAP Message Class W3 (Messages for WebRFC)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CI-WEBR (Application Component) WebRFC, Web Reporting
⤷ SWWW (Package) Development class for basis WWW project
⤷ BC-CI-WEBR (Application Component) WebRFC, Web Reporting
⤷ SWWW (Package) Development class for basis WWW project
Attributes
Message class | W3 | |
Short Description | Messages for WebRFC | |
Changed On | 19971218 | |
Last Changed At | 093439 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 00 | **** Structure explosion ************** | ||
2 | 000 | ******* 001-009 : hierarchical display of product hierarchy ******* | ||
3 | 001 | Object & already exists | ||
4 | 002 | Specify a MIME type | ||
5 | 003 | Specify a processing program | ||
6 | 004 | Specify a name for the object | ||
7 | 005 | Please enter a development class. | ||
8 | 006 | Select an entry | ||
9 | 007 | Object & already processed | Space: object requires documentation | |
10 | 008 | Program for editing Web object does not exist | ||
11 | 009 | No MIME type assigned to object & | ||
12 | 01 | An equipment must be entered before making an assembly selection | ||
13 | 010 | Only object types HTML, MIME, HTRC and SRVC are supported | ||
14 | 011 | Incorrect language | Space: object requires documentation | |
15 | 012 | Development class &1 does not exist. | ||
16 | 013 | Report &1 has been successfully released for the Internet | Space: object requires documentation | |
17 | 014 | Report &1 has already been released for the Internet. | Space: object requires documentation | |
18 | 015 | An error has occurred releasing Report &1. | Space: object requires documentation | |
19 | 016 | The release of Report &1 for the Internet has been reset | Space: object requires documentation | |
20 | 017 | The release of Report &1 cannot be reset | Space: object requires documentation | |
21 | 018 | No reports have been released for the Internet | Space: object requires documentation | |
22 | 019 | Report &1 does not exist. Please check spelling. | Space: object requires documentation | |
23 | 02 | No bill of material exists | ||
24 | 020 | The release of function module &1 can not be reset | Space: object requires documentation | |
25 | 021 | An error has occurred resetting release of function module &1. | Space: object requires documentation | |
26 | 022 | Internet release of function module &1 has been reset | Space: object requires documentation | |
27 | 023 | Module &1 does not exist. Please check spelling. | Space: object requires documentation | |
28 | 024 | The function module &1 has been released for the Internet. | Space: object requires documentation | |
29 | 025 | The function module &1 has already been released for the Internet | Space: object requires documentation | |
30 | 026 | No function modules have yet been released for the Internet. | Space: object requires documentation | |
31 | 027 | The authorization group for report &1 is not maintained. | Space: object requires documentation | |
32 | 028 | No report trees have yet been released for the Internet. | Space: object requires documentation | |
33 | 029 | Tree &1 does not exist. Please check spelling. | Space: object requires documentation | |
34 | 03 | No reference object selected | ||
35 | 030 | Report tree &1 has been released for the Internet | Space: object requires documentation | |
36 | 031 | Report tree &1 has already been for the Internet. | Space: object requires documentation | |
37 | 032 | The release of report tree &1 cannot be revoked. | Space: object requires documentation | |
38 | 033 | An error has occurred when resetting the release of report tree &1. | Space: object requires documentation | |
39 | 034 | Report tree &1 has been released for the Internet | Space: object requires documentation | |
40 | 035 | There are no report trees in your system | Space: object requires documentation | |
41 | 036 | Hierarchy type is missing: Assignments cannot be made | ||
42 | 037 | Error updating assignment & | ||
43 | 038 | Node cannot be deleted: invalid assignments would occur | ||
44 | 039 | Vendor & not maintained for purchasing organization & | ||
45 | 04 | The order was created w/o reference to a notification | ||
46 | 040 | Object &1 is already locked in a correction request | Space: object requires documentation | |
47 | 041 | Selection date lies in the past: Data will only be displayed | ||
48 | 042 | Vendor $ not maintained | ||
49 | 043 | Vendor & not defined as being assigned to & | ||
50 | 044 | Please enter a purchasing organization | ||
51 | 045 | Purchasing organization cannot be entered without vendor number | ||
52 | 046 | Please enter a vendor number | ||
53 | 047 | Assignment not possible (higher-level vendor not maintained) | ||
54 | 048 | Purchasing organization assignment is not defined | ||
55 | 05 | The order has no reference to a functional location | ||
56 | 050 | Valid-from date cannot lie in the past | ||
57 | 051 | Validity period is not allowed (From-date lies after the to-date) | ||
58 | 052 | The assignment is also active outside of the given time period | ||
59 | 053 | The assignment is already active in the given time period | ||
60 | 054 | Different assignments exist outside of the given time period | ||
61 | 055 | Incorrect assignments cannot be processed | ||
62 | 056 | Select hierarchy node | ||
63 | 058 | Node & will be assigned to the same level | ||
64 | 059 | Select hierarchy header nodes for higher-level assignment | ||
65 | 06 | No equipment was entered in the order | ||
66 | 060 | Selected sub-hierarchy contains all nodes and cannot be reassigned | ||
67 | 061 | Nodes cannot be reassigned: unpermitted assignments would occur | ||
68 | 062 | Hierarchy contains no allowed alternative higher-level assignments | ||
69 | 063 | Higher-level node already maintained as a subordinate node | ||
70 | 064 | Assigned node is also a higher-level node | ||
71 | 065 | You cannot assign node to itself | ||
72 | 066 | Assignment has different attributes outside of the given time period | ||
73 | 071 | Partner determination error: Function not possible | ||
74 | 073 | There are no hierarchy nodes to be displayed | ||
75 | 074 | Function not possible: Maximum number of hierarchy steps (26) exceeded | ||
76 | 075 | Lowest hierarchy level reached (26): lower steps will be ignored | ||
77 | 076 | Hierarchy node cannot be removed as invalid assignments would arise | ||
78 | 077 | Selected hierarchy node is a header node: subhierarchy cannot be removed | ||
79 | 078 | Select incorrect hierarchy nodes | ||
80 | 079 | Rebate and pricing assignments updated | ||
81 | 080 | Attributes (pricing, rebate) are up-to-date for all assignments | ||
82 | 081 | Date cannot be changed (inconsistent validity periods) | ||
83 | 082 | Hierarchy type & is not defined | ||
84 | 083 | Node & is not active or not available for selection date | ||
85 | 084 | Node & is not available in the hierarchy | ||
86 | 085 | Hierarchy level & cannot be transferred due to inconsistencies | ||
87 | 086 | Hierarchy level assignment(s) updated | ||
88 | 087 | Hierarchy level assignment not updated or not updated for all points | ||
89 | 088 | Assignment not allowed: incorrect hierarchy level assignment | ||
90 | 089 | 'Reassigning' can lead to inconsistencies in the hierarchy lvl assignmnt | ||
91 | 090 | Initial Date Limit(s): a new validity period has been proposed | ||
92 | 100 | Objects not included in transport request | Space: object requires documentation | |
93 | 116 | Schedule line category & & deleted | ||
94 | 117 | Default indicator for & & & & cannot be reset | ||
95 | 118 | The new default item category for & & & is & | ||
96 | 119 | The new default schedule line category for & & is & | ||
97 | 120 | Default indicator for & & & cannot be reset | ||
98 | 121 | The new default item category for & & is & | ||
99 | 122 | Deletion unnecessary: no assignments exist | ||
100 | 123 | Enter a usage for structure configuration for BOM explosion | ||
101 | 124 | Internal error creating assignment table: Item categ & (ret code &) | ||
102 | 125 | No changes made to item category assignments | ||
103 | 126 | Changed item category assignments saved | ||
104 | 127 | Partner group & does not contain any payers who cannot be changed | ||
105 | 128 | Entry & & & missing in Table & | ||
106 | 129 | Item usage must be specified for item category group 'Blank' | ||
107 | 130 | Defaults for Item category & & changed | ||
108 | 131 | Customer-specific document types should begin with 'Z or Y' | ||
109 | 132 | Customer-specific item categories should begin with 'Z or Y' | ||
110 | 133 | Item category & already exists | ||
111 | 134 | Item category & & has been created | ||
112 | 135 | No changes made to the schedule line category assignments | ||
113 | 136 | Changes to schedule line category assignments have been saved | ||
114 | 137 | System blocking error for Table & | ||
115 | 138 | If a storage location is required, a batch check must be carried out | ||
116 | 139 | Error in transferring table entries to correction | ||
117 | 140 | The selected table entries have been transferred to correction | ||
118 | 141 | A condition type's access sequence in the pricing procedure is incorrect | ||
119 | 143 | An assignment for & already exists | ||
120 | 144 | Item category & is not allowed as a higher-level item category | ||
121 | 145 | Possible entries can only be displayed once the doc.type has been entered | ||
122 | 146 | Possible entries can only be displayed if a matl item category exists | ||
123 | 147 | Schedule line category & deleted from Table TVEP: please enter it again | ||
124 | 148 | Defaults for schedule line category & & changed | ||
125 | 149 | Schedule line category & & has been created | ||
126 | 150 | Schedule line category & already exists | ||
127 | 151 | Availability check without transfer of requirements is not allowed | ||
128 | 152 | Only condition types used for 'Pricing' are allowed | ||
129 | 20 | *** Task list connection | ||
130 | 200 | Text control | ||
131 | 201 | Please select a text object | ||
132 | 202 | You can only select one text object | ||
133 | 203 | System error occurred reading Internal table ( & ) | ||
134 | 204 | The entry already exists | ||
135 | 205 | Text determination procedure & has not been specified | ||
136 | 206 | Sales document type & does not exist | ||
137 | 207 | System error posting an internal table ( & ) | ||
138 | 208 | Access sequence & does not exist | ||
139 | 209 | Item category & does not exist | ||
140 | 21 | Equipment task list selectn not possible, as order contains no equipment | ||
141 | 210 | Delivery type & does not exist | ||
142 | 211 | Billing type & does not exist | ||
143 | 212 | Account group & does not exist | ||
144 | 213 | Text ID & does not exist | ||
145 | 214 | The language must be clearly specified | ||
146 | 215 | Include & does not exist | ||
147 | 216 | No access sequences can be defined for customer texts | ||
148 | 217 | Only text types can be defined for contact persons | ||
149 | 218 | No separate text procedures can be defined for billing item texts | ||
150 | 219 | Deletion not allowed: Text ID & is still being used. | ||
151 | 22 | No task list selected | ||
152 | 220 | Only special text objects are allowed | ||
153 | 221 | The language does not come from the partner function AG for MVKE | ||
154 | 222 | This combination (&,&) already exists | ||
155 | 223 | Language & is not defined | ||
156 | 224 | Partner function & not defined | ||
157 | 225 | This combination (&,&) is not defined | ||
158 | 226 | Access generated | ||
159 | 227 | Text determination procedure & already exists | ||
160 | 228 | Enter a number for the text determination procedure | ||
161 | 229 | Access sequence & already exists | ||
162 | 23 | Task list selection for order from maintenance plan not allowed | ||
163 | 230 | Enter a number for the access sequence | ||
164 | 231 | Copying control module & does not exist | ||
165 | 232 | Text ID & in Procedure & & does not exist in TTXID | ||
166 | 233 | Text determination procedure & does not exist in Table & | ||
167 | 234 | Text ID & is already present in the text determination procedure | ||
168 | 235 | A unit must be assigned to the time period entered | ||
169 | 236 | Please maintain the unit only in the existing time period | ||
170 | 237 | Calendar ID and time period cannot be maintained at the same time | ||
171 | 238 | Calendar ID and time period cannot be maintained at the same time | ||
172 | 239 | The cancellation period can only be assigned a positive value | ||
173 | 24 | Task list selection not possible due to order status | ||
174 | 240 | Deleting not allowed: the entry is being used in another position | ||
175 | 241 | There are no pop-up windows for billing document texts | ||
176 | 242 | The FORM routine & is not active or not available | ||
177 | 243 | 'Last of month' field and calendar ID cannot be maintained at one time | ||
178 | 244 | The rule for the contract start date refers to the contract start date | ||
179 | 245 | The rule for the contract end date refers to the contract end date | ||
180 | 25 | General maint.task list & & included | ||
181 | 250 | Partner control | ||
182 | 251 | Please select a partner object | ||
183 | 252 | You have selected more than one object: please select only one | ||
184 | 253 | System error occurred reading Internal table ( & ) | ||
185 | 254 | The entry already exists | ||
186 | 255 | Partner determination procedure & does not exist | ||
187 | 256 | Sales document type & does not exist | ||
188 | 257 | System error posting an internal table ( & ) | ||
189 | 258 | Partner determtn procedure & is already being used for Partner object & | ||
190 | 259 | Item category & does not exist | ||
191 | 26 | Equipment task list & & included | ||
192 | 260 | Transport into delivery system is only possible using & | ||
193 | 261 | Maintaining new partner functions in & is only possible in central functn | ||
194 | 263 | Partner function & has not been created | ||
195 | 264 | Partner function & cannot be used for partner procedures | ||
196 | 265 | Only customer partner functions can be defined as sources | ||
197 | 267 | Partner function does not exist in the customer partner determtn procdr | ||
198 | 269 | Deletion not allowed: Function & is used elsewhere | ||
199 | 27 | System: No operations could be determined | ||
200 | 270 | Partner determination procedure & not defined for customer master | ||
201 | 271 | Partner determination procedure & not defined for sales document headers | ||
202 | 272 | Partner determination procedure & not defined for sales document items | ||
203 | 273 | Partner determination procedure & is not defined for deliveries | ||
204 | 274 | Partner determination procedure & not defined for billing header(s) | ||
205 | 275 | Partner determination procedure & is not defined for billing items | ||
206 | 276 | Partner determination procedure & is not defined for sales activities | ||
207 | 28 | Include task list: operation number - number overflow | ||
208 | 280 | Sales documents require a sold-to party that cannot be changed | ||
209 | 281 | Sales document items may not have a sold-to party | ||
210 | 282 | Deliveries require a ship-to party that cannot be changed | ||
211 | 283 | Billing items may not have a payer | ||
212 | 284 | A payer which cannot be changed is required for billing documents | ||
213 | 29 | No operation selected | ||
214 | 290 | Assignment only makes sense for customer functions | ||
215 | 291 | Another partner function has already been converted to & | ||
216 | 292 | Function & is not used in Procedure & | ||
217 | 293 | Function & is a higher-level function than Function & | ||
218 | 294 | Partner function & does not exist | ||
219 | 295 | You cannot block Object & in display mode | ||
220 | 296 | Entries saved | ||
221 | 297 | Partner & is not defined | ||
222 | 298 | Select a sort field which is greater than that assigned to source functn | ||
223 | 299 | Sort sequences of previously determined partners are inconsistent | ||
224 | 30 | *** Maintenance plan calls | ||
225 | 300 | Conditions, Pricing | ||
226 | 301 | Function & does not exist | ||
227 | 302 | Initialization error for View & | ||
228 | 303 | Maintenance error for view & | ||
229 | 304 | Both groups need to be defined | ||
230 | 305 | Procedure & requires two groups | ||
231 | 31 | No package for call exists | ||
232 | 310 | Accrual billing document type & does not exist | ||
233 | 311 | Only accrual billing document types w/o cancellation billing type allowed | ||
234 | 32 | Maintenance plan data in order header incomplete | ||
235 | 33 | Error in determining costs for maint.item & schedule & : -> error log | ||
236 | 34 | Error in order schedule for maint.item & schedule & : -> error log | ||
237 | 35 | Posting terminated & with SY-Subrc & | ||
238 | 350 | Copy control, Graphics | ||
239 | 351 | Table & is blocked. It can only be displayed. | ||
240 | 352 | ABEND due to system error | ||
241 | 36 | Caution: Order resulted from counter-based maintenance | ||
242 | 400 | Incompletion log | ||
243 | 401 | Procedure & does not exist | ||
244 | 402 | Procedure & already exists | ||
245 | 403 | Procedure & saved | ||
246 | 404 | Procedure & deleted | ||
247 | 405 | Procedure & referred to elsewhere | ||
248 | 406 | & | ||
249 | 407 | Procedure & is already assigned to item category & | ||
250 | 408 | Procedure & is already assigned to Schedule line category & | ||
251 | 409 | Procedure & is already assigned to Partner function & | ||
252 | 410 | Procedure & already has texts assigned to it | ||
253 | 411 | Procedure & is already assigned to Sales document type & | ||
254 | 412 | Procedure & will be deleted when you press 'Enter' | ||
255 | 413 | Select one object only for processing | ||
256 | 414 | Enter an incompletion procedure for editing | ||
257 | 415 | Incompletion procedure & is already defined for another object | ||
258 | 416 | Enter an incompletion procedure | ||
259 | 417 | Incompletion procedure & is not defined for sales document types | ||
260 | 418 | Incompletion procedure & is not defined for items | ||
261 | 419 | Incompletion procedure & is not defined for schedule lines | ||
262 | 420 | Changes will not be saved when you press 'Enter' | ||
263 | 421 | Procedure is still being used: Object & cannot be blocked | ||
264 | 422 | Procedure is still being used: usages will be deleted | ||
265 | 423 | Incompletion procedure & is not defined for sales activities | ||
266 | 424 | Status group & does not exist | ||
267 | 50 | *** Status *** | ||
268 | 51 | System: Status object does not exist | ||
269 | 52 | System: Status profile & not allowed with object type & | ||
270 | 60 | *** CUA Status and CUA Title *** | ||
271 | 61 | System: CUA status could not be determined ( & & ) | ||
272 | 63 | System: CUA status: & & | ||
273 | 75 | ** PRT *** | ||
274 | 76 | System: Entry in system table does not exist ( & & & & & ) |
History
Last changed on/by | 19971218 | SAP | |
SAP Release Created in |