Hierarchy

⤷

⤷

Basic Data
Data Element | CRMT_TOP_PROCESS_TYPE_CO |
Short Description | Leading Business Transaction Type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CRM_PROCESS_TYPE_CO | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
Value Table | CRMC_PR_TYP_CO |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Ldg BT Ty. |
Medium | 15 | Leadng BT Type |
Long | 26 | Leading BT Type |
Heading | 7 | L.BTTy. |
Documentation
Definition
Specifies the transaction type of the first business transaction in a CRM document flow.
Exception: A contract cannot determine the leading transaction type. When a business transaction refers to a contract, the leading transaction type is the transaction type of the first business transaction, which is downstream from the contract.
The leading transaction type is transferred to the ECC as additional information for each business transaction.
Use
The leading transaction type determines the controlling scenario for the first business transaction and all downstream business transactions. In other words, all controlling settings for this leading transaction type also apply to downstream business transactions with different transaction types. This ensures that consistent data is available and uniform controlling procedures are used for all logically-related business transactions.
Dependencies
To use the leading transaction type for downstream business transactions of all transaction types, you have to mask the CRM transaction type with '*'.
To perform amount allocation, you have to specify a leading transaction type.
Amount allocation is not available until after SAP CRM 4.0.For this reason this field is not taken into account for these releases.
Example
You want to use amount allocation for orders. To do so, you have to define a controlling scenario as follows:
- Enter the transaction type of the CRM order as the leading transaction type.
- Mask the CRM transaction type with '*'.
- Choose Single-object controlling as Controlling type and Transaction as Controlling level.
- Set the Extended Cost Analysis indicator.
As a result, this controlling scenario is used automatically for each confirmation created for an order and the confirmation-related costs are saved in ECC. It is also used for the subsequent billing request, which ensures that the detailed revenues are saved in ECC. This, in turn, ensures that all the data required for the amount allocation is available in the system.
History
Last changed by/on | SAP | 20031111 |
SAP Release Created in | 2003_1_470 |