SAP ABAP Message Class UPA_MCB (UPA_MCB)
Basic Data
Hierarchy
☛
BI_CONT (Software Component) Business Intelligence Content
⤷ BW-BCT-PLA-MCB (Application Component) PLM Maintenance Cost Budgeting
⤷ UPA_MCB (Package) Planning Application PLM Maintenance Cost Budgeting (MCB)
⤷ BW-BCT-PLA-MCB (Application Component) PLM Maintenance Cost Budgeting
⤷ UPA_MCB (Package) Planning Application PLM Maintenance Cost Budgeting (MCB)
Attributes
Message class | UPA_MCB | |
Short Description | ||
Changed On | 20141101 | |
Last Changed At | 091708 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Characteristic &3 is expected in exit for variable &1 (area &2) | Space: object requires documentation | |
2 | 002 | Settings for planning area &1 were not found | The short text describes the object sufficiently | |
3 | 003 | Planning scenario for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | |
4 | 004 | Planning scenario for variable &1 (area &2) is not unique | The short text describes the object sufficiently | |
5 | 005 | Controlling area for area &1 cannot be determined | Space: object requires documentation | |
6 | 006 | Fiscal year variant for controlling area &1 is not defined | Space: object requires documentation | |
7 | 007 | Fiscal year variant for planning area &1 is not unique | The short text describes the object sufficiently | |
8 | 008 | Currency for controlling area &1 is not defined | Space: object requires documentation | |
9 | 009 | Currency for planning area &1 is not unique | The short text describes the object sufficiently | |
10 | 010 | Budget year for controlling area &1 is not defined | The short text describes the object sufficiently | |
11 | 011 | Budget year for controlling area &1 is not unique | The short text describes the object sufficiently | |
12 | 012 | Planning version for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | |
13 | 013 | Key figure type for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | |
14 | 014 | Key figure type for variable &1 (area &2) is not unique | The short text describes the object sufficiently | |
15 | 015 | Budget category for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | |
16 | 016 | Budget use for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | |
17 | 025 | Only one controlling area should be configured for area &1 | The short text describes the object sufficiently | |
18 | 026 | Variable &3 must be assigned to planning version &1 (area &2) | The short text describes the object sufficiently | |
19 | 027 | Not all settings for planning area &1 may be changed | Space: object requires documentation | |
20 | 028 | The setting for the planning area &1 should not be deleted | Space: object requires documentation | |
21 | 029 | Budgeting method &1 is still used in planning scenarios | The short text describes the object sufficiently | |
22 | 030 | No (suitable) entry found in Customizing table &1 | The short text describes the object sufficiently | |
23 | 031 | Delete planning version &1 from all planning applications first | The short text describes the object sufficiently | |
24 | 032 | Delete amount key figure &1 from all planning applications first | The short text describes the object sufficiently | |
25 | 033 | Delete budget category &1 from all planning scenarios first | The short text describes the object sufficiently | |
26 | 034 | Delete budget use &1 from all planning scenarios first | The short text describes the object sufficiently | |
27 | 035 | Delete planning scenario &1 from all planning applications first | The short text describes the object sufficiently | |
28 | 036 | Planning area &1 is already defined as a multiarea | The short text describes the object sufficiently | |
29 | 037 | Multiarea &1 is already defined as a planning area | The short text describes the object sufficiently | |
30 | 038 | Multiarea &1 is already used in another planning area | The short text describes the object sufficiently | |
31 | 039 | There is already a planning scenario of the same category in area &1 | The short text describes the object sufficiently | |
32 | 040 | There is already a planning version of the same type in area &1 | The short text describes the object sufficiently | |
33 | 041 | There is already an amount key figure of the same type in area &1 | The short text describes the object sufficiently | |
34 | 042 | The target year &1 for the budgeting is in the past | The short text describes the object sufficiently | |
35 | 043 | The source year &1 for the budgeting is not before the target year | The short text describes the object sufficiently | |
36 | 044 | You have not activated the new budgeting year &1 | The short text describes the object sufficiently | |
37 | 045 | No entry is maintained for the controlling area &1 in table &2 | The short text describes the object sufficiently | |
38 | 046 | No entry is maintained for the order type &1 in table &2 | The short text describes the object sufficiently | |
39 | 047 | No entry is maintained in table &2 for the maintenance activity &1 | The short text describes the object sufficiently | |
40 | 048 | No entry is maintained in table &2 for the WBS element &1 | The short text describes the object sufficiently | |
41 | 049 | No default entry is defined for the budget category | The short text describes the object sufficiently | |
42 | 050 | No default entry is defined for the budget use | The short text describes the object sufficiently | |
43 | 051 | Internal: DDIC structure &1 not found | The short text describes the object sufficiently | |
44 | 052 | Internal: DDIC structure &1 contains unsupported components | The short text describes the object sufficiently | |
45 | 053 | Internal: Invalid entry (index &1) in table (structure &2) | The short text describes the object sufficiently | |
46 | 054 | Internal: Ambiguous entry (index &1) in table (structure &2) | The short text describes the object sufficiently | |
47 | 055 | Internal: Ambiguous entry (index &1) in table (structure &2) | The short text describes the object sufficiently | |
48 | 056 | Invalid entry for table (structure &1) | The short text describes the object sufficiently | |
49 | 057 | Duplicate entry (line &1) for table (structure &2) | The short text describes the object sufficiently | |
50 | 058 | Ambiguous entry (line &1) for table (structure &2) | The short text describes the object sufficiently | |
51 | 059 | No entry is maintained for the entry &1 in table &2 | The short text describes the object sufficiently | |
52 | 101 | Data was already sent for approval | The short text describes the object sufficiently | |
53 | 150 | Retraction of Approved Budget Planning Data: &1 &2 | The short text describes the object sufficiently | |
54 | 151 | Zero-Data-Based Copy of Basis Cube => Planning Cube: &1 &2 | The short text describes the object sufficiently | |
55 | 152 | History-Based Copy of Basis Cube => Planning Cube: &1 &2 | The short text describes the object sufficiently | |
56 | 153 | Copy &1 &2 &3 &4 | The short text describes the object sufficiently | |
57 | 154 | Ignore Record: Master Data for Equipment & Not Found | The short text describes the object sufficiently | |
58 | 155 | Ignore Record: Master Data for Functional Location & Not Found | The short text describes the object sufficiently | |
59 | 156 | Ignore Record: Master Data for Maintenance Item & Not Found | The short text describes the object sufficiently | |
60 | 157 | Ignore Record: Master Data for Order & Not Found | The short text describes the object sufficiently | |
61 | 158 | Task list &1 for equipment &2 is used in maintenance item(s) | The short text describes the object sufficiently | |
62 | 159 | Task list &1 for funct. location &2 is used in maintenance item(s) | The short text describes the object sufficiently | |
63 | 160 | Check the hierarchy area for the user &1 | Space: object requires documentation | |
64 | 161 | The order numbers are missing for & records | The short text describes the object sufficiently | |
65 | 162 | The maintenance item and the task list are missing for & records | The short text describes the object sufficiently | |
66 | 163 | Copy records without assignment: &1 | The short text describes the object sufficiently | |
67 | 164 | BAdI (UPA_MCB_RETRACT) for the retraction was not implemented | The short text describes the object sufficiently | |
68 | 165 | Enter a valid RFC destination | The short text describes the object sufficiently | |
69 | 166 | Approved budget planning data retracted to system: &1 | The short text describes the object sufficiently | |
70 | 170 | Records (without assignment) were processed | The short text describes the object sufficiently | |
71 | 171 | Task lists (without maintenance item) were processed | The short text describes the object sufficiently | |
72 | 172 | Maintenance items (without technical object) were processed | The short text describes the object sufficiently | |
73 | 173 | Functional locations (without equipment) were processed | The short text describes the object sufficiently | |
74 | 174 | Equipment records were processed | The short text describes the object sufficiently | |
75 | 175 | Data for maintenance orders couldn't be read | The short text describes the object sufficiently |
History
Last changed on/by | 20141101 | SAP | |
SAP Release Created in | 352 |