Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 687
Message text: No update rules exist at time &1
There are no update rules at the time &V1& (table TMC2D or TMC2F) for
update group &V2&.
As the document to be processed is relevant for subsequent settlement,
this is not permitted.
The function has been terminated.
INCLUDE ISR_VERWALTUNG
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.
MN687
- No update rules exist at time &1 ?The SAP error message MN687 "No update rules exist at time &1" typically occurs in the context of data extraction or data loading processes, particularly when working with SAP BW (Business Warehouse) or SAP BI (Business Intelligence). This error indicates that there are no update rules defined for the specified time period or for the data source you are trying to work with.
Cause:
- Missing Update Rules: The most common cause is that there are no update rules defined for the InfoObject or InfoProvider you are trying to load data into.
- Incorrect Time Reference: The time reference specified in the error message may not correspond to any existing update rules.
- Data Source Configuration: The data source may not be properly configured or activated, leading to the absence of update rules.
- Transport Issues: If the update rules were recently transported from another system, they may not have been activated in the target system.
Solution:
Check Update Rules:
- Go to the Data Warehousing Workbench (transaction code RSA1).
- Navigate to the InfoProvider or InfoObject in question.
- Check if the update rules are defined and active for the relevant time period.
Create or Activate Update Rules:
- If no update rules exist, you will need to create them. This can be done by:
- Right-clicking on the InfoObject or InfoProvider and selecting "Create Update Rules."
- Following the prompts to define the necessary update rules.
- If update rules exist but are inactive, activate them.
Check Data Source:
- Ensure that the data source is correctly configured and activated.
- Verify that the data source is linked to the correct InfoProvider.
Review Time Characteristics:
- Ensure that the time characteristics used in your data loading process are correctly defined and match the update rules.
Transport Issues:
- If the update rules were transported, check the transport logs for any errors and ensure that all necessary objects were transported correctly.
Consult Documentation:
- Refer to SAP documentation or help resources for specific guidance on creating and managing update rules.
Related Information:
By following these steps, you should be able to resolve the MN687 error and ensure that your data loading processes function correctly.
Get instant SAP help. Start your 7-day free trial now.
MN686
Condition type &1 is indep. of bus. vol. (no subseq. update of bus. vol.)
What causes this issue? Business volume updating is not required or defined for business-volume- independent condition type (here &V1& for ap...
MN685
Subs. sttlmnt indep. of bus. vol. does not permit settlmnt at plant level
What causes this issue? Condition type group &V2& includes condition type &V1&. Condition type &V1& is business volume-indepe...
MN688
Billing doc. unit of measure for item &2 of billing document &1 missing
What causes this issue? The billing document unit for item &V2& in supplier billing document &V1& is missing.System Response The sys...
MN689
Error in update simulation (subsequent settlement)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.