How To Fix MMRP01136 - Period profile &1 was saved, table of periods not updated in liveCache

SAP Error Message - Details

• Message type: E = Error

• Message class: MMRP01 - Rapid Planning Matrix

• Message number: 136

• Message text: Period profile &1 was saved, table of periods not updated in liveCache

What causes this issue?

The period profile has been saved, but the related table of periods
could not be updated in the liveCache because the liveCache was not
available.

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?

Update the table of periods in the liveCache using the transaction
<DS:TRAN.RPM_DATEVECTORS_REOR>Reorganize Table of Periods in liveCache
</> as soon as the liveCache is available again.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MMRP01136 - Period profile &1 was saved, table of periods not updated in liveCache ?

  The SAP error message MMRP01136 indicates that there is an issue with the period profile in the context of the liveCache system, which is often used in SAP for planning and optimization tasks, particularly in the areas of production planning and detailed scheduling.
  Cause:
  The error message "Period profile &1 was saved, table of periods not updated in liveCache" typically arises due to one of the following reasons:
  
  
  LiveCache Connection Issues: There may be a problem with the connection between the SAP application server and the liveCache instance. This could be due to network issues, configuration problems, or the liveCache service not running.
  
  
  Data Consistency Issues: The data being saved may not be consistent or valid, leading to a failure in updating the liveCache. This could be due to incorrect or incomplete data in the period profile.
  
  
  Authorization Issues: The user may not have the necessary authorizations to update the liveCache, which can prevent the system from making the required changes.
  
  
  Configuration Errors: There may be configuration issues in the period profile settings or in the liveCache setup that prevent the update from occurring.
  
  
  Solution:
  To resolve the MMRP01136 error, you can take the following steps:
  
  
  Check LiveCache Status: Ensure that the liveCache instance is running and accessible. You can check the status of the liveCache using transaction codes like LC10 or LC11 in SAP.
  
  
  Review Connection Settings: Verify the connection settings between the SAP system and the liveCache. Ensure that the configuration is correct and that there are no network issues.
  
  
  Validate Data: Check the data being saved in the period profile for any inconsistencies or errors. Make sure that all required fields are filled out correctly and that the data adheres to the expected formats.
  
  
  Check Authorizations: Ensure that the user performing the operation has the necessary authorizations to update the liveCache. You may need to consult with your SAP security team to verify this.
  
  
  Consult Logs: Review the application logs and liveCache logs for any additional error messages or warnings that could provide more context about the failure.
  
  
  Recreate Period Profile: If the issue persists, consider recreating the period profile to ensure that it is set up correctly.
  
  
  SAP Notes and Support: Check for any relevant SAP Notes that may address this specific error. You can search the SAP Support Portal for updates or patches that may resolve the issue.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes related to liveCache management, such as LC10 (LiveCache Administration) and LC11 (LiveCache Monitor).
  SAP Documentation: Refer to the official SAP documentation for detailed information on liveCache and period profiles.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem continues after following these steps, it may be necessary to escalate the issue to SAP support for further assistance.