They are all purchased, and we found the source of some of the grossly inflated costs to be the supplier for purchase part’s primary supplier set to a price of 1000000000000. The customer was using this value as a flag that they didn’t have a correct price, and they were updating the price on the work order’s purchase requisition directly. So even though the work order planned cost was correct, the project was calculating a planned cost for that work order from the supplier for purchase part cost. After updating the supplier for purchase part price and refreshing the project connections, the project was showing the correct planned cost, however we think this is still an issue that it’s not using the actual planned cost from the work order.
We’re seeing this same issue in Cloud 22R1 where the work order materials show the correct cost, but there is a massively inflated planned cost on the project connection. We’re using the FIFO costing method on the inventory parts, don’t have a cost on the supplier for purchase part, and haven’t run a cost calculation that is explaining it.The planned cost showing on the project connection does equal to the sales price of the sales parts for those inventory parts, though.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
