Hi,
Can anyone recommend how best to track items in I/C to see how many we had to issue credit on? I would like to see which items we may have quality issues by looking at the rate of units credited vs. units sold during a particular time period.(Monthly or quarterly would be ideal). It would be great to see it broken out by total returned to stock and total not returned to stock.

Thanks!

Hi Kristin,

If you religiously enter credit notes for these items, then a GridView report on the OrderEntry Sales History could tell you this pretty quickly.

Ki Kristin,
I will send you the NFR codes for Gridview.

Softrak has stated that Gridview has become the main reporting tool for Adagio. We might want to think about migrating from Crystal to GV.

Carol

Main "ad hoc" reporting tool, Adagio still relies on Crystal for management reports that are "formatted"

I'm bringing this topic back to life because Kristin asked me two related questions.

#1) She needs to be able to track the status of sales returns, especially whether they have received the merchandise that the customer returned (at which point the customer should be credited). What's the best way to handle this?

#2) She would like to assign "reason" codes to a credit note, one per item, and generate a report using that code. Is there a detail text field she can use when entering a credit note to enter the 3 digit reason code? I thought of item optional fields but unlike customer optional fields they don't flow to OrderEntry. There may be different reasons for different items on the same credit note, so I can't use a header field. Right now they are entering the reason code as a prefix in front of the item description, but I was hoping there was a better way.

Steve

Normally, someone would have replied by now. Should I try using different words?

Can this topic be moved to the Technical Support forum, where it really belongs.

Thanks

Steve

I know of a site using SalesCQ to track RMA's. That's the best solution available at the moment. Perhaps you could use a Price List code to classify the return reason?

Hi Andrew

Price Lists codes are already in use.

Let me suggest two changes to OrderEntry that would go a long way towards resolving the two issues above.

#1) Allow for negative quantities on orders, which can be turned into credit notes/negative invoices. It would be fine if the negative quantities reflect in the "On SO" field, since that would accurately describe the status of the soon-to-be-returned item.

#2) Pull the inventory optional fields into an order, so that they can be edited just like customer optional fields. I'm sure you've heard complaints about how few editable text fields there are when entering item details on an order, so this is very needed.

For now, I'll advise Kristin to continue tracking pending returns manually, and to enter a reason code as a prefix in the item description field.

Steve

We believe Adagio requires RMA processing as well as optional fields at the line level.

I believe that too. I don't know how you plan to allocate your resources, so I was suggesting something workable that requires less effort than the development of full RMA functionality. It would certainly be better than what we have right now. But if you intend to develop RMA functionality in the near future, then ignore my first suggestion.

Steve