How To Fix CRM_MKTTGGRP_EXP720 - All target groups processed in a previous run

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_MKTTGGRP_EXP - CRM Marketing: Messages for Target Group Selection

• Message number: 720

• Message text: All target groups processed in a previous run

What causes this issue?

Background processing was stopped because all the business partners in
the target group(s)(or the active target group(s) belonging to the
relevant marketing segments) have already been contacted in a previous
run.
If the job has been started again manually from the Marketing Planner
because one of the attached target groups (or one of the profiles or
profile sets attached to the target groups) was inactive in an earlier
campaign export ('Job incorrect') and not at least one of these
inactive target groups is now active, processing will be terminated.
If there is periodic execution, the execution is also terminated. In
the first job schedule, all active target groups are processed.
However, there were also inactive target groups assigned to the
campaign. Before further processing of those active target groups
already transferred can take place, the inactive target groups must be
activated or their assignment to the campaign deleted.

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?

Starting manually from the Marketing Planner:
Set the inactive target groups to active. These target groups are then
copied over in the next campaign export and are processed. Target
groups that are already exported are not copied over again.
The inactive target groups that should not be copied over again can be
deleted in the Marketing Planner (direct assignment of a target group)
or in the Segment Builder (assignment of a target group via profile
set)
Periodic execution of campaigns:
Set the inactive target groups to active. These target groups are then
copied over in the next periodic execution of the campaign export and
are processed. The target groups that are already copied over are not
taken into consideration for this run.
After processing of all target groups that are now active, all target
groups assigned to the campaign are processed again in the next
periodic run.

Procedure for System Administrators

Use
In this step you set the parameters for parallel processing of a
campaign. You have to enter a server group from which the dialog work
processes for parallel execution can be accessed and also enter the
number of dialog work processes via which processing will later take
place. You can only activate one setting for each communication medium.
This is then used for parallel execution. <ZH>Parallel processing must
be defined per communication medium</>. If campaign execution is
started with a communication medium not entered in this transaction,
then no parallel processing can be carried out. Therefore the system
resources must be assigned to the relevant medium (CIC, E-Mail, and so
on). The use of server groups has the advantage that the system uses
the current workload as a basis when selecting the instance to be used.
When deducing an RFC with a server group entry, the instance is only
determined at the point of execution at which a dialog work process is
used for execution. All instances belonging to a group are taken into
consideration.
As a result of the dynamic load distribution of the implemented
workload you will find that some of the system component utilizations
described under 'Determine the number of dialog work processes' (such
as the main memory utilization) will occur much less often. Another
advantage of this method is that the next package to be processed is
automatically sent to the job which up until this point has had the
least work. Using measurements a package size of 100 business partners
is set for parallel processing.
<ZH>Note the guidelines for configuration and maintenance of the system
in note 524647. These guidelines are important for achieving long-term
high-performing parallel processing.</>
<ZU>Background:</>
1. Determining the number of dialog work processes:
By using a greater number of parallel processes, the throughput can be
reduced. This may be because of locking conflicts (ENQUEUEs or database
locks) or overloading of system components (CPU, main memory, ENQUEUE
server overload, database IO). The system overload in intensive
parallel processing is therefore higher than in normal, serial
execution. If the capacity limit of one of the above system components
is reached, this restricts the throughput of the whole process. If you
start further processes, there will even be a reduction in throughput.
Defining the exact process number is project-specific and depends on
available system resources. No general rule applies here. But it is
urgently recommended that you determine the exact setting as part of a
stress test.
At the beginning of parallel execution, the required server group is
initialized and the dialog work processes currently available are
determined. If the number of dialog work processes currently available
on the server group is smaller than that entered by the user, this
number available is used as a guide value for execution. Otherwise the
number entered by the user is used.
2. Entering a server group
You can define a server group with instance assignment and temporarily
define the limit values for the load situation of the instance using
transaction RZ12. The F1 help gives more details on the individual
parameters.
When you enter the server group, you should pay attention to
capitalization. To avoid errors, you should use the input help.
<ZH>Note for defining a server group</>: Nearly all parameters in RZ12
are given in percentages. The execptions are: parameters for generally
switching on and off limit values; parameters for defining the minimum
no. of free dialog processes and parameters for the maximum waiting
time after a load check in the system. For each instance there is also
only one valid parameter per record. You cannot define different values
for an instance in different server groups.
Practise has shown that it is better to set the parameter for the
minimum of free dialog processes at >= 3 zu and then to offer more
dialog work processes via the server group than can actually be used at
the same time. This then miminizes overloading and problems with
resources.
Requirements
Standard settings
Activities
Example

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_MKTTGGRP_EXP720 - All target groups processed in a previous run ?

  The SAP error message CRM_MKTTGGRP_EXP720 indicates that all target groups have already been processed in a previous run. This typically occurs in the context of marketing campaigns or target group processing within the SAP Customer Relationship Management (CRM) module.
  Cause:
  
  Previous Execution: The error usually arises when a job or process that is supposed to create or update target groups has already been executed successfully, and there are no new target groups to process in the current run.
  No Changes: If there have been no changes to the underlying data or criteria for the target groups since the last execution, the system recognizes that there is nothing new to process.
  Job Scheduling: If the job is scheduled to run at regular intervals, it may be running too frequently without any new data to process.
  
  Solution:
  
  Check Previous Runs: Review the logs or history of previous runs to confirm that the target groups were indeed processed. This can help you understand if the error is valid or if there is an issue with the job scheduling.
  Modify Selection Criteria: If you need to process the target groups again, consider modifying the selection criteria or the underlying data to ensure that there are new records to process.
  Manual Execution: If necessary, you can manually trigger the processing of target groups to see if any changes have occurred since the last run.
  Job Scheduling Adjustment: If the job is scheduled too frequently, consider adjusting the schedule to allow for more time between runs, ensuring that there is new data to process.
  Consult Documentation: Refer to SAP documentation or notes related to the specific transaction or process you are working with for any additional insights or troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CRMD_ORDER, CRMD_ORDERADM_H, or others related to marketing and target group management.
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional context on target group processing.
  Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support or your internal SAP team for further assistance.
  
  By following these steps, you should be able to address the error message and ensure that your target group processing runs smoothly.