Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-MTD (Application Component) Metadata (Repository)⤷
RSD (Package) BW: Data Basis InfoObjects and Core Services
Basic Data
| Data Element | RSADIMDATCLS |
| Short Description | BW: Data class for aggregate dimension tables |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TABART | |
| Data Type | CHAR | Character String |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| Value Table | DDART |
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 | Data Type |
| Medium | 15 | Data Type |
| Long | 20 | Data Type |
| Heading | 6 | D.Type |
Documentation
Definition
You use the data class to define at logical level the physical area of the database (with ORACLE - TABLESPACE) in which your table is stored. If you choose correctly. your table will automatically be assigned to the correct area of the database when it is created.
The most important data classes (apart from system data) are:
- APPL0 Master data
- APPL1 Transaction data
- APPL2 Organization and Customizing data
Master data is often read but seldom updated. Transaction data is often updated. Organization and Customizing data is specified when the system is set up, but seldom changed therafter.
Customers also have the choice of data classes USR and USR1, which are both for customer-specific development. Tables assigned to these data classes are stored in a tablespace for customer development.
Note: Remember that the data class only influences how the tables are stored if you are using an ORACLE or an INFORMIX database system.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 30A |
