Message type: E = Error
Message class: AA - Messages for Asset Accounting
Message number: 702
Message text: Error when determining periods
You cannot convert periods in this company code.
This company code will be missed out, processing will be continued in
the next company code.
Contact your Systems Specialist.
Tables T009 and T009B have to be corrected.
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 AA702 ("Error when determining periods") typically occurs in the Asset Accounting (FI-AA) module when there is an issue with the period determination for asset transactions. This can happen during various processes, such as asset acquisition, transfer, or retirement.
Causes of AA702 Error
Incorrect Period Settings: The fiscal year variant or the period settings in the configuration may not be set correctly. This can include closed periods or incorrect period intervals.
Missing or Incorrect Master Data: The asset master data may be incomplete or incorrect, leading to issues in determining the correct posting periods.
Authorization Issues: The user may not have the necessary authorizations to post in the specified periods.
Configuration Issues: There may be issues in the configuration of the Asset Accounting module, such as incorrect settings in the fiscal year variant or posting periods.
System Date: The system date may be outside the allowed posting periods, leading to the error.
Solutions to AA702 Error
Check Period Settings:
- Go to the transaction code OB52 to check the open and closed periods for the relevant company code and fiscal year. Ensure that the period you are trying to post to is open.
Review Asset Master Data:
- Use transaction code AS03 to display the asset master data and ensure that all required fields are filled out correctly.
Verify User Authorizations:
- Ensure that the user has the necessary authorizations to post to the asset accounts. This can be checked with the help of your SAP security team.
Check Configuration:
- Review the configuration settings for Asset Accounting, particularly the fiscal year variant and posting periods. This can be done using transaction code OAVC for fiscal year variants.
System Date:
- Check the system date to ensure it is set correctly. If the system date is outside the allowed posting periods, it may need to be adjusted.
Consult SAP Notes:
- Check for any relevant SAP Notes that may address this specific error. You can search for notes in the SAP Support Portal.
Related Information
Transaction Codes:
SAP Documentation: Refer to the official SAP documentation for Asset Accounting for detailed information on configuration and troubleshooting.
SAP Community: Engage with the SAP Community forums for insights and solutions from other users who may have encountered the same issue.
If the problem persists after checking the above points, it may be necessary to involve your SAP support team or consult with an SAP expert for further investigation.
Sign up takes 1 minute. 7-day free trial.
AA701 Parameter 'New fiscal year' entered incorrectly
What causes this issue? The parameter 'New fiscal year' has been ente...
AA700 Error Messages from Batch Depreciation Routines.....(700 - 799)
Self-Explanatory Message Since SAP believes that this specific error message is ...
AA703 Company code is not in the last posting period
What causes this issue? The company code is <ZH>not</> in the last ...
AA704 The target fiscal year is not the next fiscal year
What causes this issue? The specified 'new fiscal year' is <ZH>...
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.