You define business transactions in the following steps. A transaction in CRM is a business transaction, for
example, a sales order, service order, activity or opportunity.
The concept of business transactions is based on the fact that there is only one user interface for processing all
types of transaction documents. A business transaction can combine several business transaction categories, that is,
a sales transaction (sales order) can, for example, also contain business activity data and complaints items.
The Customizing settings for the transaction type specify processing of a business transaction, that is, the
characteristics. attributes and control attributes. A transaction type therefore controls processing of a specfic business
transaction.
One or several business transaction
categories (for example, sales, business activity, service) is assigned to a transaction type. The business transaction
category specifies the business context in which a transaction type can be used.
The user interface actually used in the CRM Online system is specified with the different screen areas and individual
field, via screen sequence control. You can either use the default profiles provided by SAP, or make the necessary
changes.
Note
In order that the transactions can be copied correctly from the CRM Online system into the OLTP R/3 system, the
setting for document processing and the business control must match in both systems. For sales transactions, for
example, this means that for the transaction type, there must be a corresponding sales document type of the same
name in the OLTP R/3 system. The same applies for the item categories, item category groups and item category
determination. Automatic matching does not occur via Middleware.
SAP provides standard settings for this.
Customer Relationship Management -> Basic Functions -> Partner Processing ->
-> Define Partner Functions
-> Define Access Sequences
-> Define Partner Determination Procedure
Customer Relationship Management -> Basic Functions -> Text Management ->
-> Set Texts
Customer Relationship Management -> Basic Functions -> Date Management ->
-> Define Date Types, Duration Types, and Date Rules
-> Define Date Profile
-> Assign Date Profile to an Activity Type
Customer Relationship Management -> Master Data -> Organizational Management -> Organizational Data
Determination -> Change Rules and Profiles ->
-> Maintain Organizational Data Profile
-> Assign Organizational Data Profile to Transaction Type
Customer Relationship Management -> Transactions -> Basic Settings -> Copying Control for Business
Transactions ->
-> Define Copying Control for Transaction Types
-> Define Copying Control for Item Categories
-> Define Item Category Determination for Copying
Customer Relationship Management -> Basic Functions -> SAP Business Workflow ->
-> Standard Settings for SAP Business Workflow
-> Execute Task-Specific Customizing
System status
User status
Various central SAP tables contain the following predefined data, which cannot be changed:
An initial table contains all statuses that can be assigned by the system (system status).
A third table (a) assigns one or more system statuses to each business transaction and (b) determines
whether the respective system is set or deleted for the business transaction.
A fourth table specifies which business transactions are permitted for which objects (for example, order
header, order item).
In combination, these assignments show you (a) the maximum system status possible for an object and (b) the
business transactions by which this status is either set or deleted.
Define Status Profile for User Status
In this activity, you create status profiles for your own (user) statuses. In a status profile, you can perform the
following activities:
Define user statuses and document their function. A status profile can contain one or more user statuses.
Determine the sequence in which the user statuses are run. This sequence is determined by the status
number. If you do not assign a status number to a user status, this status can always be set. Note, however,
that only one user status with a status number can be active at any one time. When you assign a status
number to a user number, you must also assign a highest and lowest status number. These numbers restrict
the status number range from which the user status can be selected.
Assign at least one object type to the status profile, by means of Object types.
The assignment of the object type determines if the status profile can be assigned to the transaction type
and/or the item category.
Example:
If you assign the object type "CRM order header" to the status profile for quotations, you can only assign this
status profile to transaction type header. If you assign the status profile for quotations the object type "CRM
Order Item", you can only assign the status profile to the item category. If you assign both object types to the
status profile for quotations, you can make the assignment to both the transaction type and item category.
You assign the status profile to the transaction type or item category in Customizing for business
transactions under Basic Settings -> Define Transaction Types, or Define Item Categories.
Define the initial status that is automatically activated when the object is created.
In the status profile, define a transaction to be executed when a given user status is reached, with the result
that one or more system statuses and/or user statuses can be set or deleted.
Activities
Define your user status for the applicable object types.
Return ->
Definition: status profile