Message type: E = Error
Message class: AA - Messages for Asset Accounting
Message number: 589
Message text: No document type for legacy data transfer is assigned for comp. code &1
You are posting a legacy data transfer.
However, <ZH>no</> document type is defined for legacy data transfers
for company code &V1&.
The posting of the legacy data transfer is <ZH>not</> possible.
Enter a document type for legacy data transfers in Customizing for <LS>
Asset Accounting</> under <DS:SIMG.V_T093C_LDT_DC>Define Document Type
for Legacy Data Transfers</>.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message AA589 indicates that there is no document type assigned for legacy data transfer for the specified company code. This error typically occurs when you are trying to upload or transfer legacy asset data into the Asset Accounting (FI-AA) module in SAP, and the system cannot find a valid document type for the transaction.
Cause:
- Missing Document Type: The document type for legacy data transfer has not been defined in the system for the specified company code.
- Configuration Issues: The configuration settings for Asset Accounting may not be properly set up, leading to the absence of a document type for legacy data transfer.
- Incorrect Company Code: The company code specified in the transaction may not have a corresponding document type configured.
Solution:
To resolve the error, you need to ensure that a document type for legacy data transfer is assigned to the relevant company code. Here are the steps to do this:
Access the Configuration:
- Go to the SAP Easy Access screen.
- Navigate to SPRO (SAP Project Reference Object) > IMG (Implementation Guide) > Financial Accounting > Asset Accounting > Legacy Data Transfer > Define Document Types for Legacy Data Transfer.
Define Document Type:
- In the configuration screen, check if a document type is already defined for the company code in question.
- If not, create a new document type by clicking on the "New Entries" button.
- Enter the required details, including the document type, description, and assign it to the relevant company code.
Assign Document Type:
- Ensure that the document type is correctly assigned to the company code you are working with.
Check Authorization:
- Ensure that you have the necessary authorizations to make changes in the configuration.
Test the Transfer:
- After making the necessary changes, try to perform the legacy data transfer again to see if the error persists.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or FI-AA consultant for further assistance.
Sign up takes 1 minute. 7-day free trial.
AA588 Enter a valid functional area
Self-Explanatory Message Since SAP believes that this specific error message is ...
AA587 Enter a valid fund
Self-Explanatory Message Since SAP believes that this specific error message is ...
AA590 Choose the transaction type appropriate for the existing asset values
acquisitions exist on a fixed asset. You want to enter manual deprec iation and...
AA591 Depreciation key has more depreciation types than previous deprec. key
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.