SAP ABAP Message Class UPC (Planning: General Error Messages)
Basic Data
Hierarchy
☛
SAP_BW (Software Component) SAP Business Warehouse
⤷ BW-PLA-BPS (Application Component) Business Planning and Simulation
⤷ UPC (Package) SEM-BPS: General Functions
⤷ BW-PLA-BPS (Application Component) Business Planning and Simulation
⤷ UPC (Package) SEM-BPS: General Functions
Attributes
Message class | UPC | |
Short Description | Planning: General Error Messages | |
Changed On | 20130531 | |
Last Changed At | 094810 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | ********** General messages *************************************** | Space: object requires documentation | |
2 | 001 | You may not have more than 3 field selection boxes together | Space: object requires documentation | |
3 | 002 | Select line | Space: object requires documentation | |
4 | 003 | Value &1 is not permitted for characteristic &2 | Space: object requires documentation | |
5 | 004 | Upper limit must be higher than lower limit | Space: object requires documentation | |
6 | 005 | Characteristic &1 does not exist in planning area &2 | Space: object requires documentation | |
7 | 006 | No input help is available for characteristic &1 | Space: object requires documentation | |
8 | 007 | Objects whose name begins with a number are in the SAP name range | Space: object requires documentation | |
9 | 008 | The name of the object may only contain letters and figures | Space: object requires documentation | |
10 | 009 | Data saved | Space: object requires documentation | |
11 | 010 | Data was deleted | Space: object requires documentation | |
12 | 011 | The name of the object may not begin with the number 0 | Space: object requires documentation | |
13 | 012 | The values were adapted | Space: object requires documentation | |
14 | 013 | Conditions adjusted | Space: object requires documentation | |
15 | 014 | Check the formula for errors | Space: object requires documentation | |
16 | 015 | Term &1 was not found in search area | Space: object requires documentation | |
17 | 016 | Select valid field | Space: object requires documentation | |
18 | 017 | Not all fields are displayed | Space: object requires documentation | |
19 | 018 | Entry is too long | Space: object requires documentation | |
20 | 019 | First enter values | Space: object requires documentation | |
21 | 020 | You may not enter an initial value here | Space: object requires documentation | |
22 | 021 | No statistics available | Space: object requires documentation | |
23 | 022 | Place the cursor in a field for the from value | Space: object requires documentation | |
24 | 023 | Position cursor on a line | Space: object requires documentation | |
25 | 024 | Attribute &1 on characteristic &2 is not available | Space: object requires documentation | |
26 | 025 | No input help is available for attribute &1 | Space: object requires documentation | |
27 | 026 | Value &1 is not available for attribute &2 | Space: object requires documentation | |
28 | 027 | Planning function will be undone | Space: object requires documentation | |
29 | 028 | There is no characteristic relationship with the number &1 | The short text describes the object sufficiently | |
30 | 029 | Area &1 is not a basic planning area | The short text describes the object sufficiently | |
31 | 030 | Multi-planning area &1 does not contain basic planning area &2 | The short text describes the object sufficiently | |
32 | 031 | Basic planning area &1 does not correspond to transferred basic area &2 | The short text describes the object sufficiently | |
33 | 055 | Make an entry in all required fields | Space: object requires documentation | |
34 | 056 | Make an entry in field &1 | Space: object requires documentation | |
35 | 057 | Enter a variable in field &1 | Space: object requires documentation | |
36 | 090 | Data requested in planning area &1 is locked by user &2 | Space: object requires documentation | |
37 | 091 | Capacity overload of lock server for planning area &1, see long text | Space: object requires documentation | |
38 | 092 | Requested data cannot be locked. See long text | Space: object requires documentation | |
39 | 098 | Generated report could not be inserted -> see long text | Space: object requires documentation | |
40 | 099 | Program is inconsistent -> see long text | Space: object requires documentation | |
41 | 200 | ***************** Basic data ******************************************** | Space: object requires documentation | |
42 | 201 | InfoCube &1 does not exist | Space: object requires documentation | |
43 | 202 | Error while calling up RFC | Space: object requires documentation | |
44 | 203 | Type & could not be activated | Space: object requires documentation | |
45 | 204 | The generated data is not contained in the selection condition | Space: object requires documentation | |
46 | 205 | Enter a value with a permitted format in field &1 | Space: object requires documentation | |
47 | 206 | Data must be saved first | Space: object requires documentation | |
48 | 207 | InfoCube &1 is already being used in planning area &2 | Space: object requires documentation | |
49 | 208 | &1 | Space: object requires documentation | |
50 | 209 | Impermissible characteristic derivation in Customer Exit | Space: object requires documentation | |
51 | 210 | Enter the RFC destination | Space: object requires documentation | |
52 | 211 | RFC destination &1 is not permitted | Space: object requires documentation | |
53 | 212 | RFC destination &1 is not a BW System with Release 1.2B or higher | Space: object requires documentation | |
54 | 213 | InfoCube &1 contains no usable characteristics | Space: object requires documentation | |
55 | 214 | InfoCube &1 contains no usable key figures | Space: object requires documentation | |
56 | 215 | Transport request &1 was compiled without errors | Space: object requires documentation | |
57 | 216 | Errors occurred during compilation of transport request &1 | Space: object requires documentation | |
58 | 217 | You have no authorization for the requested data | Space: object requires documentation | |
59 | 218 | You have no authorization to read the desired data | Space: object requires documentation | |
60 | 219 | Multiplanning area &1 cannot be used | Space: object requires documentation | |
61 | 220 | Data record is locked by data slice &1 | Space: object requires documentation | |
62 | 221 | For SEM 2.0B FCS, you cannot use BW 2.0B yet.You can use 2.0A | Space: object requires documentation | |
63 | 222 | You may not plan for the combination of characteristic values | Space: object requires documentation | |
64 | 223 | Multiplanning area &1 cannot be used | Space: object requires documentation | |
65 | 224 | &1 data records were read, &2 of them were changed, &3 generated | Space: object requires documentation | |
66 | 225 | Only the values EQ and BT are allowed in field OPTION, not &1 | Space: object requires documentation | |
67 | 226 | Only the value I is allowed in field SIGN, not &1 | Space: object requires documentation | |
68 | 227 | Higher-level characteristics must be selected with single values | Space: object requires documentation | |
69 | 228 | Planning profile &1 does not exist | Space: object requires documentation | |
70 | 229 | Selection to characteristic &1 is not restricted | Space: object requires documentation | |
71 | 230 | Rescheduling lead to invalid values | Space: object requires documentation | |
72 | 231 | User &1 does not exist | Space: object requires documentation | |
73 | 232 | Method was canceled after an error | Space: object requires documentation | |
74 | 233 | Invalid input parameter | Space: object requires documentation | |
75 | 234 | Value for characteristic &1 must be initial | Space: object requires documentation | |
76 | 235 | InfoCube &1 is not a real-time InfoCube | Space: object requires documentation | |
77 | 236 | No documents can be created in this multi area | Space: object requires documentation | |
78 | 237 | Planning cannot be performed for real-time InfoCube &1; see long text | Space: object requires documentation | |
79 | 238 | Selection is not suitable for any basic area | Space: object requires documentation | |
80 | 239 | Note: Change could make Customizing invalid; see long text | Space: object requires documentation | |
81 | 240 | Enter Customizing task | Space: object requires documentation | |
82 | 241 | Time shift for characteristic &1, value &2, shift &3 not possible | The short text describes the object sufficiently | |
83 | 242 | Characteristic &1 cannot be documented | Space: object requires documentation | |
84 | 243 | Processing of planning function was terminated | Space: object requires documentation | |
85 | 244 | You are not authorized to use the SEM-BPS API Trace | The short text describes the object sufficiently | |
86 | 300 | **** Execution of planning methods | Space: object requires documentation | |
87 | 301 | Planning function &1, parameter group &2 was carried out with no errors | Space: object requires documentation | |
88 | 302 | Errors occurred when executing planning function &1/&2 | Space: object requires documentation | |
89 | 303 | Object &1 | Space: object requires documentation | |
90 | 304 | The planning function cannot be executed | Space: object requires documentation | |
91 | 305 | Job &1 was scheduled for background processing | Space: object requires documentation | |
92 | 306 | Report &1 could not be entered in job &2 | Space: object requires documentation | |
93 | 307 | Fields (&1) that are not in the level, must remain initial | Space: object requires documentation | |
94 | 308 | Global planning sequence was terminated with errors | Space: object requires documentation | |
95 | 309 | Planning sequence &1 has been executed | The short text describes the object sufficiently | |
96 | 400 | ************* Hierarchy - BW Interface ********************************** | Space: object requires documentation | |
97 | 401 | &1 | Space: object requires documentation | |
98 | 402 | Error during data selection | Space: object requires documentation | |
99 | 403 | No suitable data records found for selection | Space: object requires documentation | |
100 | 404 | Parameter errors occurred during selection | Space: object requires documentation | |
101 | 405 | Selection was cancelled | Space: object requires documentation | |
102 | 406 | Error occurred during numbering of new hierarchy nodes | Space: object requires documentation | |
103 | 407 | Hierarchy &1 was not found | Space: object requires documentation | |
104 | 408 | Characteristic &1 was not found | Space: object requires documentation | |
105 | 409 | Conversion error of value &2 (characterictic &1) | Space: object requires documentation | |
106 | 410 | Value &2 for characteristic &1 not found | Space: object requires documentation | |
107 | 411 | Error during text selection for characterictic &1 (value &2) | Space: object requires documentation | |
108 | 412 | Incorrect hierarchy structure | Space: object requires documentation | |
109 | 413 | Hierarchy &1 is not valid for date &2 | Space: object requires documentation | |
110 | 414 | Hierarchy &1 was saved but not activated | Space: object requires documentation | |
111 | 415 | Hierarchy ID could not be found | Space: object requires documentation | |
112 | 416 | There is no description in the logon language for hierarchy &1 | Space: object requires documentation | |
113 | 417 | Hierarchy &1 is maintained inconsistently | Space: object requires documentation | |
114 | 418 | Hierarchies with link nodes cannot be used | Space: object requires documentation | |
115 | 419 | Selected node &1 does not exist | Space: object requires documentation | |
116 | 420 | Hierarchy &1 cannot be used | Space: object requires documentation | |
117 | 500 | **** Maintenance characteristic relationships *************************** | Space: object requires documentation | |
118 | 501 | Enter a basic characteristic | Space: object requires documentation | |
119 | 502 | Maintain the entries for the hierarchy | Space: object requires documentation | |
120 | 503 | Enter the source and target characteristic | Space: object requires documentation | |
121 | 504 | Characteristics must be different | Space: object requires documentation | |
122 | 505 | Characteristic &1 is not used in the hierarchy | Space: object requires documentation | |
123 | 506 | Enter two characteristics | Space: object requires documentation | |
124 | 507 | Characteristic &1 is not available in the planning area | Space: object requires documentation | |
125 | 508 | Characteristic &1 is not a valid attribute of &2 | Space: object requires documentation | |
126 | 509 | Enter a valid class name | Space: object requires documentation | |
127 | 510 | &1 characteristic relationships were deleted | Space: object requires documentation | |
128 | 511 | Maintain the version for the hierarchy | Space: object requires documentation | |
129 | 512 | Maintain the validity date for the hierarchy | Space: object requires documentation | |
130 | 513 | Enter characteristic(s) | Space: object requires documentation | |
131 | 514 | Specify a function module | Space: object requires documentation | |
132 | 515 | Value &1 of chara &2 does not correspond to the attrib.val &3 of chara &4 | Space: object requires documentation | |
133 | 516 | No value &2 can be found for characteristic &3 in hierarchy &1 | Space: object requires documentation | |
134 | 517 | The higher-level node to &1, does not have the value &2 and &3 | Space: object requires documentation | |
135 | 518 | No value was found for node &1 (characteristic &2) in step &3 | Space: object requires documentation | |
136 | 519 | Field &1 is not derived from characteristic relationships | Space: object requires documentation | |
137 | 520 | &1 is not a valid key figure | Space: object requires documentation | |
138 | 521 | No reference data available to derive | Space: object requires documentation | |
139 | 522 | No reference data available to check | Space: object requires documentation | |
140 | 523 | Values do not agree with reference data | Space: object requires documentation | |
141 | 524 | No attributes exist on the characteristic | Space: object requires documentation | |
142 | 525 | No combination could be generated in step &1 | Space: object requires documentation | |
143 | 526 | No combinations could be generated | Space: object requires documentation | |
144 | 527 | Characteristic combinations: No values could be found for chara. &1 | Space: object requires documentation | |
145 | 528 | Attribute &1 on characteristic &2 with value &3 is not available | Space: object requires documentation | |
146 | 529 | Characteristic combinations cannot be assigned to any basic area | Space: object requires documentation | |
147 | 530 | A record contains the incorrect value &1 in the planning area field | Space: object requires documentation | |
148 | 531 | Overflow with forecast of number of combinations | Space: object requires documentation | |
149 | 532 | Reference data is not unique | Space: object requires documentation | |
150 | 533 | Offset entries are only allowed for time characteristics | Space: object requires documentation | |
151 | 534 | Variable &1 must be restricted to a value | Space: object requires documentation | |
152 | 535 | Variable is not of the correct type | Space: object requires documentation | |
153 | 536 | Derivation: In hierarchy &1 no value can be found for characteristic &2 | Space: object requires documentation | |
154 | 537 | Derivation: In hierarchy &1 no value &2 exists for characteristic &3 | Space: object requires documentation | |
155 | 538 | Error occurred in exit implementation for variable exit | The short text describes the object sufficiently | |
156 | 539 | You have no authorization to change the planning area | The short text describes the object sufficiently | |
157 | 540 | Choose at least one planning area | The short text describes the object sufficiently | |
158 | 541 | BW installation has changed for &1 planning areas | The short text describes the object sufficiently | |
159 | 542 | Choose an RFC destination | The short text describes the object sufficiently |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in |