Hello,

Recently we made a PO and ordered something incorrectly. Previous using the old PO system (POWIN) there was a inv/adust/Rtns button that we could use to do return, but I don't see that in the new PO module. Is this functionality not possible in the new module or am I missing something?

Thanks.

Carlos:

To do a return you must to a negative Quick Receipt.

Hello,

How to track returns by PO?
In old PO 8.X there was a document flow display showing all transactions related to any particular PO (receipts, adjustments, returns). How to connect return(s) to a receipt.

Regards
Victor

Hi,
We don't think the dataflow in the PO 9.2A, or 8.1D, works the same as the Old POA.

It appears to work fine for simple transactions, but as soon as you start to do combine PO's, combine quick receipts (positive or negative) with other receipts to firm up the invoice amount, the quick receipts become orphans.

If you combine any transactions quick or otherwise, then the transactions that make up the data flow, should show up in the DataFlow display of the resultant document. And so Victor, if you cannot fine the connection, it's not there but should be.

Best,
Brian

Hi Brian,

Thank you for your comment.
I think this is serious problem in data processing flow.
All users complaining about not having ability to reconcile orders/receipt/returns, especially for large vendor purchases. Very often vendors accept returns and issue a credit note for multiple POs which we can not process and track properly.
It's equal to having PO application without return functionality.
Using disconnected quick receipt with the negative quantities it's a big nonsense.

My Question is to R&D or/and tech support team:
How quickly it could be fixed?

Regards
Victor

Hi All,

This is very unfortunate that the Softrak ignoring such a critical issues:

- PO 9.2 Validated return (PO - return link and displaying in data flow view)
- PO 9.2 Manual proration of misc. charges

I'm asking my Question again:
When this issues will be fixed?

Regards
Victor

Hello Victor,

I can assure you that Softrak does not ignore critical issues that are brought to its attention. We regularly release Hot Fixes and Service Packs to resolve circumstances where a module operates incorrectly. However, “incorrectly” means that it does not conform to the documentation or some portion of the accounting is incorrect. Neither of the concerns you raise falls in this category.

Adagio PurchaseOrders was subjected to a 6 month Beta cycle before Version 8.1C was released. The manual proration functionality has been unchanged in the product for over 2.5 years without end user complaint. We decided, in consultation with POA users who participated in the Beta, not to implement Returns in PO in the initial release as no one liked the way it worked in Purchase Orders for Adagio.

Most of the automatic proration methods in PurchaseOrders for Adagio did not work correctly. All of these function properly in Adagio PurchaseOrders. Your post indicated that you use a spreadsheet to calculate your prorations. If you would document what method you use and the information you require to calculate a single miscellaneous charge over the items on a purchase order, then we would consider automating that process for you so a spreadsheet would no longer be required. But that development would wait for the next Upgrade cycle on PurchaseOrders which would likely not take place for a year or more.

If a PO user will provide a database where they believe the display of the document flow is incorrect, then we will be happy to see whether it is a problem we can resolve.

We have expended disproportionate resources on Adagio PurchaseOrders over the last 3 years, and other modules require attention.