How To Fix MMPUR_CAT_EXTR_LGMSG190 - Periodic scheduling of full import is not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: MMPUR_CAT_EXTR_LGMSG - Extractor Log Messages

• Message number: 190

• Message text: Periodic scheduling of full import is not allowed

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message MMPUR_CAT_EXTR_LGMSG190 - Periodic scheduling of full import is not allowed ?

  The SAP error message MMPUR_CAT_EXTR_LGMSG190 indicates that there is an issue with the periodic scheduling of a full import in the context of the SAP Material Management (MM) module, specifically related to the procurement process. This error typically arises when there is an attempt to schedule a full import of data that is not permitted due to system settings or configurations.
  Cause:
  
  Configuration Settings: The system may be configured to disallow periodic full imports. This is often a safeguard to prevent performance issues or data inconsistencies.
  Job Scheduling: There may be an attempt to schedule a job that is not allowed to run periodically, or the job type may not support periodic execution.
  System Restrictions: Certain system restrictions or policies may be in place that prevent the execution of full imports on a scheduled basis.
  
  Solution:
  
  Check Configuration: Review the configuration settings in the SAP system related to the import jobs. Ensure that the settings allow for the type of import you are trying to schedule.
  Job Scheduling: If you are trying to schedule a job, consider changing the job type to a one-time execution instead of a periodic one. You can do this in the job scheduling transaction (e.g., SM36).
  Consult Documentation: Refer to the SAP documentation or help resources for specific guidelines on scheduling imports and the limitations that may apply.
  System Administrator: If you do not have the necessary permissions or knowledge to change the settings, consult with your SAP system administrator or BASIS team. They can provide insights into the system configuration and help resolve the issue.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message. SAP Notes often provide patches or additional guidance for known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM36 (Job Scheduling), and others that may help in managing background jobs.
  SAP Community: Engage with the SAP Community forums or support channels for additional insights and shared experiences from other users who may have encountered similar issues.
  Performance Considerations: Understand the implications of running full imports, especially in a production environment, as they can impact system performance and data integrity.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.