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
⤷
⤷
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 | Planning version &2 for network &1 does not exist | The short text describes the object sufficiently | ||
| 2 | Inconsistency of planning data; lines for non-existing items found | Space: object requires documentation | ||
| 3 | No identification (UUID) generated; contact your admin or SAP | Space: object requires documentation | ||
| 4 | System locking error | Space: object requires documentation | ||
| 5 | Planning horizon dates adapted to planning period | The short text describes the object sufficiently | ||
| 6 | Modified planning data was saved successfully | The short text describes the object sufficiently | ||
| 7 | Planning table for network &1 is blocked by user &2 | The short text describes the object sufficiently | ||
| 8 | Planning table for network &1 planning version &2 is blocked by user &3 | The short text describes the object sufficiently | ||
| 9 | Object links for network &1 not maintained within planning horizon | Space: object requires documentation | ||
| 10 | Network model for network &1 is not complete | The short text describes the object sufficiently | ||
| 11 | No allocation rule assigned to network object &1 | The short text describes the object sufficiently | ||
| 12 | Allocation rules not maintained completely | Space: object requires documentation | ||
| 13 | There is currently no message in the message log | The short text describes the object sufficiently | ||
| 14 | Simulation ID &2 for network &1 does not exist | The short text describes the object sufficiently | ||
| 15 | Network &1 has no planning relevant network objects | Space: object requires documentation | ||
| 16 | Multiple node allocation rule for node &1, medium &2 and qty category &3 | Space: object requires documentation | ||
| 17 | Validity date of network object link &1 not set correctly | The short text describes the object sufficiently | ||
| 18 | Network object &1 not marked as planning-relevant although start/end node | The short text describes the object sufficiently | ||
| 19 | Object &1 with required inputs for allocation must be planning-relevant | Space: object requires documentation | ||
| 20 | Allocation values of &1 were copied with factor &3 to planning values | The short text describes the object sufficiently | ||
| 21 | Planned values copied with factor &3 from &1 to &2 | The short text describes the object sufficiently | ||
| 22 | No planned values copied | The short text describes the object sufficiently | ||
| 23 | The from-date &1 of the target horizon is in the past | The short text describes the object sufficiently | ||
| 24 | The from-date &1 is in the past | The short text describes the object sufficiently | ||
| 25 | The source horizon &1 is smaller than the target horizon &2 | The short text describes the object sufficiently | ||
| 26 | The target horizon &2 is smaller than the source horizon &1 | The short text describes the object sufficiently | ||
| 27 | The from-date &1 is later as the to-date &2 | The short text describes the object sufficiently | ||
| 28 | Target horizon was limited to &1 | The short text describes the object sufficiently | ||
| 29 | Source horizon was limited to &1 | The short text describes the object sufficiently | ||
| 30 | The source horizon &1 contains days without planning values | The short text describes the object sufficiently | ||
| 31 | The source horizon start date &1 is outside of the planning horizon | The short text describes the object sufficiently | ||
| 32 | The source horizon start date was set to &1 | The short text describes the object sufficiently | ||
| 33 | The target horizon end date &1 is outside of the planning horizon | The short text describes the object sufficiently | ||
| 34 | The target horizon end date was set to &1 | The short text describes the object sufficiently | ||
| 35 | Items are not valid in the target horizon; not all values copied, see log | The short text describes the object sufficiently | ||
| 36 | Actual values copied as planned values from &1 to &2 | The short text describes the object sufficiently | ||
| 37 | The to-date &1 is outside of the planning horizon | The short text describes the object sufficiently | ||
| 38 | The to-date &1 is in the past | The short text describes the object sufficiently | ||
| 39 | Planned values of version &4 copied with factor &3 successfully | The short text describes the object sufficiently | ||
| 40 | Allocated values of version &4 copied with factor &3 to planned values | The short text describes the object sufficiently | ||
| 41 | Planning data of plannning version &1 read in successfully | The short text describes the object sufficiently | ||
| 42 | Comparison of current planning version to itself is not permitted | The short text describes the object sufficiently | ||
| 43 | Planned values of &1 deleted successfully | The short text describes the object sufficiently | ||
| 44 | The from-date &1 is outside of the planning horizon | The short text describes the object sufficiently | ||
| 45 | Item &1 not found for date &2 | The short text describes the object sufficiently | ||
| 46 | Values of complete structure will be copied to the target horizon | The short text describes the object sufficiently | ||
| 47 | Actual values can only be copied from the past | The short text describes the object sufficiently | ||
| 48 | Planning version to compare was discarded | The short text describes the object sufficiently | ||
| 49 | Operational planning values have been loaded into the planning table | The short text describes the object sufficiently | ||
| 50 | Planning version &1 for network &2 was created successfully | The short text describes the object sufficiently | ||
| 51 | Planning version &1 for network &2 was modified successfully | The short text describes the object sufficiently | ||
| 52 | Planning version &1 for network &2 was deleted successfully | The short text describes the object sufficiently | ||
| 53 | Planning version &1 for &2 cannot be deleted because of dependent objects | Space: object requires documentation | ||
| 54 | Existing planning quantities in planning version &1 for &2 were deleted | The short text describes the object sufficiently | ||
| 55 | Planning quantities for planning version &1 in &2 do not exist (any more) | Space: object requires documentation | ||
| 56 | Planning version &1 for network &2 already exists | The short text describes the object sufficiently | ||
| 57 | Planning version &1 for network &2 does not exist | The short text describes the object sufficiently | ||
| 58 | Criteria of Filter &1 could not be loaded; Recreate the filter | The short text describes the object sufficiently | ||
| 59 | Filter &1 does not exist; choose a different filter | The short text describes the object sufficiently | ||
| 60 | Filter &1 could not be deleted | The short text describes the object sufficiently | ||
| 61 | Filter &1 could not be saved | The short text describes the object sufficiently | ||
| 62 | Filter &1 can only be used with network &2 | The short text describes the object sufficiently | ||
| 63 | Filter &1 can only be used by user &2 | The short text describes the object sufficiently | ||
| 64 | Filter &1 has been loaded | The short text describes the object sufficiently | ||
| 65 | Filter &1 has been deleted | The short text describes the object sufficiently | ||
| 66 | Filter &1 has been saved | The short text describes the object sufficiently | ||
| 67 | Filter criteria do not correspond to values stored under filter ID &1 | The short text describes the object sufficiently | ||
| 68 | Filter usage does not correspond to usage of filter ID &1 | The short text describes the object sufficiently | ||
| 69 | Number of days to be considered too large; reduce to a reasonable number | Space: object requires documentation | ||
| 70 | Filter &1 can only be changed by user &2 | The short text describes the object sufficiently | ||
| 71 | No filter was entered | The short text describes the object sufficiently | ||
| 72 | Network object type &1 does not exist | The short text describes the object sufficiently | ||
| 73 | No network object will be selected (Filter criteria line &1) | The short text describes the object sufficiently | ||
| 74 | Medium &1 does not exist | The short text describes the object sufficiently | ||
| 75 | No allocation material will be selected (Filter criteria line &1) | The short text describes the object sufficiently | ||
| 76 | Network links build cycles between objects, Level assignment incomplete | The short text describes the object sufficiently | ||
| 77 | No authorization for user &1 in network &2 for &3 | The short text describes the object sufficiently | ||
| 78 | Production network &1 does not exist | The short text describes the object sufficiently | ||
| 79 | Planning allocation was executed sucessfully in interval &1 to &2 | The short text describes the object sufficiently | ||
| 80 | Planning allocation executed in interval &1 to &2 had error messages | Space: object requires documentation | ||
| 81 | Capacity allocation was executed sucessfully in interval &1 to &2 | The short text describes the object sufficiently | ||
| 82 | Capacity allocation executed in interval &1 to &2 had error messages | Space: object requires documentation | ||
| 83 | Planning allocation is started in interval &1 to &2 | The short text describes the object sufficiently | ||
| 84 | Capacity allocation is started in interval &1 to &2 | The short text describes the object sufficiently | ||
| 85 | Required input for node &1 and production date &2 is zero | The short text describes the object sufficiently | ||
| 86 | Allocated data of planning version &1 read in successfully | The short text describes the object sufficiently | ||
| 87 | Operational allocated values have been loaded into the planning table | The short text describes the object sufficiently | ||
| 88 | Previously saved operational allocated values loaded | The short text describes the object sufficiently | ||
| 89 | Previously saved allocated data of planning version &1 loaded | The short text describes the object sufficiently | ||
| 90 | Previously saved operational planning values loaded | The short text describes the object sufficiently | ||
| 91 | Previously saved planning data of plannning version &1 loaded | The short text describes the object sufficiently | ||
| 92 | Planned values of operational version copied with factor &3 | The short text describes the object sufficiently | ||
| 93 | Allocated values of operational version copied with factor &3 to planned | The short text describes the object sufficiently | ||
| 94 | The source horizon end date &1 is outside of the planning horizon | The short text describes the object sufficiently | ||
| 95 | Object &1 is only part of compare version &2; values not copied. | The short text describes the object sufficiently | ||
| 96 | Some selected objects are only part of compare version &1; see log. | The short text describes the object sufficiently | ||
| 97 | Item &1 with medium &2, material &3 and quantity category &4 is not valid | The short text describes the object sufficiently | ||
| 98 | No valid items selected within source horizon &1. Function not possible | The short text describes the object sufficiently | ||
| 99 | Application cannot be used: Business Function OIL_OPM_UPST is inactive | Space: object requires documentation | ||
| 100 | UoM rules not maintained completely | The short text describes the object sufficiently | ||
| 101 | No UoM for medium &1 on network object &2 | The short text describes the object sufficiently | ||
| 102 | No node allocation rules defined for network &1 within planning horizon | Space: object requires documentation | ||
| 103 | Planning horizon adapted to simulation interval | The short text describes the object sufficiently | ||
| 104 | No unit of measure defined for network object &1 and medium &2 | Space: object requires documentation | ||
| 105 | No unit of measure or UoM rule defined at all for network object &1 | Space: object requires documentation | ||
| 106 | The short text describes the object sufficiently | |||
| 107 | 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 |