Using Data Push

Every Transaction in History

When using Data Push, you may see multiple transactions for the same order. Transactions record every step of order processing, so a History record is created every time something is processed in PPG. That means each order line will have separate transaction.

An order may also have more transactions if some order lines were deleted, if there were shortages/deviated quantities, or materials in the order were picked from/put to multiple locations.

Each order line has its own History record, since an order can have multiple lines at different stages. For example, an order could have one order line fully processed, another order line partially processed, and another order line not yet processed.

It can be helpful to include the Motive Type in your integration Mappings to see corrections and deletions, as well as the Order Status Type. Here's an excerpt about Order Status Types from this API guide:

Order Status Types

An order's status is automatically set to "Untouched" when it is created, but these values can be helpful when updating or searching for the status of an order.

  • 1: "Untouched"
  • 2: "Ready for Allocation" (when reverted from "Is Allocated”)
  • 10: "Is Allocated”
  • 11: "In Process" (order is imported but not fully picked/put)
  • "Processed" (order is fulfilled and can be found via name or orderId in the History/Transactions list)

Putting Filters on an Integration

Filters in a Data Push integration's Settings filter by the History Type field from the History table in PPG. You can use filters to only include transactions that match a certain History Type. This API guide lists these History Types and other common types used for transactions.

Most Data Push users want at least an integration for Put orders and an integration for Pick orders.

Data push 1 integrations

You can add more than one History Type to an integration's filters. For a Put integration, we recommend filtering by both Put types (1 and 3), and for a Pick integration, filtering by both Pick types (2 and 4).

Data push 2 filters

If you would like to send other transactions with other history types (not picks and puts), we recommend creating a new integration (or multiple) with those filters. Other common History Types include Transfers (5), Counts (6), Corrections (10), and Cancellations (11).

Data push 3 types

Two Types of Puts & Picks

The reason for the two Put types and two Pick types is to differentiate between Manual and Order transactions.

The two "Put" History Types are Manual Put (1) and Order Put (3). A Manual Put is typically made by the user at the storage unit. They may type or scan the material name/part number and enter the Put quantity manually before putting the order away. An Order Put comes from an order created or imported in PPG.

In the same way, the two "Pick" History Types are Manual Pick (1) and Order Pick (3). A Manual Pick is typically made by the user at the storage unit, as they type or scan the material name/part number and manually enter the quantity they're picking. An Order Pick comes from an order created or imported in PPG.

However, both Manual and Order types can be simulated virtually for test purposes, and don't necessarily require someone to be physically at the storage unit. Connect with Kardex support for resources on how to virtually process an order in your PPG admin software.

Testing and Error Logging

If the "test" function shows no response, you might not have enough History transactions to test with. Try creating more transactions in PPG before testing your integration, or manually copy a History ID (e.g. from a History report in ItemPath) and paste it into the integration's Test field.

Data push 4 test

For checking for errors, we recommend adding a report per integration that check for an Export State Type of 5. Pre-built templates of these reports can be downloaded from this list here. Look for Pick Confirmations with Errors and Put Confirmations with Errors.

You could then connect each report to a workflow to automatically get notified if there are errors in the report.

Data push 5 errors