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)
⤷
⤷
Attributes
| Message class | UPA_MCB | |
| Short Description | ||
| Changed On | 20141101 | |
| Last Changed At | 091708 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Characteristic &3 is expected in exit for variable &1 (area &2) | Space: object requires documentation | ||
| 2 | Settings for planning area &1 were not found | The short text describes the object sufficiently | ||
| 3 | Planning scenario for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | ||
| 4 | Planning scenario for variable &1 (area &2) is not unique | The short text describes the object sufficiently | ||
| 5 | Controlling area for area &1 cannot be determined | Space: object requires documentation | ||
| 6 | Fiscal year variant for controlling area &1 is not defined | Space: object requires documentation | ||
| 7 | Fiscal year variant for planning area &1 is not unique | The short text describes the object sufficiently | ||
| 8 | Currency for controlling area &1 is not defined | Space: object requires documentation | ||
| 9 | Currency for planning area &1 is not unique | The short text describes the object sufficiently | ||
| 10 | Budget year for controlling area &1 is not defined | The short text describes the object sufficiently | ||
| 11 | Budget year for controlling area &1 is not unique | The short text describes the object sufficiently | ||
| 12 | Planning version for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | ||
| 13 | Key figure type for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | ||
| 14 | Key figure type for variable &1 (area &2) is not unique | The short text describes the object sufficiently | ||
| 15 | Budget category for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | ||
| 16 | Budget use for variable &1 (area &2) cannot be determined | The short text describes the object sufficiently | ||
| 17 | Only one controlling area should be configured for area &1 | The short text describes the object sufficiently | ||
| 18 | Variable &3 must be assigned to planning version &1 (area &2) | The short text describes the object sufficiently | ||
| 19 | Not all settings for planning area &1 may be changed | Space: object requires documentation | ||
| 20 | The setting for the planning area &1 should not be deleted | Space: object requires documentation | ||
| 21 | Budgeting method &1 is still used in planning scenarios | The short text describes the object sufficiently | ||
| 22 | No (suitable) entry found in Customizing table &1 | The short text describes the object sufficiently | ||
| 23 | Delete planning version &1 from all planning applications first | The short text describes the object sufficiently | ||
| 24 | Delete amount key figure &1 from all planning applications first | The short text describes the object sufficiently | ||
| 25 | Delete budget category &1 from all planning scenarios first | The short text describes the object sufficiently | ||
| 26 | Delete budget use &1 from all planning scenarios first | The short text describes the object sufficiently | ||
| 27 | Delete planning scenario &1 from all planning applications first | The short text describes the object sufficiently | ||
| 28 | Planning area &1 is already defined as a multiarea | The short text describes the object sufficiently | ||
| 29 | Multiarea &1 is already defined as a planning area | The short text describes the object sufficiently | ||
| 30 | Multiarea &1 is already used in another planning area | The short text describes the object sufficiently | ||
| 31 | There is already a planning scenario of the same category in area &1 | The short text describes the object sufficiently | ||
| 32 | There is already a planning version of the same type in area &1 | The short text describes the object sufficiently | ||
| 33 | There is already an amount key figure of the same type in area &1 | The short text describes the object sufficiently | ||
| 34 | The target year &1 for the budgeting is in the past | The short text describes the object sufficiently | ||
| 35 | The source year &1 for the budgeting is not before the target year | The short text describes the object sufficiently | ||
| 36 | You have not activated the new budgeting year &1 | The short text describes the object sufficiently | ||
| 37 | No entry is maintained for the controlling area &1 in table &2 | The short text describes the object sufficiently | ||
| 38 | No entry is maintained for the order type &1 in table &2 | The short text describes the object sufficiently | ||
| 39 | No entry is maintained in table &2 for the maintenance activity &1 | The short text describes the object sufficiently | ||
| 40 | No entry is maintained in table &2 for the WBS element &1 | The short text describes the object sufficiently | ||
| 41 | No default entry is defined for the budget category | The short text describes the object sufficiently | ||
| 42 | No default entry is defined for the budget use | The short text describes the object sufficiently | ||
| 43 | Internal: DDIC structure &1 not found | The short text describes the object sufficiently | ||
| 44 | Internal: DDIC structure &1 contains unsupported components | The short text describes the object sufficiently | ||
| 45 | Internal: Invalid entry (index &1) in table (structure &2) | The short text describes the object sufficiently | ||
| 46 | Internal: Ambiguous entry (index &1) in table (structure &2) | The short text describes the object sufficiently | ||
| 47 | Internal: Ambiguous entry (index &1) in table (structure &2) | The short text describes the object sufficiently | ||
| 48 | Invalid entry for table (structure &1) | The short text describes the object sufficiently | ||
| 49 | Duplicate entry (line &1) for table (structure &2) | The short text describes the object sufficiently | ||
| 50 | Ambiguous entry (line &1) for table (structure &2) | The short text describes the object sufficiently | ||
| 51 | No entry is maintained for the entry &1 in table &2 | The short text describes the object sufficiently | ||
| 52 | Data was already sent for approval | The short text describes the object sufficiently | ||
| 53 | Retraction of Approved Budget Planning Data: &1 &2 | The short text describes the object sufficiently | ||
| 54 | Zero-Data-Based Copy of Basis Cube => Planning Cube: &1 &2 | The short text describes the object sufficiently | ||
| 55 | History-Based Copy of Basis Cube => Planning Cube: &1 &2 | The short text describes the object sufficiently | ||
| 56 | Copy &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 57 | Ignore Record: Master Data for Equipment & Not Found | The short text describes the object sufficiently | ||
| 58 | Ignore Record: Master Data for Functional Location & Not Found | The short text describes the object sufficiently | ||
| 59 | Ignore Record: Master Data for Maintenance Item & Not Found | The short text describes the object sufficiently | ||
| 60 | Ignore Record: Master Data for Order & Not Found | The short text describes the object sufficiently | ||
| 61 | Task list &1 for equipment &2 is used in maintenance item(s) | The short text describes the object sufficiently | ||
| 62 | Task list &1 for funct. location &2 is used in maintenance item(s) | The short text describes the object sufficiently | ||
| 63 | Check the hierarchy area for the user &1 | Space: object requires documentation | ||
| 64 | The order numbers are missing for & records | The short text describes the object sufficiently | ||
| 65 | The maintenance item and the task list are missing for & records | The short text describes the object sufficiently | ||
| 66 | Copy records without assignment: &1 | The short text describes the object sufficiently | ||
| 67 | BAdI (UPA_MCB_RETRACT) for the retraction was not implemented | The short text describes the object sufficiently | ||
| 68 | Enter a valid RFC destination | The short text describes the object sufficiently | ||
| 69 | Approved budget planning data retracted to system: &1 | The short text describes the object sufficiently | ||
| 70 | Records (without assignment) were processed | The short text describes the object sufficiently | ||
| 71 | Task lists (without maintenance item) were processed | The short text describes the object sufficiently | ||
| 72 | Maintenance items (without technical object) were processed | The short text describes the object sufficiently | ||
| 73 | Functional locations (without equipment) were processed | The short text describes the object sufficiently | ||
| 74 | Equipment records were processed | The short text describes the object sufficiently | ||
| 75 | 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 |