SAP ABAP Data Element KKA_MAXANZ (Maximum Message Type for Objects)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-CIC (Application Component) Interaction Center WinClient
⤷
KKAG (Package) Period costing individual case
⤷
⤷
Basic Data
| Data Element | KKA_MAXANZ |
| Short Description | Maximum Message Type for Objects |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | MMT/object |
| Medium | 15 | MMT/objects |
| Long | 36 | Maximum message type for objects |
| Heading | 1 | M |
Documentation
Definition
If this indicator is set, the maximum message type will be determined and displayed for each order.
Use
Exceptions are set in accordance with the maximum message type:
- If the maximum message type of the order is W, E, or A, a yellow exception is set.
- If the maximum message type of the order is I, a green exception is set.
If no work in process could be calculated due to an error, a red exception will be set regardless of how you set this indicator.
Determining the maximum message type for each order increases the runtime of WIP calculation.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19990310 |
| SAP Release Created in |