After deployment, verify that your data model aligns with the accelerator’s expectations. Ensure your Transactions Datamart includes at least the following fields:
|
Fields |
Data Type |
Description |
|
Unique Id |
String |
Unique identifier of the transaction. |
|
Product Id |
String |
Identifier of the product. |
|
Product Label |
String |
Human-readable product name or label shown in dashboards. |
|
Customer Id |
String |
Identifier of the customer; mandatory if Customer Master is deployed. |
|
Customer Label |
String |
Human-readable customer name or label shown in dashboards. |
|
Revenue |
Money/Number |
Total revenue amount for the transaction. |
|
Date |
Date |
The date used for grouping and filtering transactions (e.g., pricing date, billing date, valid from). |
|
List Price |
Money/Number |
Transaction list price. |
|
Profit |
Money/Number |
Transaction profit. |
|
Quantity |
Number |
Transaction quantity. |
|
Additional waterfall-related fields |
Money/Number |
Optional: Additional fields for waterfall analysis. |
|
Product Hierarchy |
String |
Optional: One or more fields representing hierarchical product groupings used for drill-down and aggregation. |
|
Product Attributes |
String |
Optional: Additional non-hierarchical product attributes available as filters and breakdown dimensions. |
|
Customer Hierarchy |
String |
Optional: One or more fields representing hierarchical customer groupings used for drill-down and aggregation. |
|
Customer Attributes |
String |
Optional: Additional non-hierarchical customer attributes available as filters and breakdown dimensions. |
|
Additional Attributes |
String |
Optional: Any other transactional attributes that you want to use for filtering, grouping, or slicing measures in dashboards. |