Skip to main content

Symon.AI help center

Order consolidation

What if your order data contains records with parts you cannot sell together in the same configuration? What if you cannot detect these parts because you don't have a consolidated view of each order?

Catch errors earlier by validating orders and preventing invalid data from propagating further through your organizational workflow. This saves workers from cost-intensive manual reviews later.

In this pipe, we aim to consolidate orders to help you see all related orders in a single view, and validate them for missing information, mismatching information and invalid combinations.

The required (starting) data sets for this blueprint is Order Consolidation - Orders, a data set that you want to consolidate and validate. Additionally, you need a Order Consolidation - Valid Orders table to match against the Order Consolidation - Orders.

This use case walks through the consolidation of your orders and how to fix the three following issues before you can use it in Incentives:

  1. Inconsistent data

  2. Missing values

  3. Currency mismatches

Workflow

In this section of the pipe, we're looking to consolidate orders and validate them for missing information, mismatches and invalid part combinations.

The Order Consolidation - Orders data set is initially set up where there are multiple rows for each order.

Order consolidation

We use the Data Part Filter (Filter) Ind Part Filer (Filter) Plat Part Filter (Filter) Source Part Filter (Filter) tools to pull each part type that comprises an order. Then we use Join tools to get each order depicted as a single row, Single Row Orders (Join)

Note

One of our orders is missing a component. We don't want to drop this column, so we carefully use a right join for one of the Join tools Right Join (Join).

Order validation

Next, we do our first data validation where we apply Symon.AI case tool Find Inconsistencies (Case) to check for inconsistencies. For example, we want to check for empty fields and mismatching currencies.

Then, we want to ensure that the order represents a valid configuration by matching our orders to a table of valid configurations Order Consolidation - Valid Orders. With this, we'll see which orders match to a valid set of parts and which we can investigate further.

The Combination Matcher tool accomplishes this by taking the existing single row orders data Drop Unnecessary Columns (Drop), and trying to match each row to one of the records in the valid configurations table Order Consolidation - Valid Orders.

combination_source.png

The combination matcher tool is set up to compare values in each of the pairs of Match columns, such as "PLATFORM ID" and "Platform ID". The orders that have a valid match will return a "TRUE" value in the "Matched" column, along with the ID of the valid order in the "MatchID" column.

Export

The valid combinations are then exported back for ingestion into Incentives, ready to be processed as valid transactions and orders. Export To Incentives (Export)

Investigate Invalid Orders (Export) exports only the transactions that failed to match a valid parts combination. This allows us to further track these records, and follow up on the errors.