Do you have any question about this error?
Message type: E = Error
Message class: BAPI1022 - Messages from FIXEDASSET BAPIs
Message number: 058
Message text: Table &1: Posting date &2 is not within the permitted date limitation
The transferred posting date &V2& is not within the valid period for a
legacy data transfer (during the year).
The process is terminated.
Check your input data and choose a posting date in the period between
the first day of the fiscal year of the legacy data transfer (&V3&) and
the date of the legacy data transfer (&V4&).
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.
BAPI1022058
- Table &1: Posting date &2 is not within the permitted date limitation ?The SAP error message BAPI1022058 indicates that the posting date specified in a BAPI (Business Application Programming Interface) call is outside the allowed date range defined in the system. This error typically occurs when trying to post a document with a date that is either too far in the past or too far in the future, based on the configuration settings in SAP.
Cause:
- Date Limitation Settings: The system has specific settings that restrict the range of posting dates. These settings can be configured in the financial accounting (FI) module.
- Document Type Settings: Certain document types may have their own date restrictions.
- Company Code Settings: Each company code can have its own fiscal year variant and date restrictions.
- User Authorization: The user may not have the necessary authorizations to post documents with the specified date.
Solution:
Check Date Configuration:
- Go to the transaction code
OB52
to check the posting period settings. Ensure that the posting date you are trying to use falls within the open posting periods.- If necessary, you can extend the open periods or adjust the settings to allow for the desired posting date.
Review Document Type Settings:
- Check the configuration for the specific document type you are using. You can do this in the transaction code
OBA7
to see if there are any restrictions on the posting dates.Verify Company Code Settings:
- Ensure that the fiscal year variant for the company code allows for the posting date you are trying to use. You can check this in the transaction code
OB29
.User Authorization:
- Ensure that the user has the necessary authorizations to post documents for the specified date. This may involve checking user roles and profiles.
Adjust Posting Date:
- If the posting date is not critical, consider adjusting the date to fall within the permitted range.
Related Information:
OB52
: Change Posting PeriodsOBA7
: Document Type ConfigurationOB29
: Fiscal Year Variant ConfigurationBy following these steps, you should be able to resolve the error message BAPI1022058 and successfully post your document.
Get instant SAP help. Start your 7-day free trial now.
BAPI1022057
Fixed asset &2-&3 in company code &1 was processed successfully
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
BAPI1022056
The test 'post-to fixed asset &1 &2-&3' was successful
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
BAPI1022059
Currency area &1 does not exist in table &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
BAPI1022060
Table &1: Inconsistent depreciation areas exist; see long text
What causes this issue? Depreciation areas were transferred in table &V1& that do <ZH>not</> exist on the fixed asset &V2&...
Click on this link to search all SAP messages.