How To Fix CRM_MKTPL_MASS070 - Mass Change aborted, no more ressources for parallel processing

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_MKTPL_MASS - Messages for Marketing Mass Change, Copy & Approval

• Message number: 070

• Message text: Mass Change aborted, no more ressources for parallel processing

What causes this issue?

You executed a Mass Change operation using parallel processing, and no
system resources were available to start parallel tasks as configured in
your system's customizing.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

Processing of your Mass Change activity was aborted.

How to fix this error?

The log for the Mass Change operation you just launched contains
information on what tasks could be completed successfully, and what
tasks failed. You may re-execute the Mass Change for the failed tasks.
If your Mass Change operations often fail because of this error, we
recommend that you get in touch with your systems administrators, and
ask them to review the settings for parallel processing.

Procedure for System Administrators

Most of the times, this error is circumstantial, and only occurs when
there is an exceptionally high level of activity in the system. However,
if it happens frequently, you should consider revising the settings for
parallel processing in the customizing activity: Customer Relationship
Management -> Trade Promotion Management -> Trade Promotions -> Parallel
Processing -> Define Settings for Parallel Processing.
The parallel processing engine roughly works this way: it divides the
number of objects to change by the parameter NUM_PER_BATCH, and as long
as less than NUM_MAX_THREADS parallel updates are executed, it tries up
to NUM_OF_RETRIES to execute the update, waiting WAIT_TIME between
another attempt is made.
<LS>NUM_MAX_THREADS</>
This parameter sets the maximum number of threads that can run in
parallel. When intensive parallel processing is used instead of serial
execution, the system is more likely to experience peak overloading.
This is especially true when you set a high number of threads. When this
occurs, throughput may be reduced as a result of lock conflicts or over
loading of system components. If the capacity limit of one of the system
components is reached, the throughput of the whole process is
restricted. When you start further processes, the throughput is further
reduced.
The optimal number of threads is project-specific and depends on the
available system resources. It is recommended that you perform a stress
test to determine the settings that would be best suited to your
installation.
If this parameter is not maintained, the default value 20 is used.
<LS>NUM_PER_BATCH</>
This parameter sets the maximum number of trade promotions to be
included in a thread. To avoid interlocking and potential inconsistency
issues, we recommend that you don't maintain anything any value for
NUM_PER_BATCH. If this parameter is not maintained, the default value 1
is used.
<LS>WAIT_TIME</>
In case no more system resources were available at the time of starting
a new tread, this parameter sets the total number of seconds that must
elapse before the system attempt to start this tread again. If this
parameter is not maintained, the default value 15 is used.
<LS>NUM_OF_RETRIES</>
This parameter sets the number of times the system will try to start a
new thread before the new error message described above is raised, and
the mass change is stopped. If this parameter is not maintained, the
default value of 15 is used.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_MKTPL_MASS070 - Mass Change aborted, no more ressources for parallel processing ?

  The SAP error message CRM_MKTPL_MASS070 indicates that a mass change operation in the SAP CRM system has been aborted due to insufficient resources for parallel processing. This typically occurs when the system is unable to allocate enough resources (like memory or processing power) to handle the requested mass change operation.
  Causes:
  
  High Volume of Data: Attempting to process a large number of records simultaneously can overwhelm the system's resources.
  System Configuration: The system may not be optimally configured for parallel processing, leading to resource allocation issues.
  Background Job Limitations: If the system has reached its limit for background jobs or parallel processing threads, it may not be able to handle additional requests.
  Database Performance: Slow database performance or locks on the database can also contribute to this error.
  
  Solutions:
  
  Reduce Data Volume: Instead of processing a large number of records at once, try breaking the operation into smaller batches. This can help manage resource usage more effectively.
  Check System Configuration: Review the configuration settings for parallel processing in your SAP system. Ensure that the parameters for background processing and parallel jobs are set appropriately.
  Monitor Background Jobs: Use transaction codes like SM37 to monitor background jobs and check if there are any jobs that are stuck or consuming excessive resources. You may need to terminate or adjust these jobs.
  Increase System Resources: If possible, consider increasing the hardware resources (CPU, memory) allocated to the SAP system to better handle mass processing tasks.
  Database Optimization: Ensure that the database is optimized and that there are no locks or performance issues that could be affecting processing times.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes or patches that may address this specific error or improve system performance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM37 (Job Monitoring), ST22 (Dump Analysis), and SM21 (System Log) to diagnose issues further.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  SAP Documentation: Review the official SAP documentation for guidelines on mass changes and parallel processing configurations.
  
  If the problem persists after trying these solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.