Module 3: BW/4HANA Data Modeling Basics
This module introduces the foundation of BW/4HANA data modeling — InfoObjects.
Even though BW/4HANA simplifies many classic concepts, InfoObjects remain the semantic backbone of enterprise data models.
A strong understanding of InfoObjects is essential for:
- Clean, reusable models
- Consistent reporting
- Performance and governance
- Interview success
1. What are InfoObjects?
InfoObjects are reusable metadata objects used to describe:
- Business entities (Characteristics)
- Measures (Key Figures)
- Time, units, and currencies
They ensure:
- Semantic consistency
- Central governance
- Reusability across models
InfoObjects define meaning, not storage.
2. Types of InfoObjects
2.1 Characteristics
Characteristics represent descriptive business entities.
Examples:
- Customer
- Material
- Company Code
- Fiscal Year
Key Properties of Characteristics
- Can have attributes
- Can have texts
- Can be time-dependent
- Can be used for navigation and filtering
Example: ZCUSTOMER
Create characteristics only for stable business dimensions.
2.2 Key Figures
Key figures represent measurable values.
Examples:
- Revenue
- Quantity
- Cost
- Margin
Types of Key Figures
| Type | Description |
|---|---|
| Amount | Currency-based |
| Quantity | Unit-based |
| Number | Unit-less |
Most calculations are pushed to HANA or BW Queries, not InfoObjects.
2.3 Time Characteristics
Why Time Characteristics Matter
Time characteristics enable:
- Time-based analysis
- Period comparisons
- Trend reporting
Standard Time Characteristics
| Characteristic | Description |
|---|---|
| 0CALDAY | Calendar Day |
| 0CALMONTH | Calendar Month |
| 0FISCYEAR | Fiscal Year |
| 0FISCPER | Fiscal Period |
Time-Dependent Data
- Attributes and texts can change over time
- BW automatically handles validity periods
Use standard SAP time InfoObjects wherever possible.
2.4 Units & Currencies
Why Units & Currencies are Special
Units and currencies:
- Control aggregation behavior
- Ensure correct calculations
- Prevent data inconsistencies
Currency InfoObjects
Examples:
- 0CURRENCY
- 0LOC_CURR
Unit InfoObjects
Examples:
- 0UNIT
- 0BASE_UOM
Key Figure Association
Key figures must reference:
- A currency InfoObject (for amounts)
- A unit InfoObject (for quantities)
Hardcoding units or currencies leads to incorrect aggregation.
3. Attributes & Texts
Attributes
Attributes provide additional information about a characteristic.
Example:
- Customer → Country, Region, Customer Group
Attribute Types
| Type | Description |
|---|---|
| Display | For reporting |
| Navigational | Can be used like characteristics |
Use navigational attributes sparingly.
Texts
Texts provide human-readable descriptions.
Types:
- Short
- Medium
- Long
Time-Dependent Attributes & Texts
- Valid-from / valid-to dates
- Enables historical reporting
Critical for audit and historical accuracy.
4. InfoObject Catalogs
What are InfoObject Catalogs?
Catalogs group InfoObjects logically.
Examples:
- ZCUST_CHAR (Characteristics)
- ZFIN_KF (Key Figures)
Purpose of Catalogs
- Organizational clarity
- Security separation
- Transport management
Use business-domain-based catalogs, not technical ones.
5. Reusability Concepts (Very Important)
Why Reusability Matters
Reusability ensures:
- Consistent reporting
- Lower maintenance
- Faster development
Reusability Strategies
- Create global InfoObjects
- Avoid local-only characteristics
- Reuse master data wherever possible
- Centralize semantics
Bad Modeling Example
- Creating same characteristic multiple times
- Duplicating master data per model
- Hardcoding logic in transformations
6. InfoObjects in BW/4HANA vs Classic BW
| Aspect | Classic BW | BW/4HANA |
|---|---|---|
| Importance | High | Still high |
| Calculations | Often in InfoObjects | Prefer pushdown/query |
| Redundancy | Common | Avoided |
| Reuse | Limited | Strongly encouraged |
BW/4HANA focuses on semantic reuse + HANA pushdown.
7. Interview-Grade Questions
Q1. Are InfoObjects still relevant in BW/4HANA?
Answer:
Yes. InfoObjects remain the semantic foundation of BW/4HANA, enabling reuse, consistency, and governed modeling, even though data persistence and calculations are reduced.
Q2. When should you create a new characteristic?
Answer:
Only when a new, stable business entity is required and cannot be represented using existing standard InfoObjects.
8. Summary
- InfoObjects define business semantics
- Characteristics and key figures are core types
- Time, units, and currencies are critical
- Attributes and texts enrich master data
- Catalogs organize objects
- Reusability is mandatory in BW/4HANA
9. What’s Next?
➡️ Module 4: DataStore Objects (aDSO) in BW/4HANA
If InfoObjects are designed poorly, no architecture can save the model.