SAP ABAP Message Class /MRSS/SGE (Messages for the Scheduling Engine)
Basic Data
Hierarchy
☛
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net
⤷
PM-WOC-MO (Application Component) Maintenance Orders
⤷
/MRSS/SGE (Package) Multiresource Planning: Scheduling Engine
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net⤷
PM-WOC-MO (Application Component) Maintenance Orders⤷
/MRSS/SGE (Package) Multiresource Planning: Scheduling Engine 
Attributes
| Message class |  |
/MRSS/SGE |
| Short Description |  |
Messages for the Scheduling Engine |
| Changed On |  |
20141109 |
| Last Changed At |  |
161336 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
Critical exception error has occurred; contact your system administrator | Space: object requires documentation | |
| 2 | 001 |
Start time of assignment is later than the end time | Space: object requires documentation | |
| 3 | 002 |
Personnel resource &1 cannot be assigned to item &2 | Space: object requires documentation | |
| 4 | 003 |
Tool resource &1 cannot be assigned to item &2 | Space: object requires documentation | |
| 5 | 004 |
Tool resource &1 cannot be used as tool &2 | Space: object requires documentation | |
| 6 | 005 |
No individual object exists for tool &1 (&2) | Space: object requires documentation | |
| 7 | 006 |
Action cannot be undone | Space: object requires documentation | |
| 8 | 007 |
Action cannot be restored | Space: object requires documentation | |
| 9 | 008 |
Cannot determine start time for the demand | Space: object requires documentation | |
| 10 | 009 |
Cannot determine end time for the demand | Space: object requires documentation | |
| 11 | 010 |
Cannot determine duration of the demand | Space: object requires documentation | |
| 12 | 011 |
Link possible between personnel resource and tool only | Space: object requires documentation | |
| 13 | 012 |
Assignment demand cannot be changed | Space: object requires documentation | |
| 14 | 013 |
Enter a valid time interval for link [&1,&2] | Space: object requires documentation | |
| 15 | 014 |
Invalid relationship type &1 for link | Space: object requires documentation | |
| 16 | 015 |
Link already exists in the specified time interval | Space: object requires documentation | |
| 17 | 016 |
Selected demand is not an operation relevant to resource planning | Space: object requires documentation | |
| 18 | 017 |
Start time must be earlier than end time | Space: object requires documentation | |
| 19 | 018 |
Resource &1 is not a personnel resource | Space: object requires documentation | |
| 20 | 019 |
Selected demand &1 is not relevant for resource planning | Space: object requires documentation | |
| 21 | 020 |
Assignment &1 for resource &2 is being processed by user &3 | Space: object requires documentation | |
| 22 | 021 |
Resource &1 is being processed by user &3 on &2 | Space: object requires documentation | |
| 23 | 022 |
Operation &1 is being processed by user &2 | Space: object requires documentation | |
| 24 | 023 |
Link &1 is being processed by user &2 | Space: object requires documentation | |
| 25 | 024 |
Time allocation &1 for resource &2 is being processed by user &3 | Space: object requires documentation | |
| 26 | 025 |
Service process &1 cannot be assigned to resource &2 | Space: object requires documentation | |
| 27 | 026 |
Start date &1 is earlier than the start date &2 of the planning period | Space: object requires documentation | |
| 28 | 027 |
End date &1 is later than the end date of the planning period, &2 | Space: object requires documentation | |
| 29 | 028 |
Resource &1 already exists in planning board | Space: object requires documentation | |
| 30 | 029 |
Resource &3 is not available | Space: object requires documentation | |
| 31 | 030 |
Cannot determine a planning board profile | Space: object requires documentation | |
| 32 | 031 |
Planning board profile &1 not found | Space: object requires documentation | |
| 33 | 032 |
&1 is not assigned to an RP node as a planner in period &2-&3 | Space: object requires documentation | |
| 34 | 033 |
Time interval for teams must not be empty | Space: object requires documentation | |
| 35 | 034 |
Resource &1 not yet created in the MRS system | Space: object requires documentation | |
| 36 | 035 |
GUID &1 does not represent an individual object | Space: object requires documentation | |
| 37 | 036 |
Could not initialize resource &1 | Space: object requires documentation | |
| 38 | 037 |
Demand &1 does not exist in the MRS system | Space: object requires documentation | |
| 39 | 038 |
No team exists for GUID &1 | Space: object requires documentation | |
| 40 | 039 |
Order &1 is not consistent with resource planning | Space: object requires documentation | |
| 41 | 040 |
Cannot change capacity planning for team &1 | Space: object requires documentation | |
| 42 | 041 |
Cannot delete team &1; assignments exist | Space: object requires documentation | |
| 43 | 042 |
Assignment is not within the validity of the team | Space: object requires documentation | |
| 44 | 043 |
Team is not assigned to a resource planning node | Space: object requires documentation | |
| 45 | 044 |
Assignments for the team exist that are not within the specified validity | Space: object requires documentation | |
| 46 | 045 |
Assignment must match the validity of the team | Space: object requires documentation | |
| 47 | 046 |
Team description is missing | Space: object requires documentation | |
| 48 | 047 |
Planning board was saved successfully | Space: object requires documentation | |
| 49 | 048 |
Planning board was saved and updated successfully | Space: object requires documentation | |
| 50 | 049 |
Error while saving; reset the planning board | Space: object requires documentation | |
| 51 | 050 |
You are not authorized to edit the data for &1 | The short text describes the object sufficiently | |
| 52 | 051 |
You are not authorized to display the data for &1 | The short text describes the object sufficiently | |
| 53 | 052 |
You are not authorized to edit the planning board for orders | Space: object requires documentation | |
| 54 | 053 |
You are not authorized to display the planning board for orders | Space: object requires documentation | |
| 55 | 054 |
Error during the authorization check (authorization object &1) | Space: object requires documentation | |
| 56 | 055 |
Resource &1 locked on &2 by user &3 | Space: object requires documentation | |
| 57 | 056 |
Operation &1 is already locked by user &2 | Space: object requires documentation | |
| 58 | 057 |
Assignment of &1 to a resource planning node is not unique in [&2,&3] | Space: object requires documentation | |
| 59 | 058 |
Data was not changed | Space: object requires documentation | |
| 60 | 059 |
Assignment duration is less than the minimum duration (&1 minutes) | Space: object requires documentation | |
| 61 | 060 |
Utilization must be greater than 0% and less than or equal to 100% | Space: object requires documentation | |
| 62 | 061 |
Assignment splitting is not possible for teams from capacity planning | Space: object requires documentation | |
| 63 | 062 |
Assignment duration is too short for splitting | Space: object requires documentation | |
| 64 | 063 |
Error during relationship check; no network available for order &1 | Space: object requires documentation | |
| 65 | 064 |
Error in WFM Core; &1 &2 &3 | Space: object requires documentation | |
| 66 | 065 |
Error while creating assignment in WFM Core | Space: object requires documentation | |
| 67 | 066 |
Error while changing assignment in WFM Core | Space: object requires documentation | |
| 68 | 067 |
Time allocation type is missing | Space: object requires documentation | |
| 69 | 068 |
Time allocation is not available | Space: object requires documentation | |
| 70 | 069 |
Assignment is not available | Space: object requires documentation | |
| 71 | 070 |
Links are inactive in the planning board profile | Space: object requires documentation | |
| 72 | 071 |
Teams are inactive in the planning board profile | Space: object requires documentation | |
| 73 | 072 |
Error while initializing resource &1 (type: &2) | Space: object requires documentation | |
| 74 | 073 |
Resources in a link cannot be changed | Space: object requires documentation | |
| 75 | 074 |
Error initializing assignment &1 (resource: &2) | Space: object requires documentation | |
| 76 | 075 |
Cannot change resource of a time allocation | Space: object requires documentation | |
| 77 | 076 |
Demand &1 cannot be assigned to resource &2 | Space: object requires documentation | |
| 78 | 077 |
Duration of time allocation must be greater than 0 | Space: object requires documentation | |
| 79 | 078 |
Automatic assignment creation of demand &1 failed | Space: object requires documentation | |
| 80 | 079 |
No geolocation is available for resource &1 | Space: object requires documentation | |
| 81 | 080 |
No geolocation is available for demand &1 (business partner: &2) | Space: object requires documentation | |
| 82 | 081 |
Capacitive assignment overlaps with absence between &1 and &2. | Space: object requires documentation | |
| 83 | 082 |
Capacitive assignment overlaps with normal assignment at &1 | Space: object requires documentation | |
| 84 | 083 |
Demand &1 is implicitly locked; unlocking is not possible | Space: object requires documentation | |
| 85 | 084 |
The selected element is not a network activity | Space: object requires documentation | |
| 86 | 085 |
You can maintain the log text only for a network operation | Space: object requires documentation | |
| 87 | 086 |
For capacitive assignments, duration must be less than the time frame | Space: object requires documentation | |
| 88 | 087 |
Demand &1 does not allow capacitive planning | Space: object requires documentation | |
| 89 | 088 |
You are not authorized to edit the data for &1 | Space: object requires documentation | |
| 90 | 089 |
You are not authorized to select the resource for RP node &1 | Space: object requires documentation | |
| 91 | 090 |
You are not authorized to select the demand for RP node &1 | Space: object requires documentation | |
| 92 | 091 |
Manual lock cannot be released: object since changed | Space: object requires documentation | |
| 93 | 092 |
Cannot change assignments in current demand status | The short text describes the object sufficiently | |
| 94 | 093 |
Determination of tool or resource required to obtain links | The short text describes the object sufficiently | |
| 95 | 094 |
Resource &1 is not available | The short text describes the object sufficiently | |
| 96 | 095 |
No links data exists for the resource specified | The short text describes the object sufficiently | |
| 97 | 096 |
Cannot create link; data is missing | The short text describes the object sufficiently | |
| 98 | 097 |
Cannot create link; time stamp is empty | The short text describes the object sufficiently | |
| 99 | 098 |
Personnel number not identified for GUID &1 | The short text describes the object sufficiently | |
| 100 | 099 |
The resource(s) cannot be planned in one operation (&1) | Space: object requires documentation | |
| 101 | 100 |
Resource &1 is overloaded from &2 to &3 | Space: object requires documentation | |
| 102 | 101 |
Resource &1 is not available from &2 to &3 | Space: object requires documentation | |
| 103 | 102 |
Assignment &1 violates link to resource &2 | Space: object requires documentation | |
| 104 | 103 |
Data for deleting links not provided | The short text describes the object sufficiently | |
| 105 | 104 |
Cannot add filtered resource &1 | The short text describes the object sufficiently | |
| 106 | 105 |
Tool &1 is not scheduled with assignment &2 | Space: object requires documentation | |
| 107 | 106 |
Spare part demand &1 is not available for assignment &2 on &3 | Space: object requires documentation | |
| 108 | 107 |
Resources for demand &1 are not scheduled for the same time | Space: object requires documentation | |
| 109 | 108 |
Linked resources &1 and &2 for &3 are scheduled in different orders | Space: object requires documentation | |
| 110 | 109 |
Assignment &1 violates the link between &2 and &3 | Space: object requires documentation | |
| 111 | 110 |
Tool &1 is scheduled several times from &2 to &3 | Space: object requires documentation | |
| 112 | 111 |
Resource &1 is not suitable for assignment &2 | Space: object requires documentation | |
| 113 | 112 |
Cannot delete link &1 | The short text describes the object sufficiently | |
| 114 | 113 |
Team &1 is overloaded from &2 to &3 | Space: object requires documentation | |
| 115 | 114 |
Team &1 does not have any capacity from &2 to &3 | Space: object requires documentation | |
| 116 | 115 |
Utilization of team &1 is &4% | Space: object requires documentation | |
| 117 | 116 |
First assignment for demand &1 starts before the earliest start date &2 | Space: object requires documentation | |
| 118 | 117 |
First assignment for demand &1 starts after the latest start date &2 | Space: object requires documentation | |
| 119 | 118 |
Last assignment for demand &1 ends before the earliest end date &2 | Space: object requires documentation | |
| 120 | 119 |
Last assignment for demand &1 ends after the latest end date &2 | Space: object requires documentation | |
| 121 | 120 |
Resource &1 does not have the qualifications required for assignment &2 | Space: object requires documentation | |
| 122 | 121 |
Total duration &2 of assignments f. demand &1 is too long (plnd dur. &3) | Space: object requires documentation | |
| 123 | 122 |
Total duration &2 of assignments f. demand &1 is too short (plnd dur. &3) | Space: object requires documentation | |
| 124 | 123 |
Total duration &2 of assignments f. demand &1 is too long (plnd dur. &3) | Space: object requires documentation | |
| 125 | 124 |
Total duration &2 of assignments f. demand &1 is too short (plnd dur. &3) | Space: object requires documentation | |
| 126 | 125 |
First assignment for demand &1 starts after the SLA start date &2 | Space: object requires documentation | |
| 127 | 126 |
Last assignment for demand &1 ends after the SLA end date &2 | Space: object requires documentation | |
| 128 | 127 |
Duration not entered for demand &1 for some assignments | Space: object requires documentation | |
| 129 | 128 |
Time stamp is initial for resource &1 | The short text describes the object sufficiently | |
| 130 | 129 |
Link &1 deleted successfully | The short text describes the object sufficiently | |
| 131 | 130 |
Assignment &3 starts before assignment &1 &2 ends | Space: object requires documentation | |
| 132 | 131 |
Assignment &1 &2 ends after demand &3 is planned to start | Space: object requires documentation | |
| 133 | 132 |
Assignment &3 starts before demand &1 &2 is planned to end | Space: object requires documentation | |
| 134 | 133 |
Start of time stamp cannot be after end of time stamp | The short text describes the object sufficiently | |
| 135 | 134 |
Assignment &3 starts before assignment &1 &2 starts | Space: object requires documentation | |
| 136 | 135 |
Assignment &1 &2 starts after demand &3 is planned to start | Space: object requires documentation | |
| 137 | 136 |
Assignment &3 starts before demand &1 &2 is planned to start | Space: object requires documentation | |
| 138 | 137 |
Cannot create link for resource &1 and tool &2 | The short text describes the object sufficiently | |
| 139 | 138 |
Assignment &3 ends before assignment &1 &2 ends | Space: object requires documentation | |
| 140 | 139 |
Assignment &1 &2 ends after demand &3 is planned to end | Space: object requires documentation | |
| 141 | 140 |
Assignment &3 ends before demand &1 &2 is planned to end | Space: object requires documentation | |
| 142 | 141 |
Link created successfully for resource &1 and tool &2 | The short text describes the object sufficiently | |
| 143 | 142 |
Assignment &3 ends before assignment &1 &2 starts | Space: object requires documentation | |
| 144 | 143 |
Assignment &1 &2 starts after demand &3 is planned to end | Space: object requires documentation | |
| 145 | 144 |
Assignment &3 ends before demand &1 &2 is planned to start | Space: object requires documentation | |
| 146 | 145 |
Time allocation details are missing | The short text describes the object sufficiently | |
| 147 | 146 |
Assignment &3 does not start at the same time as assignment &1 | Space: object requires documentation | |
| 148 | 147 |
Assignment &1 does not start at same time as demand &3 is plnd to start | Space: object requires documentation | |
| 149 | 148 |
Assignment &3 does not start at same time as demand &1 is plnd to start | Space: object requires documentation | |
| 150 | 149 |
Error while creating time allocation for resource &1 | The short text describes the object sufficiently | |
| 151 | 150 |
Concrete status is already assigned to status &1 | Space: object requires documentation | |
| 152 | 151 |
Time allocation for resource &1 created successfully | The short text describes the object sufficiently | |
| 153 | 152 |
Time allocation &1 is not changed | The short text describes the object sufficiently | |
| 154 | 153 |
Time allocation &1 changed successfully | The short text describes the object sufficiently | |
| 155 | 154 |
Time stamp for &1 is empty | The short text describes the object sufficiently | |
| 156 | 155 |
Time allocation for resource &1 updated successfully | The short text describes the object sufficiently | |
| 157 | 156 |
Time allocation &1 not deleted | The short text describes the object sufficiently | |
| 158 | 157 |
Time allocation &1 deleted successfully | The short text describes the object sufficiently | |
| 159 | 158 |
Order number must be transferred with operation number | The short text describes the object sufficiently | |
| 160 | 159 |
Demand ID or GUID of demand must be provided | The short text describes the object sufficiently | |
| 161 | 160 |
Planning is not complete for demand &1 (planned start &2) | Space: object requires documentation | |
| 162 | 161 |
No time data available for assignment &1 (planned start &2) | Space: object requires documentation | |
| 163 | 162 |
Start of work delayed (&1) for assignment &2 (planned start &3) | Space: object requires documentation | |
| 164 | 163 |
End of work delayed (&1) for assignment &2 (planned end &3) | Space: object requires documentation | |
| 165 | 164 |
Work not yet ended for assignment &1 (planned end &2) | Space: object requires documentation | |
| 166 | 165 |
Premature end of work (&1) for assignment &2 (planned end &3) | Space: object requires documentation | |
| 167 | 166 |
&1% completion achieved for assignment &2 | Space: object requires documentation | |
| 168 | 167 |
Timeframe for assignment must be provided | The short text describes the object sufficiently | |
| 169 | 168 |
Resource must be provided to create assignment | The short text describes the object sufficiently | |
| 170 | 169 |
Abstract status &1 is already defined as the mobile status | Space: object requires documentation | |
| 171 | 170 |
Demand &1/&2: Automatic creation of assignment failed | Space: object requires documentation | |
| 172 | 171 |
You have no authorization for resource &1 from resource planning node &2 | The short text describes the object sufficiently | |
| 173 | 172 |
You are not authorized to access order &1 | The short text describes the object sufficiently | |
| 174 | 173 |
You have no authorization for resource planning node &1 | The short text describes the object sufficiently | |
| 175 | 174 |
No valid assignments were found for assignment GUID &1 | The short text describes the object sufficiently | |
| 176 | 175 |
No demands found | The short text describes the object sufficiently | |
| 177 | 176 |
No valid assignments found | The short text describes the object sufficiently | |
| 178 | 177 |
Assignment key must be provided | The short text describes the object sufficiently | |
| 179 | 178 |
Mobile status &1 is already defined as the abstract status | Space: object requires documentation | |
| 180 | 179 |
No date rule exists for this demand | The short text describes the object sufficiently | |
| 181 | 180 |
Capacitive assignment &1 has duration 0 | Space: object requires documentation | |
| 182 | 181 |
Extended assignment &1 has duration 0 | Space: object requires documentation | |
| 183 | 182 |
Stretched assignment for resource &1 exceeds planning horizon | Space: object requires documentation | |
| 184 | 183 |
MRS: Cannot delete demand for operation &1/&2 | Space: object requires documentation | |
| 185 | 184 |
Cannot change demand &1 | The short text describes the object sufficiently | |
| 186 | 185 |
Demand &1 does not allow changes due to status | The short text describes the object sufficiently | |
| 187 | 186 |
Start date is after end date | The short text describes the object sufficiently | |
| 188 | 187 |
Start date is earlier than start date of date rule &1 | The short text describes the object sufficiently | |
| 189 | 188 |
End date is later than end date of date rule &1 | The short text describes the object sufficiently | |
| 190 | 189 |
Start date &1 and end date &2 are outside planning period | The short text describes the object sufficiently | |
| 191 | 190 |
Resource &1 is not valid in period | The short text describes the object sufficiently | |
| 192 | 191 |
&2 &3: Field &1 has been changed | The short text describes the object sufficiently | |
| 193 | 192 |
Start and end dates must be provided for capacitive assignments | The short text describes the object sufficiently | |
| 194 | 193 |
Assignments can only be created for teams | Space: object requires documentation | |
| 195 | 194 |
Demand is not an offer (offer status not set) | The short text describes the object sufficiently | |
| 196 | 195 |
Offer demand does not have status "Manual resource confirmation" | The short text describes the object sufficiently | |
| 197 | 196 |
Offer demand has planned assignments: you cannot reject it | The short text describes the object sufficiently | |
| 198 | 197 |
& & & & | The short text describes the object sufficiently | |
| 199 | 198 |
Transfer time intervals with resource &1 | The short text describes the object sufficiently | |
| 200 | 199 |
No input parameters provided | The short text describes the object sufficiently | |
| 201 | 200 |
Link &1 was changed by user &2 | Space: object requires documentation | |
| 202 | 201 |
Link &1 was deleted by user &2 | Space: object requires documentation | |
| 203 | 202 |
Assignment &1 was changed by user &2 | Space: object requires documentation | |
| 204 | 203 |
Assignment &1 was deleted previously | Space: object requires documentation | |
| 205 | 204 |
Time allocation &1 was changed by user &2 | Space: object requires documentation | |
| 206 | 205 |
Time allocation &1 was deleted previously | Space: object requires documentation | |
| 207 | 206 |
Resource &1 was edited by user &3 on &2 | Space: object requires documentation | |
| 208 | 207 |
Transaction &1 was processed by user &2 | Space: object requires documentation | |
| 209 | 208 |
Operation &1 has since been changed | Space: object requires documentation | |
| 210 | 209 |
Operation &1 has since been deleted | Space: object requires documentation | |
| 211 | 210 |
Action is not permitted for assignment; check status | Space: object requires documentation | |
| 212 | 211 |
GUID for resource &1 not found | The short text describes the object sufficiently | |
| 213 | 212 |
Partner role &1 is already assigned | Space: object requires documentation | |
| 214 | 213 |
Start and end dates must be in the planning period between &1 and &2 | The short text describes the object sufficiently | |
| 215 | 214 |
Tool resource &1 is invalid | The short text describes the object sufficiently | |
| 216 | 215 |
Type of assignment is not permitted (&1) | The short text describes the object sufficiently | |
| 217 | 216 |
Time allocation deleted successfully | The short text describes the object sufficiently | |
| 218 | 217 |
There are no links between resource &1 and tool &2 | The short text describes the object sufficiently | |
| 219 | 218 |
Dates of assignment &1 are different from date rule of demand | The short text describes the object sufficiently | |
| 220 | 219 |
Could not create assignment for resource &1 | The short text describes the object sufficiently | |
| 221 | 220 |
Dur. of stretched assignment &1 for resource &2 is less than availability | Space: object requires documentation | |
| 222 | 221 |
Demand already has assignments; distribution is no longer possible | The short text describes the object sufficiently | |
| 223 | 222 |
Demand contains a time rule; cannot distribute | The short text describes the object sufficiently | |
| 224 | 223 |
Demand in process variant "manual confirmation"; cannot distribute | The short text describes the object sufficiently | |
| 225 | 224 |
Time interval is to be transferred | The short text describes the object sufficiently | |
| 226 | 225 |
Offer demand not yet arrived; distribution is not possible | The short text describes the object sufficiently | |
| 227 | 226 |
Assignment is not within the validity of the team | The short text describes the object sufficiently | |
| 228 | 227 |
Assignment for resource &1 is outside validity of team | The short text describes the object sufficiently | |
| 229 | 228 |
Demand &1 is already being processed by user &2 | The short text describes the object sufficiently | |
| 230 | 229 |
No further information is available | The short text describes the object sufficiently | |
| 231 | 230 |
Start time missing | Space: object requires documentation | |
| 232 | 231 |
End time missing | Space: object requires documentation | |
| 233 | 232 |
Time frame of capacitive assignment is smaller than duration | Space: object requires documentation | |
| 234 | 233 |
Time frame of capacitive assignment is equal to duration | Space: object requires documentation | |
| 235 | 234 |
Invalid on-call type &1; time allocation not created | The short text describes the object sufficiently | |
| 236 | 235 |
Error: external check class for demand type &1 | Space: object requires documentation | |
| 237 | 236 |
No work center found for resource | Space: object requires documentation | |
| 238 | 237 |
Object type does not correspond to subtype | Space: object requires documentation | |
| 239 | 238 |
Start or end time of demand &1 is outside original demand | The short text describes the object sufficiently | |
| 240 | 239 |
Start or end time of demand &1 not changed | The short text describes the object sufficiently | |
| 241 | 240 |
Selected equipment &1 is invalid | The short text describes the object sufficiently | |
| 242 | 241 |
You must adhere to the sum of total work | Space: object requires documentation | |
| 243 | 242 |
You must adhere to the sum of the duration | Space: object requires documentation | |
| 244 | 243 |
Total work must be larger than 0 | The short text describes the object sufficiently | |
| 245 | 244 |
Number of resources must be larger than 0 | The short text describes the object sufficiently | |
| 246 | 245 |
No valid resource planning node &1 | The short text describes the object sufficiently | |
| 247 | 246 |
No work center found for resource &1 | The short text describes the object sufficiently | |
| 248 | 247 |
Assignment probability must be 100% or less | The short text describes the object sufficiently | |
| 249 | 248 |
Cannot create assignment; resource is unavailable from &1 &2 to &3 &4 | The short text describes the object sufficiently | |
| 250 | 249 |
Time between assignment &1 and &2 is longer than normal working time &3 H | The short text describes the object sufficiently | |
| 251 | 250 |
Availability not possible for more than &1 hours; check Customizing | The short text describes the object sufficiently | |
| 252 | 251 |
Data for this resource is not buffered in the table | The short text describes the object sufficiently | |
| 253 | 252 |
&1 is not a valid resource | The short text describes the object sufficiently | |
| 254 | 253 |
&1 is not a valid organizational unit | The short text describes the object sufficiently | |
| 255 | 254 |
Buffered resource data is no longer valid | The short text describes the object sufficiently | |
| 256 | 255 |
Demand &1 is indicated as no longer changeable | Space: object requires documentation | |
| 257 | 256 |
Travel time cannot overlap with the assignment &1) | The short text describes the object sufficiently | |
| 258 | 257 |
This function is not supported | The short text describes the object sufficiently | |
| 259 | 258 |
Concretization exists in parallel w/ attendance time alloc. from &1 to &2 | The short text describes the object sufficiently | |
| 260 | 259 |
Concretization exists in parallel w/ absence time alloc. from &1 to &2 | The short text describes the object sufficiently | |
| 261 | 260 |
Calculating travel time requires planning period to be change from & to & | Space: object requires documentation | |
| 262 | 261 |
Duration of res. &1 availability longer than that of stretched assgmnt &2 | Space: object requires documentation | |
| 263 | 262 |
Resource &1 is overloaded due to the concretization of &2 to &3 | The short text describes the object sufficiently | |
| 264 | 263 |
Team &1 is overloaded due to the concretization of &2 to &3 | The short text describes the object sufficiently | |
| 265 | 264 |
Changing parallel assignments | The short text describes the object sufficiently | |
| 266 | 265 |
Start time of arrival is later than end time of arrival (&1) | The short text describes the object sufficiently | |
| 267 | 266 |
Start time of departure is later than end time of departure (&1) | The short text describes the object sufficiently | |
| 268 | 267 |
For resource &, the travel time falls in a non-availability from & to & | The short text describes the object sufficiently | |
| 269 | 268 |
For team &1, the travel time falls in a non-availability from &2 to &3 | The short text describes the object sufficiently | |
| 270 | 269 |
Assignment GUID &1 is not a valid GUID | The short text describes the object sufficiently | |
| 271 | 270 |
Cannot redo any more work steps | Space: object requires documentation | |
| 272 | 271 |
You cannot save a temporary, external demand key | The short text describes the object sufficiently | |
| 273 | 272 |
Enter a value for concretization option for parallel stretched assignment | The short text describes the object sufficiently | |
| 274 | 273 |
Assignment &1 must be within planning horizon | The short text describes the object sufficiently | |
| 275 | 274 |
Start date &1 is earlier than the start date &2 of the planning period | The short text describes the object sufficiently | |
| 276 | 275 |
End date &1 is later than the end date of the planning period, &2 | The short text describes the object sufficiently | |
| 277 | 276 |
Start and end dates must be in the planning period between &1 and &2 | The short text describes the object sufficiently | |
| 278 | 277 |
Source code called is obsolete (&1) | The short text describes the object sufficiently | |
| 279 | 278 |
Geolocations not maintained for demand &1 | The short text describes the object sufficiently | |
| 280 | 279 |
Address for demand &1 is not maintained | The short text describes the object sufficiently | |
| 281 | 280 |
Object for GUID &1 does not exist | The short text describes the object sufficiently | |
| 282 | 281 |
Resource &1 was removed from the current selection | The short text describes the object sufficiently | |
| 283 | 282 |
Cannot remove resource &1 from the current selection | The short text describes the object sufficiently | |
| 284 | 283 |
Intelligent shifting is not allowed for capacitive planning in teams | The short text describes the object sufficiently | |
| 285 | 284 |
Resource &1 does not have any information about the geolocation | The short text describes the object sufficiently | |
| 286 | 285 |
Not all resources are displayed (insufficient authorization) | The short text describes the object sufficiently | |
| 287 | 286 |
Error in MRS: &1 &2 &3 | The short text describes the object sufficiently | |
| 288 | 287 |
Team &1 is overloaded by &2 hours work | The short text describes the object sufficiently | |
| 289 | 288 |
Duration of link is outside validity period of team | The short text describes the object sufficiently | |
| 290 | 289 |
Subordinate assignment &1 is outside higher-level assignment &2 | The short text describes the object sufficiently | |
| 291 | 290 |
Date rule is outside time frame for assignment &1 | The short text describes the object sufficiently | |
| 292 | 291 |
Demand &1 does not permit abstract assignments | The short text describes the object sufficiently | |
| 293 | 292 |
Abstract assignment &1 has duration 0 | The short text describes the object sufficiently | |
| 294 | 293 |
Time frame of abstract assignment is shorter than duration | The short text describes the object sufficiently | |
| 295 | 294 |
&1 is not a valid organizational unit | The short text describes the object sufficiently | |
| 296 | 295 |
You cannot create abstract assignments for tool demands | The short text describes the object sufficiently | |
| 297 | 296 |
Subordinate assignment &1 is not within its higher-level assignment &2 | The short text describes the object sufficiently | |
| 298 | 297 |
Subordinate assignment &1 overlaps subordinate assignment &2 | The short text describes the object sufficiently | |
| 299 | 298 |
Ttl duration of sub. assgmnts is longer than that of higher-level ones | The short text describes the object sufficiently | |
| 300 | 299 |
Subordinate assgmnt &1 does not belong to same demand of higher-lvl assgm | The short text describes the object sufficiently | |
| 301 | 300 |
Duration &1 &2 is not a multiple of &3 minutes | Space: object requires documentation | |
| 302 | 301 |
Time &1 does not match the time granularity of &2 minutes | Space: object requires documentation | |
| 303 | 302 |
Time stamp &1 does not match the time granularity of &2 minutes | Space: object requires documentation | |
| 304 | 303 |
Sub. assgmt &1 does not belong to same resource as higher-level assgmt | The short text describes the object sufficiently | |
| 305 | 304 |
Abstract assignment &1 has duration 0 | The short text describes the object sufficiently | |
| 306 | 305 |
Manual splitting is not permitted for subordinate assignments | The short text describes the object sufficiently | |
| 307 | 306 |
Cutting is not permitted for subordinate assignments | The short text describes the object sufficiently | |
| 308 | 307 |
Enter a target resource for reassignment | The short text describes the object sufficiently | |
| 309 | 308 |
Cannot assign tool since assignment for demand &1 is capacitive | The short text describes the object sufficiently | |
| 310 | 309 |
Cannot cut since it is not possible to attach duration &1 | The short text describes the object sufficiently | |
| 311 | 310 |
Duration of split period is less than minimum duration (&1 minutes) | Space: object requires documentation | |
| 312 | 311 |
Split period is outside limits of assignment period | Space: object requires documentation | |
| 313 | 312 |
Resource &1 is not available for new assignment on &2 at &3 | Space: object requires documentation | |
| 314 | 313 |
Cannot create assignment | Space: object requires documentation | |
| 315 | 314 |
Split period must not be identical to assignment period | Space: object requires documentation | |
| 316 | 315 |
Cannot assign tool to selected demand | The short text describes the object sufficiently | |
| 317 | 316 |
Cannot assign tool to a technically completed order | The short text describes the object sufficiently | |
| 318 | 317 |
Tool &1 is not relevant to resource planning | Space: object requires documentation | |
| 319 | 318 |
Tool &1 does not exist in plant &2 | The short text describes the object sufficiently | |
| 320 | 319 |
Tool &1 is not a production resource or tool | The short text describes the object sufficiently | |
| 321 | 320 |
Cannot create tool &1 due to deletion indicator | The short text describes the object sufficiently | |
| 322 | 321 |
Could not assign tool since no plant was specified | The short text describes the object sufficiently | |
| 323 | 322 |
Equipment &1 does not exist or is not valid | The short text describes the object sufficiently | |
| 324 | 323 |
Could not assign tool since equipment or plant is missing | The short text describes the object sufficiently | |
| 325 | 324 |
Could not assign tool; no material exists in equipment | Space: object requires documentation | |
| 326 | 325 |
Resource &1 is not configured in the WFM Core to use Groupware | Space: object requires documentation | |
| 327 | 326 |
The task has a duration of zero | Space: object requires documentation | |
| 328 | 327 |
Cutting is not permitted for assignment type &1 | The short text describes the object sufficiently | |
| 329 | 328 |
Choose an on-call type | Space: object requires documentation | |
| 330 | 329 |
Specified on-call type is incorrect | Space: object requires documentation | |
| 331 | 330 |
No on-call types maintained for &1 | Space: object requires documentation | |
| 332 | 331 |
Cannot save due to alerts | Space: object requires documentation | |
| 333 | 332 |
Cannot change time allocations from HR | The short text describes the object sufficiently | |
| 334 | 333 |
HR transfer for resource &1 is in process | Space: object requires documentation | |
| 335 | 334 |
HR transfer for resource &1 complete | Space: object requires documentation | |
| 336 | 335 |
Cannot save since HR transfer for &1 is in process | The short text describes the object sufficiently | |
| 337 | 336 |
You are not authorized to plan resource &1 | The short text describes the object sufficiently | |
| 338 | 337 |
You are not authorized to plan operation &1 | The short text describes the object sufficiently | |
| 339 | 338 |
Assignment exceeds validity period for resource &1 | The short text describes the object sufficiently | |
| 340 | 339 |
Cannot determine end time of stretched assignment for resource &1 | Space: object requires documentation | |
| 341 | 340 |
Resource is not available for the current timeframe | The short text describes the object sufficiently | |
| 342 | 341 |
Resource &1 is currently being processed by user &2 | The short text describes the object sufficiently | |
| 343 | 342 |
Work center &1 in plant &2 is overloaded from &3 to &4 | The short text describes the object sufficiently | |
| 344 | 343 |
Resource-planning-relevant operation &1 is not copied to MRS | Space: object requires documentation | |
| 345 | 344 |
WBS element &1 is locked by user &2 | The short text describes the object sufficiently | |
| 346 | 345 |
Project &1 is locked by user &2 | The short text describes the object sufficiently | |
| 347 | 346 |
You cannot create a new demand for this network | Space: object requires documentation | |
| 348 | 347 |
Team &1 cannot be assigned to demand item &2 | The short text describes the object sufficiently | |
| 349 | 348 |
Assignment for demand &1 is carried out by another team resource | The short text describes the object sufficiently | |
| 350 | 349 |
You cannot change the work center of a scheduled demand | Space: object requires documentation | |
| 351 | 350 |
Creation of change documents is inactive for &1 | The short text describes the object sufficiently | |
| 352 | 351 |
Order/network closed; cannot create new demand | The short text describes the object sufficiently | |
| 353 | 352 |
No valid items found for order &1 | The short text describes the object sufficiently | |
| 354 | 353 |
Work center of demand is not assigned to an organizational unit | The short text describes the object sufficiently | |
| 355 | 354 |
No availability information for resource &1 after period &2 exists | Space: object requires documentation | |
| 356 | 355 |
End time of optimization is before the start time | Space: object requires documentation | |
| 357 | 356 |
Cannot optimize in the past | The short text describes the object sufficiently | |
| 358 | 357 |
Assignment description is too long; enter a maximum of 80 characters | The short text describes the object sufficiently | |
| 359 | 358 |
Cannot recalculate splits for &1 assignment type | The short text describes the object sufficiently | |
| 360 | 359 |
Assignment cannot be changed; split is already confirmed | The short text describes the object sufficiently | |
| 361 | 360 |
You can create a time allocation of type &1 only after you save | Space: object requires documentation | |
| 362 | 361 |
Time allocation of type &1 cannot be changed or deleted | The short text describes the object sufficiently | |
| 363 | 362 |
Resource &1 is locked by another user | The short text describes the object sufficiently | |
| 364 | 363 |
Could not create &1 in HCM; check your settings | The short text describes the object sufficiently | |
| 365 | 364 |
Availability of resource &1 has been changed | The short text describes the object sufficiently | |
| 366 | 365 |
&1&2&3&4 | The short text describes the object sufficiently | |
| 367 | 366 |
Enter a daily work schedule | The short text describes the object sufficiently | |
| 368 | 367 |
Logical system for HCM is not defined | Space: object requires documentation | |
| 369 | 368 |
Mapping of time allocation types to infotype/subtype is not unique | Space: object requires documentation | |
| 370 | 369 |
Details for alternative working time are missing | The short text describes the object sufficiently | |
| 371 | 370 |
Cannot create alternative working time; enter start and end date/time | The short text describes the object sufficiently | |
| 372 | 371 |
Error while creating alternative working time for resource &1 | The short text describes the object sufficiently | |
| 373 | 372 |
Alternative working time for resource &1 created successfully | The short text describes the object sufficiently | |
| 374 | 373 |
Cannot create alternative working time; enter a subtype | The short text describes the object sufficiently | |
| 375 | 374 |
Subtype &1 is not planning-relevant for resource &2 | The short text describes the object sufficiently | |
| 376 | 375 |
Cannot create alternative working time; enter a daily work schedule | The short text describes the object sufficiently | |
| 377 | 376 |
Daily work schedule &1, variant &2 is not valid for resource &3 | The short text describes the object sufficiently | |
| 378 | 377 |
Cannot determine alternative working time; time stamp is empty | The short text describes the object sufficiently | |
| 379 | 378 |
Cannot determine alternative working time for resource &1 | The short text describes the object sufficiently | |
| 380 | 379 |
Period must be defined as full-day; time is not relevant | The short text describes the object sufficiently | |
| 381 | 380 |
Error during HR backward integration | Space: object requires documentation | |
| 382 | 381 |
Fatal exception error in HCM (dump) during HR backward integration | The short text describes the object sufficiently | |
| 383 | 382 |
Fatal exception error &1 &2 | The short text describes the object sufficiently | |
| 384 | 383 |
Alternative working time must be defined as full-day | The short text describes the object sufficiently | |
| 385 | 384 |
You can create/delete alternative working times only after you have saved | The short text describes the object sufficiently | |
| 386 | 385 |
Time allocation type &1 is not intended for resource &2 | The short text describes the object sufficiently | |
| 387 | 386 |
Cannot delete alt. working time; "Can Be Deleted" indicator not selected | The short text describes the object sufficiently | |
| 388 | 387 |
Time allocation GUID &1 replaced by GUID &2 | The short text describes the object sufficiently | |
| 389 | 388 |
No time allocation found for GUID &1 | The short text describes the object sufficiently | |
| 390 | 389 |
Alternative working time for resource &1 deleted successfully | The short text describes the object sufficiently | |
| 391 | 390 |
Error while deleting alternative working time for resource &1 | The short text describes the object sufficiently | |
| 392 | 391 |
Alternative working time for resource &1 deleted successfully | The short text describes the object sufficiently | |
| 393 | 392 |
Enter a work center | The short text describes the object sufficiently | |
| 394 | 393 |
Enter the plant for the work center | The short text describes the object sufficiently | |
| 395 | 394 |
Duration of the demand is invalid | The short text describes the object sufficiently | |
| 396 | 395 |
Start and end dates must be in the planning period between &1 and &2 | The short text describes the object sufficiently | |
| 397 | 396 |
Start date &1 is earlier than the start date &2 of the planning period | The short text describes the object sufficiently | |
| 398 | 397 |
End date &1 is later than the end date of the planning period, &2 | The short text describes the object sufficiently | |
| 399 | 398 |
Work of the demand is invalid | The short text describes the object sufficiently | |
| 400 | 399 |
Number of resources must not be zero | The short text describes the object sufficiently | |
| 401 | 400 |
Totals bar: time overlap during assignment &2 for resource &1 | Space: object requires documentation | |
| 402 | 401 |
Scheduling demand &1 did not result in scheduling changes | The short text describes the object sufficiently | |
| 403 | 402 |
Planning node &1 already exists in the planning board | The short text describes the object sufficiently | |
| 404 | 403 |
Planning node &1 is not assigned to an organizational unit; cannot load | The short text describes the object sufficiently | |
| 405 | 404 |
Order type cannot be initial | The short text describes the object sufficiently | |
| 406 | 405 |
Abstract status &1 is not assigned to a concrete status | The short text describes the object sufficiently | |
| 407 | 406 |
Resource data inconsistent; cannot process the data | The short text describes the object sufficiently | |
| 408 | 407 |
Vehicle already exists on the planning board | The short text describes the object sufficiently | |
| 409 | 408 |
Start date &1, end date &2 must be in the planning period &3 - &4 | The short text describes the object sufficiently | |
| 410 | 409 |
& & & & | The short text describes the object sufficiently | |
| 411 | 410 |
Backward integration of the demand is deactivated; cannot split | The short text describes the object sufficiently | |
| 412 | 411 |
Updating demand data for order &1 from &2 | Space: object requires documentation | |
| 413 | 412 |
Additional customer attribute for the team is invalid | The short text describes the object sufficiently | |
| 414 | 413 |
Only one additional customer attribute is supported | The short text describes the object sufficiently | |
| 415 | 414 |
Additional customer attribute is supported only for the team | The short text describes the object sufficiently | |
| 416 | 415 |
Enter data for the field name for the additional customer attribute | The short text describes the object sufficiently | |
| 417 | 416 |
Assignment &1 does not permit concrete or stretched planning | The short text describes the object sufficiently | |
| 418 | 417 |
User not recognized; set &1 as the active user | Space: object requires documentation | |
| 419 | 418 |
Selected status for demand type &1 is not permitted | The short text describes the object sufficiently | |
| 420 | 419 |
Demand split for &1 orders is not permitted | The short text describes the object sufficiently | |
| 421 | 420 |
Resource &1 already belongs to the team | The short text describes the object sufficiently | |
| 422 | 421 |
Start date &1 is earlier than start date &2 of team for resource &3 &4 | The short text describes the object sufficiently | |
| 423 | 422 |
End date &1 is later than the end date &2 of the team for resource &3 &4 | The short text describes the object sufficiently | |
| 424 | 423 |
Start and end date must be in the period btw &1 and &2 for resource &3 &4 | The short text describes the object sufficiently | |
| 425 | 424 |
No team manager is assigned to the team between &1 and &2 | The short text describes the object sufficiently | |
| 426 | 425 |
Resource &1 &2 must be within team validity between &3 and &4 | The short text describes the object sufficiently | |
| 427 | 426 |
Start time is after the end time for resource &1 | The short text describes the object sufficiently | |
| 428 | 427 |
Enter valid times for resource &1 &2 | The short text describes the object sufficiently | |
| 429 | 428 |
Start date &1 of resource &2 is before start date &3 of PLB horizon | The short text describes the object sufficiently | |
| 430 | 429 |
End date &1 of resource &2 is after end date &3 of PLB horizon | The short text describes the object sufficiently | |
| 431 | 430 |
There is more than one team manager in a given period | The short text describes the object sufficiently | |
| 432 | 431 |
Resource &1 already exists in the team in the period specified | The short text describes the object sufficiently | |
| 433 | 432 |
No team manager exists between &1 and &2 in the team validity specified | The short text describes the object sufficiently | |
| 434 | 433 |
Start date is after end date for team &3 | The short text describes the object sufficiently | |
| 435 | 434 |
Enter valid start and end times for team &1 | The short text describes the object sufficiently | |
| 436 | 435 |
Tool &1 and demand &1 originate from different systems | The short text describes the object sufficiently | |
| 437 | 436 |
&1: class does not exist | The short text describes the object sufficiently | |
| 438 | 437 |
Start and end date is falling in the past | The short text describes the object sufficiently | |
| 439 | 438 |
Order operation is already assigned to resource &1 on &2 at &3 | The short text describes the object sufficiently | |
| 440 | 439 |
Breaks cannot be moved beyond the permitted intervals &1 - &2 | The short text describes the object sufficiently | |
| 441 | 440 |
Stretched assignm. &1 could not be changed; beyond planning horizon | Space: object requires documentation | |
| 442 | 441 |
Cannot create additional assignment; demand already has &1 assignments | Space: object requires documentation | |
| 443 | 442 |
Demand time frame was chosen for employee search | Space: object requires documentation | |
| 444 | 443 |
Specify the language | The short text describes the object sufficiently | |
| 445 | 444 |
Backward integration of the demand duration is deactivated; cannot split | The short text describes the object sufficiently | |
| 446 | 445 |
&1 is not a valid status | Space: object requires documentation | |
| 447 | 446 |
Planning period was recalculated from demand dates | The short text describes the object sufficiently | |
| 448 | 447 |
Demand &1 is of a type for which printing is not supported | Space: object requires documentation | |
| 449 | 448 |
Save your changes before displaying or printing documents | Space: object requires documentation | |
| 450 | 449 |
Assignment cut is not allowed; "Assignment Follows Demand" is active | The short text describes the object sufficiently | |
| 451 | 450 |
Collisions between planning board elements detected | Space: object requires documentation | |
| 452 | 451 |
&1: Collision between two travel times is not permitted | The short text describes the object sufficiently | |
| 453 | 452 |
Limited number of proposals; no. of working days exceeds planning horizon | Space: object requires documentation | |
| 454 | 453 |
Assignment &1 not created; conflicts during assignment follows demand | The short text describes the object sufficiently | |
| 455 | 454 |
Assignment &1 deleted; conflicts during assignment follows demand | Space: object requires documentation | |
| 456 | 455 |
Assignment split is not allowed; assignment follows demand is active | The short text describes the object sufficiently | |
| 457 | 456 |
End date &1 of team &2 is after end date &3 of PLB horizon | The short text describes the object sufficiently | |
| 458 | 457 |
Assignment is following demand dates | The short text describes the object sufficiently | |
| 459 | 458 |
Space: object requires documentation | ||
| 460 | 459 |
An entry already exists with priority &1 | The short text describes the object sufficiently | |
| 461 | 460 |
Assignment &1 has a longer duration than normal working time &2 H | The short text describes the object sufficiently | |
| 462 | 461 |
Cannot create assignment; demand is not relevant for resource planning | The short text describes the object sufficiently | |
| 463 | 462 |
Assignment &1 not created; conflicts during assignment follows demand | The short text describes the object sufficiently | |
| 464 | 463 |
Assignment &1 deleted; conflicts during assignment follows demand | The short text describes the object sufficiently | |
| 465 | 464 |
Assignment split is not allowed; assignment follows demand is active | The short text describes the object sufficiently | |
| 466 | 465 |
Assignment is created/updated based on demand dates; assign. follows dem. | The short text describes the object sufficiently | |
| 467 | 466 |
Not all single demands in the complex demand &1 could be shifted | Space: object requires documentation | |
| 468 | 467 |
Demand &1 has relationships that cannot be handled | Space: object requires documentation | |
| 469 | 468 |
Assignment precedes validity period for resource &1 | The short text describes the object sufficiently | |
| 470 | 469 |
Original start and end dates of demand &1 are not within planning period | Space: object requires documentation | |
| 471 | 470 |
Resource &1 is not valid from &2 to &3 | The short text describes the object sufficiently | |
| 472 | 471 |
Maintain the correct time unit for day-based planning in Customizing | The short text describes the object sufficiently | |
| 473 | 472 |
Qualification matching was not performed for &1; see long text | Space: object requires documentation | |
| 474 | 473 |
A mixture of HR resources and teams are selected for matching | The short text describes the object sufficiently | |
| 475 | 474 |
Enter both order type and time zone indicator | The short text describes the object sufficiently | |
| 476 | 475 |
An entry with the same key already exists | The short text describes the object sufficiently | |
| 477 | 476 |
The role type specified does not belong to an abstract role type | The short text describes the object sufficiently | |
| 478 | 477 |
Enter valid order type | The short text describes the object sufficiently | |
| 479 | 478 |
No resource/team valid for qualification matching | The short text describes the object sufficiently | |
| 480 | 479 |
Could not create assignment for tool resource | Space: object requires documentation | |
| 481 | 480 |
Selected status &1 is not valid for demand | The short text describes the object sufficiently | |
| 482 | 481 |
Tool demand was created | The short text describes the object sufficiently | |
| 483 | 482 |
&1: No free slot found for the order | The short text describes the object sufficiently | |
| 484 | 483 |
&1: No resource found within utilization threshold | The short text describes the object sufficiently | |
| 485 | 484 |
&1: Assignment already exists for demand; auto. assignment not created | The short text describes the object sufficiently | |
| 486 | 485 |
&: Constraint check: Relationship to existing assignments; no date found | The short text describes the object sufficiently | |
| 487 | 486 |
Single demands with multiple FS relationships exist in selected demand &1 | Space: object requires documentation | |
| 488 | 487 |
&1: No resource found with free availability | The short text describes the object sufficiently | |
| 489 | 488 |
&1: No resource found with sufficient qualifications | The short text describes the object sufficiently | |
| 490 | 489 |
No valid team members found for qualification matching | The short text describes the object sufficiently | |
| 491 | 490 |
HR time allocations cannot be created for multiple resources | The short text describes the object sufficiently | |
| 492 | 491 |
Duplicate time record entered for &1 , demand &2 at &3 &4 | The short text describes the object sufficiently | |
| 493 | 492 |
Planning horizon lies in the past; no slots can be found | The short text describes the object sufficiently | |
| 494 | 493 |
Assignments cannot be aligned; see long text | Space: object requires documentation | |
| 495 | 494 |
Assignment is completed; changes are no longer possible | The short text describes the object sufficiently | |
| 496 | 495 |
Assignment cannot be moved from N.N. resource to another resource type | The short text describes the object sufficiently | |
| 497 | 496 |
Assignment cannot be moved to N.N. resources | The short text describes the object sufficiently | |
| 498 | 497 |
The short text describes the object sufficiently | ||
| 499 | 500 |
Entry & does not exists as abstract status or mobile status | The short text describes the object sufficiently | |
| 500 | 501 |
Assignment &1 overlaps with the arrival of assignment &2 from &3 to &4 | The short text describes the object sufficiently | |
| 501 | 502 |
Assignment &1 overlaps with the departure of assignment &2 from &3 to &4 | The short text describes the object sufficiently | |
| 502 | 503 |
Travel time from &1 to &2 overlaps with absence of resource &3 | The short text describes the object sufficiently | |
| 503 | 504 |
Travel times &1 &2 and &3 &4 overlap | The short text describes the object sufficiently | |
| 504 | 505 |
Order &1 has been changed; see long text | Space: object requires documentation | |
| 505 | 506 |
Order &1 has since been deleted | The short text describes the object sufficiently | |
| 506 | 507 |
No suitable time slot found for an assignment | The short text describes the object sufficiently | |
| 507 | 508 |
Availability for team is not found for stretched assignment | The short text describes the object sufficiently | |
| 508 | 509 |
Travel to distance for assignment &1 exceeds configured value of &2 &3 | Space: object requires documentation | |
| 509 | 510 |
Travel from distance for assignment &1 exceeds configured value of &2 &3 | The short text describes the object sufficiently | |
| 510 | 511 |
Planned status logic for order type & item type & not provided | The short text describes the object sufficiently | |
| 511 | 512 |
Demand type cannot be blank | The short text describes the object sufficiently | |
| 512 | 515 |
Bundle &1 was created | The short text describes the object sufficiently | |
| 513 | 516 |
Bundle &1 was updated | The short text describes the object sufficiently | |
| 514 | 517 |
Bundle &1 was deleted | The short text describes the object sufficiently | |
| 515 | 518 |
Cut is not possible; cannot determine utilization (availability) | The short text describes the object sufficiently | |
| 516 | 519 |
Demand & is bundled; scheduling cannot be done | The short text describes the object sufficiently | |
| 517 | 522 |
Demand &1/&2 duration does not fit in the bundle period | Space: object requires documentation | |
| 518 | 523 |
Demand &1/&2 has a different main object | The short text describes the object sufficiently | |
| 519 | 524 |
Demand &1/&2 has a different customer | The short text describes the object sufficiently | |
| 520 | 525 |
Demand with GUID &1 does not exist; check with your system administrator | The short text describes the object sufficiently | |
| 521 | 526 |
Bundle does not exist for the demand | The short text describes the object sufficiently | |
| 522 | 527 |
No Service Area found for the demand &1 | Space: object requires documentation | |
| 523 | 528 |
Demand &1/&2 belongs to bundling group &3 | Space: object requires documentation | |
| 524 | 529 |
Demand &1/&2 has operation user status &3 which is set for exclusion | Space: object requires documentation | |
| 525 | 530 |
Assignments cannot be aligned; assignment simulation failed | The short text describes the object sufficiently | |
| 526 | 531 |
Assignments cannot be aligned; splits are not allowed for alignment | The short text describes the object sufficiently | |
| 527 | 532 |
Assignments cannot be aligned; parallel assignments exist | The short text describes the object sufficiently | |
| 528 | 533 |
Specify a maximum allowed time gap to activate alignment | The short text describes the object sufficiently | |
| 529 | 534 |
Assignments cannot be aligned; assignment lies in non-availability | The short text describes the object sufficiently | |
| 530 | 535 |
Assignments cannot be aligned; assignment lies outside demand dates | The short text describes the object sufficiently | |
| 531 | 536 |
Interval ID &1 does not lie on the same level of interval ID &2 | The short text describes the object sufficiently | |
| 532 | 537 |
Time frame of interval ID &1 lies outside the range of parent ID &2 | The short text describes the object sufficiently | |
| 533 | 538 |
Time frame of interval ID &1 overlaps with interval ID &2 | The short text describes the object sufficiently | |
| 534 | 539 |
Demand &1/&2 has a different error-causing object | The short text describes the object sufficiently | |
| 535 | 540 |
Demand &1/&2 has different main or error-causing object | The short text describes the object sufficiently | |
| 536 | 542 |
Demand &1/&2; planning node &3 has no working time in capacity settings | Space: object requires documentation | |
| 537 | 543 |
Enter an interval ID | The short text describes the object sufficiently | |
| 538 | 544 |
Enter a qualification category | The short text describes the object sufficiently | |
| 539 | 545 |
Parent Interval ID: &1 is not defined | The short text describes the object sufficiently | |
| 540 | 546 |
The short text describes the object sufficiently | ||
| 541 | 547 |
Demand &1 was not shifted; work center capacity is not exceeded | Space: object requires documentation | |
| 542 | 548 |
Slots could not be found for demand &1; not enough capacity left | Space: object requires documentation | |
| 543 | 549 |
Demand &1/&2 has a different number of resources | The short text describes the object sufficiently | |
| 544 | 550 |
Demand is not relevant for planning | The short text describes the object sufficiently | |
| 545 | 551 |
Resource &1 cannot be dragged, see long text | Space: object requires documentation | |
| 546 | 552 |
Resource &1 cannot be dragged, see long text | Space: object requires documentation | |
| 547 | 553 |
Resource &1 cannot be dragged, see long text | Space: object requires documentation | |
| 548 | 554 |
Order &1 is locked | The short text describes the object sufficiently | |
| 549 | 555 |
The short text describes the object sufficiently | ||
| 550 | 556 |
Bundle priority &1 is lower than the highest demand priority &2 | The short text describes the object sufficiently | |
| 551 | 557 |
Total demand duration does not fit into the bundling period | The short text describes the object sufficiently | |
| 552 | 558 |
Bundle start date and time is less than end date and time | The short text describes the object sufficiently | |
| 553 | 559 |
Demand &1/&2 cannot be bundled in &3; demand already belongs to bundle &4 | The short text describes the object sufficiently | |
| 554 | 560 |
Bundle ID cannot be generated; number range has not been defined | Space: object requires documentation | |
| 555 | 561 |
Bundle GUID error; contact your system administrator | The short text describes the object sufficiently | |
| 556 | 562 |
Demand &1/&2; no overlapping period found | The short text describes the object sufficiently | |
| 557 | 563 |
Demand &1 belongs to bundle &2; &3 cannot be changed/added | The short text describes the object sufficiently | |
| 558 | 564 |
Demand &1 is deleted from bundle &2; &3 was changed/added | The short text describes the object sufficiently | |
| 559 | 565 |
The short text describes the object sufficiently | ||
| 560 | 566 |
Enter a bundle start date and time | The short text describes the object sufficiently | |
| 561 | 567 |
Enter a bundle end date and time | The short text describes the object sufficiently | |
| 562 | 568 |
Bundle cannot exist without any demand | The short text describes the object sufficiently | |
| 563 | 569 |
Demand &1/&2; planning node &3 has no start time in capacity settings | Space: object requires documentation | |
| 564 | 570 |
Single demands and complex demands cannot be shifted together | Space: object requires documentation | |
| 565 | 571 |
Selected demand &1 is not relevant for this action | Space: object requires documentation | |
| 566 | 572 |
Selected demand has no work center | Space: object requires documentation | |
| 567 | 573 |
Demand &1/&2; planning node &3 has no end time in capacity settings | Space: object requires documentation | |
| 568 | 575 |
You cannot change the demand dates according to Customizing settings | Space: object requires documentation | |
| 569 | 576 |
Assignment creation failed for the order; see long text for details | Space: object requires documentation | |
| 570 | 577 |
You cannot create a new demand in the planning board; see long text | Space: object requires documentation | |
| 571 | 578 |
Demand split is not allowed according to Customizing settings | Space: object requires documentation | |
| 572 | 579 |
The short text describes the object sufficiently | ||
| 573 | 582 |
The short text describes the object sufficiently | ||
| 574 | 583 |
Demand split is not allowed; demand is part of a bundle | The short text describes the object sufficiently | |
| 575 | 586 |
Demand &1/&2 has a different work center | The short text describes the object sufficiently | |
| 576 | 587 |
Demand &1/&2 does not belong to the same bundling group as other demands | The short text describes the object sufficiently | |
| 577 | 588 |
Select all bundled demands | The short text describes the object sufficiently | |
| 578 | 589 |
Demand &1 could not be added to any bundle | The short text describes the object sufficiently | |
| 579 | 590 |
Demand &1 cannot be modified | The short text describes the object sufficiently | |
| 580 | 591 |
Demand &1 has assignments | The short text describes the object sufficiently | |
| 581 | 592 |
Demand &1 has time rules | The short text describes the object sufficiently | |
| 582 | 593 |
Demand &1 cannot be deleted from bundle | The short text describes the object sufficiently | |
| 583 | 594 |
Demand &1; order basic start date is blank | The short text describes the object sufficiently | |
| 584 | 595 |
Demand &1; order basic end date is blank | The short text describes the object sufficiently | |
| 585 | 597 |
Bundle & cannot be modified | The short text describes the object sufficiently | |
| 586 | 598 |
Logging profile &1 not found for log activity &2 | Space: object requires documentation | |
| 587 | 600 |
Cannot move assignments to the past | The short text describes the object sufficiently | |
| 588 | 601 |
Demand not updated with bundled status; abstract status mapping not found | Space: object requires documentation | |
| 589 | 602 |
Demand & is already included in the bundle proposal | The short text describes the object sufficiently | |
| 590 | 603 |
Demands cannot be added to bundle | The short text describes the object sufficiently | |
| 591 | 604 |
Bundle &2 and its demand &1 are not in sync; &3 was modified after saving | The short text describes the object sufficiently | |
| 592 | 605 |
Demand &1 belongs to bundle &2; &3 is changed/added | The short text describes the object sufficiently | |
| 593 | 606 |
Demands are not locked; manual locking inactive in planning board profile | Space: object requires documentation | |
| 594 | 608 |
Bundle &1 cannot be deleted | The short text describes the object sufficiently | |
| 595 | 610 |
Check the log for details | The short text describes the object sufficiently | |
| 596 | 611 |
Demand &1 was skipped; automatic scheduling is not allowed | Space: object requires documentation | |
| 597 | 619 |
Automatic Scheduling of Multiday Assignments was executed; check the log | Space: object requires documentation | |
| 598 | 621 |
All demands were filtered; no demands are left for automatic scheduling | Space: object requires documentation | |
| 599 | 622 |
All resources were filtered; no resources left for automatic scheduling | Space: object requires documentation | |
| 600 | 623 |
All assignments for the selected demands were deleted | The short text describes the object sufficiently | |
| 601 | 624 |
All assignments within the selected time frame were deleted | The short text describes the object sufficiently | |
| 602 | 625 |
Demand &1: all resources filtered out;no resources left for asg. creation | The short text describes the object sufficiently | |
| 603 | 627 |
Demand &1 was skipped; technical object is blocked | The short text describes the object sufficiently | |
| 604 | 628 |
No capacity information found for resource &1 | The short text describes the object sufficiently | |
| 605 | 629 |
Demand &1 &2: no or not enough slots found for assignment | The short text describes the object sufficiently | |
| 606 | 630 |
Demand &1: slots for assignments found for resource &2 | The short text describes the object sufficiently | |
| 607 | 631 |
Demand &1: an error occurred during assignment creation | The short text describes the object sufficiently | |
| 608 | 632 |
Optimizer was executed for remaining demands | The short text describes the object sufficiently | |
| 609 | 633 |
Demand & was skipped; default asg. type is not concrete or stretched | The short text describes the object sufficiently | |
| 610 | 634 |
Resource &1 was skipped for demand &1; capacity information is missing | Space: object requires documentation | |
| 611 | 635 |
Demand &1 is not locked manually; cannot unlock | Space: object requires documentation | |
| 612 | 636 |
Demand &1 is locked by system; cannot unlock manually | Space: object requires documentation | |
| 613 | 637 |
Demand &1 is locked by system; manual lock is no longer possible | Space: object requires documentation | |
| 614 | 638 |
Some of the demands were skipped; check the log for more details | Space: object requires documentation | |
| 615 | 639 |
Some of the resources were skipped; check the log for more details | Space: object requires documentation | |
| 616 | 640 |
All selected assignments must belong to the same resource | The short text describes the object sufficiently | |
| 617 | 641 |
Select all assignments for demand &1; asg. on &2 (res. &3) not selected | The short text describes the object sufficiently | |
| 618 | 642 |
There is no factory calendar assigned to &1 | The short text describes the object sufficiently | |
| 619 | 643 |
Error during calculation of assignment shift | The short text describes the object sufficiently | |
| 620 | 644 |
Shifting assignment outside the planning period is not possible | The short text describes the object sufficiently | |
| 621 | 645 |
Demand &1&2: assignments were created for resource &3 | The short text describes the object sufficiently | |
| 622 | 646 |
Error occurred during automatic assignment execution; check the log | Space: object requires documentation | |
| 623 | 647 |
Error during assignment creation | The short text describes the object sufficiently | |
| 624 | 648 |
Error during assignment deletion | The short text describes the object sufficiently | |
| 625 | 649 |
No valid time interval found for resource &1 | The short text describes the object sufficiently | |
| 626 | 650 |
Assignment status &1 not permitted | The short text describes the object sufficiently | |
| 627 | 651 |
Resource &1 is team manager for team &2 between &3 and &4 | The short text describes the object sufficiently | |
| 628 | 652 |
Resource &1 is already a member of team &2 from &3 to &4 | The short text describes the object sufficiently | |
| 629 | 653 |
Team &1 does not exist | The short text describes the object sufficiently | |
| 630 | 654 |
Technical object &1 of demand &2 is not available for the assignment | The short text describes the object sufficiently | |
| 631 | 655 |
Relationship type was changed from &1 to &2 | The short text describes the object sufficiently | |
| 632 | 656 |
You have not maintained an offset unit for the relationship | Space: object requires documentation | |
| 633 | 657 |
Cannot create a relationship to the same demand; select different demands | The short text describes the object sufficiently | |
| 634 | 658 |
Cannot create or modify relationship; contact your system administrator | Space: object requires documentation | |
| 635 | 659 |
You cannot create hierarchical and simultaneous relationships | The short text describes the object sufficiently | |
| 636 | 660 |
You cannot modify relationships for orders that are already completed | The short text describes the object sufficiently | |
| 637 | 661 |
All demands in a relationship must be of the same type | The short text describes the object sufficiently | |
| 638 | 662 |
You can only create relationships for PM/CS orders and PS networks | The short text describes the object sufficiently | |
| 639 | 663 |
Successor demand is already involved in another relationship | Space: object requires documentation | |
| 640 | 664 |
Cannot create relationship in order to avoid cyclic dependency | Space: object requires documentation | |
| 641 | 665 |
You cannot delete the only implicit relationship in the demand | Space: object requires documentation | |
| 642 | 666 |
You cannot delete the last remaining relationship within a complex demand | The short text describes the object sufficiently | |
| 643 | 667 |
Relationship offset was updated | The short text describes the object sufficiently | |
| 644 | 668 |
No changes were made to the existing relationship | The short text describes the object sufficiently | |
| 645 | 669 |
Relationship was deleted | The short text describes the object sufficiently | |
| 646 | 670 |
Relationships were deleted | The short text describes the object sufficiently | |
| 647 | 685 |
Assignment note is currently locked by user &1 | The short text describes the object sufficiently | |
| 648 | 686 |
Resource note is currently locked by user &1 | The short text describes the object sufficiently | |
| 649 | 700 |
Class &1 does not support interface /MRSS/IF_SGE_WL_ATT | Space: object requires documentation | |
| 650 | 701 |
Class &1 does not support interface /MRSS/IF_SGE_CHECK | Space: object requires documentation | |
| 651 | 720 |
&1 is not a unit of speed | The short text describes the object sufficiently | |
| 652 | 721 |
&1 is not a unit of time | The short text describes the object sufficiently | |
| 653 | 729 |
Default pre-booking status is not set for demand type &1 | The short text describes the object sufficiently | |
| 654 | 730 |
Automatic assignment creation is deactivated for demand &1 | The short text describes the object sufficiently | |
| 655 | 731 |
Automatic assignment creation failed for demand &1 | The short text describes the object sufficiently | |
| 656 | 732 |
Self-planning failed for demand &1 | The short text describes the object sufficiently | |
| 657 | 733 |
Resource &1 cannot be included for automatic planning of demand &2 | The short text describes the object sufficiently | |
| 658 | 734 |
Automatic assignment creation failed because demand is already planned | The short text describes the object sufficiently | |
| 659 | 735 |
Auto. assgmnt creation for demand &1 failed; partner is not available | The short text describes the object sufficiently | |
| 660 | 736 |
Auto. assgmnt creation for demand &1 failed; no suitable resource found | The short text describes the object sufficiently | |
| 661 | 737 |
Auto. assgmnt creation for demand &1 not executed due to Customizing | The short text describes the object sufficiently | |
| 662 | 738 |
No requirements profile is assigned to demand &1 | The short text describes the object sufficiently | |
| 663 | 739 |
No partners exist for the demand | The short text describes the object sufficiently | |
| 664 | 740 |
No qualified resources found | The short text describes the object sufficiently | |
| 665 | 741 |
No resources found for resource planning node | The short text describes the object sufficiently | |
| 666 | 742 |
Enter explicit resource planning nodes | The short text describes the object sufficiently | |
| 667 | 743 |
Enter an ID for the preselection | The short text describes the object sufficiently | |
| 668 | 744 |
Automatic scheduling failed; order/network not completely loaded | The short text describes the object sufficiently | |
| 669 | 745 |
Automatic resource creation for demand &1 failed; see long text | Space: object requires documentation | |
| 670 | 746 |
Automatic resource creation for demand &1 failed; see long text | Space: object requires documentation | |
| 671 | 747 |
Automatic resource creation for demand &1 failed; see long text | Space: object requires documentation | |
| 672 | 748 |
Automatic resource creation for demand &1 failed; see long text | Space: object requires documentation | |
| 673 | 749 |
Automatic resource creation for demand &1 failed; see long text | Space: object requires documentation | |
| 674 | 750 |
Demand &1 was not automatically planned | The short text describes the object sufficiently | |
| 675 | 752 |
Demands in the bundle do not have the same default assignment type | The short text describes the object sufficiently | |
| 676 | 753 |
Demands in the bundle do not have the same setting for daily travel | The short text describes the object sufficiently | |
| 677 | 754 |
Demands in the bundle do not have the same settings for daily processing | The short text describes the object sufficiently | |
| 678 | 760 |
No resource found within maximum distance of service area &1 | The short text describes the object sufficiently | |
| 679 | 761 |
During the requested interval, no resource works in the service area &1 | The short text describes the object sufficiently | |
| 680 | 762 |
No resource found for the service area &1 | The short text describes the object sufficiently | |
| 681 | 763 |
No resource has the required qualifications | The short text describes the object sufficiently | |
| 682 | 764 |
No resource found for interval group &1 between &2 | The short text describes the object sufficiently | |
| 683 | 765 |
Earliest appointment date for spare parts is later than requested date | Space: object requires documentation | |
| 684 | 766 |
Resource &1 is not available in MRS | The short text describes the object sufficiently | |
| 685 | 767 |
The given resource is not working in any service area | The short text describes the object sufficiently | |
| 686 | 768 |
No technical object exists for GUID &1 | The short text describes the object sufficiently | |
| 687 | 769 |
&1 is not a valid attribute | The short text describes the object sufficiently | |
| 688 | 770 |
&1 is not a valid function | The short text describes the object sufficiently | |
| 689 | 771 |
&1 is not a valid application | The short text describes the object sufficiently | |
| 690 | 772 |
No valid log data found to be displayed | The short text describes the object sufficiently | |
| 691 | 773 |
No valid log data found to be deleted | The short text describes the object sufficiently | |
| 692 | 774 |
You are not authorized to display or delete the logged data | The short text describes the object sufficiently | |
| 693 | 775 |
Data was deleted from the log table | The short text describes the object sufficiently | |
| 694 | 776 |
Demand &1 can have only one status as default pre-booking status | The short text describes the object sufficiently | |
| 695 | 778 |
Plannning node for work center &1, plant &2 was transferred | The short text describes the object sufficiently | |
| 696 | 779 |
Asynchronous queue was started for planning node capacity calculation | The short text describes the object sufficiently | |
| 697 | 780 |
Plannning node for org. unit &1 was transferred | The short text describes the object sufficiently | |
| 698 | 781 |
No org. unit details found for org. unit &1 | The short text describes the object sufficiently | |
| 699 | 782 |
No work center details found; no work center is linked to org. unit &1 | The short text describes the object sufficiently | |
| 700 | 783 |
No valid org. unit found for &1 in this system; see longtext | Space: object requires documentation | |
| 701 | 784 |
You are using a multi back-end landscape; enter the logical system | The short text describes the object sufficiently | |
| 702 | 800 |
No start information available for resource &1 and demand &2 | Space: object requires documentation | |
| 703 | 801 |
Change from time info. &1 to &2 is not permitted (resource &3, demand &4) | Space: object requires documentation | |
| 704 | 802 |
Time data exists for resource &1 and demand &2 after the time stamp &3 | Space: object requires documentation | |
| 705 | 803 |
Assignment type &1 is not permitted | Space: object requires documentation | |
| 706 | 804 |
Site supervisor indicator must be changed to assignments btw &1 and &2 | The short text describes the object sufficiently | |
| 707 | 805 |
Site Supervisor cannot be set, it is set in another Asgn.of the Operation | The short text describes the object sufficiently | |
| 708 | 806 |
Status &1 does not exist or is not permitted for resource category &2 &3 | The short text describes the object sufficiently | |
| 709 | 807 |
Choose a valid resource | The short text describes the object sufficiently | |
| 710 | 808 |
Function code &1 for type &2 does not exist | The short text describes the object sufficiently | |
| 711 | 809 |
No valid slot found for time data addition | The short text describes the object sufficiently | |
| 712 | 810 |
No valid time data found to be deleted | The short text describes the object sufficiently | |
| 713 | 811 |
Start time of preparation is later than end time of preparation (&1) | The short text describes the object sufficiently | |
| 714 | 812 |
Wrap-up phase cannot overlap with the assignment (&1) | The short text describes the object sufficiently | |
| 715 | 813 |
Start time of wrap-up is later than end time of wrap-up (&1) | The short text describes the object sufficiently | |
| 716 | 814 |
Arrival time cannot overlap with the preparation phase | The short text describes the object sufficiently | |
| 717 | 815 |
Status of language &1 retained | The short text describes the object sufficiently | |
| 718 | 816 |
Preparation phase cannot overlap with the assignment (&1) | The short text describes the object sufficiently | |
| 719 | 817 |
Preparation end is overlapping with assignment & | The short text describes the object sufficiently | |
| 720 | 818 |
Travel time is colliding with preparation for & | The short text describes the object sufficiently | |
| 721 | 819 |
Set default status indicator for demand type &1 | The short text describes the object sufficiently | |
| 722 | 821 |
Demand split is not allowed for RM demands | The short text describes the object sufficiently | |
| 723 | 822 |
Select an appointment interval group | The short text describes the object sufficiently | |
| 724 | 823 |
Select a search strategy | The short text describes the object sufficiently | |
| 725 | 826 |
Application was not initialized; contact your system administrator | The short text describes the object sufficiently | |
| 726 | 827 |
Could not find demands | The short text describes the object sufficiently | |
| 727 | 828 |
Bundles were not saved; contact your system administrator | The short text describes the object sufficiently | |
| 728 | 829 |
Bundles were saved | The short text describes the object sufficiently | |
| 729 | 830 |
Technical object &1 (&2 &3) is blocked due to &4 in assignment time frame | The short text describes the object sufficiently | |
| 730 | 831 |
Functional location &1 is blocked due to &2 in assignment time frame | The short text describes the object sufficiently | |
| 731 | 832 |
Technical object &1 (&2 &3) is blocked due to &4 in assignment time frame | The short text describes the object sufficiently | |
| 732 | 833 |
Technical object &1 (&2 &3) is blocked in assignment time frame (Date &4) | The short text describes the object sufficiently | |
| 733 | 834 |
No free demands found for bundling | The short text describes the object sufficiently | |
| 734 | 835 |
Technical object &1 is blocked in the assignment time frame &2 | The short text describes the object sufficiently | |
| 735 | 840 |
Transaction is intended for internal use only | The short text describes the object sufficiently | |
| 736 | 850 |
Cannot execute queue &1 due to a system error | Space: object requires documentation | |
| 737 | 860 |
Demand &1 excluded from bundling | The short text describes the object sufficiently | |
| 738 | 870 |
Assignments for demand &1 are independent of MRS time rule | The short text describes the object sufficiently | |
| 739 | 890 |
Update termination: STATUS | The short text describes the object sufficiently | |
| 740 | 891 |
Update termination: MAP | The short text describes the object sufficiently | |
| 741 | 893 |
Time allocation data has been changed | The short text describes the object sufficiently | |
| 742 | 894 |
Resource &1 is overloaded from &2 to &3 at Day level | The short text describes the object sufficiently | |
| 743 | 895 |
Could not find suitable time frame for assignment | The short text describes the object sufficiently | |
| 744 | 900 |
Assignment split is not possible for assignment &1 | Space: object requires documentation | |
| 745 | 901 |
Links are not allowed for external resources | The short text describes the object sufficiently | |
| 746 | 902 |
Teams allocations are not allowed for external resources | The short text describes the object sufficiently | |
| 747 | 903 |
No capacity slots found for the resource | The short text describes the object sufficiently | |
| 748 | 904 |
Resource is in frozen period; cannot plan between &1 and &2 | The short text describes the object sufficiently | |
| 749 | 906 |
No assignment or more than one assignment exist | The short text describes the object sufficiently | |
| 750 | 950 |
Capacitive assignment overlaps with absence between &1 and &2 | Space: object requires documentation | |
| 751 | 951 |
Cannot execute cap. assignment &1; resource is not sufficiently available | Space: object requires documentation | |
| 752 | 952 |
Assignment for demand &1 is scheduled to finish on &2 | Space: object requires documentation | |
| 753 | 953 |
Assignment for demand &1 is scheduled to start on &2 | Space: object requires documentation | |
| 754 | 954 |
Capacitive assignment for demand &1 exceeds planned end date | Space: object requires documentation | |
| 755 | 960 |
Assignments for demand &1 of &2 to &3 not created | Space: object requires documentation | |
| 756 | 961 |
Demand &1 for the same customer is assigned to resource &2 | Space: object requires documentation | |
| 757 | 962 |
Site supervisor indicator not set in any demand for order &1 | Space: object requires documentation | |
| 758 | 963 |
Site supervisor indicator set in several demands for order &1 | Space: object requires documentation | |
| 759 | 964 |
Demand &1 should start no later than &2 according to SLA | Space: object requires documentation | |
| 760 | 965 |
Resource is not valid | The short text describes the object sufficiently | |
| 761 | 966 |
For operation &1 (Order Operation Level), no supervisor is set | The short text describes the object sufficiently | |
| 762 | 967 |
For Order operation &1 (Order Operation Level), no supervisor is set | The short text describes the object sufficiently | |
| 763 | 968 |
For &, there are other Teams for the same period | The short text describes the object sufficiently | |
| 764 | 969 |
Note management is inactive for object & of type & | The short text describes the object sufficiently | |
| 765 | 970 |
No Valid members found for the team &, during the Period & to & | The short text describes the object sufficiently | |
| 766 | 971 |
Automatic assignment split could not be performed | Space: object requires documentation | |
| 767 | 999 |
Test message for related assignments | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141109 | SAP |
| SAP Release Created in | 401 |
