Do you have any question about this error?
Message type: E = Error
Message class: AU - FI-AA utility program error messages
Message number: 260
Message text: Create depreciation key "0000"
You want to assign depreciation area &v1& of this asset to a group
asset. However, there is no depreciation key in the data record of the
input file, nor could the system determine a default depreciation key
from the asset class.
The depreciation for this asset is supposed to be calculated in
depreciation area &v1& using the group asset, and the system uses the
depreciation key of the group asset for this depreciation. Therefore
any depreciation key can be transferred to the asset in this
depreciation area.
However, it is important that the asset receives a depreciation key
(any key) in depreciation area &v1&, so that the checks for the posting
transactions run correctly. The system therefore tries to enter
depreciation key "0000" in depreciation area &v1& of the asset.
Depreciation key "0000", however, is not defined in chart of
depreciation &v2&.
Chooose one of the following options:
Define depreciation key "0000" in chart of depreciation &v2&.
Enter a depreciation key as default value in asset class &v3& for chart
of depreciation &v2& in depreciation area &v1&.
Transfer a depreciation key in the data record of the input file in
depreciation area &v1&.
Error message extract from SAP system. Copyright SAP SE.
AU260
- Create depreciation key "0000" ?The SAP error message AU260, which states "Create depreciation key '0000'", typically occurs when the system is unable to find a valid depreciation key for the asset in question. This can happen for several reasons, including configuration issues or missing data in the asset master record.
Cause:
- Missing Depreciation Key: The depreciation key '0000' is not defined in the system. This key is often used for assets that do not depreciate.
- Incorrect Configuration: The depreciation key may not be properly configured in the Asset Accounting (FI-AA) module.
- Asset Master Record Issues: The asset master record may not have the necessary information or may be incomplete.
- Transaction Type Issues: The transaction type being used may not be compatible with the depreciation key.
Solution:
Create or Modify Depreciation Key:
- Go to the transaction code OAYZ (or navigate through the menu: SPRO > Financial Accounting > Asset Accounting > Depreciation > Define Depreciation Keys).
- Check if the depreciation key '0000' exists. If it does not, you may need to create it or modify an existing key to meet your requirements.
- Ensure that the depreciation key is configured correctly with the necessary parameters (e.g., useful life, method of depreciation).
Check Asset Master Record:
- Use transaction code AS02 to display the asset master record.
- Ensure that the depreciation key is correctly assigned in the asset master data.
- Verify that all required fields are filled out correctly.
Review Transaction Type:
- Ensure that the transaction type being used is compatible with the depreciation key.
- Check the configuration of the transaction type in the system.
Consult Documentation:
- Review SAP documentation or consult with your SAP support team for specific guidance related to your system configuration.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further assistance.
Get instant SAP help. Start your 7-day free trial now.
AU259
Capitalization date &1 is invalid
What causes this issue? An invalid capitalization date was transferred in a data record in the input file.System Response The system issues an error...
AU258
Capitalization date not entered
What causes this issue? The capitalization date is not completed in the data record in the input file.System Response The system issues an error mes...
AU261
Transaction code not specified or invalid
What causes this issue? In the data record of the input file, the transaction code (field BALTD-TCODE) has not been transferred or an invalid value h...
AU262
Transfer on last day allowed only in closed fiscal year
What causes this issue? In company code &v1&, the legacy data transfer date &v2& (the last day of fiscal year &v3&) has to be...
Click on this link to search all SAP messages.