Hierarchy

⤷

⤷

Basic Data
Data Element | CMPC_MULT_CAMPAIGN |
Short Description | Multiple Campaigns/Trade Promotions Active Indicator |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CMPGN_MULT_CAMPAIGN | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
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 | Mult. Pr. |
Medium | 19 | Multiple Promotions |
Long | 20 | Multiple Promotions |
Heading | 19 | Multiple Promotions |
Documentation
Definition
Indicates whether one or several campaigns are to be determined.
Use
This indicator must be set if you want to assign several campaigns/ trade promotions.
The following values are possible:
- 'Blank character' (not active)
The assignment of multiple campaigns/trade promotions is not supported. A maximum of one campaign will be determined.
- 'A' (compatible with CRM (sorting by access sequence))
The assignment of multiple campaigns/trade promotions is supported.
The system is able to determine multiple campaigns/trade promotions. You use this value in a CRM Enterprise/SAP ECC scenario, that is, without Mobile Sales. The campaigns/trade promotions that are determined are sorted according to the access sequence, making them only compatible with CRM Enterprise.
- 'B' (compatible with CRM and CRM Mobile (simple sorting))
The assignment of multiple campaigns/trade promotions is supported and is compatible with both CRM Enterprise and Mobile Sales. The system is able to determine multiple campaigns/trade promotions. In addition, the system behaves in a way that is compatible with Mobile Sales: when determining the sequence of the campaigns/trade promotions, the sequence in the campaign determination procedure is not taken into account.
Dependencies
Example
History
Last changed by/on | SAP | 20060208 |
SAP Release Created in | 600 |