Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 664
Message text: Arrangement or condition record number is missing in LIS structure &1
You tried to delete statistical data for an arrangement from LIS
structure &V1&, even though neither key figure "Condition record
number" nor "Arrangement" is used in the statistics.
As key figures "Arrangement" and "Condition record number" are missing
for the data, the operation cannot be carried out for statistics &V1&.
A complete recompilation of statistical data is required for info
structure &V1& (transaction MEBA or MERA).
Error message extract from SAP system. Copyright SAP SE.
MN664
- Arrangement or condition record number is missing in LIS structure &1 ?The SAP error message MN664, which states "Arrangement or condition record number is missing in LIS structure &1," typically occurs in the context of Logistics Information System (LIS) when there is an issue with the data related to arrangements or condition records. This error can arise during various processes, such as reporting or data extraction, where the system expects certain records to be present but cannot find them.
Causes:
- Missing Data: The arrangement or condition record that the system is trying to access does not exist in the specified LIS structure.
- Incorrect Configuration: The LIS structure may not be properly configured to include the necessary arrangement or condition records.
- Data Transfer Issues: There may have been issues during data transfer or updates that resulted in missing records.
- Authorization Issues: The user may not have the necessary authorizations to access the required records.
Solutions:
- Check Data Existence: Verify that the arrangement or condition record exists in the relevant LIS structure. You can do this by checking the relevant tables or using transaction codes like
SE16
orSE11
.- Recreate Missing Records: If the records are indeed missing, you may need to recreate them. This could involve entering the necessary data manually or running a data upload process.
- Review Configuration: Check the configuration settings for the LIS structure to ensure that it is set up correctly to include the necessary records. This may involve consulting with your SAP Basis or configuration team.
- Data Consistency Check: Run consistency checks on the LIS data to identify and rectify any inconsistencies or missing records.
- Authorization Check: Ensure that the user has the necessary authorizations to access the required records. This may involve checking user roles and permissions.
- Consult SAP Notes: Look for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
Related Information:
MC.9
(LIS: Display Info Structure) or MC.1
(LIS: Maintain Info Structure) to help diagnose and resolve issues.By following these steps, you should be able to identify the cause of the MN664 error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
MN663
Database inconsistency (internal error)
What causes this issue? An internal error occurred. Inconsistent data was found in the settlement index (EBOX) and the document conditions. This is p...
MN662
Compil. of income data for large no. of reb. arrangements (See long text)
See also long text 407 -> largely identicalWhat causes this issue? Because of the selection criteria, compilation of der income data covers a lar...
MN665
Reversal document for document &V1& could not be determined
What causes this issue? The system could not determine which of the two documents &V1& and &V2& (company code &V3& in fiscal ...
MN666
Status &2 of settlement document &1 does not allow updating
What causes this issue? Business volume data in <DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</> is only updated from a...
Click on this link to search all SAP messages.