SAP ABAP Message Class PPECHK (iPPE Consistency Check)
Basic Data
Hierarchy
☛
EA-IPPE (Software Component) SAP iPPE
⤷ AP-PPE (Application Component) Integrated Product and Process Engineering
⤷ CPPECHK (Package) Consistency Check of Production Version
⤷ AP-PPE (Application Component) Integrated Product and Process Engineering
⤷ CPPECHK (Package) Consistency Check of Production Version
Attributes
Message class | PPECHK | |
Short Description | iPPE Consistency Check | |
Changed On | 20110810 | |
Last Changed At | 073719 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | ************Consistency Check Messages**************************** | The short text describes the object sufficiently | |
2 | 001 | No valid &1 was found for this selection | Space: object requires documentation | |
3 | 002 | Save your changes before executing the consistency check | The short text describes the object sufficiently | |
4 | 003 | The log was already saved | The short text describes the object sufficiently | |
5 | 004 | Select a log | The short text describes the object sufficiently | |
6 | 005 | Log was saved | Space: object requires documentation | |
7 | 006 | When restricting the creation time, the start must come before the end | Space: object requires documentation | |
8 | 100 | ************Messages for Product Structure Checks******************** | The short text describes the object sufficiently | |
9 | 101 | Change statuses (&1) of &2 &3 have no standard configuration | The short text describes the object sufficiently | |
10 | 102 | &2 &3 has not standard configuration | The short text describes the object sufficiently | |
11 | 103 | Change status &1 of &2 &3 has no &4 | Space: object requires documentation | |
12 | 104 | &2 &3 has no &4 | Space: object requires documentation | |
13 | 105 | &1 cannot be used from &2 (status) in change status &3 of &4 | Space: object requires documentation | |
14 | 106 | &1 cannot be used from &2 (status) in &4 | Space: object requires documentation | |
15 | 107 | &1 &2 not found in &3 &4 | Space: object requires documentation | |
16 | 108 | &1 cannot be used in change status &3 of &4 (status) | Space: object requires documentation | |
17 | 109 | &1 cannot be used in &4 (status) | Space: object requires documentation | |
18 | 110 | Object dependency in change status &1 of &2 &3 is not released | The short text describes the object sufficiently | |
19 | 111 | The object dependency of &2 &3 is not released | The short text describes the object sufficiently | |
20 | 112 | Change status &1 of &2 &3 has no obj. dep. and no standard indicator | Space: object requires documentation | |
21 | 113 | &2 &3 has no object dependency and no standard indicator | Space: object requires documentation | |
22 | 114 | Change status &1 of &2 &3 has no &4 (phantom assembly) | Space: object requires documentation | |
23 | 115 | &2 &3 has no &4 (phantom assembly) | Space: object requires documentation | |
24 | 120 | Fixed quantity in change status &1 of &2 &3 not valid with &4 | The short text describes the object sufficiently | |
25 | 121 | Indicator - fixed quantity of &2 &3 with &4 not taken into account | Space: object requires documentation | |
26 | 125 | &1 &2 of &3 &4 cannot be used in Demand Planning | Space: object requires documentation | |
27 | 130 | &1 &2 has no components in the product structure | Space: object requires documentation | |
28 | 198 | Internal error: Extract data for &2 &1 | Space: object requires documentation | |
29 | 199 | Internal error: Check for &1 | The short text describes the object sufficiently | |
30 | 200 | ************Messages for Process Structure Checks********************* | The short text describes the object sufficiently | |
31 | 201 | &1 &2 has no components assigned | The short text describes the object sufficiently | |
32 | 202 | &1 &2 has already been assigned to the activities &3 and &4 | The short text describes the object sufficiently | |
33 | 203 | &1 &2 has not been assigned to an activity | The short text describes the object sufficiently | |
34 | 204 | Component variant &1 has already been assigned to activity &4 above &2 &3 | The short text describes the object sufficiently | |
35 | 205 | Activities below &1 &2 have no component assignment | Space: object requires documentation | |
36 | 210 | You can only assign single values at &1 &2 and characteristic &3 | The short text describes the object sufficiently | |
37 | 211 | Characteristic &1 of &2 &3 has not been assigned to resource &4 | Space: object requires documentation | |
38 | 212 | Characteristic value &1 of &2 &3 is not defined for resource &4 | The short text describes the object sufficiently | |
39 | 213 | Character. &1 at &2 &3: Max. of 15 characters and 3 decimal places only | Space: object requires documentation | |
40 | 214 | &1 &2 not classified although &3 &4 is activated for block planning | Space: object requires documentation | |
41 | 215 | No reporting point type defined on &1 &2 | Space: object requires documentation | |
42 | 300 | ************Messages for Line Structure Checks********************* | The short text describes the object sufficiently | |
43 | 301 | &1 is used multiple times in line structure &2 (&3, &4) | The short text describes the object sufficiently | |
44 | 302 | Relationships missing in the structure of &1 below the line | Space: object requires documentation | |
45 | 303 | Different MRP areas in group of alternative lines: &1 in &2 and &3 in &4 | Space: object requires documentation | |
46 | 304 | &1 &2 has not been assigned a supply area | The short text describes the object sufficiently | |
47 | 305 | Rep. pt. &1 at &2 &3 backfl. no comp./act. bef. split to parallel struct. | The short text describes the object sufficiently | |
48 | 306 | Reporting point missing at &1 &2 before splitting to parallel structures | Space: object requires documentation | |
49 | 307 | Reporting point &1(&2) and &3(&4) are at the same logical position | The short text describes the object sufficiently | |
50 | 308 | The end of alternative line &1 does not have a reporting point | The short text describes the object sufficiently | |
51 | 309 | The end of alternative work center &1 does not have a reporting point | The short text describes the object sufficiently | |
52 | 310 | There is no reporting point at the end of &1 &2 | The short text describes the object sufficiently | |
53 | 311 | Rep. point &1 at &2 at end of alt. line &3 backflushes no comp./prod.act. | The short text describes the object sufficiently | |
54 | 312 | Rep. pt. &1 at &2 at end of alt. work center &3 backfl. no comp./work ctr | The short text describes the object sufficiently | |
55 | 313 | Production rate of line resource &1 at &2 &3 is not maintained | The short text describes the object sufficiently | |
56 | 314 | Action point &1 at line network &2 cannot be assigned to a line resource | Space: object requires documentation | |
57 | 315 | The model &2 of &1 is not assigned to the APO resource &3 | Space: object requires documentation | |
58 | 316 | No line resources are assigned to line &1 | Space: object requires documentation | |
59 | 317 | No model is assigned to the production version | Space: object requires documentation | |
60 | 318 | The action points &1(&2) and &3(&4) have the same logical position | Space: object requires documentation | |
61 | 319 | Backflush supports no multi-level, multiple work centers (&1 &2) | Space: object requires documentation | |
62 | 320 | Relationships missing in the structure of &1 above the line | Space: object requires documentation | |
63 | 321 | Line area &1 contains no line objects | Space: object requires documentation | |
64 | 322 | No priority selected for alternative line &1 (&2 &3) | Space: object requires documentation | |
65 | 324 | &1 &2 has no alternative lines | Space: object requires documentation | |
66 | 325 | &2 is assigned at start of alternative line &1 | Space: object requires documentation | |
67 | 400 | ************Messages for Line Balance Checks************************* | The short text describes the object sufficiently | |
68 | 401 | &1 &2 has no valid line balance | The short text describes the object sufficiently | |
69 | 402 | Production version &1, line &2: No valid line balance from &3 to &4 | The short text describes the object sufficiently | |
70 | 403 | Valid line balances for &1 &2 are not included for the explosion | The short text describes the object sufficiently | |
71 | 404 | Activity &1 has not been assigned a line object between &2 and &3 | The short text describes the object sufficiently | |
72 | 405 | Mode &1 in &3 and mode &2 in &4 have different line activities | The short text describes the object sufficiently | |
73 | 406 | Activity &1 is not assigned to alternative line &2 between &3 and &4 | The short text describes the object sufficiently | |
74 | 407 | Multiple work center &3: Modes &1 and &2 not allowed (line balance &4) | The short text describes the object sufficiently | |
75 | 408 | Mode &1 is not assigned to alternative work center &2 (line balance &3) | The short text describes the object sufficiently | |
76 | 409 | Invalid multiple assignment: &1(&2) and &3(&4) | The short text describes the object sufficiently | |
77 | 410 | There is no line balance relationship for line balance &1 | The short text describes the object sufficiently | |
78 | 500 | ************Messages for Access Object Checks******************** | The short text describes the object sufficiently | |
79 | 501 | The access object has not yet been saved | The short text describes the object sufficiently | |
80 | 502 | Internal error in iPPE access object; see long text | Space: object requires documentation | |
81 | 510 | You must assign a process structure to &1 &2/&3/&4 | The short text describes the object sufficiently | |
82 | 511 | You must assign a line structure to &1 &2/&3/&4 | The short text describes the object sufficiently | |
83 | 512 | You cannot assign a line structure to &1 &2/&3/&4 | The short text describes the object sufficiently | |
84 | 513 | No line structure or process structure has been assigned to &1 &2/&3/&4 | The short text describes the object sufficiently | |
85 | 514 | No product cost collector exists for &1 &2/&3/&4 | Space: object requires documentation | |
86 | 515 | &1 is not a routing header. Assignment to a &2 is not possible | Space: object requires documentation | |
87 | 600 | ************General Messages for Application Log**************** | The short text describes the object sufficiently | |
88 | 601 | Checks for Product Structure: &1 | The short text describes the object sufficiently | |
89 | 602 | Checks for Process Structure: &1 | The short text describes the object sufficiently | |
90 | 603 | Checks for line structure: &1 | The short text describes the object sufficiently | |
91 | 604 | Checks for line balances | The short text describes the object sufficiently | |
92 | 605 | Initial Screen | The short text describes the object sufficiently | |
93 | 606 | Messages without assignment | Space: object requires documentation | |
94 | 607 | Checks for PDS Generation | Space: object requires documentation | |
95 | 610 | &1/&2/&3 &4 | Space: object requires documentation | |
96 | 611 | &1 | The short text describes the object sufficiently |
History
Last changed on/by | 20110810 | SAP | |
SAP Release Created in | 200 |