Administration, Core Financials, and Project Accounting

[trodman]

We have noticed something that we consider to be a bug, but we're not sure if the behavior is by design or possibly due to one of our customizations.  I haven't had a chance yet to test in a non-customized environment.

We did a "Project Sale" transaction of an item to a project:

• Item Type = "Finished Good"
• Track Method = "Lot"
• Valuation Method = "Actual"

We then did more "Project Sale" transactions to other projects.  When we went back and did a "Project Sale Return" transaction for the original project, it did not use the same cost as the original "Project Sale" transaction when putting the part back into inventory.

In our minds, the "Project Sale Return" transaction should use the same cost as the "Project Sale" transaction.  Does anyone know if this behavior is by design?

[MCarlise]

I duplicated the issue on 7.50 (not released yet), but my guess it has behaved this way for a while. Can you tell me if it is entering the Replacement cost for the item, or the cost of the last tier? When we are adding inventory the system will automatically enter the replacement cost (just like in a PO). However since my original cost on the project was 12.00, does it really make sense to book 20.00 back into the project? I don't think so.

I am still doing a bit of research, but when you can please let me know where you think the new costs from the return are coming from.

Thanks!

[trodman]

Mari,

I'll test and let you know.  My suspicion is that it's using the last cost tier cost, but I'm not sure.