SAP ABAP Message Class KG1 (CO-PA planning)
Basic Data
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
KE (Package) Profitability Analysis
⤷
⤷
⤷
Attributes
| Message class | KG1 | |
| Short Description | CO-PA planning | |
| Changed On | 20020118 | |
| Last Changed At | 155426 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | <<<<<<<<<<<<<Application Core CO-PA Planning>>>>>>>>>>>>>>>>>>>>>>>>>>>>> | Space: object requires documentation | ||
| 2 | The planning layout cannot be saved, see longtext | Space: object requires documentation | ||
| 3 | Planning package cannot be edited with planning layout &1 | Space: object requires documentation | ||
| 4 | Planning layout &1 cannot be used here | Space: object requires documentation | ||
| 5 | Planning package cannot be edited with planning layout &1 | Space: object requires documentation | ||
| 6 | Characteristic &1 must be included in the planning level | Space: object requires documentation | ||
| 7 | The planning level must contain either 'period' or 'week' | Space: object requires documentation | ||
| 8 | Only individual values can be specified for characteristic &1 | Space: object requires documentation | ||
| 9 | A selection condition must be specified for characteristic &1 | Space: object requires documentation | ||
| 10 | The characteristic 'company code' must be included in the planning level | Space: object requires documentation | ||
| 11 | Only one individual value may be specified for characteristic &1 | Space: object requires documentation | ||
| 12 | Profitability Analysis type '&1' not permitted | Space: object requires documentation | ||
| 13 | Profitability Analysis type '&1' not permitted | Space: object requires documentation | ||
| 14 | Characteristic &1 is not permitted as a planning characteristic | Space: object requires documentation | ||
| 15 | Characteristic &1 must be included in the planning level | Space: object requires documentation | ||
| 16 | The planning level must contain either 'period' or 'week' | Space: object requires documentation | ||
| 17 | Characteristic &1 is not in the planning level | Space: object requires documentation | ||
| 18 | Selection criterion not permitted | Space: object requires documentation | ||
| 19 | Characteristic &2 must be included in the planning level | Space: object requires documentation | ||
| 20 | Planning layout cannot be generated | Space: object requires documentation | ||
| 21 | The transferred data does not match the selection criteria | Space: object requires documentation | ||
| 22 | You are not authorized to create planning layouts | Space: object requires documentation | ||
| 23 | Characteristic &1 is not permitted as a planning characteristic | Space: object requires documentation | ||
| 24 | Characteristic &1 must be included in the field list | Space: object requires documentation | ||
| 25 | Planning level &1 has been created | Space: object requires documentation | ||
| 26 | The selection made for "Period" or "Week" is not permitted | Space: object requires documentation | ||
| 27 | Variable "&1" not found for characteristic "&2" | Space: object requires documentation | ||
| 28 | Planning layouts were converted | Space: object requires documentation | ||
| 29 | <<<<<<<<<<<<<<<<<<<<<<<CO-PA Planning Interface>>>>>>>>>>>>>>>>>>>>>>>>>> | Space: object requires documentation | ||
| 30 | Planning level '&' does not exist | Space: object requires documentation | ||
| 31 | Planning level '&' already exists | Space: object requires documentation | ||
| 32 | Characteristic '&' is not permitted | Space: object requires documentation | ||
| 33 | Selection characteristic '&' must be included in the planning level | Space: object requires documentation | ||
| 34 | Characteristic value '&' invalid for characteristic '&' | Space: object requires documentation | ||
| 35 | Planning level '&' marked for deletion | Space: object requires documentation | ||
| 36 | Planning package '&' marked for deletion | Space: object requires documentation | ||
| 37 | Planning package '&' already exists | Space: object requires documentation | ||
| 38 | Planning package '&' does not exist | Space: object requires documentation | ||
| 39 | Inconsistency between planning level "&1" and planning package "&2" | Space: object requires documentation | ||
| 40 | You must first maintain the method parameters (see long text) | Space: object requires documentation | ||
| 41 | No planning package has been selected | Space: object requires documentation | ||
| 42 | Parameter set "&" has been marked for deletion | Space: object requires documentation | ||
| 43 | Parameter set "&" already exists | Space: object requires documentation | ||
| 44 | Parameter set "&" does not exist | Space: object requires documentation | ||
| 45 | Data saved | Space: object requires documentation | ||
| 46 | Error calling up a "control method" | Space: object requires documentation | ||
| 47 | Planning method '&' marked for deletion | Space: object requires documentation | ||
| 48 | Planning method '&' already exists | Space: object requires documentation | ||
| 49 | Planning method '&' does not exist | Space: object requires documentation | ||
| 50 | Characteristic '&' is a mandatory characteristic | Space: object requires documentation | ||
| 51 | Enter a planning layout | Space: object requires documentation | ||
| 52 | Enter a text describing the planning layout | Space: object requires documentation | ||
| 53 | Distribution key '&' is invalid | Space: object requires documentation | ||
| 54 | Distribution profile '&' is invalid | Space: object requires documentation | ||
| 55 | Access '&' is invalid | Space: object requires documentation | ||
| 56 | Entry currency '&' is invalid | Space: object requires documentation | ||
| 57 | Personalization profile '&' is invalid | Space: object requires documentation | ||
| 58 | Personalization profile '&' already exists | Space: object requires documentation | ||
| 59 | Layout "&" has been created | Space: object requires documentation | ||
| 60 | Layout & does not exist | Space: object requires documentation | ||
| 61 | You do not have an authorization for the requested function | Space: object requires documentation | ||
| 62 | Editing has been completed successfully | Space: object requires documentation | ||
| 63 | Personalization profile "&1" has been marked for deletion | Space: object requires documentation | ||
| 64 | Invalid access-level characteristic "&1" in ratio scheme "&2" | Space: object requires documentation | ||
| 65 | You do not have an authorization for distribution key "&1" | Space: object requires documentation | ||
| 66 | Distribution key "&1" is locked by "&2" | Space: object requires documentation | ||
| 67 | Distribution key "&1" already exists | Space: object requires documentation | ||
| 68 | Choose value field | Space: object requires documentation | ||
| 69 | Enter a distribution key | Space: object requires documentation | ||
| 70 | Enter an access key | Space: object requires documentation | ||
| 71 | Enter a revaluation key | Space: object requires documentation | ||
| 72 | Enter an event | Space: object requires documentation | ||
| 73 | Enter a forecast profile | Space: object requires documentation | ||
| 74 | Enter a ratio scheme | Space: object requires documentation | ||
| 75 | Enter a user exit | Space: object requires documentation | ||
| 76 | Choose at least one receiver characteristic | Space: object requires documentation | ||
| 77 | Choose at least one value field | Space: object requires documentation | ||
| 78 | Specify the period shift | Space: object requires documentation | ||
| 79 | Enter a "from value" for the period | Space: object requires documentation | ||
| 80 | Enter a "to value" for the period | Space: object requires documentation | ||
| 81 | The reference distribution key must be standard key 1, 2, or 7 | Space: object requires documentation | ||
| 82 | Enter a plan version | Space: object requires documentation | ||
| 83 | Characteristic "&" is no longer used | Space: object requires documentation | ||
| 84 | Enter operating concern and type of Profitability Analysis | Space: object requires documentation | ||
| 85 | Enter the operating concern, the type of CO-PA, and the planning level | Space: object requires documentation | ||
| 86 | Enter the operating concern, type of CO-PA, planning level and function | Space: object requires documentation | ||
| 87 | Enter the operating concern | Space: object requires documentation | ||
| 88 | Enter the transaction variant | Space: object requires documentation | ||
| 89 | The period units for the target data and reference data are incompatible | Space: object requires documentation | ||
| 90 | Planning level "&" does not exist! | Space: object requires documentation | ||
| 91 | Planning package "&" does not exist! | Space: object requires documentation | ||
| 92 | Enter an exit number without reference data | Space: object requires documentation | ||
| 93 | Enter an exit number with reference data | Space: object requires documentation | ||
| 94 | Receiver characteristics &2 (&1) must not be changed | Space: object requires documentation | ||
| 95 | In the package for the period, select a single value or an interval | Space: object requires documentation | ||
| 96 | The ref. data periods must correspond to the planning package periods | Space: object requires documentation | ||
| 97 | Settings in the parameter set for background processing are not suitable | Space: object requires documentation | ||
| 98 | Select a planning level | Space: object requires documentation | ||
| 99 | Select a planning package | Space: object requires documentation | ||
| 100 | Select a planning method | Space: object requires documentation | ||
| 101 | Select a parameter group | Space: object requires documentation | ||
| 102 | Assignment can only be made once | Space: object requires documentation | ||
| 103 | Enter all parameters | Space: object requires documentation | ||
| 104 | First character must be a letter | Space: object requires documentation | ||
| 105 | No errors were found | Space: object requires documentation | ||
| 106 | Reference data periods must precede the planning package periods | Space: object requires documentation | ||
| 107 | The "to-value" for the period has to be greater than the "from-value" | Space: object requires documentation | ||
| 108 | No detailed information exists for the log | Space: object requires documentation | ||
| 109 | No line items posted | Space: object requires documentation | ||
| 110 | You do not have the necessary authorization for this function | Space: object requires documentation | ||
| 111 | Planning method &1 does not exist | Space: object requires documentation | ||
| 112 | Parameter set &1 &2 does not exist | Space: object requires documentation | ||
| 113 | Enter planning method and parameter set | Space: object requires documentation | ||
| 114 | Select line | Space: object requires documentation | ||
| 115 | It is not possible to generate the variant with several versions | Space: object requires documentation | ||
| 116 | It is not possible to generate the variant with several record types | Space: object requires documentation | ||
| 117 | The variant can only be generated for the planning method "ACOP" | Space: object requires documentation | ||
| 118 | The parameter set is still used in planning sequence &1 | Space: object requires documentation | ||
| 119 | Enter a valuation strategy | Space: object requires documentation | ||
| 120 | Error in one or more processing steps | Space: object requires documentation | ||
| 121 | "Exclude" selection options are not supported in manual planning | Space: object requires documentation | ||
| 122 | Enter a valuation strategy | Space: object requires documentation | ||
| 123 | You do not have authorization to call up the general overview | Space: object requires documentation |
History
| Last changed on/by | 20020118 | SAP | |
| SAP Release Created in |