Ansicht
Dokumentation

CRMC_MKTPL_ACT_DEF - Define Action Profiles and Actions

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

All maximal allowed actions are defined for an object type. You also specify general conditions in the action profile for the actions contained in the profile, for example:

• The time period at which the system starts the action (for example, when saving the document)

• The way in which the system executes the action (workflow, method call or Smart Forms)

In this activity, you create an action profile and templates for actions.

In Marketing, note that you should only choose date profiles with suitable date rules and without date types or durations.

For the action profile, the class that provides the attributes for your business object must be entered. These business objects can be used for planning actions.

When you create an action profile, note the object type for which you can use this action profile. You must assign the relevant business object type to the action profile. The assignment of the business object type ensures that the attributes for the relevant object type (for example, marketing campaign) can be used for defining and processing the conditions. If, for example, you wish to make the action dependent on the planning customer for the object, the profile must be assigned to a business object type containing the attribute planning customer. Only one business object can be assigned for each action profile.

You also define here whether an action is to be partner-dependent.

You can enter several processing types for one action definition. Under processing, choose:

• Method call
  If the action consists of one single step, for example, create campaign element from campaign attributes.
  During the method call, processing is carried out via Business-Add-Ins (BAdIs). Standard methods (BAdIs) are available.
  When creating your own BAdI implementations, make sure that the method 'get_ref_object' is always called from the class 'CL_ACTION_EXECUTE' and the method 'register_for_save' always at the end. You can use the implementation 'CREATE_CPT_FROM_CPG' as a template.

• Workflow
  If the action consists of a process with several steps, for example, a subsequent document with approval procedure.
  

• Smart Forms
  for issuing documents via fax, printing or e-mail

Standard Settings

SAP delivers the following standard action profiles:

• Common profile for object class CP (campaigns and campaign elements)
  Contains the following action definitions:
  
  - PRINT_PREVIEW_CP: Print Preview
  - SEND_BY_MAIL_CP: Send PDF of object by e-mail

• Common profile for object class TP (trade promotions and trade promotion elements)
  Contains the following action definitions:
  
  - PRINT_PREVIEW_TP: Print Preview
  - SEND_BY_MAIL_TP: Send PDF of object by e-mail

• For object type CPG (marketing campaign)
  Contains the action definitions from the common profile for object class CP (CRM_MKTPL_CP)
  

• For object type CPT (marketing campaign element)
  Contains the action definitions from the common profile for object class CP (CRM_MKTPL_CP)

• For object type TPM (trade promotion)
  Contains the action definitions from the common profile for object class TP (CRM_MKTPL_TP)

• For object type TPT (trade promotion element)
  Contains the action definitions from the common profile for object class TP (CRM_MKTPL_TP)

We recommend that you do not change the delivered profiles, but copy and adapt them if necessary.

Recommendation

If you create your own action profiles and action definitions, these should begin with Y or Z, because the name range is not overwritten for an SAP import.

Activities

To create an action profile with action templates, proceed as follows:

1. Choose New Entries in the Change Action Profile view and enter a name and description for the action profile.
   
   Assign the context class CL_CRM_MKTPL_OBJ_CONTEXT_PPF in the field Context Class.
   
   If necessary, assign a business transaction type (business object type) to the action profile. To assign a business transaction type, choose the relevant business transaction type with the input help in the Category BO - BOR object type and Object Type fields.
2. Go into the Action Definition screen and choose New Entries.
   The screen for defining actions appears.
3. Enter a name and description for the action.
4. Specify the default values for the action. Consider the following:
   Processing time period:
   - Immediate processing - the action is started as soon as the start condition is fulfilled.
   - Processing when saving document - the action is started directly after the update.
   - Processing using selection report- the action is started by a report after expiration and evaluation. After selecting using the report, the system first checks whether a start condition is available. If no start condition is available, or the condition is correct, the action is started.
   
   If you select the partner-dependent field, you can define a partner function or partner function category for which the action is valid. For example, you can use partner function categories if you want a reminder e-mail to be sent to all business partners that are involved in the transaction and assigned to the specific partner function category. You can use partner functions to trigger an action for a specific partner function, for example, to send a reminder e-mail to the employee responsible for the transaction. You can, however, also define the action partner-dependently via the conditions.
   
   Select the field Changeable in Dialog if you want the user to change the condition and processing parameter for the action in the Marketing Planner.
   
   Select the field Executable in Dialog if you want the user to be able to trigger the action manually on the Actionstab page.
   
   Select the field Display in Toolbox if you want the action to be displayed as a symbol in the generic Object Services toolbar, and the user to be able to plan it from here.
   
   In the Determination Technique field, choose Determination using conditions that can be transported.
   
   In the field Action Merging, choose:
   
   - a maximum of one action for each action definition if the action is to be executed exactly once
   - a maximum of one unprocessed action for each action definition if you want to be able to call up the action several times
5. Go to the Processing Types screen to set how (with which technique) the action is executed.
6. Choose New Entriesand choose a processing type (workflow, method call or Smart Forms). If you wish to define several processing types, you can choose a standard one by setting the default indicator.
7. Select the processing type and choose Set Processing.
   
   - For processing with method call:
   Select a method (Business-Add-In) in the Filter Value field.
   If you choose Display Implementation, you can display the coding for the selected method. If you choose Create New Implementation, you can define your own methods (BAdI).
   Define the processing parameters (container) and maintain the standard values.
   
   - For processing with workflow.
   Enter a workflow dummy.
   
   - For processing with Smart Forms:
   Choose print, fax or e-mail and enter a form name, a processing class and a processing method.
   
   If you want the creator of a campaign to receive an e-mail if his campaign is changed, use Smart Form CRM_MKTPL_DEFAULT_CONSUMER. This Smart Form is delivered with the standard configuration.
8. Repeat the steps as of 2 for each action template you wish to define.
   

Further Notes

If you wish to specify multiple output for the same object type, you must define them in the same action profile.

You can find information about the BAdI implementation in the SAP Library under mySAP Technology Components → ABAP Workbench → BC - ABAP Workbench: Tools → Other Concepts → Business Add-Ins

You can find information about the SAP Business Workflow in the SAP Library under mySAP Technology Components → Business Management (BC-BMT) → WebFlow Engine (BC-BMT-WFM)

ABAP Short Reference   General Data in Customer Master  
This documentation is copyright by SAP AG.

Length: 10133 Date: 20240523 Time: 182144     sap01-206 ( 156 ms )