SAP ABAP Message Class MD (Material Requirements Planning (MRP))
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MD (Package) Application development R/3 requirements planning
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MD (Package) Application development R/3 requirements planning
Attributes
Message class | MD | |
Short Description | Material Requirements Planning (MRP) | |
Changed On | 20100310 | |
Last Changed At | 182645 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | ****COMMENT: Messages used generally | ||
2 | 001 | Function & is not supported | ||
3 | 002 | System locking error | Space: object requires documentation | |
4 | 003 | Choose a line | ||
5 | 004 | You do not have the necessary authorization for this function | ||
6 | 005 | Consistency check error in program &1 routine &1 | ||
7 | 006 | Background job & was scheduled | ||
8 | 007 | Plant ID is invalid | The short text describes the object sufficiently | |
9 | 008 | MRP controller not found | The short text describes the object sufficiently | |
10 | 011 | Individual project planning for &1 &2 locked | Space: object requires documentation | |
11 | 050 | Selection rule & does not exist | The short text describes the object sufficiently | |
12 | 051 | Display filter & does not exist | The short text describes the object sufficiently | |
13 | 052 | MRP list for material & & & has been created | The short text describes the object sufficiently | |
14 | 053 | Requirements/stock list for material & & & has been created | The short text describes the object sufficiently | |
15 | 054 | Stock/requirements list for material & & & could not be compiled | The short text describes the object sufficiently | |
16 | 055 | MRP list for material & & & could not be compiled | The short text describes the object sufficiently | |
17 | 091 | Only one setting is possible for this option | Space: object requires documentation | |
18 | 095 | Discontinued parts not possible. Discontinuation is controlled by SAP APO | Space: object requires documentation | |
19 | 100 | *****COMMENT: Messages for long-term planning | ||
20 | 101 | No data changed | ||
21 | 102 | Error saving planning scenario & | ||
22 | 103 | Error saving the independent requirements versions for the scenario | ||
23 | 104 | Planning scenario & was saved | ||
24 | 105 | Planning scenario & exists already | ||
25 | 106 | Planned ind. reqmts version & has already been assigned | ||
26 | 107 | Simulation version is same as the version to be replaced | ||
27 | 108 | Finish date lies before the start date | ||
28 | 109 | Planning scenario & does not exist | ||
29 | 110 | Planning scenario & was deleted | ||
30 | 111 | Error deleting planning scenario & | ||
31 | 112 | Version & must be allocated to the scenario first | ||
32 | 113 | Error reading planning scenario & | ||
33 | 114 | Planning scenario & has not been released | ||
34 | 115 | Planning scenario & is blocked by another user | ||
35 | 116 | Scenario & is not available for plant & | ||
36 | 117 | Error saving the plants for the scenario | ||
37 | 118 | Date & lies outside the planning period | ||
38 | 119 | Please adjust dates for the independent requirements versions | ||
39 | 120 | Plant & has already been allocated | ||
40 | 121 | You have not yet allocated any planned indep.reqmts versions | ||
41 | 122 | You have not yet allocated any plants | ||
42 | 123 | Planning scenario & was released and saved | ||
43 | 124 | Version & of the purchasing info system is already being used | ||
44 | 125 | Planning version & has already been allocated to the scenario | ||
45 | 126 | The planned indep.reqmts versions were activated | ||
46 | 127 | No appropriate planned indep.reqmts were found for the version | ||
47 | 128 | Start date not valid for fixed receipts | ||
48 | 129 | Background job could not be created | ||
49 | 130 | You do not have the necess.authorization for this function (see long txt) | ||
50 | 131 | Simulation planned orders cannot be changed manually | Space: object requires documentation | |
51 | 132 | Simulation planned orders cannot be converted | ||
52 | 133 | Simulation planned orders cannot be firmed | ||
53 | 134 | Multi-level replacements are not possible | ||
54 | 135 | Replacements in overlapping periods is not possible | ||
55 | 136 | Please enter a target version | ||
56 | 137 | Simulation version &1 cannot be copied to the same version number | ||
57 | 138 | Planning period in the past | ||
58 | 139 | Version & of stock controlling is used already | ||
59 | 140 | No data saved. Please evaluate scenario first | ||
60 | 141 | Please enter a scenario number not equal to '000' | ||
61 | 142 | Firmed recpts not taken into consideration in planning scenario & | ||
62 | 143 | Planned order &1 does not belong to planning scenario &2 | Space: object requires documentation | |
63 | 144 | No single-item planning exists in planning scenario &. | Space: object requires documentation | |
64 | 145 | Simulative orders should not be displayed or changed using & | Space: object requires documentation | |
65 | 146 | Scenario &1 is not assigned to sales order plant &2 | Space: object requires documentation | |
66 | 147 | Scenario &1 is not set for single-item planning. | Space: object requires documentation | |
67 | 148 | 'Use firm puchase requisitions' without including fixed receipts | Space: object requires documentation | |
68 | 149 | 'Use firm planned orders' without including fixed receipts | Space: object requires documentation | |
69 | 150 | *****COMMENT Messages for : long-term planning / PURCHIS | ||
70 | 151 | No data saved. Please evauluate the scenario for the PURCHI first | ||
71 | 152 | Please specify which planned price (1-3) is to be used | ||
72 | 153 | A new version &1 for info structure S012 will be created | ||
73 | 154 | Version &1 '&2' will be evaluated | ||
74 | 155 | No data for scenario &1 exists in PURCHIS | Space: object requires documentation | |
75 | 156 | Material &1 is a direct production material - function not permitted | Space: object requires documentation | |
76 | 157 | Do not enter planning scenario for copying - function not possible | Space: object requires documentation | |
77 | 158 | Please enter start date | Space: object requires documentation | |
78 | 159 | No data for scenario &1 exist in Inventory Controlling | Space: object requires documentation | |
79 | 160 | *** COMMENT: Calculation of simulative initial stock | ||
80 | 161 | Simulative initial stocks for scenario & were saved | ||
81 | 162 | Error at date entry | ||
82 | 163 | No authorization for plant & | ||
83 | 164 | Planning scenario & has not been assigned any plants | ||
84 | 165 | Simulative opening balance (stock) not allowed with MRP areas | Space: object requires documentation | |
85 | 170 | *** COMMENT: Delete planning scenario | Space: object requires documentation | |
86 | 171 | Firstly delete dependent data for scenario &1 | Space: object requires documentation | |
87 | 172 | No dependent data for scenario &1 has been found | Space: object requires documentation | |
88 | 173 | No dependent data has been selected for deletion | Space: object requires documentation | |
89 | 174 | Check dependent data: &1 | Space: object requires documentation | |
90 | 180 | *** COMMENT: Gross lot sizes | Space: object requires documentation | |
91 | 181 | Enter a gross lot size for the scenario | Space: object requires documentation | |
92 | 182 | Lot size procedure &1 being used is not gross lot size procedure | Space: object requires documentation | |
93 | 183 | Lot size procedure &1 is not defined | Space: object requires documentation | |
94 | 190 | Different periods not possible during activation | Space: object requires documentation | |
95 | 200 | *****COMMENT: Messages for CO integration (Maintain T442C) | ||
96 | 201 | Version &1 is not a planned version | ||
97 | 202 | No planned integration for version &1 in fiscal year &2 | ||
98 | 203 | No change possible as data already transferred | ||
99 | 210 | Error reading version &1 in controlling area &2 | ||
100 | 211 | Version &2 is not maintained for fiscal year &1 | ||
101 | 212 | Please enter a planning scenario | ||
102 | 250 | *****COMMENT: Messages for parallel MRP | ||
103 | 251 | Please check the destinations for parallel MRP | Space: object requires documentation | |
104 | 252 | Total planning run stopped due to &1 terminations (dumps) of &2 materials | Space: object requires documentation | |
105 | 253 | No instance exists for planned order &1 (Please see long text!) | Space: object requires documentation | |
106 | 260 | Error in server group. The system will switch to sequential reading | Space: object requires documentation | |
107 | 261 | Error with RFCs. The system will switch to sequential reading | Space: object requires documentation | |
108 | 300 | *****COMMENT: Capacity planning messages (SAPLM61D) | ||
109 | 301 | Choose a valid field | ||
110 | 302 | Please select a valid field for the display of the pegged capacity | ||
111 | 303 | Please place the cursor on a planned order number | ||
112 | 304 | No capacity load exists for the specified work center | ||
113 | 305 | No work centers with capacity requirements were found | ||
114 | 306 | Processing terminated by the user | ||
115 | 307 | No scheduling log exists | ||
116 | 309 | Program error: internal table & is inconsistent | ||
117 | 310 | No planning calendar exists for the material | ||
118 | 311 | Period & was not found | ||
119 | 312 | No periods exist with overload | ||
120 | 313 | Capacity for planned order has been scheduled | ||
121 | 314 | The scrap quantity was adjusted proportionally | ||
122 | 315 | Please enter start and finish date | ||
123 | 316 | Planned order belongs to another material | ||
124 | 317 | MRP area &1 is not defined in plant &2 | Space: object requires documentation | |
125 | 318 | MRP area &1 has not been defined | Space: object requires documentation | |
126 | 319 | Material &1 is not defined for MRP area &2 | Space: object requires documentation | |
127 | 320 | Enter plant or MRP area | Space: object requires documentation | |
128 | 321 | Plant MRP area and plant must have the same name | Space: object requires documentation | |
129 | 322 | Only plant MRP areas are allowed to have 1 to 4 digits | Space: object requires documentation | |
130 | 323 | MRP area &1 has been marked to be deleted for material &2 | Space: object requires documentation | |
131 | 324 | Material &1 is not defined in plant &2 | Space: object requires documentation | |
132 | 325 | Storage loc. &3 does not belong to the same MRP area as storage loc. &3 | Space: object requires documentation | |
133 | 326 | Storage location &1 does not belong to MRP area &2 | Space: object requires documentation | |
134 | 327 | Enter plant | Space: object requires documentation | |
135 | 328 | The storage location type of MRP area must be allocated a recvg stor. loc | Space: object requires documentation | |
136 | 329 | Capacity overload for capacity &1 and capacity category &2 in period &3 | Space: object requires documentation | |
137 | 335 | When planning with MRP areas, you should use scope of planning | Space: object requires documentation | |
138 | 350 | *****COMMENT: Customizing MRP area | Space: object requires documentation | |
139 | 351 | View &1 is not possible for MRP type &2 | Space: object requires documentation | |
140 | 352 | With MRP area type &1, you are not intended to enter a recvg stor. loc. | Space: object requires documentation | |
141 | 353 | Subcontractor MRP area &1 in plant &2 maintained incorrectly | Space: object requires documentation | |
142 | 354 | With MRP area type 02, you have to enter a receiving storage location | Space: object requires documentation | |
143 | 355 | Data record could not be stored in table &1 | ||
144 | 357 | Plant &1 has already been assigned a different MRP area | Space: object requires documentation | |
145 | 359 | Assignment MRP area &1, plant &2 is already available | ||
146 | 361 | Assignment MRP area &1, plant &2 and storage loc. &3 already available | ||
147 | 363 | Subcontractor &1 has already been allocated to MRP area &2 | Space: object requires documentation | |
148 | 364 | Storage location &2 in plant &1 already allocated to MRP area &3 | ||
149 | 365 | Not possible to delete MRP area &1 | Space: object requires documentation | |
150 | 366 | Not possible to delete storage location &3. Used by material &2 | Space: object requires documentation | |
151 | 367 | Not possible to delete MRP area &1, as it is assigned to material &2 | Space: object requires documentation | |
152 | 368 | Storage location &2 is receiving storage location of MRP area &1 | Space: object requires documentation | |
153 | 369 | Only plant MRP area is possible for this element | Space: object requires documentation | |
154 | 370 | Vendor &1 is being used by material &2, therefore cannot be changed | Space: object requires documentation | |
155 | 371 | Function cannot be executed - MRP areas are not activated | Space: object requires documentation | |
156 | 400 | ***** COMMENT: Exception messages in MRP | ||
157 | 401 | &1: &2 (A1) | ||
158 | 402 | &1: &2 (A9) | ||
159 | 403 | &1: &2 (N1) | ||
160 | 404 | &1: &2 (N2) | ||
161 | 405 | &1: &2 (N3) | ||
162 | 406 | &1: &2 (N4) | ||
163 | 407 | &1: &2 (S1) | ||
164 | 408 | &1: &2 (S2) | ||
165 | 409 | &1: &2 (S3) | ||
166 | 410 | &1: &2 (S6) | ||
167 | 411 | &1: &2 (S7) | ||
168 | 412 | &1: &2 (S8) | ||
169 | 413 | &1: &2 (T2) | ||
170 | 414 | &1: &2 (T3) | ||
171 | 415 | &1: &2 (T4) | ||
172 | 416 | &1: &2 (V1) | ||
173 | 417 | &1: &2 (V2) | ||
174 | 418 | &1: &2 &3 (V3) | ||
175 | 419 | &1: &2 &3 (U1) | ||
176 | 420 | &1: &2 &3 (U2) | ||
177 | 421 | &1: &2 &3 (U3) | ||
178 | 422 | &1: &2 &3 (U4) | ||
179 | 423 | &1: &2 (U5) | ||
180 | 424 | &1: &2 (P1) | ||
181 | 425 | &1: &2 (P2) | ||
182 | 426 | &1: &2 (P3) | ||
183 | 427 | &1: &2 (P4) | ||
184 | 428 | &1: &2 (S9) | ||
185 | 429 | &1: &2 (U6) | ||
186 | 430 | &1: &2 (C1) | ||
187 | 431 | &1: &2 (S4) | Space: object requires documentation | |
188 | 432 | &1: &2 (U9) | Space: object requires documentation | |
189 | 433 | &1: &2 (U8) | Space: object requires documentation | |
190 | 434 | &1: &2 (S5) | Space: object requires documentation | |
191 | 435 | &1: &2 (W1) | Space: object requires documentation | |
192 | 436 | &1: &2 (W2) | Space: object requires documentation | |
193 | 448 | Stock assigned to the follow-up material is too high | Space: object requires documentation | |
194 | 449 | Part to be discontinued; receipt transferred to follow-up material | Space: object requires documentation | |
195 | 450 | ***** COMMENT: New exception message for MD04/MD05 | Space: object requires documentation | |
196 | 451 | The list was created at &1 hours | Space: object requires documentation | |
197 | 452 | The start date of the interval must be before the end date | Space: object requires documentation | |
198 | 453 | Define traffic light for range of coverage: Press F1 for more information | Space: object requires documentation | |
199 | 454 | Define traffic light for exception groups. Press F1 for more information | Space: object requires documentation | |
200 | 455 | The user settings for traffic lights have been saved | Space: object requires documentation | |
201 | 456 | The user settings for traffic lights have been deleted | Space: object requires documentation | |
202 | 457 | Specify a start or finish date, or delete the time interval | Space: object requires documentation | |
203 | 458 | Split reset to days due to error setting up period totals | Space: object requires documentation | |
204 | 459 | The previous material is displayed again. Press ENTER. | Space: object requires documentation | |
205 | 460 | MRP views for &1 not maintained | Space: object requires documentation | |
206 | 461 | Start Date Set to Current Date | Space: object requires documentation | |
207 | 480 | Scheduling carried out successfully | ||
208 | 481 | Scheduling parameters are not maintained in Customizing | ||
209 | 482 | No capacity requirements determined, see customizing | ||
210 | 483 | Routing does not exist | ||
211 | 484 | No valid routing can be selected | ||
212 | 485 | Scheduling terminated, see log | ||
213 | 486 | Scheduling carried out, see log for error messages | ||
214 | 487 | Scheduling executed, see log for information messages | ||
215 | 488 | Exception group 8 is predefined for terminations | Space: object requires documentation | |
216 | 489 | Range of coverage (yellow) may not be less than range of coverage (red) | Space: object requires documentation | |
217 | 490 | &1: Ranges of coverage and exception groups within range of &2 | Space: object requires documentation | |
218 | 491 | &1 for material &2: &3 days' supply is less than limiting value of &4 | Space: object requires documentation | |
219 | 492 | &1 for material &2: Rcpt days' supply 1 &3 is less than limiting value &4 | Space: object requires documentation | |
220 | 493 | &1 for material &2: Rcpt day's supply 2 &3 is less than limiting value &4 | Space: object requires documentation | |
221 | 494 | &1 for material &2: There are exceptions to exception group &3 | Space: object requires documentation | |
222 | 495 | You can display a maximum of &1 curves at the same time | Space: object requires documentation | |
223 | 496 | The display period must be a minimum of 1 day | Space: object requires documentation | |
224 | 497 | The minimum Y value must be less than the maximum Y value | Space: object requires documentation | |
225 | 498 | Range of coverage (green) must not be lower than range of cov. (yellow) | The short text describes the object sufficiently | |
226 | 500 | ***** COMMENT: new exception messages in MRP for components | Space: object requires documentation | |
227 | 501 | &1: Not covered by master production schedule at component level (S8) | Space: object requires documentation | |
228 | 502 | &1: Start date of components in past (T3) | Space: object requires documentation | |
229 | 503 | &1: Finish date of components in past (T4) | Space: object requires documentation | |
230 | 504 | &1: Preference for operation at component level (U1) | Space: object requires documentation | |
231 | 505 | &1: Move operation to component level (U2) | Space: object requires documentation | |
232 | 510 | Overflow: More than 9999 items in BOM recursive for BOM &? | Space: object requires documentation | |
233 | 511 | Could not explode phantom assembly &1 | Space: object requires documentation | |
234 | 550 | ***** COMMENT: Messages for grouping | Space: object requires documentation | |
235 | 551 | WBS element has not been defined as a grouping WBS element | Space: object requires documentation | |
236 | 575 | ******Remarks ****Messages for SOA | The short text describes the object sufficiently | |
237 | 576 | Value PeriodTotalTimeMeasure is mandatory for value 2 of agg. code | The short text describes the object sufficiently | |
238 | 577 | Enter the MaterialSupplyAndDemandViewAggregationLevelCode | The short text describes the object sufficiently | |
239 | 578 | Enter the SupplyPlanningAreaID | The short text describes the object sufficiently | |
240 | 579 | Enter the MaterialInternalID | The short text describes the object sufficiently | |
241 | 580 | Enter the SupplyPlanningAreaTypeCode | The short text describes the object sufficiently | |
242 | 581 | MaterialSupplyAndDemandViewAggregationLevelCode &1 does not exist | The short text describes the object sufficiently | |
243 | 582 | Enter the MaterialSupplyAndDemandViewCategoryCode | The short text describes the object sufficiently | |
244 | 583 | MaterialSupplyAndDemandViewCategoryCode &1 does not exist | The short text describes the object sufficiently | |
245 | 584 | Enter a value in the period_totals_time_measure-unit_code field | The short text describes the object sufficiently | |
246 | 585 | SupplyPlanningAreaTypeCode &1 does not exist | The short text describes the object sufficiently | |
247 | 601 | Only total requirements with manual cost collectors are permitted | Space: object requires documentation | |
248 | 650 | ***** COMMENT: messages for BAPIs | Space: object requires documentation | |
249 | 651 | No imported data has been set with the flag for "change" | Space: object requires documentation | |
250 | 652 | Planned order number has not been entered | Space: object requires documentation | |
251 | 653 | Not possible to change component firming indicator with reqmts totaling | Space: object requires documentation | |
252 | 654 | Planned order & cannot be changed manually | Space: object requires documentation | |
253 | 655 | & planned orders have been selected | Space: object requires documentation | |
254 | 656 | Planning scenario & does not exist | Space: object requires documentation | |
255 | 657 | Planned order & exists | Space: object requires documentation | |
256 | 658 | Enter order type | Space: object requires documentation | |
257 | 659 | Enter a planning plant | Space: object requires documentation | |
258 | 660 | There is a conflict in the import parameters. | Space: object requires documentation | |
259 | 661 | No material components in original planned order & | Space: object requires documentation | |
260 | 662 | Imported component data is identical to available data | Space: object requires documentation | |
261 | 666 | No filter for the external view has been created | Space: object requires documentation | |
262 | 667 | Vendor & has been entered in the system. Correct | Space: object requires documentation | |
263 | 668 | Enter vendor | Space: object requires documentation | |
264 | 669 | This is a SAP standard variant. See long text! | Space: object requires documentation | |
265 | 675 | Implementation of the BAdI delivered inconsistent values | Space: object requires documentation | |
266 | 676 | BAdI & implemented multiple times | Space: object requires documentation | |
267 | 677 | BAdI & for the extraction has no active implementation | Space: object requires documentation | |
268 | 700 | *****COMMENT: Messages for missing table entries | ||
269 | 701 | No entry exists with key '&1' '&2' '&3' in Table T460P | ||
270 | 702 | Unit of measure & does not exist | ||
271 | 703 | Special procurement & has not been maintained for plant & | ||
272 | 704 | Lot size & not maintained | ||
273 | 705 | Warehouse cost record & not maintained for plant & | ||
274 | 706 | Release period key & has not been maintained for plant & | ||
275 | 720 | *****COMMENT: Message for maintenance of flexible transaction calls | Space: object requires documentation | |
276 | 721 | Please choose 'New entries' to maintain navigations of your choice | Space: object requires documentation | |
277 | 722 | The display of examples is only possible after choosing 'New entries' | Space: object requires documentation | |
278 | 723 | Enter a sequential number for this navigation | Space: object requires documentation | |
279 | 724 | Enter a transaction code | Space: object requires documentation | |
280 | 725 | Enter a text | Space: object requires documentation | |
281 | 726 | There are no examples for the MRP element &1 | Space: object requires documentation | |
282 | 727 | Please specify either a text or an icon with text | Space: object requires documentation | |
283 | 728 | A pushbutton has been added for the chosen example | Space: object requires documentation | |
284 | 729 | Invalid transaction code or indicator for external system not set | Space: object requires documentation | |
285 | 730 | Material &1 in plant &2 is not APO-relevant | The short text describes the object sufficiently | |
286 | 731 | No APO system connected | The short text describes the object sufficiently | |
287 | 732 | No active APO integration model for material &1 in plant &2 | The short text describes the object sufficiently | |
288 | 733 | No RFC destination for APO system &1 and CIF application case MD | Space: object requires documentation | |
289 | 734 | Not possible to access the transactions in logical system &1 | Space: object requires documentation | |
290 | 735 | Only materials with unit of measure convertible to &1 are displayed | The short text describes the object sufficiently | |
291 | 736 | Not possible to call up in external system without material context | The short text describes the object sufficiently | |
292 | 750 | *****COMMENT: Messages for production lot master data | Space: object requires documentation | |
293 | 751 | &1 for the production lot &2 is already being processed by &3 | Space: object requires documentation | |
294 | 752 | Enter a production lot number | Space: object requires documentation | |
295 | 753 | Project & for production lot already exists | Space: object requires documentation | |
296 | 754 | WBS element & for production lot already exists | Space: object requires documentation | |
297 | 755 | Enter profile or production lot as reference | Space: object requires documentation | |
298 | 756 | Project &1 for &2 does not exist | Space: object requires documentation | |
299 | 757 | WBS element &1 for &2 does not exist | Space: object requires documentation | |
300 | 758 | No data was changed | Space: object requires documentation | |
301 | 759 | Production lot & created | Space: object requires documentation | |
302 | 760 | Production lot & was changed | Space: object requires documentation | |
303 | 761 | Enter production lot or indicator for reference | Space: object requires documentation | |
304 | 762 | Production lot and reference production lot must be different | Space: object requires documentation | |
305 | 763 | Profile &1 of reference production lot &2 is used instead of profile &3 | Space: object requires documentation | |
306 | 764 | Production lot and reference production lot must have the same material | Space: object requires documentation | |
307 | 765 | WBS BOM for production lot & already exists | Space: object requires documentation | |
308 | 766 | WBS BOM for reference production lot & already exists | Space: object requires documentation | |
309 | 767 | Profile & is for non-valuated project stock | Space: object requires documentation | |
310 | 800 | *** Comment **** Check Material Master for APO | Space: object requires documentation | |
311 | 801 | Check MRP type | Space: object requires documentation | |
312 | 802 | Use a suitable lot-sizing procedure | Space: object requires documentation | |
313 | 850 | *****COMMENT: messages for XPRA's | ||
314 | 851 | & entries were adjested in the planned order | ||
315 | 852 | KBKO records were set up for & planned order records | ||
316 | 853 | Run-time: & ms | ||
317 | 854 | &1 &2 &3 &4 | Space: object requires documentation | |
318 | 855 | Error determining duration of working time | The short text describes the object sufficiently | |
319 | 856 | No available capacities maintained at &1 | The short text describes the object sufficiently | |
320 | 900 | ******Remarks ****Messages for SOA | The short text describes the object sufficiently | |
321 | 901 | AggregationLevelCode &1 does not exist | The short text describes the object sufficiently | |
322 | 902 | Enter the MaterialSupplyAndDemandViewAggregationLevelCode | The short text describes the object sufficiently | |
323 | 903 | Enter the SupplyPlanningAreaID | The short text describes the object sufficiently | |
324 | 904 | Enter the MaterialInternalID | The short text describes the object sufficiently | |
325 | 905 | Enter the SupplyPlanningAreaTypeCode | The short text describes the object sufficiently | |
326 | 906 | SupplyPlanningAreaTypeCode &1 does not exist | The short text describes the object sufficiently | |
327 | 907 | Enter the MaterialSupplyAndDemandViewCategoryCode | The short text describes the object sufficiently | |
328 | 908 | MaterialSupplyAndDemandViewCategoryCode &1 does not exist | The short text describes the object sufficiently | |
329 | 909 | Enter value in period total time measure - Unit Code field | The short text describes the object sufficiently |
History
Last changed on/by | 20100310 | SAP | |
SAP Release Created in |