FCOM_PLANNING_CORE - Messages for Package FCOM_PLANNING_CORE
The following messages are stored in message class FCOM_PLANNING_CORE: Messages for Package FCOM_PLANNING_CORE.
It is part of development package FCOM_PLANNING_CORE in software component CO-OM-CCA-B. This development package consists of objects that can be grouped under "Planning".
It is part of development package FCOM_PLANNING_CORE in software component CO-OM-CCA-B. This development package consists of objects that can be grouped under "Planning".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Internal error &1 &2 &3 &4; contact your system administrator |
| 001 | Virtual InfoProvider &1 is not supported by this class |
| 002 | Internal error; contact your system administrator |
| 003 | Cannot read virtual hierarchies for &1; class is invalid |
| 004 | Settings for hierarchy parameter are invalid for &1 |
| 005 | Currency &4 is not the controlling area currency &3 |
| 006 | Currency &4 is not the object currency &3 |
| 007 | Currency type &3 is invalid for WBS element &1; enter currency type &4 |
| 008 | InfoObject &1 does not exist |
| 009 | DataSource &2 for InfoObject &1 is inactive or does not exist |
| 010 | User &1 has insufficient authorization |
| 011 | Error when saving plan data |
| 012 | You are not authorized to perform activity &1 for WBS element &2 |
| 013 | You are not authorized to perform activity &1 for project &2 |
| 014 | Projects have different currency types |
| 015 | Data reset |
| 016 | Currency type &1 is invalid |
| 017 | Cost element &1 cannot be used for cost element planning |
| 018 | Controlling area &1 has fiscal year variant &2 whereas &3 is entered |
| 019 | Planning profile &1 does not allow planning of overall values |
| 020 | Planning profile &1 does not allow planning of annual values |
| 021 | Fiscal year is not in the time frame |
| 022 | Invalid currency key; enter company currency &2 instead of &1 |
| 023 | Invalid currency key; enter controlling area currency &2 instead of &1 |
| 024 | Invalid currency key; enter &2 instead of &1 |
| 025 | Value &2 for parameter &1 and ABAP data type &3 not supported |
| 026 | Pattern &2 for parameter &1 and ABAP data type &3 not supported |
| 027 | Missing authorizations for planning on WBS element &1 |
| 028 | Missing authorizations for planning on project &1 |
| 029 | Cannot plan for WBS element &1; version &2 blocked for fiscal year &3 |
| 030 | Enter a valid cost element category for primary costs |
| 031 | Enter a valid cost element category for revenues or sales deductions |
| 032 | Enter a valid cost element category for internal settlements |
| 033 | Invalid unit of measure; enter activity unit &2 instead of &1 |
| 034 | Cost center &1 does not exist in fiscal year &2 |
| 035 | Cost element &1 does not exist in fiscal year &2 |
| 036 | Activity type &1 does not exist in fiscal year &2 |
| 037 | Error when reading hierarchy &1: &2 |
| 038 | You are not authorized for cost center planning in controlling area &1 |
| 039 | You are not authorized to plan on cost center &1/&2 |
| 040 | You cannot enter activity quantities; activity type &2 is invalid |
| 041 | Invalid activity type unit; enter &2 instead of &1 |
| 042 | No common validity period for cost center &2 and activity type &3 |
| 043 | Some records to be planned have already been planned with quantities |
| 044 | Cost center &1 activity type &2 does not exist in fiscal year &3 |
| 045 | Please specify the default controlling area in your user profile. |
| 046 | No restriction for fiscal year given at locking |
| 047 | Error during unit conversion &1 &2 &3 &4; contact system administrator |
| 048 | Enter a WBS element for project &1 |
| 049 | Enter a WBS element |
| 050 | Planning profile is not entered for project &1 |
| 051 | Select a line and choose the Details pushbutton |
| 052 | Cannot plan for order &1; version &2 blocked for fiscal year &3 |
| 053 | Order &1 not found |
| 054 | You are not authorized to plan for order &1 |
| 055 | Invalid currency key; enter sender currency &2 instead of &1 |
| 056 | InfoObject &1 was not activated |
| 057 | InfoObject &1 was not saved |
| 058 | All saved InfoObjects activated |
| 059 | Operating concern &1 is not of PA type 2 or 3 |
| 060 | Access type &1 not supported |
| 061 | Specify a controlling area in the select options |
| 062 | Operating concern could not be derived from the costing area &1 |
| 063 | Field &1 is already assigned to InfoObject &2. See Long Text |
| 064 | Assignment for field &1 changed from InfoObject &2 to &3 |
| 065 | & & & & |
| 066 | With this option generated InfoObjects (/RKE/*) could not be assigned |
| 067 | Data type or length of InfoObject &1 doesn't match field &2. |
| 068 | InfoObject &1 was not transported |
| 069 | The infoobject &1 could not be mapped to a field |
| 070 | Missing entry in tab. COSP_VTYPE for keys VRGNG_OLTP &1 and WRTTP_OLTP &2 |
| 071 | Cost element &1 cannot be used for cost element planning |
| 072 | An SQL exception occurred, DB schema cannot be determined |
| 073 | Master data DB views cannot be generated |
| 074 | More than one compound dependency for field &1 |
| 075 | Error when generating plan data view &1. Check info cube &2 |
| 076 | Error when generating view &1. Check info cube &2 |
| 077 | You may either specify cost element selections or account selections |
| 078 | Sorry, but we can't generate HDI view &1. Please contact SAP. |
| 079 | Cost element &1 cannot be used for cost element planning |
| 080 | The select options for cost center must not include '#' |
| 081 | Invalid debit/credit-indicator &1 for account &2, enter value &3 instead |
| 082 | Financials integration IBP to ERP: Activity allocation w/o sender |
| 083 | Financials integration IBP to ERP: Cannot transfer activity type &1 |
| 084 | Financials integration IBP to ERP: Overhead cost element |
| 085 | Financials integration IBP to ERP: Primary planning with sender |
| 086 | Financials integration IBP to ERP: Primary order costs with sender |
| 087 | Financials integration IBP to ERP: Secondary order costs w/o sender cc |
| 100 | Set of &1 linear equations solved by using Gaussian elimination in &2 |
| 101 | Set of &1 linear equations solved by using Gauss-Seidel method in &2 |
| 102 | Set of &1 linear equations solved by using matrix inversion method in &2 |
| 103 | Divison by zero (matrix element A(i,i), i=&1). Please contact SAP. |
| 104 | Iteration method not converged after &1 steps. Please contact SAP. |
| 105 | Internal error AMDP call &1. Please contact SAP. |
| 106 | Matrix cannot be inverted. Please contact SAP. |
| 107 | Matrix is empty or not square. Please contact SAP. |
| 108 | InfoObject &1 is inactive. Please activate it. |
| 109 | Planning function &1 can't find sender and receiver cost objects. |
| 110 | Planning function &4 can't determine parameter &1. Please correct. |
| 111 | Planning function &V2& requires InfoObject /ERP/DCINDCO. Please correct. |
| 112 | Planning function &2 needs InfoObject &1 as changeable field. |
| 113 | Planning function &4 can't determine parameter &1. Please correct. |
| 114 | &2 &1 (InfoObject &3) has zero output. Please correct. |
| 115 | Sorry, but we couldn't solve the set of &1 linear equations. Contact SAP. |
| 116 | Allocation factors of cost object &1 have different units of measure. |
| 117 | Start solving set of &1 linear eqns by using Gaussian elimination (ABAP) |
| 118 | Start solving set of &1 linear eqns by using Gauss-Seidel method (ABAP) |
| 119 | Start solving set of &1 linear equations by using Gauss-Seidel method (L) |
| 120 | Start solving set of &1 linear equations by using matrix inversion (L) |
| 121 | Error in planning function parameter definition |
| 122 | Error in planning function definition |
| 123 | Allocation factors of cost object &1 have different algebraic signs. |
| 124 | Cost allocation ends in a loop. Please correct. |
| 125 | Characteristic &1 is too long |
| 126 | Key figure &1 is too long |
| 127 | Redundant key figure &1 in aggregation level &2. Please remove it. |
| 128 | Planning function parameter &1 contains inapplicable data selections |
| 129 | Planning function parameter &1 contains inapplicable data selections |
| 130 | Cost object &2 and partner object &1 have different data types or lengths |
| 131 | Field &1 does not exist in table &2; please use the value help |
| 132 | InfoProvider &1 not active; please activate (see setup note 1972819) |
| 133 | Could not set field &1 as attribute |
| 134 | Field &1 is already mapped to InfoObject &2. New mapping not possible. |
| 135 | Field &1 requires additional key &2. Therefore, please assign &2 first. |
| 136 | Please use the value help to enter a field name |
| 137 | You already assigned field &1 as InfoObject &2 to your InfoProviders. |
| 138 | You entered a new field; please check the settings |
| 139 | InfoObject &2 requires compounding InfoObject &1. |
| 140 | InfoObject &1 is already assigned to field &2; choose a different one |
| 141 | Key field &1 in check table of field &2 does not exist in ACDOCA |
| 142 | &1 sent to transport system |
| 143 | You can run this transaction in a customer system only |
| 144 | Please generate field &1 before sending it to the transport system |
| 145 | Could not add generated objects to transport request |
| 146 | Planning function must not have any fields for conditions. |
| 147 | Make InfoObject &V1& in planning function &V2& a block characteristic. |
| 148 | InfoObject &1 is inactive. Please activate it (RSD1). |
| 149 | InfoObject &1 has been modified. Please activate it (RSD1). |
| 150 | Generation error. Repeat saving planning function &1 and try again. |
| 151 | Field &1 exceeds maximum length for InfoObject generation (note 460652). |
| 152 | Field &1 requires unit &2. Please assign &2 first. |
| 153 | Field &2 has the forbidden data type &1. Please choose a different field. |
| 154 | No lot size for category &4, product &2 in plant &1 and in unit &3. |
| 155 | Plan your sales quantities in identical units. Correct�plan for &2 in &1. |
| 156 | Field &1 only allows single value selection. |
| 157 | System cannot convert quantities from &1 to &2. |
| 158 | Category for &1 doesn't exist. |
| 159 | Don't delete or change category &1. It is required by &2. |
| 160 | HDI container &1 doesn't exist in HTA persistence. Contact SAP. |
| 161 | All done. There's nothing more to migrate. |
| 162 | View &1 in package &2 generated. |
| 163 | Couldn't convert the HANA view used by Info Object &1 into an HDI view. |
| 164 | Couldn't convert the HANA view used by InfoProvider &1 into an HDI view. |
| 165 | Don't use category &1 for more than one purpose. |
| 166 | For usage &1 there must be only one category with availability control. |
| 167 | For usage &1 there must be a category with &2. |
| 168 | No MET generated views found, nothing to generate. |
| 169 | Enter a value for mandatory property &1. |
| 170 | No measure property selected |
| 180 | Account groups deactivated as account hierarchy in client &1 |
| 181 | Account groups activated as account hierarchy in client &1 |
| 200 | *** sFIN 056-199, messages 201-299 reserved for CO renovation *** |
| 201 | Wrong category for statistical key figure &1 entered (&2 should be &3) |
| 202 | Wrong unit for statistical key figure &1 entered (&2 should be &3) |
| 203 | Do not exceed the maximum value of & for an amount, quantity or price |
| 204 | Do not exceed the minimum value of & for an amount, quantity or price |
| 300 | * messages 300-349 reserved for OData Planning Services |
| 301 | The GUID could not be created |
| 302 | The uploaded file could not be processed |
| 303 | The entity &1 does not exist |
| 304 | The amount &1 couldn't be converted |
| 305 | The column separator of the file must be a semicolon |
| 306 | The field &1 is not a valid field for plan data |
| 307 | Hierachies of InfoObject &1 are deleted from shared buffer. |
| 308 | Use of buffer for hierarchy &1 is switched on. |
| 309 | Use of buffer for hierarchy &1 is switched off. |