FAA_CMP - Asset Accounting: Configuration Object Company Code
The following messages are stored in message class FAA_CMP: Asset Accounting: Configuration Object Company Code.
It is part of development package FINS_FAA_CFG_CMP in software component FI-AA-AA. This development package consists of objects that can be grouped under "Asset Accounting: Configuration Object Company Code".
It is part of development package FINS_FAA_CFG_CMP in software component FI-AA-AA. This development package consists of objects that can be grouped under "Asset Accounting: Configuration Object Company Code".
Message Nr ▲ | Message Text |
---|---|
000 | ********* Company code runtime settings E R R O R messages ************** |
001 | Switch to update mode not possible; activity canceled |
002 | Switch to display mode not possible; activity canceled |
003 | Data cannot be saved; activity canceled |
004 | You are not authorized to maintain company code settings |
005 | Activity canceled by user |
006 | Settings for company code &1 unchanged; you do not have to save |
007 | Legacy data transfer status &1 is not defined |
008 | Company code status &1 is not defined |
009 | Editing not possible due to LDT assets in company code &1 |
010 | Error when validating field &1: Field content &2 is not correct |
011 | No segment for legacy data transfer was created yet in company code &1 |
012 | Error when updating table FAAT_CMP; contact your system administrator |
013 | Error when updating table FAAT_CMP_LDT; contact your system administrator |
014 | Processing had to be terminated because of an internal error in method &1 |
015 | Transfer date &1 is in the closed fiscal year &2 |
016 | LDT segment &1 could not be completed for company code &2 |
017 | You are not authorized to display company code &1 |
018 | You are not authorized to edit company code &1 |
019 | Editing not possible due to company code status |
020 | Editing not possible due to legacy data transfer status |
021 | Before you can create a new LDT segment, the last one must be saved |
022 | It is only possible to create a new LDT segment in update mode |
023 | Before you can create a new LDT segment, the last one must be completed |
024 | Legacy data transfer segment can only be completed in edit mode |
025 | It is not possible to complete the LDT segment in status &1 |
026 | It is not possible to complete the LDT segment if you changed its data |
027 | It is only possible to complete the current LDT segment |
028 | The legacy data transfer date is missing for company code &1 |
029 | Legacy data transfer date &1 is in the future |
030 | Legacy data transfer date &1 is in a closed fiscal year |
031 | It is not possible to change and save data in display mode |
032 | The validation of general settings failed for company code &1 |
033 | Legacy data transfer: New segment could not be created for comp. code &1 |
034 | Validation failed; LDT segment could not be completed |
035 | The system could not read the current LDT segment |
036 | Document type is missing from company code &1 |
037 | Validation failed; LDT segment of company code &1 could not be saved |
038 | Validation failed; settings for company code &1 could not be saved |
039 | Validation failed for legacy data transfer settings of company code &1 |
040 | Ledger &2, depreciation area &3: Closed fiscal year is set to &1 |
041 | Ledger &2: Current fiscal year is set to &1 |
042 | Check failed due to LDT postings not reversed in company code &1 |
043 | CoCode &1: You are not allowed to change the LDT status to a previous one |
044 | Check failed due to LDT assets existing in company code &1 |
045 | A newly created legacy data transfer segment can't be completed |
046 | You are not allowed to change LDT data if company code is deactivated |
047 | Posting not possible in company code &1; specify open fiscal year |
048 | Posting not possible in company code &1; specify closed fiscal year |
049 | Editing not possible for ledger nodes |
050 | Editing not possible for depreciation area nodes |
051 | You are not allowed to have more than 2 fiscal years open |
052 | Configuration settings for company code &1 are inconsistent |
053 | SAP has locked company code &1 against changes in Asset Accounting |
054 | Fiscal year entered can be a max. of 3 years apart from current fisc. yr |
055 | Current fiscal year of ledger &1 is initial |
056 | Ledger &2, depreciation area &1: Closed fiscal year is initial |
057 | Ledger &2, depreciation area &1: Closed fiscal year is invalid |
058 | Runtime settings of company code &1 are inconsistent |
059 | LDT date &1 is in the future but BCF was not executed and postings exist |
060 | Legacy data transfer date &1 is invalid for company code &2 |
061 | Legacy data transfer date &1 must not be before G/L migration date &2 |
062 | Not all previous legacy data transfer segments have status 'completed' |
063 | Fiscal years could not be derived from LDT date for ledger &1 |
064 | LDT date changed; check if the fiscal year has to be adjusted |
065 | LDT date must be later than the LDT dates of previous LDT segments |
066 | Only possible to deactivate company code if there are no active assets |
067 | Multiple changes for fisc. year only possible for same closed fisc. year |
068 | CoCd &1: Settings inconsistent; synchronization w/o config. not possible |
069 | Change of LDT date only possible if LDT status is 'In Preparation' |
070 | Not all ledgers of company code &1 have the same current fiscal year |
071 | The opening of a fiscal year is only allowed via balance carryforward |
072 | Closing of fiscal year &1 failed for depreciation area &2 |
073 | Reopening of fiscal year &1 failed for depreciation area &2 |
074 | Reopening of closed fisc. year only possible if current LDT is completed |
075 | CoCd &1 could not be synchronized and was therefore removed from display |
076 | It is only possible to delete LDT segment for current segment |
077 | It is not possible to delete LDT segment if assets exist for this segment |
078 | Only one open FY is allowed if legacy data transfer is at end of year |
079 | The last closed fiscal year &1 is the same as the current fiscal year &2 |
080 | Closed fiscal year is not allowed to be higher than current fiscal year |
081 | Mandatory entries are missing. Please check your entries. |
082 | Company code &2: No fiscal year was opened via BCF for ledger &1 |
083 | Company code &1 is locked against changes in Asset Accounting |
084 | Quantity migration not possible in &1; specify open fiscal year |
085 | Depr. recalcualtion is required to update planned values of ledger &1 |
086 | Planning horizon feature is currently not enabled |
087 | The maximum planning horizon is limited to 5 years |
088 | Planning values will be deleted for ledger &1 from fiscal year &2 onwards |
089 | Planning horizon for ledger &1 changed to &2 fiscal year(s) |
090 | Ldgr &1: Balance carryforward necessary before you reopen the fiscal year |
091 | The legacy data transfer has to be performed in an open fiscal year |
092 | Year-end transfer: Subsequent year must be the highest fiscal year |
093 | Navigation to SAP Fiori app is not supported by current implementation |
094 | Status of deactivated company code &1 cannot be changed |
095 | No valid run could be determined for the selected closing parameters |
096 | You cannot reopen the year before the year of first legacy data segment |
097 | Depr. area &1: Fiscal year must be changed for all constituent areas |
100 | ******* Company code runtime settings S U C C E S S messages ************ |
101 | Settings for company code &1 saved successfully |
102 | No errors found for company code &1 |
103 | Legacy data transfer segment &1 completed for company code &2 |
104 | New legacy data transfer segment &1 created for company code &2 |
105 | Validation successful for legacy data transfer segment of company code &1 |
106 | Validation successful for general settings of company code &1 |
107 | Objects in the display have now been synchronized with configuration |
108 | Closed fiscal year is set to &1 |
109 | Current fiscal year is set to &1 |
110 | Fiscal year &1 is already closed for company code &2 and ledger &3 |