Testing Your Data Push Integrations

Data Push involves sending transaction results (fulfillment, counts, etc) from Power Pick back to your Business System for final processing. Once your integrations have been configured, it's important to conduct testing to ensure various scenarios have the intended results in each system.

This article provides a starting point for developing your Data Push testing plan. While your specific Business System configuration will dictate the final test cases, these suggestions cover common scenarios for validating successful data exchange.

Transactions = History Records

In Power Pick, a Transaction is a record of every step of order processing. A single Order Line may generate multiple transactions (e.g., picking the same item from three different bins, or a pick resulting in a shortage).

Understanding Consolidation Logic

Data Push uses the Consolidate Transactions setting to determine how many records it sends back to your Business System:

Setting	Data Push Will Send Data For...
Disabled (No Consolidation)	Each Transaction completed.
Consolidate Lines	Each Order Line completed.
Consolidate Orders	Each Order completed.

Non-Consolidated (Transaction-Level) Tests

These tests apply when Consolidate Transactions is set to: Disabled.

Test Case	Test Scenario	Expected Result in Business System
Pick Order Completion - Full Pick	A single order line is fulfilled, requiring picking from two separate bins (two Power Pick transactions).	The Business System receives two separate transactions/history records, one for the fulfillment from each bin.
Pick Order Discrepancy - Decrease	A pick results in a shortage, generating two transactions (partial fulfillment + shortage).	The Business System receives at least two separate transactions/history records detailing the confirmed pick quantity and the deviated (shortage) quantity/reason.
Count Completion	A Count Order is fully processed, resulting in zero variance.	The Business System receives a confirmation for each transaction in the Count Order fulfillment.
Count Discrepancy	The physical count is more or less than the Power Pick inventory.	The Business System receives a transaction for each step of the count process and creates an inventory adjustment to update the Business System stock.

Consolidate Lines Test

This test applies when Consolidate Transactions is set to: Consolidate Lines.

Test Case	Test Scenario	Expected Result in Business System
Pick Line Consolidation Check (Multi-Bin)	Fulfill a single Order Line that required picking from multiple locations/bins (multiple Power Pick transactions).	Verify only one single confirmation is created in the Business System with the correct total quantity.
Multiple Location Cycle Count	A single Count Order for a material required counting multiple storage locations (multiple Power Pick transactions).	Verify the Business System receives a single consolidated count confirmation for the material, and any resulting net adjustment is calculated correctly.

Consolidate Orders Test

This test applies when Consolidate Transactions is set to: Consolidate Orders.

Test Case	Test Scenario	Expected Result in Business System
Order Consolidation Check	Fulfill one Pick Order in Power Pick with multiple lines and underlying transactions.	The Business System receives one confirmation for the completion of the entire order.

Verify Mappings

Incorrect mappings are the number one cause of integration failure.

Field Mapping Check: For a test transaction, verify that all critical fields (Material Name, Location Name, Order Number) are correctly mapped and transferring between the two systems via ItemPath.
Transformation Logic Check: If ItemPath is used to transform data (e.g., converting a Power Pick location name to a Business System location code), verify the logic executes as programmed.
Consolidation Logic Check: Verify that your consolidation settings (Disabled, Consolidate Lines, or Consolidate Orders) are correctly configured in ItemPath to align with your Business System's requirements.

Review Logs

Reviewing logs is the fastest way to confirm success and troubleshoot errors. After every test scenario, check the logs for both successful transactions (to establish a baseline) and intentionally failed transactions. Learn more about ItemPath Logs here.

Power Pick Logs: Check the Power Pick transaction history to ensure the operation (pick, put, count) was successfully recorded and that the data was released to the host interface.
ItemPath Logs: Check the logs for confirmation that the data was successfully received from Power Pick and that the final payload was successfully sent to the Business System. For failures, ItemPath logs will contain the specific error message returned by the Business System.
Business System Logs: Verify the Business System's internal logs show the expected transaction result (e.g., "Transaction Successful," "Inventory Adjustment Created"). For failed pushes, verify the log contains a clear, descriptive error code that matches the error seen in ItemPath.

See when a Data Push integration has run and what was returned using the Integration Logs.

Failed Records

Check ItemPath Failed Attempts. ItemPath stores the specific error code returned directly from the Business System.
Correct any underlying data issues in the Business System or Power Pick.
Use ItemPath's interface to manually resend the failed transaction payload to the Business System after the correction is made.

Use ItemPath Reports to Validate Your Tests

Reports provide a clear and effective method for viewing your data and validating integration performance. Leverage our pre-built report templates for History Reports or Log Reports for comprehensive validation:

Data Push Errors Last 7 Days

Pick Transactions where Export Failed

Put Transactions where Export Failed

Resources

To learn more about ItemPath and see it in action, please book a demo with our sales team. In the meantime, here are some of our popular articles and key topics.

Book a Sales Demo

Data Push

Integration Failed Attempts

Integration Failed Attempts Resend erroring lines in the Data Push app by checking the Failed Attempts tab in your integrations. This list shows each transaction’s ID, Order Name, history Type, Status, ...

Data Push & Data Pull

Testing Your Data Pull Integrations

Data Pull involves retrieving master data from your Core Business Application (ERP, WMS, etc) and synchronizing it with Power Pick. Once your integrations have been configured, it's important to conduct ...