Labor Admin - Errors#
Reviewing and Resolving Error Transactions#
This topic covers how to resolve transactions that weren’t successfully migrated from the WMS to Rebus.
Resolving Quarantined Transactions#
This procedure covers how to resolve quarantined transaction s. This is done by repairing whatever issue caused the configuration error and then having Rebus attempt to process the transactions again.
Go to Admin Tools -> Labor -> Transaction Error Review. You are at the Transaction Error Review screen.
Click the Quarantined Transactions tab. The Quarantined Transactions table opens in the main interface area.
Use the Search Fields panel to run a query to produce a list of quarantined transactions that you want to resolve. For more on searching through activities, see Searching through Activities. The Quarantined Transactions table is populated with details of transactions that couldn’t be converted into activities because of configuration issues.
For each transaction, look at the error message and then repair the configuration issue that’s preventing this transaction from being converted into an activity:
Error |
What the Problem is… |
What You Need to Do… |
|---|---|---|
Null Activity ID |
Activity ID field is not populated in the incoming data. |
Check to see that the activity groups are properly configured. If you can’t find the configuration issue or you otherwise can’t resolve it, contact Rebus Customer Support. |
Null ActivityId – More than one row matched for the <attribute matrix name> Matrix for AUX value |
Transaction has a value in the mapped auxiliary field that matches more than one row in the mapped attribute matrix, because the attribute mapping expression uses the LIKE or NOT LIKE operator. |
Either correct the mapping attribute expression of the activity group by selecting the right operator. or correct the matrix by including only one row with the right lookup value. |
Null ActivityId – Cannot perform mathematical operator(>) on String data field<(field name)> |
Mapping attribute expression uses a mathematical operator (>, >=, <, <=), and the transaction’s AUX value format is a string. |
Either correct mapping attribute expression of the activity group by selecting the right operator, or correct the matrix by changing the vector value. |
Invalid User |
This transaction’s user is not set up as a labor user. |
From the Transaction Error Review screen, set up the transaction’s user as a labor user. For more information on how to set up the labor user, see Creating a Labor User from the Transaction Error Review Screen. |
Invalid Activity ID |
Activity ID field is populated with an invalid value in the incoming data. |
Set up an activity type for this transaction. For more information about how to set up activity types, see Setup Procedure 6 of 7: Setting up Activity Types for Imported Transactions. |
Invalid Activity Group |
Activity group field is populated with an invalid value in the incoming data. |
Set up an activity group for this transaction. For more information about how to set up activity groups, see Setup Procedure 5 of 7: Setting up Activity Groups. |
Invalid QTY |
Invalid quantity value in the incoming data. Quantity cannot be null or less than or equal to zero. |
Contact Rebus Customer Support. |
Invalid Step |
Steps in the incoming transaction don’t match the step configuration in the activity type. E.g., Activity type is configured to have one step called START, but incoming transaction has STOP as step value. A labor user probably isn’t correctly following your processes. |
Make sure that the labor user understands how to properly follow your processes. If this is a transaction that you don’t need to preserve, you can delete the transaction. For more information, see Deleting Transactions. Otherwise, contact Rebus Customer Support. |
Extra Indirect Signoff |
The non-essential transaction has an extra stop step. Non-essential transactions should have one Start and one Stop step. An extra Stop step can happen when a user in the WMS stops the transaction multiple times by mistake. |
Caused by a user forgetting to stop a non-essential transaction, starting another transaction, and then remembering later on to stop the non-essential transaction, which results in an extra stop step. Make sure that the labor user understands how to properly follow your processes. If this is a transaction that you don’t need to preserve, you can delete the transaction. For more information, see Deleting Transactions. Otherwise, contact Rebus Customer Support. |
Query UOM does not match configured UOM |
The labor transaction’s UOM in your WMS doesn’t match the configured activity type’s UOM in Rebus. |
If the configured UOM in Rebus is incorrect, change it to the correct UOM, and save the activity type. To find out where to change the UOM, see Setup Procedure 6 of 7: Setting up Activity Types for Imported Transactions. Otherwise, please contact Rebus Customer Support. |
Invalid Modification |
Rebus cannot find the SIGN-ON or SIGN-OFF to be updated or deleted. |
Confirm that the user’s last SIGN-ON or SIGN-OFF is correct from the Activity Adjustment Admin screen. If it’s correct, delete the quarantined transaction. If it’s incorrect, contact contact Rebus Customer Support. |
Invalid Time Component # - <Time component name> - Combination not found in <Matrix name> |
Transaction does not satisfy time component mapping. |
Compare transaction’s auxiliary fields to time component mapping - all fields that are included in the mapping must be populated for the transaction. |
Invalid Time Component # – <Time component name> – More than one row matched for the <Matrix name> matrix |
Transaction has a value in the mapped auxiliary field that matches more than one row in the mapped numeric matrix, because the time component expression uses the LIKE or NOT LIKE operator. |
Either correct the time component expression of the activity type by selecting the right operator, or correct the matrix by including only one row with the right lookup value. |
Invalid Time Component # – <Time component name> – Cannot perform mathematical operator(>) on String data field <(field name)> |
Time component expression uses a mathematical operator (>, >=, <, <=), and the transaction’s AUX value format is a string. |
Either correct the time component expression of the activity type by selecting the right operator, or correct the matrix by changing the vector value. |
Invalid Time Component # – <Time component name> |
Configured time components or mapping atributes are missing information. The root cause could be any of the following: |
|
Possible Root Cause 1: Transaction has a value in the mapped auxiliary field that cannot be found in the corresponding vector of an attribute matrix. |
Add missing value (e.g., location) to the attribute matrix, with the corresponding value to be returned. |
|
Possible Root Cause 2: Transaction has a value in the mapped auxiliary field that cannot be found in the corresponding vector of a vector matrix |
Add missing value (e.g., to & from zone combination) to the numeric matrix, with the corresponding value to be returned. |
After the configuration issues are repaired, come back to the Transaction Error Review screen and run a query to produce the list of quarantined transactions caused by configuration issues that you just repaired. For more on searching through activities, see Searching through Activities.
For each quarantined transaction whose configuration issue you repaired, click the checkbox. To select the whole list of quarantined transactions, click the checkbox at the top of the grid.
Click ‘Resolved Quarantined Transactions’. Rebus tries to process the selected quarantined transactions. A message appears telling you how many transactions were resolved. The screen refreshes to show any remaining quarantined transactions that remain unresolved.
What if this doesn’t work?#
If there are still quarantined transactions in the table that weren’t resolved, contact Rebus Customer Support.
Resolving Incomplete Transactions#
This procedure covers how to resolve incomplete transaction s. This is done by having Rebus add to each selected incomplete transaction a step whose values address the validation that the transaction failed.
Go to Admin Tools -> Labor -> Transaction Error Review. You are at the Transaction Error Review screen.
Click the Incomplete Transactions tab. The Incomplete Transactions table opens in the main interface area.
Use the Search Fields panel to run a query to produce a list of incomplete transactions that you want to resolve. For more on searching through activities, see Searching through Activities. The Incomplete Transactions table is populated with details of transactions that couldn’t be converted into activities because they failed a validation.
Make sure that the rows of the table are grouped by grouping number. The grouping number should be in the bar above the column headings.
For each grouping that you want to resolve, make sure that at least one transaction is selected.
Click ‘Complete Selected Grouping’. Rebus does the following:
Adds to each selected transaction a step whose values address the validation that the transaction failed. I.e., It adds a step that has the same quantity and the same labor user as the first step. This resolves most validation errors.
Tries to process the selected transactions again.
Produces a message telling how many transactions were successfully processed and refreshes the screen to show any of the remaining unresolved incomplete transactions.
What if this doesn’t work?#
In rare cases, Rebus’s attempts to automatically resolve incomplete transactions won’t work because the transaction is failing too many validations at once. To resolve these, you’ll need to contact Rebus Customer Support.
Deleting Transactions#
You can delete an error transaction from a table on the Transaction Error Review screen if you don’t need or don’t want it to be processed (e.g., an error transaction caused by user error.). To delete a transaction from a table of the Transaction Error Review screen, do the following:
For each transaction that you want to delete, click the checkbox.
Click ‘Delete’ and then click ‘Yes’ when the confirmation dialog appears. You have deleted the selected transactions.
Any incomplete transaction that is five working days old will be automatically deleted.
Creating a Labor User from the Transaction Error Review Screen#
To resolve Quarantined Transactions with the ‘Invalid User’ Error, follow these steps:
From the Transaction Error Review screen, click ‘+Create New User’. The ‘Add New User’ form appears.
Fill in the fields needed to create the new labor user. For more information on these fields, see Setup Procedure 3 of 7: Setting up Labor Users.
Click ‘Save and Close’ or ‘Save and Add Another’ if you wish to add another labor user.
To finish resolving this error, go to step 5 of Resolving Quarantined Transactions.