Hierarchy
BI_CONT (Software Component) Business Intelligence Content⤷
BW-BCT-PLA-RMP (Application Component) Retail Merchandise Planning⤷
/MAP/E (Package) BW: Content MAP Events, DB- and Application Layer
Basic Data
| Data Element | /MAP/E_Y_PRODMODE |
| Short Description | MAP: Relationship Type of Product Dimensions |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | /MAP/E_DO_PRODMODE | |
| 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 | RelProdDim |
| Medium | 15 | Rel.Prod.Dim. |
| Long | 20 | Relationship ProdDim |
| Heading | 20 | Relationship ProdDim |
Documentation
Definition
Relationship type of the product dimensions of events.
Use
If several product dimensions are assigned to an event, you must define how these dimensions define the validity of an event occurrence.
There are three relationship types:
- An event occurrence is valid for a characteristic combination if an assignment of the relevant characteristic value for the event occurrence exists for every product dimension ('Dim1 AND Dim2 AND Dim3').
- An event occurrence is valid for a characteristic combination if an assignment of the relevant characteristic value for the event occurrence exists for at least one product dimension ('Dim1 OR Dim2 OR Dim3').
- Exclusively for the assignment of three product dimensions:
An event occurrence is valid for a characteristic combination, if:
- An assignment of the relevant characteristic value for the event occurrence exists for product dimension 1
- AND an assignment of the relevant characteristic value for the event occurrence exists ('Dim1 AND (Dim2 OR Dim3)') for product dimensions 2 OR 3.
In the case of relationship types 1 or 2, the logical formula is abbreviated accordingly for missing product dimensions. Relationship type 3 is only permitted for exactly three product dimensions.
Dependencies
The relationship type comes into effect for the following:
- Event processing:
Exactly three event occurrences are imported that are relevant for the selection executed. This relationship type controls the relevance.
- Influencing factor of the category "Event":
The relationship type controls the quantity of the event occurrences that match the selection. In addition, it has an effect on the calculation of the value of this influencing factor (because various event occurrences are processed for a characteristic combination, depending on the relationship type).
Example
The following example provides further clarification:
- The product dimensions "Category" (dimension 1), "Subcategory" (dimension 2), and "Segment" (dimension 3) are assigned to event XYZ.
- The event occurrence 001 exists for this event. The following product dimension values are assigned to the event occurrence:
- Category: A, B
- Subcategory: AA, AB
- Segment: ABA, BAA
- You want to check if the event occurrence is relevant for the following characteristic combinations:
- Combination K1: Category A, subcategory, AA, segment AAB
- Combination K2: Category A, subcategory AB, segment ABA
- Combination K3: Category B, subcategory BA, segment BAA
- Relationship type 1:
- Occurrence 001 is not relevant for combination K1, because the segment assignment AAB does not exist.
- Occurrence 001 is relevant for combination K2, because category assignment A, subcategory assignment AA, and segment assignment ABA exist.
- Occurrence 001 is not relevant for combination K3, because the subcategory assignment BA does not exist.
- Relationship type 2:
- Occurrence 001 is relevant for combination K1, because the category assignment A (and the subcategory assignment AA) exists.
- Occurrence 001 is relevant for combination K2, because the category assignment A (and the subcategory assignment AA and the segment assignment ABA) exists.
- Occurrence 001 is relevant for combination K2, because the cateogry assignment B (and the segement assignment BAA) exists.
- Relationship type 3:
- Occurrence 001 is relevant for combination K1, because the category assignment A and the subcategory assignment AA exist. The missing segment assignment AAB does not come into effect.
- Occurrence 001 is relevant for combination K2, because the category assignment A and the subcategory assignment AA (and the segment assignment ABA) exist.
- Occurrence 001 is relevant for combination K2, because the category assignment B and the segment assignment BAA exist. The missing subcategory assignment BA does not come into effect.
History
| Last changed by/on | SAP | 20141031 |
| SAP Release Created in | 702 |
