Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 791
Message text: Index created for settlement documents contains invalid entries
An error occurred during the compilation of the index of the created
settlement documents for condition records for arrangement &V1&.
The settlement documents created are not posted.
Contact your system administrator, as this problem is due to an internal
program error.
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.
MN791
- Index created for settlement documents contains invalid entries ?The SAP error message MN791 indicates that there are invalid entries in the index created for settlement documents. This typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with settlement documents related to internal orders, projects, or other cost objects.
Cause:
The error can be caused by several factors, including:
- Data Inconsistencies: There may be inconsistencies in the data related to settlement documents, such as missing or incorrect entries in the database tables.
- Corrupted Index: The index itself may be corrupted or not properly updated, leading to invalid entries.
- Custom Developments: If there are custom developments or modifications in the system, they might interfere with the standard processing of settlement documents.
- System Upgrades or Changes: Changes in the system, such as upgrades or patches, may lead to inconsistencies in the data or the index.
Solution:
To resolve the MN791 error, you can follow these steps:
Rebuild the Index:
- Use transaction code SARA to access the Archive Administration.
- Check if there are any inconsistencies in the index and rebuild it if necessary.
Check for Inconsistencies:
- Use transaction code SE16 or SE11 to check the relevant database tables (e.g., COEP, COSS, etc.) for inconsistencies or missing entries.
- You can also use transaction KOB1 to analyze the settlement documents and identify any discrepancies.
Run Consistency Checks:
- Use transaction KSV5 to run consistency checks for the relevant cost objects and settlement documents.
- This can help identify and correct any inconsistencies in the data.
Clear Invalid Entries:
- If you identify specific invalid entries, you may need to delete or correct them manually, depending on the nature of the data.
Consult SAP Notes:
- Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that can resolve the issue.
Contact SAP Support:
- If the issue persists after trying the above steps, consider reaching out to SAP Support for further assistance. They can provide more specific guidance based on your system configuration and the nature of the error.
Related Information:
By following these steps, you should be able to identify and resolve the issue related to the MN791 error message in SAP.
Get instant SAP help. Start your 7-day free trial now.
MN790
No. range object "Coll. processing of cust. billing docs." does not exist
What causes this issue? Each debit-side settlement of an arrangement via the general customer billing document interface is assigned a collective pro...
MN789
No. range int. &1 "Coll. processing of cust. bill. docs." does not exist
What causes this issue? Each debit-side settlement of an arrangement via the general customer billing document interface is assigned a collective pro...
MN792
Unable to determine a settlement run number
What causes this issue? Each settlement run for an arrangement in Purchasing is assigned a unique run number. However, all the numbers in number rang...
MN793
Number range interval &1, settlement run number, nearly exhausted
What causes this issue? Each settlement run for an arrangement in Purchasing is assigned a unique number. All the numbers in related number range &am...
Click on this link to search all SAP messages.