Publish segmentation results

TABLE OF CONTENTS

• Overview
• Key capabilities
• Configuration setup (Prerequisite) 
  • The purpose of maintaining separate segmentation attributes.
• How to publish segmentation results
• Hierarchy publishing logic
• Overwriting behavior

Overview

The Segmentation Publish feature allows planners to publish segmentation results (e.g., ABC/XYZ classifications) directly to a selected entity, such as Product, Product–Customer, or Product–Location.

This ensures segmentation outputs are stored as attributes within the corresponding entities, making them reusable across planning views, filters, and analytics.

Key capabilities

• Allows planners to publish segmentation results to specific entities configured in the Admin App.
• Supports publishing to different hierarchy levels depending on the segmentation creation level.
• Enables the use of published segmentation attributes in filters, forecasts, and planning views.
• Automatically overwrites older segmentation results upon new publish.

Configuration setup (Prerequisite) 

Before segmentation results can be published, the implementer must configure standard internal attributes in the Admin App → Data Mappings. 

The application currently supports three internal group attributes for publishing segmentation results. These attributes capture ABC and XYZ analysis separately.

Available internal attributes

The purpose of maintaining separate segmentation attributes.

The purpose of maintaining separate segmentation attribute groups (such as Segmentation_1, Segmentation_2, and Segmentation_3) is to provide greater flexibility in storing, managing, and publishing different types of segmentation analyses within the system.

Each segmentation group — for example, Segmentation_1, Segmentation_2, and Segmentation_3 — acts as a logical container that combines both ABC Segmentation and XYZ Segmentation attributes for a specific analysis stream. 

• For instance, Segmentation_1 includes ABC Segmentation_1 and XYZ Segmentation_1, which may represent one analytical perspective, such as Demand Segmentation. While Segmentation_2 and Segmentation_3 can be used for other perspectives, such as Inventory Segmentation or Revenue Segmentation

.

This structure allows you to perform and manage multiple segmentation analyses independently within the same entity (e.g., product, customer, or product–location) without overwriting each other’s results. 

Maintaining separate attributes to capture ABC and XYZ analysis helps planners distinguish between different business objectives — for example, demand-based classification (A/B/C) versus volatility-based classification (X/Y/Z) — and enables cleaner configuration, publication, and reporting in the Business App.

In essence, maintaining these groups ensures data separation, contextual clarity, and scalability — empowering you to run multiple segmentation models in parallel and publish their results independently while keeping the overall data model consistent and organized.

Below is a sample setup of how an Implementer configured for a Tenant

The following is the display names configured in the admin app by the implementer for Segmentation groups.

The following is the display names configured in the admin app by the implementer for the respective segmentation attributes in different entities.

Each group (e.g., Segmentation_1) includes both ABC and XYZ attributes. Hence, there are two attributes to capture ABC and XYZ details. 

Note: These internal attributes are system-defined and do not depend on external data loads.

How to publish segmentation results

Step 1: Open segmentation results

In the Segmentation Results screen, review the segmentation output generated for your selected dataset.

Step 2: Click “Publish”

Clicking the Publish button opens a pop-up that shows the available entity for which the segmentation results can be published. If multiple groups are configured within an entity, the pop-up displays all available groups, and you can select only one group.

Step 3: Notice the target entity

Confirm the entity where segmentation results should be published — for example:

• Product Master
• Product–Customer Master
• Product–Source Master

Step 4: Select the segmentation group

Based on the Entity selected, the application displays the configured Segmentation Group (e.g., Demand Analysis, Inventory Analysis) in the pop-up. 

Note: During implementation, the Implementer can provide a display name for each of these Segmentation groups. 

Example 1, if you want to publish the demand segmentation results generated at Product : All: All: All for sales history to the Product Master.  Then, the implementer should have already configured the segmentation group attributes in Product Master and named it accordingly.

In the above example : The attribute names can be ABC Demand Analysis and XYZ Demand Analysis. The implementer can name this group as Demand Analysis.

Example 2: Similarly, if you want to publish the inventory segmenation results generated at Product : All: Location : All for Purchase orders to the Product Location Master. Then the Implementer can configure one additional group called Inventory Analysis and introduce two attributes, say, ABC Inventory Analysis and XYZ Inventory Analysis in the Product location Master.

Step 5: Confirm publish

Click Publish to proceed.

 A success message appears: “Segmentation results published successfully.”

Hierarchy publishing logic

The available publishing options depend on the level at which segmentation was created.

The available publishing options depends on the hierarchy level at which the segmentation is created and on the Entity in which it is configured. For example, if the segmentation attributes are configured in only the product master and the Product location master, then the publish option should be available only for these two entities.

Let's consider the following examples. The left column indicates the level at which the segmentation results are generated. The right column indicates the possible entity in which the segmentation results can be published.

When a segmentation is published, results automatically cascade to all relevant combinations under that hierarchy (for example, all Product–Customer records within a region).

Scenario:

A planner runs segmentation at the Family–Region–All–All level, for which the ABC and XYZ classifications are also generated at the same level.

Once the planner opens the Segmentation Results screen and clicks Publish.

The application shows Product–Customer Master as the eligible entity. Let's assume the implementer has enabled Demand Analysis (Segmentation_2 group) for this entity.

Upon confirmation, the segmentation results (e.g., AX, BY, CZ) are saved in the Product–Customer Master under the ABC Demand Analysis and XYZ Demand Analysis attributes.

These attributes can now be used to filter data or analyze demand patterns within the Business App.

Overwriting behavior

When a new segmentation is published to an entity that already contains segmentation results, the previous values are overwritten.

Example:

Suppose segmentation results are published to Product Master, and later a new segmentation is generated and published again to the same entity. In that case, the latest results will replace the existing segmentation data.