Do you have any question about this error?
Message type: E = Error
Message class: F5 - Document Editing
Message number: 429
Message text: Document & does not exist in company code & or has been archived
The following causes are possible:
Document &V1& &V2& does not exist in fiscal year &V3&.
The document is still being updated.
The document has already been archived or is located in the cold area of
the database.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
If you want to retrieve the document from the archive in order to
display it, you must first change your document display processing
options (select the option "Search for documents in archive").
<DS:TRAN.FB00> Change processing options</>
In order to display the document from the archive you must specify the
fiscal year and the document index must have been maintained in the
archive to enable you to access documents. To maintain the index, you
must set the option 'Build index' for the delete program for object
FI_DOCUMNT, in the archiving configuration function. Failing that, you
can generate the index retroactively using program RSARCH15.
No prerequisites are required for documents in the cold area of the
database.
Error message extract from SAP system. Copyright SAP SE.
F5429
- Document & does not exist in company code & or has been archived ?The SAP error message F5429 indicates that a specific document does not exist in the specified company code or has been archived. This error typically occurs in the context of financial transactions, such as when trying to display or process a financial document (like an invoice or payment) that the system cannot find.
Causes:
Document Does Not Exist: The document number you are trying to access may not exist in the specified company code. This could be due to a typo in the document number or an incorrect company code being used.
Document Has Been Archived: The document may have been archived as part of the data management process in SAP. Archiving is a way to manage data volume by moving older data to an archive storage, making it unavailable for regular transactions.
Incorrect Company Code: The company code specified in the transaction may not match the company code associated with the document.
Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the document, leading to the perception that it does not exist.
Solutions:
Verify Document Number and Company Code: Double-check the document number and ensure that you are using the correct company code. Make sure there are no typographical errors.
Check Document Status: If you suspect the document has been archived, you can check the archiving settings in your SAP system. You may need to consult with your SAP Basis or data management team to see if the document is archived.
Use Archive Information System: If the document has been archived, you can use the Archive Information System (transaction SARA) to search for archived documents. You may need to restore the document from the archive if necessary.
Authorization Check: Ensure that you have the necessary permissions to access the document. If you suspect an authorization issue, contact your SAP security team to verify your access rights.
Consult SAP Support: If the issue persists and you cannot determine the cause, consider reaching out to SAP support for further assistance. They can provide insights based on system logs and configurations.
Related Information:
By following these steps, you should be able to identify the cause of the F5429 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
F5428
Check that the posting date is still correct
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
F5427
Previous company code is taxed differently
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
F5430
Baseline date for pmnt is & days after the document date; check
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
F5431
System error: Table BUZTAB is not filled from called program
What causes this issue? The internal program table BUZTAB was not filled by the calling program. Further processing at this point does not make sense...
Click on this link to search all SAP messages.