FCO_COPA - SFIN message class for CO-PA relevant issues
The following messages are stored in message class FCO_COPA: SFIN message class for CO-PA relevant issues.
It is part of development package FINS_CO_COPA in software component CO-PA. This development package consists of objects that can be grouped under "Management Accounting - Profitability Accounting".
It is part of development package FINS_CO_COPA in software component CO-PA. This development package consists of objects that can be grouped under "Management Accounting - Profitability Accounting".
Message Nr ▲ | Message Text |
|---|---|
| 000 | <<< Generation CO-PA environment/data structure messages >>> |
| 001 | Error while generating append &. Check activation log |
| 002 | Characteristic name & too long. It can not be carried forward in ACDOCA |
| 003 | Generation of GLU1, GLU2 and FI-SL programs done |
| 004 | Append & was created for table ACDOCA |
| 005 | Field & was added to table ACDOCA for charateristic & |
| 006 | Structure & could not be updated. |
| 007 | Characteristic & can not be mapped to ACDOCA field (inform SAP) |
| 008 | Data structure of operating concern & is not allowed to be updated |
| 009 | Mapping data (CO-PA characteristic - ACDOCA field) are missing |
| 010 | Account-based Profitability Analysis inactive for operating concern &1 |
| 011 | Account-based Profitability Analysis inactive for operating concern &1 |
| 012 | Error during updating of ACDOCA field catalog for characteristic & |
| 013 | Entries from table TKEOE (&1) and TKECCU (&2) were removed |
| 014 | New CO-PA characteristic for ACDOCA. Please start report &1 in background |
| 015 | Operating concern &1 must not be created |
| 016 | Account-based Profitability Analysis inactive for operating concern &1 |
| 017 | Entries from table TKEOE (&1) were updated |
| 018 | New ACDOCA fields: Operating concern & was checked |
| 019 | Append &1 was created for structure &2 |
| 020 | Append &1 was updated for structure &2 |
| 021 | Error while generating cloud environment for Profitability Analysis |
| 025 | <<< Profitability segment determination >>> |
| 026 | Transferred contr. area does not match the one derived from company code |
| 027 | Company code must be transferred |
| 028 | Industry version for operating concern &1 not found |
| 029 | Determining prof. segment for object &1 in operating concern &2 failed |
| 030 | Transferred company code does not match the one in the prof. segment |
| 031 | Cross-client information for operating concern &1 not found |
| 032 | Transferred controlling area does not match the one in the prof. segment |
| 033 | Transferred op. concern does not match the one derive from contr. area |
| 034 | Company code for functional area determination is missing |
| 035 | No or no unique sales order item assigned to work package &1 |
| 036 | Account-based Profitability Analysis inactive for operating concern &1 |
| 037 | Expected delivery date missing in prof. segment determination |
| 050 | <<< Migration >>> |
| 051 | Adapt settings for "Profitability Segment Characteristics" |
| 052 | Processing mode: &1 |
| 053 | Deleted entries for summarized characteristics: &1 |
| 054 | Number of deleted entries must be bigger or equal the inserted ones |
| 055 | Update run successfully executed |
| 056 | Deleted entries for exceptions to summarization: &1 |
| 057 | "Profitab. Segment Characteristics" not supported in the finance add-on |
| 058 | Realignments are not supported in the finance add-on |
| 059 | Realignments are not supported in the finance add-on |
| 060 | Number of deleted and updated entries differs from selected entries |
| 061 | Remaining entries for summarized chars. (only costing-based): &1 |
| 062 | Not all TKEOE entries could be updated |
| 063 | Not all TKECCU entries could be deleted |
| 075 | <<< Top-down distribution >>> |
| 076 | Variant &1 contains invalid Processing Instructions and has been adapted |
| 077 | For char "&1 (&2)" only "Retain" allowed in the Proc. Instructions |
| 078 | No documents to be reversed have been found |
| 079 | Not all documents to be reversed have been found |
| 080 | No line items to be reversed have been found for document &1 |
| 081 | Variant &1 contains invalid Value Field settings and has been adapted |
| 082 | In the Proc. Instructions set unit of measure "&1 (&2)" to "Retain" |
| 083 | Function can only be started with saved variant |
| 100 | <<< Other CO-PA relevant messages >>> |
| 101 | Transaction & is not supported in S/4Hana Cloud |
| 102 | Field name must be between & and & characters long for CI_COBL fields |
| 103 | Field name must begin with ZZ, YY or & |
| 104 | Field name must begin with ZZ or YY |
| 105 | CO-PA characteristic name must be same like CI_COBL field name |
| 106 | TKEF entry & & could not be removed from database |
| 107 | Report & must be started in background |
| 108 | An unspecified error has occurred in program & |
| 109 | No error is occurred for operating concern & |
| 110 | Component &1 does not exist in table ACDOCA |
| 111 | Input type is not supported |
| 112 | Component &1 is not character-like or does not have length 1 |
| 113 | Update ACDOCA line items with OBJNR 'AO*' |
| 114 | Number of ACDOCA line items read: &1 |
| 115 | Number of ACDOCA line items updated: &1 |
| 116 | Thereof in operating concern &1: &2 |
| 117 | CO-PA characteristic &1 exists in table ACDOCA. Deleting impossible. |
| 118 | Error occurred during the checking of table ACDOCA. Deleting impossible. |
| 119 | Settings for profitability segment characteristics will be deleted |
| 120 | Timestamp &1 could not be converted to UTC time |
| 121 | SEM Banking not supported in S/4 Hana |
| 122 | Only enter G/L accounts of type "N - Nonoperating Expense or Income" |
| 150 | <<< Summarization >>> |
| 151 | Enter a valid characteristic |
| 152 | An entry already exists for characteristic "&1" |
| 153 | Characteristic "&1" activated for summarization globally |
| 154 | Characteristic "&1" deactivated for summarization globally |
| 155 | Enter a valid field name |
| 156 | Profitability segment - G/L line item table ACDOCA summarization |
| 157 | Field "&1" activated for summarization globally |
| 158 | Field "&1" deactivated for summarization globally |
| 159 | An entry already exists for field "&1" |
| 160 | Enter an operating concern |
| 161 | Enter a valid company code |
| 162 | An entry already exists for company code "&1" |
| 163 | Restricted summarization depending on company code |
| 164 | Characteristic "&1" activated for summarization in company code "&2" |
| 165 | Characteristic "&1" deactivated for summarization in company code "&2" |
| 166 | Operating concern: "&1" |
| 167 | Characteristic "&1" deactivated for summarization in other company codes |
| 200 | <<< Realignment >>> |
| 201 | &1: No realignment for real account assignment to profitability segment |
| 202 | &1: No attributed profitability segment shall be determined |
| 203 | Characteristic &1 (&2) is relevant for legal reporting -> See long text |
| 204 | Characteristic &1 (&2) is only realigned, if not filled -> See long text |
| 205 | Selection on field &1 (&2) only relevant for ACDOCA -> See long text |
| 206 | Selection on field &1 (&2) only relevant for ACDOCA -> See long text |
| 207 | Characteristic &1 (&2) is relevant for legal reporting -> See long text |
| 208 | Characteristic &1 (&2) is only realigned, if not filled -> See long text |
| 243 | |
| 250 | <<< Transport >>> |
| 251 | Transport object &1 is not allowed |
| 252 | Operating concern is initial |
| 253 | Workbench request is empty. Workbench request is obligatory. |
| 254 | Customizing request is empty. Customizing request is obligatory. |
| 255 | Request category &1 is not allowed for workbench request |
| 256 | A task is missing for request &1 |
| 257 | Locking of transport task &1 not possible |
| 258 | Request category &1 is not allowed for customizing request |
| 259 | Transport requests were not filled |
| 260 | Type of entered request &1 is incorrect. Type is &2 instead of &3. |
| 261 | Entered request &1 not available in system. |
| 262 | Application log could not be saved |
| 263 | Transport & set new version for CO-PA environments |
| 264 | It is an upgrade |
| 265 | |
| 266 | CO-PA environment was set successfully to & & |
| 267 | Complete generation is set for all operating concerns |
| 268 | Generation of environment is not possible during import |
| 269 | Client independent environment generated successfully |
| 270 | Client independent environment has not been generated completely |
| 271 | Operating concern &1 does not exist |
| 272 | Operating concern &1 is only in initital state |
| 273 | Generation of environment not possible |
| 300 | <<< CO-PA XPRAs >>> |
| 301 | No data conversion required for cloud systems |
| 302 | User &1 does not have authorization to perform XPRA &2 |
| 303 | Data element &1 not found |
| 304 | Reading of data element &1 raised an error |
| 305 | Starting to replace domain WERTV8 for CO-PA value fields at &1 &2 |
| 306 | Replacing domain WERTV8 for CO-PA value fields finished at &1 &2 |
| 307 | Error raised during saving of data element &1 |
| 308 | Error raised during activation of relevant data elements |
| 309 | Object &1 &2 was not activated correctly |
| 310 | For data element &1 domain is replaced and data element is saved |
| 311 | Object &1 &2 was activated correctly |
| 312 | For relevant value fields old domain WERTV8 was replaced |
| 313 | Field catalogs were deleted for all active operating concerns |
| 314 | XPRA: &1 data elements were updated and saved |
| 315 | XPRA: &1 data elements were only saved |
| 316 | XPRA: &1 data elements were activated |
| 317 | XPRA: &1 additional objects were activated |
| 318 | XPRA: &1 data elements were not activated correctly |
| 319 | XPRA: &1 additional objects were not activated correctly |
| 320 | No relevant data element is found |
| 321 | XPRA: &1 data elements could not be found |
| 322 | XPRA: &1 data elements with reading error |
| 323 | Field catalog of operating concern &1 was removed |
| 324 | XPRA: &1 data elements were not saved correctly |
| 325 | Data element &1 could not be activated correctly |
| 350 | <<<<<<<< COPA - Extensibility >>>>>>>>>>>>>>>>>>>>>> |
| 351 | Make sure that this field is not used in external reporting and processes |
| 352 | Custom field &1 will be added |
| 353 | Custom field &1 will be deleted |
| 354 | Custom field &1 will be adapted |
| 355 | Custom field &1 not contained in include INCL_EEW_MARKET_SEGMENT_PS |
| 356 | Inconsistency in table &1 for custom field &2 |
| 357 | Entry for custom field &1 missing in table &2 for structure &3 |
| 358 | Update mode &1 for custom field &2 unknown |
| 359 | Custom field &1 to be deleted from table TKEF not found |
| 360 | No unique key field for custom field &1 found in check table &2 |
| 361 | Entry for KNDNR not found in table CE4_FLAG |
| 362 | Errors occurred during custom field update |
| 363 | Update with custom fields was successful |
| 364 | Insertion or correction of custom field &1 failed |
| 365 | Deletion of custom field &1 failed |
| 366 | Status in table TKEBB is not "1 - Environment generated completely" |
| 367 | Entry for custom field &1 still exists in table &2 for structure &3 |
| 368 | Invalid code value. Profitability Analysis is inactive. |
| 369 | For field & check field is missing in field catalog |
| 370 | Check table & of field & has case sensitive entries |
| 371 | CO-PA environment status of operating concern & was set to error |
| 372 | Check table & not found in system |
| 373 | Custom Field &1 not contained in field catalog TKEF |
| 374 | Deletion of key user field &1 is not allowed. |
| 375 | Consistency check can not be executed for field &1 |
| 376 | Field &1 is missing in field catalog of operating concern &2 |
| 377 | The length of field & was increased |
| 378 | Field catalog of operating concern &1 deleted |
| 379 | Invalid code value. Operating concern &1 is inactive. |
| 380 | The & custom field cannot be maintained in this transaction. |
| 381 | The & field contains customer generated objects. |
| 382 | ABAP Dictionary objects for the & field are inactive. |
| 383 | Either the short text or the description of the & field is missing. |
| 384 | The & field is already available in the operating concern. |
| 385 | Data type length for the & field exceeds the limit of 18 characters. |
| 386 | Maximum length of the & field exceeds the limit of 23 characters. |
| 387 | The check table for the & field contains lowercase entries. |
| 388 | Field must be unassigned from all operating concerns in all systems |
| 389 | This field is used in the Operating Concern &. |
| 390 | You can remove it by using transaction KEA0. |
| 391 | All the Codelist fields are consistent |
| 392 | The custom BO field & is incomplete. Please create an incident. |
| 393 | The custom BO field & should have length of 10 characters only. |
| 400 | << CO-PA Environment generation and handling of Operating Concern A000 >> |
| 401 | Operating Concern & is not available |
| 402 | Field & could not be inserted into table TKEFE |
| 403 | Import parameters are empty |
| 404 | The Currency type & is not available |
| 405 | Error occured while inserting into table TKEFE |
| 406 | The Fiscal Year Variant & is not available |
| 407 | Error occured while executing the function module & |
| 408 | Operating concern &1 is locked by &2. |
| 409 | Error occured while deletion of TKEFE entries |
| 410 | Table or View & does not exist |
| 411 | Field catalog of operating concern & was not created |
| 412 | No attributes found for operating concern & in client & |
| 413 | Operating concern & has not yet been generated |
| 414 | Generation terminated: Program & not in the database |
| 415 | Upgrade TKEF / TKEFD not possible |
| 416 | Client independent environment generated successfully |
| 417 | Client independent environment generated, warning were issued |
| 418 | Client independent environment has not been generated completely |
| 419 | Operating Concern Language Key/Description is missing |
| 420 | No Derivation Step found for operating concern & |
| 421 | Initializing component profitability analysis has failed |
| 422 | Client dependent environment generated successfully |
| 423 | Client dependent environment generated, warning were issued |
| 424 | Client dependent environment has not been generated completely |
| 425 | Report & was generated correctly |
| 426 | Report & was not generated correctly |
| 427 | Update of component profitability analysis has failed |
| 428 | Deletion of the derivation step failed for & |
| 429 | Insertion of the derivation step failed for & |
| 430 | Function not supported for OnPremise |
| 431 | Reset of the derivation step failed for & |
| 432 | The derivation step already exists for & |
| 433 | Missing text for the derivation step |
| 434 | Generated structures updated with explicit search helps |
| 435 | No or not all generated structures updated with explicit search helps |
| 436 | Explicit search helps added to structure &1 |
| 437 | No explicit search helps added to structure &1 |
| 438 | No generated structures updated with explicit search helps |
| 439 | Currency type at controlling area information is missing |
| 440 | Fiscal year variant at controlling area information is missing |
| 441 | Client independent attributes from operating concern &1 have errors |
| 442 | Client independent attributes from operating concern &1 are checked |
| 443 | Client independent attributes from operating concern &1 are corrected |
| 444 | Client dependent attributes from operating concern &1 have errors |
| 445 | Client dependent attributes from operating concern &1 are checked |
| 446 | Client dependent attributes from operating concern &1 are corrected |
| 447 | CO-PA fields from operating concern &1 have errors |
| 448 | CO-PA fields from operating concern &1 are checked |
| 449 | CO-PA fields from operating concern &1 are corrected |
| 450 | CO-PA environment from operating concern &1 has errors |
| 451 | CO-PA environment from operating concern &1 is checked |
| 452 | CO-PA environment from operating concern &1 is successfully corrected |
| 453 | TABLE entry of TKEBB is corrected and updated for operating concern &1 |
| 454 | TABLE entry of TKEB is corrected and updated for operating concern &1 |
| 455 | TABLE entry of TKEBL is corrected and updated for operating concern &1 |
| 456 | Attributes from operating concern &1 successfully corrected |
| 457 | Correction of attributes from operation concern &1 have failed |
| 458 | Correction of CO-PA fields from operation concern &1 have failed |
| 459 | Correction of operating concern &1 has failed |
| 460 | Functionality only provided at Cloud-Release |
| 461 | Required fields of controlling area &1 are not filled |
| 462 | Entries Custom Fields for operating concern &1 are missing |
| 463 | Fields added to table TKEFE for operating concern &1 |
| 464 | Field &1 added to table TKEFE for operating concern &2 |
| 465 | Field &1 could not be inserted to table TKEFE for operating concern &2 |
| 466 | Field &1 deleted from table TKEFE for operating concern &2 |
| 467 | Field &1 could not be deleted from table TKEFE for operating concern &2 |
| 468 | Function not supported for S/4Hana Cloud |
| 469 | Transport funtion is not supported in S/4Hana Cloud |
| 470 | No initial description of derivation step found |
| 471 | Derivation step of operating concern &1 successfully corrected |
| 472 | Correction derivation step of operating concern &1 have failed |
| 473 | No initial description of operating concern found |
| 474 | No initial description of derivation step found |
| 475 | <<<<<<<<< OP Best Practice Content for A000 >>>>>>>>>>> |
| 476 | Structure preparation step failed for operating concern &1 |
| 477 | Field &1 is missing in std. field catalog TKES for operating concern &2 |
| 478 | Fields already added to table TKEFE for operating concern &1 |
| 479 | Domain information is missing for elememt &1 of operating concern &1 |
| 480 | No dependency fields found for operating concern &1 |
| 481 | Saving of structures failed for operating concern &1 |
| 482 | Activation of structures failed for operating concern &1 |
| 483 | Structures of operating concern &1 saved and activated |
| 500 | << CO-PA Environment generation and handling of Operating Concern A000 >> |
| 501 | Derivation step of operating concern &1 has error |
| 502 | Derivation step of operating concern &1 is checked |
| 503 | Initial descriptions of operating concern &1 has error |
| 504 | Initial descriptions of operating concern &1 is checked |
| 510 | Number range &1 interval &2 must start with at least &3: &4 is too small |
| 551 | You can�t use costing-based profitability analysis in op. concern &1. |
| 552 | System has operating concerns using costing-based profitability analysis |
| 553 | Operating concern &1 was deactivated |
| 700 | >>>>>>> from 700 to 799 reserved for statistical SD conditions >>>>>>> |
| 701 | Ledger &2 of Ledger Group &1 is not of type 'Prediction and ...' |
| 702 | Ledger Group is initial |
| 800 | >>>>>>> from 800 to 899 reserved for Custom BO Scenario >>>>>>> |
| 801 | Accounting: Market Segment Field extensibility |
| 802 | Sub-nodes are not allowed for the Market Segment Scenario |
| 803 | Type &1 not supported |
| 804 | The number of key fields must not be greater than 1 |
| 805 | Only upper case characters are supported |
| 806 | Custom Business Object &1 is not associated to scenario &2 |
| 807 | Unique name could not be generated for integration of custom BO &1 |
| 808 | DDIC activation protocoll &1 |
| 809 | Market Segment Scenario is not supported in Cloud-Release |
| 810 | Maximum length of the name &1 exceeds the limit of &2 characters. |