Do you have any question about this error?
Message type: E = Error
Message class: RDSV_FI_XX - Regulatory Document and Signature Validation in FI
Message number: 828
Message text: Document must not be parked since a chronological numbering is required
Chronological numbering is active for the country of the company code
that you use.
Parking a document that requires a chronological document number, can
paralyze the system.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The system prevents activities that can interrupt document posting.
Parking a document requires a final real posting on the same day when
the chronological numbering is active.
Therefore you cannot use the document parking feature for postings with
chronological document numbering.
Error message extract from SAP system. Copyright SAP SE.
RDSV_FI_XX828
- Document must not be parked since a chronological numbering is required ?The SAP error message RDSV_FI_XX828, which states "Document must not be parked since a chronological numbering is required," typically occurs in the context of financial document processing. This error indicates that the system requires documents to be processed in a specific chronological order, and the document you are trying to park does not meet this requirement.
Cause:
- Chronological Numbering Requirement: The system is configured to enforce a chronological numbering sequence for financial documents. This means that documents must be posted in a specific order, and parking a document that disrupts this order is not allowed.
- Document Type Settings: The document type you are using may have settings that enforce strict chronological processing.
- Configuration Issues: There may be configuration settings in the financial accounting module that are causing this restriction.
Solution:
- Check Document Sequence: Ensure that the document you are trying to park does not violate the chronological numbering requirement. Verify the sequence of previously posted documents to ensure that the current document fits into the expected order.
- Review Document Type Settings: Check the configuration of the document type you are using. You may need to adjust the settings to allow for parking if it is appropriate for your business process.
- Consult with SAP Basis or Functional Consultant: If you are unsure about the configuration or how to resolve the issue, it may be beneficial to consult with an SAP Basis or Functional Consultant who can provide insights into the specific settings and requirements for your SAP environment.
- Use Alternative Posting Methods: If parking is not allowed, consider using other methods to process the document, such as directly posting it if that aligns with your business processes.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
RDSV_FI_XX826
Specific address data in document is missing for one-time customer &1
What causes this issue? You tried to create an invoice for a one-time customer without assigning name and address information.System Response The sy...
RDSV_FI_XX816
Document with number &1 already exists; cannot create recovery document
What causes this issue? The recovery invoice document that you tried to post has a reference number that already exists in the system as an original ...
RDSV_FI_XX830
Doc. &1 for co.cd. &2 and fisc.year &3 requires reference doc.number
What causes this issue? Credit memo and debit memo documents require a specific invoice reference from a legal point of view. You have not specified ...
RDSV_FI_XX831
Doc. &1 for co.cd. &2 and fisc.year &3 requ. recovery doc.number
What causes this issue? You have not specified a mandatory reference correctly. The recovery invoice number was not entered.System Response The syst...
Click on this link to search all SAP messages.