Hierarchy
BI_CONT (Software Component) Business Intelligence Content⤷
BW-BCT-PLA-RAP (Application Component) Retail Assortment Planning⤷
RS_BCT_RETAIL_MAP (Package) BW: Content MAP
IMG Activity
| ID | BW_BCT_RT_EM02 | Define Event Dimension |
| Transaction Code | S_B72_29000004 | (empty) |
| Created on | 20050315 | |
| Customizing Attributes | BW_BCT_RT_EM02 | Define Event Dimension |
| Customizing Activity | BW_BCT_RT_EM02 | Define Event Dimension |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | /MAP/E_IMG_02 |
Use
In this IMG activity, you define the dimensions that can be assigned to an event. The implementation of an event dimension takes place using two classes:
- A class for the database access, text determination and value verification
- A class for the management of event assignments during runtime
Requirements
The creation of an entry for a new event dimension requires the creation of the two aforementioned classes.
Standard settings
SAP delivers the following event dimensions:
Product dimensions
- 0CM_CDT1 (dimension "Category"), corresponds to info object 0CM_CDT1
- 0CM_CDT2 (dimension "Subcategory"), corresponds to info object 0CM_CDT2
- 0CM_CDT3 (dimension "Segment"), corresponds to info object 0CM_CDT3
Location dimensions
- 0COUNTRY (dimension "Land"), corresponds to info object 0COUNTRY
- 0REGION (dimension "Region"), corresponds to info object 0REGION
- 0PLANT_SHOP (dimension "Shop"), corresponds to info object 0PLANT with the attribute value 0RF_STORETY = '2'
- 0PLANT_STORE (dimension "Store"), corresponds to info object 0PLANT with the attribute value 0RF_STORETY = space
- 0PLANT_DSTORE (dimension "Department Store"), corresponds to info object 0PLANT with the attribute value 0RF_STORETY = '1'
You can use this event dimension productively.
Activities
Example
If you want a 1:1 relationship between event dimension and info object, you have to take the following into account:
- Copy the class /MAP/CL_EVT_EVASSIGN_DEFAULT (Management of event assignments during runtime) to a new class "A"
- Copy the class /MAP/CL_EVT_DB_TEMPLATE (database access, text determination and value verification) "B"
- Create a new data store object for storing the dimension assignments for event occurrences.
You can use the data store object 0RME_DS03 ("Regions for event occurrences") as a template. In this case, you replace the key fields 0REGION and 0COUNTRY with the relevant info object. Bear in mind that, in the case of compound info objects, you should also copy those info objects that are compounded to the key.
- In the newly created class "B", change the attributes:
- C_IOBJNM to the relevant info object
- C_ODSO to the relevant data store object
If you want to implement special logic for the master data check in the new dimension, modify the following methods of the new class "B":
- MD_CHECK()
- TEXT_GET()
You can use the class /MAP/CL_EVT_DB_STORE as a template. In this template, only plants with the attribute store category (0RF_STORETY = "SPACE") are regarded as permitted values.
Business Attributes
| ASAP Roadmap ID | 105 | Define functions and processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| /MAP/E_V_EVDIM | V - View | SM30 |
History
| Last changed by/on | SAP | 20050315 |
| SAP Release Created in | 702 |
