| UPC202 |
Error while calling up RFC |
| UPC203 |
Type & could not be activated |
| UPC204 |
The generated data is not contained in the selection condition |
| UPC205 |
Enter a value with a permitted format in field &1 |
| UPC206 |
Data must be saved first |
| UPC207 |
InfoCube &1 is already being used in planning area &2 |
| UPC208 |
&1 |
| UPC209 |
Impermissible characteristic derivation in Customer Exit |
| UPC210 |
Enter the RFC destination |
| UPC211 |
RFC destination &1 is not permitted |
| UPC212 |
RFC destination &1 is not a BW System with Release 1.2B or higher |
| UPC213 |
InfoCube &1 contains no usable characteristics |
| UPC214 |
InfoCube &1 contains no usable key figures |
| UPC215 |
Transport request &1 was compiled without errors |
| UPC216 |
Errors occurred during compilation of transport request &1 |
| UPC217 |
You have no authorization for the requested data |
| UPC218 |
You have no authorization to read the desired data |
| UPC219 |
Multiplanning area &1 cannot be used |
| UPC220 |
Data record is locked by data slice &1 |
| UPC221 |
For SEM 2.0B FCS, you cannot use BW 2.0B yet.You can use 2.0A |
| UPC222 |
You may not plan for the combination of characteristic values |
| UPC223 |
Multiplanning area &1 cannot be used |
| UPC224 |
&1 data records were read, &2 of them were changed, &3 generated |
| UPC225 |
Only the values EQ and BT are allowed in field OPTION, not &1 |
| UPC226 |
Only the value I is allowed in field SIGN, not &1 |
| UPC227 |
Higher-level characteristics must be selected with single values |
| UPC228 |
Planning profile &1 does not exist |
| UPC229 |
Selection to characteristic &1 is not restricted |
| UPC230 |
Rescheduling lead to invalid values |
| UPC231 |
User &1 does not exist |
| UPC232 |
Method was canceled after an error |
| UPC233 |
Invalid input parameter |
| UPC234 |
Value for characteristic &1 must be initial |
| UPC235 |
InfoCube &1 is not a real-time InfoCube |
| UPC236 |
No documents can be created in this multi area |
| UPC237 |
Planning cannot be performed for real-time InfoCube &1; see long text |
| UPC238 |
Selection is not suitable for any basic area |
| UPC239 |
Note: Change could make Customizing invalid; see long text |
| UPC240 |
Enter Customizing task |
| UPC241 |
Time shift for characteristic &1, value &2, shift &3 not possible |
| UPC242 |
Characteristic &1 cannot be documented |
| UPC243 |
Processing of planning function was terminated |
| UPC244 |
You are not authorized to use the SEM-BPS API Trace |
| UPC300 |
**** Execution of planning methods |
| UPC301 |
Planning function &1, parameter group &2 was carried out with no errors |
| UPC302 |
Errors occurred when executing planning function &1/&2 |
| UPC303 |
Object &1 |
| UPC304 |
The planning function cannot be executed |
| UPC305 |
Job &1 was scheduled for background processing |
| UPC306 |
Report &1 could not be entered in job &2 |
| UPC307 |
Fields (&1) that are not in the level, must remain initial |
| UPC308 |
Global planning sequence was terminated with errors |
| UPC309 |
Planning sequence &1 has been executed |
| UPC400 |
************* Hierarchy - BW Interface ********************************** |
| UPC401 |
&1 |
| UPC402 |
Error during data selection |
| UPC403 |
No suitable data records found for selection |
| UPC404 |
Parameter errors occurred during selection |
| UPC405 |
Selection was cancelled |
| UPC406 |
Error occurred during numbering of new hierarchy nodes |
| UPC407 |
Hierarchy &1 was not found |
| UPC408 |
Characteristic &1 was not found |
| UPC409 |
Conversion error of value &2 (characterictic &1) |
| UPC410 |
Value &2 for characteristic &1 not found |
| UPC411 |
Error during text selection for characterictic &1 (value &2) |
| UPC412 |
Incorrect hierarchy structure |
| UPC413 |
Hierarchy &1 is not valid for date &2 |
| UPC414 |
Hierarchy &1 was saved but not activated |
| UPC415 |
Hierarchy ID could not be found |
| UPC416 |
There is no description in the logon language for hierarchy &1 |
| UPC417 |
Hierarchy &1 is maintained inconsistently |
| UPC418 |
Hierarchies with link nodes cannot be used |
| UPC419 |
Selected node &1 does not exist |
| UPC420 |
Hierarchy &1 cannot be used |
| UPC500 |
**** Maintenance characteristic relationships *************************** |
| UPC501 |
Enter a basic characteristic |
| UPC502 |
Maintain the entries for the hierarchy |
| UPC503 |
Enter the source and target characteristic |
| UPC504 |
Characteristics must be different |
| UPC505 |
Characteristic &1 is not used in the hierarchy |
| UPC506 |
Enter two characteristics |
| UPC507 |
Characteristic &1 is not available in the planning area |
| UPC508 |
Characteristic &1 is not a valid attribute of &2 |
| UPC509 |
Enter a valid class name |
| UPC510 |
&1 characteristic relationships were deleted |
| UPC511 |
Maintain the version for the hierarchy |
| UPC512 |
Maintain the validity date for the hierarchy |
| UPC513 |
Enter characteristic(s) |
| UPC514 |
Specify a function module |
| UPC515 |
Value &1 of chara &2 does not correspond to the attrib.val &3 of chara &4 |
| UPC516 |
No value &2 can be found for characteristic &3 in hierarchy &1 |
| UPC517 |
The higher-level node to &1, does not have the value &2 and &3 |
| UPC518 |
No value was found for node &1 (characteristic &2) in step &3 |
| UPC519 |
Field &1 is not derived from characteristic relationships |
| UPC520 |
&1 is not a valid key figure |
| UPC521 |
No reference data available to derive |
| UPC522 |
No reference data available to check |
| UPC523 |
Values do not agree with reference data |
| UPC524 |
No attributes exist on the characteristic |
| UPC525 |
No combination could be generated in step &1 |