Report Scenarios for Rejected Transactions Report
The following scenarios explain why some transactions stays active in the queue and how to fix them.
Scenario 1
A lot (L1) for product (P1) is reported produced on a manufacturing order in warehouse W1. The package materials that are not lot controlled has been reported as consumed by the order but the purchased raw material (R1) lot (L2) has not been reported. Product P1 lot L1 is shipped on customer order 100 line 10 delivery 20.
The transaction (From Step=Manufacture, From Step Id=MO.W1.P1.L1, To Step=Customer, To Step Id CO.100.10.20) is entered in the data queue and shows in the Rejected Transaction List as "active in queue" because the from Step Id does not exist and the customer delivery cannot connect.
This scenario can be corrected by going back to M3 Business Engine and report the consumed quantity of raw material R1 and lot L2 against the manufacturing order. This will create a transaction in the GLT data queue as From Step=Purchase, From Step Id=PO.W1.R1.L2, To Step=Manufacture, To Step Id MO.W1.P1.L1.
Assuming the receiving of the purchase has been registered this transaction will be accepted and the Step Id MO.W1.P1.L1 will be entered into the system and the transaction for the delivery to the customer will be accepted without further manual action in M3 Graphical Lot Tracker.
Scenario 2
Product P1 lot L1 has been manufactured in warehouse W1, it has been shipped to warehouse W2 but the distribution order was never created. The lot is later registered into stock by a stock count and then sold to a customer on order 101, line 10 delivery 30.
The transaction
(From Step=Distribute, From Step Id=MO.W2.P1.L1, To Step=Customer, To Step Id CO.101.10.30)
is entered in the data queue and shows in the Rejected Transaction List as "active in queue" because the from Step Id does not exist and the customer delivery cannot connect.
The way to solve this scenario is to create the distribution order, receive it in warehouse W2 and correct the quantity in stock by a stock count. Again, no action is required in M3 Graphical Lot Tracker.
Scenario 3
Product P3 lot L1 does not exist in M3 Business Engine. It’s found in warehouse W1 and entered using a stock count and later sold to a customer on order 102, line 10 delivery 40.
The transaction (From Step=Unknown, From Step Id=XX.W1.P3.L1, To Step=Customer, To Step Id CO.102.10.40)
is entered in the data queue and shows in the Rejected Transaction List as "active in queue" because the from Step Id does not exist and the customer delivery cannot connect.
If there is no way to correct this transaction in M3 Business Engine, it is recommended to accept the transaction in M3 Graphical Lot Tracker as a trace with an unknown starting point. The other option would be to inspect the transaction, thereby making it invisible to trace.