SAP ABAP Message Class VQ (SD Archiving and Product Allocation)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷ VZ (Package) Application development R/3 RV central functions
⤷ CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷ VZ (Package) Application development R/3 RV central functions
Attributes
Message class | VQ | |
Short Description | SD Archiving and Product Allocation | |
Changed On | 19980608 | |
Last Changed At | 143143 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 100 | Enter an archive. Archive list can be created with ? | ||
2 | 101 | No archives exist in the archiving administration | ||
3 | 201 | Product allocation & is invalid | ||
4 | 202 | No characteristics available for item &1/&2 | Space: object requires documentation | |
5 | 203 | Please enter the date, product allocation procedure and object | ||
6 | 204 | The date is not the end of a period (periods cannot be determined) | ||
7 | 205 | Specified period & in info structure & is not known | ||
8 | 206 | Undefined error during blocking of product allocation | ||
9 | 207 | Please check the available product allocation quantities | ||
10 | 208 | Error during communication with 'enqueue server' | ||
11 | 209 | Product allocation object & is locked by user & | ||
12 | 210 | Date set to & (last day in period &) | ||
13 | 211 | Product allocation check found changes to the confirmation | ||
14 | 212 | No entries for business year variant & in T009 | ||
15 | 213 | Date set to & | ||
16 | 214 | No statistical structure could be determined for procedure & | ||
17 | 215 | The business year variant is missing in stat. structure & | ||
18 | 216 | Info structure & does not fit procedure & | ||
19 | 217 | Default format missing for remaining product allocation | ||
20 | 218 | Table/structure & is not an information structure | ||
21 | 219 | Entries missing in the Data Dictionary for info structure & | ||
22 | 220 | The object must be the first lead column in info structure & | ||
23 | 221 | Fields missing for info structure | ||
24 | 222 | The info structure is not active | ||
25 | 223 | Error while reading the structure of the info structure | ||
26 | 224 | The key cannot be filled completely from SD (long text) | Space: object requires documentation | |
27 | 225 | There are still & lead columns from the customer name area! | ||
28 | 226 | Structure & for procedure & has no valid period type | ||
29 | 227 | Key fiedl & for info structure & has no value | ||
30 | 228 | & data columns missing for the product allocation info structure | ||
31 | 229 | No feature combination exists for the selection specified | ||
32 | 230 | Please enter the date and product allocation procedure | ||
33 | 231 | No objects may be specified if product allocation is inactive | ||
34 | 232 | Period type & is not supported | ||
35 | 233 | Periodicity of TMC4 (&,&) and T445A (&,&) are different! | ||
36 | 234 | Info structure & already in use for procedure &! | Space: object requires documentation | |
37 | 235 | More than one masking indicator (&2,&3) defined for &1! | Space: object requires documentation | |
38 | 236 | The step counter is empty for the discrete check against prod. allocation | Space: object requires documentation | |
39 | 237 | One step is needed for cumulative check against product allocations! | Space: object requires documentation | |
40 | 238 | Several check steps still exist! | Space: object requires documentation | |
41 | 239 | Check the step counter in hierarchy controlling! | Space: object requires documentation | |
42 | 240 | The info structure is already used for another method | Space: object requires documentation | |
43 | 241 | Internal error during account determination! | Space: object requires documentation | |
44 | 242 | Format & is not allowed! | ||
45 | 243 | Please select characteristic from which enhancement is to be carried out | ||
46 | 244 | Please select the characteristic from which deletion is to be carried out | ||
47 | 245 | Error when configuring update for product allocation | Space: object requires documentation | |
48 | 246 | Product allocation determination & is not defined | Space: object requires documentation | |
49 | 247 | Item &/& not found | Space: object requires documentation | |
50 | 248 | Error during scheduling in product allocation! | Space: object requires documentation | |
51 | 249 | The period settings for info structure &1 agree | Space: object requires documentation | |
52 | 250 | The period settings for the info structure do not agree | Space: object requires documentation | |
53 | 260 | Remote Function Call (RFC) could not be carried out! | Space: object requires documentation | |
54 | 280 | No consumption intervals have been maintained. | Space: object requires documentation | |
55 | 281 | Consumption intervals are not used! | Space: object requires documentation | |
56 | 282 | More than &2 product allocation stpes have been defined for procedure &1. | Space: object requires documentation | |
57 | 283 | Info structure &1 can be used for product allocation. | Space: object requires documentation | |
58 | 284 | Planning should be consistent for info structure &1. | Space: object requires documentation | |
59 | 285 | Planning version &2 has not been defined for info structure &1! | Space: object requires documentation | |
60 | 286 | Planning version &2 is defined for info structure &1. | Space: object requires documentation | |
61 | 287 | Periodicity &2(&3) is set for info structure &1. | Space: object requires documentation | |
62 | 288 | Info structure &1 is not in any update! | Space: object requires documentation | |
63 | 289 | Several update data (&1) defined for info structure &2! | Space: object requires documentation | |
64 | 290 | Updating is not defined for &1 at schedule line level! | Space: object requires documentation | |
65 | 291 | The update date is not permitted for &1 (permitted; &2, &3, &4)! | Space: object requires documentation | |
66 | 292 | Confirmed quantity (&2-&3) of the schedule line not updated | Space: object requires documentation | |
67 | 293 | Info structure only updated asynchronously | Space: object requires documentation | |
68 | 294 | The info structure is updated synchronously. | Space: object requires documentation | |
69 | 295 | Updating info structure is not switched on! | Space: object requires documentation | |
70 | 296 | No formulae are set for the order incoming quantity! | Space: object requires documentation | |
71 | 297 | Formula &2 is used for the order incoming quantity | Space: object requires documentation | |
72 | 298 | Not every characteristic has a formula | Space: object requires documentation | |
73 | 299 | There are no tax entries for product allocation procedure &1, &2! | Space: object requires documentation | |
74 | 300 | No active times have been defined for procedure &1, step &2. | Space: object requires documentation | |
75 | 301 | End of allocation validity should always be end of a period (&1, &2). | Space: object requires documentation | |
76 | 302 | The product allocation objects are entered in the planning hierarchy. | Space: object requires documentation | |
77 | 303 | Object &1 not contained in the planning hierarchy! | Space: object requires documentation | |
78 | 304 | No allocation quantities defined for product allocation object &1! | Space: object requires documentation |
History
Last changed on/by | 19980608 | SAP | |
SAP Release Created in |