SAP ABAP Message Class GHO_PP_PT (GHO_PP_PT)
Basic Data
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ PP-PN-NOP (Application Component) Network Operations
⤷ APPL_GHO_PP_PT_GEN (Package) GHO PP: Planning Table Backend General
⤷ PP-PN-NOP (Application Component) Network Operations
⤷ APPL_GHO_PP_PT_GEN (Package) GHO PP: Planning Table Backend General
Attributes
Message class | GHO_PP_PT | |
Short Description | ||
Changed On | 20130531 | |
Last Changed At | 100614 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Planning version &2 for network &1 does not exist | The short text describes the object sufficiently | |
2 | 002 | Inconsistency of planning data; lines for non-existing items found | Space: object requires documentation | |
3 | 003 | No identification (UUID) generated; contact your admin or SAP | Space: object requires documentation | |
4 | 004 | System locking error | Space: object requires documentation | |
5 | 005 | Planning horizon dates adapted to planning period | The short text describes the object sufficiently | |
6 | 006 | Modified planning data was saved successfully | The short text describes the object sufficiently | |
7 | 007 | Planning table for network &1 is blocked by user &2 | The short text describes the object sufficiently | |
8 | 008 | Planning table for network &1 planning version &2 is blocked by user &3 | The short text describes the object sufficiently | |
9 | 009 | Object links for network &1 not maintained within planning horizon | Space: object requires documentation | |
10 | 010 | Network model for network &1 is not complete | The short text describes the object sufficiently | |
11 | 011 | No allocation rule assigned to network object &1 | The short text describes the object sufficiently | |
12 | 012 | Allocation rules not maintained completely | Space: object requires documentation | |
13 | 013 | There is currently no message in the message log | The short text describes the object sufficiently | |
14 | 014 | Simulation ID &2 for network &1 does not exist | The short text describes the object sufficiently | |
15 | 015 | Network &1 has no planning relevant network objects | Space: object requires documentation | |
16 | 016 | Multiple node allocation rule for node &1, medium &2 and qty category &3 | Space: object requires documentation | |
17 | 017 | Validity date of network object link &1 not set correctly | The short text describes the object sufficiently | |
18 | 018 | Network object &1 not marked as planning-relevant although start/end node | The short text describes the object sufficiently | |
19 | 019 | Object &1 with required inputs for allocation must be planning-relevant | Space: object requires documentation | |
20 | 020 | Allocation values of &1 were copied with factor &3 to planning values | The short text describes the object sufficiently | |
21 | 021 | Planned values copied with factor &3 from &1 to &2 | The short text describes the object sufficiently | |
22 | 022 | No planned values copied | The short text describes the object sufficiently | |
23 | 023 | The from-date &1 of the target horizon is in the past | The short text describes the object sufficiently | |
24 | 024 | The from-date &1 is in the past | The short text describes the object sufficiently | |
25 | 025 | The source horizon &1 is smaller than the target horizon &2 | The short text describes the object sufficiently | |
26 | 026 | The target horizon &2 is smaller than the source horizon &1 | The short text describes the object sufficiently | |
27 | 027 | The from-date &1 is later as the to-date &2 | The short text describes the object sufficiently | |
28 | 028 | Target horizon was limited to &1 | The short text describes the object sufficiently | |
29 | 029 | Source horizon was limited to &1 | The short text describes the object sufficiently | |
30 | 030 | The source horizon &1 contains days without planning values | The short text describes the object sufficiently | |
31 | 031 | The source horizon start date &1 is outside of the planning horizon | The short text describes the object sufficiently | |
32 | 032 | The source horizon start date was set to &1 | The short text describes the object sufficiently | |
33 | 033 | The target horizon end date &1 is outside of the planning horizon | The short text describes the object sufficiently | |
34 | 034 | The target horizon end date was set to &1 | The short text describes the object sufficiently | |
35 | 035 | Items are not valid in the target horizon; not all values copied, see log | The short text describes the object sufficiently | |
36 | 036 | Actual values copied as planned values from &1 to &2 | The short text describes the object sufficiently | |
37 | 037 | The to-date &1 is outside of the planning horizon | The short text describes the object sufficiently | |
38 | 038 | The to-date &1 is in the past | The short text describes the object sufficiently | |
39 | 039 | Planned values of version &4 copied with factor &3 successfully | The short text describes the object sufficiently | |
40 | 040 | Allocated values of version &4 copied with factor &3 to planned values | The short text describes the object sufficiently | |
41 | 041 | Planning data of plannning version &1 read in successfully | The short text describes the object sufficiently | |
42 | 042 | Comparison of current planning version to itself is not permitted | The short text describes the object sufficiently | |
43 | 043 | Planned values of &1 deleted successfully | The short text describes the object sufficiently | |
44 | 044 | The from-date &1 is outside of the planning horizon | The short text describes the object sufficiently | |
45 | 045 | Item &1 not found for date &2 | The short text describes the object sufficiently | |
46 | 046 | Values of complete structure will be copied to the target horizon | The short text describes the object sufficiently | |
47 | 047 | Actual values can only be copied from the past | The short text describes the object sufficiently | |
48 | 048 | Planning version to compare was discarded | The short text describes the object sufficiently | |
49 | 049 | Operational planning values have been loaded into the planning table | The short text describes the object sufficiently | |
50 | 050 | Planning version &1 for network &2 was created successfully | The short text describes the object sufficiently | |
51 | 051 | Planning version &1 for network &2 was modified successfully | The short text describes the object sufficiently | |
52 | 052 | Planning version &1 for network &2 was deleted successfully | The short text describes the object sufficiently | |
53 | 053 | Planning version &1 for &2 cannot be deleted because of dependent objects | Space: object requires documentation | |
54 | 054 | Existing planning quantities in planning version &1 for &2 were deleted | The short text describes the object sufficiently | |
55 | 055 | Planning quantities for planning version &1 in &2 do not exist (any more) | Space: object requires documentation | |
56 | 056 | Planning version &1 for network &2 already exists | The short text describes the object sufficiently | |
57 | 057 | Planning version &1 for network &2 does not exist | The short text describes the object sufficiently | |
58 | 059 | Criteria of Filter &1 could not be loaded; Recreate the filter | The short text describes the object sufficiently | |
59 | 060 | Filter &1 does not exist; choose a different filter | The short text describes the object sufficiently | |
60 | 061 | Filter &1 could not be deleted | The short text describes the object sufficiently | |
61 | 062 | Filter &1 could not be saved | The short text describes the object sufficiently | |
62 | 063 | Filter &1 can only be used with network &2 | The short text describes the object sufficiently | |
63 | 064 | Filter &1 can only be used by user &2 | The short text describes the object sufficiently | |
64 | 065 | Filter &1 has been loaded | The short text describes the object sufficiently | |
65 | 066 | Filter &1 has been deleted | The short text describes the object sufficiently | |
66 | 067 | Filter &1 has been saved | The short text describes the object sufficiently | |
67 | 068 | Filter criteria do not correspond to values stored under filter ID &1 | The short text describes the object sufficiently | |
68 | 069 | Filter usage does not correspond to usage of filter ID &1 | The short text describes the object sufficiently | |
69 | 070 | Number of days to be considered too large; reduce to a reasonable number | Space: object requires documentation | |
70 | 071 | Filter &1 can only be changed by user &2 | The short text describes the object sufficiently | |
71 | 072 | No filter was entered | The short text describes the object sufficiently | |
72 | 073 | Network object type &1 does not exist | The short text describes the object sufficiently | |
73 | 074 | No network object will be selected (Filter criteria line &1) | The short text describes the object sufficiently | |
74 | 075 | Medium &1 does not exist | The short text describes the object sufficiently | |
75 | 076 | No allocation material will be selected (Filter criteria line &1) | The short text describes the object sufficiently | |
76 | 077 | Network links build cycles between objects, Level assignment incomplete | The short text describes the object sufficiently | |
77 | 080 | No authorization for user &1 in network &2 for &3 | The short text describes the object sufficiently | |
78 | 081 | Production network &1 does not exist | The short text describes the object sufficiently | |
79 | 090 | Planning allocation was executed sucessfully in interval &1 to &2 | The short text describes the object sufficiently | |
80 | 091 | Planning allocation executed in interval &1 to &2 had error messages | Space: object requires documentation | |
81 | 092 | Capacity allocation was executed sucessfully in interval &1 to &2 | The short text describes the object sufficiently | |
82 | 093 | Capacity allocation executed in interval &1 to &2 had error messages | Space: object requires documentation | |
83 | 094 | Planning allocation is started in interval &1 to &2 | The short text describes the object sufficiently | |
84 | 095 | Capacity allocation is started in interval &1 to &2 | The short text describes the object sufficiently | |
85 | 096 | Required input for node &1 and production date &2 is zero | The short text describes the object sufficiently | |
86 | 101 | Allocated data of planning version &1 read in successfully | The short text describes the object sufficiently | |
87 | 102 | Operational allocated values have been loaded into the planning table | The short text describes the object sufficiently | |
88 | 103 | Previously saved operational allocated values loaded | The short text describes the object sufficiently | |
89 | 104 | Previously saved allocated data of planning version &1 loaded | The short text describes the object sufficiently | |
90 | 105 | Previously saved operational planning values loaded | The short text describes the object sufficiently | |
91 | 106 | Previously saved planning data of plannning version &1 loaded | The short text describes the object sufficiently | |
92 | 107 | Planned values of operational version copied with factor &3 | The short text describes the object sufficiently | |
93 | 108 | Allocated values of operational version copied with factor &3 to planned | The short text describes the object sufficiently | |
94 | 109 | The source horizon end date &1 is outside of the planning horizon | The short text describes the object sufficiently | |
95 | 110 | Object &1 is only part of compare version &2; values not copied. | The short text describes the object sufficiently | |
96 | 111 | Some selected objects are only part of compare version &1; see log. | The short text describes the object sufficiently | |
97 | 112 | Item &1 with medium &2, material &3 and quantity category &4 is not valid | The short text describes the object sufficiently | |
98 | 113 | No valid items selected within source horizon &1. Function not possible | The short text describes the object sufficiently | |
99 | 120 | Application cannot be used: Business Function OIL_OPM_UPST is inactive | Space: object requires documentation | |
100 | 150 | UoM rules not maintained completely | The short text describes the object sufficiently | |
101 | 151 | No UoM for medium &1 on network object &2 | The short text describes the object sufficiently | |
102 | 152 | No node allocation rules defined for network &1 within planning horizon | Space: object requires documentation | |
103 | 153 | Planning horizon adapted to simulation interval | The short text describes the object sufficiently | |
104 | 154 | No unit of measure defined for network object &1 and medium &2 | Space: object requires documentation | |
105 | 155 | No unit of measure or UoM rule defined at all for network object &1 | Space: object requires documentation | |
106 | 156 | The short text describes the object sufficiently | ||
107 | 160 | Enddate &1 not allowed. Maximum allowed cleanup until date &2. | Space: object requires documentation |
History
Last changed on/by | 20130531 | SAP | |
SAP Release Created in | 606 |