PO entered on 11/15/02; item was delivered on 11/19/02; however, returned to vendor for replacement due to QC fail and was not received in Macola. On 11/21/02, item was delivered, passed QC and was ready to be received into Macola; however, when entering the receipt, qty on order reflected zero not 1.
The process here on returns is as follows:
A PO is entered with the same PO number; however suffix field is used for returns for credit/replacements, as we do not process any blanket purchase orders. Based on my knowledge of Macola, the program looks at the two po's as separate entities, though they share the same PO number with different suffixes.
Since going Live with Macola in March 2002, there were no issues in using the suffix field to track the credit/replacements until now. Since Macola is setup with audit capabilities, I ran the PO audit on receipts and came up with no transactions. I also ran the IM Trx History report on the item and it only noted the entry transaction of the purchase order. I ran testing in Macola Electronics company (same apples and pears) and had no problems which is a normal occurrence. However, in this one particular situation, and maybe its a fluke, the situation above occurred. As a troubleshooter, I would like to know why this occurred and to prevent any future occurrences.
Any input would be greatly appreciated.
The process here on returns is as follows:
A PO is entered with the same PO number; however suffix field is used for returns for credit/replacements, as we do not process any blanket purchase orders. Based on my knowledge of Macola, the program looks at the two po's as separate entities, though they share the same PO number with different suffixes.
Since going Live with Macola in March 2002, there were no issues in using the suffix field to track the credit/replacements until now. Since Macola is setup with audit capabilities, I ran the PO audit on receipts and came up with no transactions. I also ran the IM Trx History report on the item and it only noted the entry transaction of the purchase order. I ran testing in Macola Electronics company (same apples and pears) and had no problems which is a normal occurrence. However, in this one particular situation, and maybe its a fluke, the situation above occurred. As a troubleshooter, I would like to know why this occurred and to prevent any future occurrences.
Any input would be greatly appreciated.