How To Fix CRM_MKTPL_MASS070 - Modificación en masa cancelada, ningún recurso p.tratamiento paralelo

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: Modificación en masa cancelada, ningún recurso p.tratamiento paralelo

¿Qué causa este problema?

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.

El sistema emite un mensaje de error y no le permitirá continuar con esta transacción hasta que se resuelva el error.

Respuesta del sistema

Processing of your Mass Change activity was aborted.

¿Cómo arreglar este 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.

Procedimiento para Administradoras de Sistemas

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.

Extracto de mensaje de error del sistema SAP. Copyright SAP SE.