Product Hierarchy

Important to know before configuring:

• The ORDER of planning_levels matters — it defines the hierarchy drill-down path from broadest to most granular.
• Labels here must match app_config.appConfig.planningLevelOptions labels exactly.

Important to know before configuring:

• The code appends _wp to get the WP-version table and _other for other versions.
• If a new L0 value appears in the data but isn't mapped here, queries for that department will silently fail.
• This must include the target schema, not the source schema — update schema prefix when onboarding.
• This is also duplicated in item_groups_configurations.hierarchy_to_table_mapping and alert_groups_configurations_test.hierarchy_to_table_mapping.
• Schema prefix must be updated for new client
• Missing L0 values = silent query failures
• Duplicated in item_groups and alert_groups

Important to know before configuring:

• RUNTIME READS FROM alert_groups_configurations, NOT grid_configurations — app/alert_groups/config.py load_client_hierarchy_config() is the actual consumer. This grid_configurations row is the onboarding source of truth.
• table_resolver_level MUST be present in the hierarchy_levels array, otherwise query routing will fail silently.
• This same config is duplicated in item_groups_configurations and alert_groups_configurations_test — keep all three in sync.
• item_groups_configurations.client_hierarchy_config has NO runtime consumer either — only the alert_groups version is actively read.

Important to know before configuring:

• Adding a version here doesn't create the data — the KPI table must already have rows with that source_type.
• kpi_formula_json, reporting_formulas, and approval_hub_kpi_config may reference version-specific formulas that break if a version is removed.

Important to know before configuring:

• Previously classified as Tier A but actually client-specific because the KEYS are business labels (Department, Division, etc.) not physical columns.
• Must be kept in sync with planning_levels labels.

Important to know before configuring:

• This is NOT necessarily the same as client_hierarchy_config.table_resolver_level. table_resolver_level controls which L0 value routes to which physical table; highest_product_level is the highest level the grid can show without scanning all tables.
• NO RUNTIME CONSUMER — no app/ code reads this key. It exists as metadata for onboarding tooling.