How To Fix GI349 - An index only was found for the document number entered


SAP Error Message - Details

  • Message type: E = Error

  • Message class: GI - FI-SL update

  • Message number: 349

  • Message text: An index only was found for the document number entered

  • Show details Hide details
  • What causes this issue?

    The system only found an index, but not an assigned record for the
    document number defined. This means that documents have been archived,
    but the assigned index file has not been archived.

    System Response

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

    How to fix this error?


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message GI349 - An index only was found for the document number entered ?

    The SAP error message GI349 ("An index only was found for the document number entered") typically occurs when you are trying to access a document in the system, but the system can only find an index entry for that document rather than the actual document itself. This can happen for several reasons, including:

    Causes:

    1. Document Deletion: The document you are trying to access may have been deleted or archived, and only the index entry remains.
    2. Indexing Issues: There may be issues with the indexing of documents in the database, leading to inconsistencies.
    3. Authorization Issues: You may not have the necessary authorizations to view the document, which can sometimes lead to misleading error messages.
    4. Database Issues: There could be underlying database issues that prevent the retrieval of the document.

    Solutions:

    1. Check Document Status: Verify if the document still exists in the system. You can do this by checking the relevant transaction or table where the document is stored.
    2. Re-indexing: If the issue is related to indexing, you may need to perform a re-indexing of the relevant tables. This usually requires administrative access and should be done by a system administrator.
    3. Authorization Check: Ensure that you have the necessary authorizations to access the document. You may need to contact your SAP security team to verify your access rights.
    4. Consult Logs: Check the system logs for any additional error messages or warnings that could provide more context about the issue.
    5. Contact Support: If the issue persists, consider reaching out to SAP support or your internal IT support team for further assistance.

    Related Information:

    • Transaction Codes: You may want to use transaction codes like SE11 (Data Dictionary) or SE16 (Data Browser) to check the relevant tables for the document.
    • Archiving: If documents are archived, you may need to access the archiving system or process to retrieve the document.
    • SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide patches or updates.

    By following these steps, you should be able to diagnose and potentially resolve the GI349 error in SAP.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant