Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
AP-MD-BP (Application Component) SAP Business Partner⤷
COM_CLEARING (Package) Clearing tool
Basic Data
| Data Element | COMT_CLEAR_HYPO_DECIDE |
| Short Description | Data Cleansing: Indicator 'Hypothesis Decision' |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| 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 | 5 | Hypo. |
| Medium | 15 | Hypoth. Decis. |
| Long | 20 | Hypothesis Decision |
| Heading | 12 | Hypothesis |
Documentation
Definition
Indicator Hypothesis Decision
If data cleansing takes place across system boundaries (Master Data Management), then you must be able to distinguish between various system types:
- Master System
Here you can decide if it really is a duplicate and which data record is to be kept. (Source / target decision when saving or doing a temporary save).
The indicator is to be set in a Master System. Other systems (if available) are notified of the decision. Other systems are not allowed to reach this decision.
- Client-System
Here you can create new cases, which have to be confirmed by the Master System. Only confirmed cases can be processed further in order to match locally-available dependent objects.
The indicator controls the data distribution as well as the possible status transfers of a cleansing case in the current system.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 620 |
