Académique Documents
Professionnel Documents
Culture Documents
Components
Actions can be determined for the whole transaction (Transaction Type) at header level
and also for an individual item (Item Category)
At execution time, these processes get scheduled based on user defined conditions which
define particular situation in the transaction processing.
An Action is a planned activity, or task and schedule condition is the situation under
which this action is to be executed.
Based on configuration and implementation for the Action Definitions and respective
conditions (Schedule Condition and Start Condition), these actions execute for the
corresponding SAP CRM transaction.
For a transaction that supports actions, action log can be analyzed in GUI using
transaction CRMD_ORDER, or within Web UI if access is provided to the corresponding
assignment block.
You can display a list of actions scheduled and executed for the transaction with
following information for individual action as in Fig. 3 and 4:
o Status (action scheduled, action processed)
o Description (purpose of action)
o Processing Type
o Creator, creation date
Example: A month before a contract expires, the responsible sales employee receives an
activity with the category 'e-mail' in his inbox to remind him to write to the customer and
find out whether they wish to renew their contract.
Conditions
These conditions for an action are defined while configuring it in t-code SPPFCADM.
Processing Times defines when an action for which start condition has been satisfied
will be executed in the transaction processing. Thus, once the start condition for a
scheduled action is satisfied, it can execute according to the Processing Time
maintained. Following are the possible options for Processing Time:
Immediate Processing:
Smart Forms
WorkFlow
Methods
Actions are configured for CRM transaction using Action profile. Actions are created in action
profile which can be assigned to different CRM transactions. Within an action profile, multiple
actions can be defined with sort order and status (Active or Inactive). Active actions can be
scheduled and scheduled actions are executed following the sort order as maintained in the
customizing. For individual action in the Action Profile, Action Definition and Action
Configuration can be maintained.
During the transaction processing, all the allowed actions are identified using the Action Profile.
For this, actions not marked as inactive in the action profile are considered for execution. Sort
order maintained in Action Profile for individual action used to identify the sequence of
execution of the actions. Further processing of these actions is done based upon the Action
Definition and Action Configuration of individual action identified.
It is possible to assign an action profile directly to a transaction type or item category. Also
condition technique, i.e. Action Profile Determination can be defined same as pricing.
In SPRO goto "Define Action Profiles and Actions"
1. Select an action profile
2. Click View