Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL (Archived)

PO Receipt Batch $ <> IN Transactions $

Posted on by Microsoft Employee

Hi Carolyn,

I had to copy the main part of this discussion thread from the other SL forum - it appears that the site is currently having issues, so currently I am not able to update that discussion thread (surprise)!

ORIGINAL QUESTION:

SL7, PO Receipt, POTran table has incorrect values. SL7 recorded a partial receipt of one PO. The PO Receipt/Invoice Entry screen reflects the correct unit cost, with the same unit price as two other receipts processed in the same batch. Updated INTran LIFO cost layer with the incorrect value, which now needs to be backed out. POTran table - CuryExtCost is correct, Extcost is incorrect.

I would just adjust out the item and receive it back into Inventory if they weren't using FIFO. I need to find how to update the one incorrect cost layer, hopefully before a sales order pulls items from this layer at the wrong unit cost.

YOUR LAST REPLY:

Sorry for the delay.  So I understand that the ExtCost is incorrect in the POTran table.  Is that correct?  Was the batch that was created in GL for the wrong amount also?  And how about the AP batch if the PO receipt was vouchered?

This issue could be due to bug 7788 'Incorrect Extcost populated in Potran table.', which is still pending resolution by development. However, there are two triggers offered as a workaround -  these are only valid when the database is not using multi currency. Is this a multi-currency database?

Also, please let me know all what needs to be corrected.

--------------------------------

I didn't look at GLTran, only POTran. The AP batch created a voucher for the correct amount. An INTran record was created for the incorrect amount. Multi-currency is not being used. At a minimum, the FIFO cost layer for this one incorrect PO receipt must be adjusted. The subsequent partial receipts on the same PO were recorded at the correct cost. No items have been sold yet from the incorrect cost layer, so fixing this error ASAP will keep the problem from expanding in scope.

*This post is locked for comments

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans