Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Unanswered

PO "null" unit type behaviour in D365 vs 2012

(0) ShareShare
ReportReport
Posted on by 67

Our business have entered a number of POs with no unit type selected which in AX2012 allowed 2 decimal places. (Typically these POs are raised this way as they are for things like utilities which are for an unknown monthly price) Most have been part invoiced and part received leaving a remaining quantity. Now these exist like the below in D365 after we've upgraded to D365. 

pastedimage1679346292674v2.png

pastedimage1679346235038v1.png

Now finance are trying to process the invoices for these POs using decimal places as they would have done in 2012 so for example want to match an invoice for £149.32 but the system will round the invoice up to £150 as it cannot handle 2 decimal places when unit type is null. Is the only solution to close the current PO line off and recreate a new line with the correct unit type that allows 2dp?  Is this a known change in behaviour between AX2012 and D365?  Obviously the PO should not have been raised without a unit type but it is a lot of work to correct.  

thanks

Joe

  • jerhsysacct Profile Picture
    jerhsysacct 67 on at
    RE: PO "null" unit type behaviour in D365 vs 2012

    Hi Andre

    I would not say it was intentional that certain POs have been processed without a unit type causing this issue but given the change in behaviour in D365 we cannot now process to 2dp against them either with a receipt or invoice. I think you are right though that we probably have to correct by raising new POs or script to update and see if that resolves the issue.

    Regards

    Joe

  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 292,162 Super User 2025 Season 1 on at
    RE: PO "null" unit type behaviour in D365 vs 2012

    Hi Joe,

    I have never seen any implementation myself where the unit was not filled. For that reason, I don't know if there is any change or not.

    You can consider writing a custom x++ script to complete the unit field on the purchase orders where it is currently empty.

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

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Congratulations to the January Top 10 leaders!

Check out the January community rock stars...

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,162 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 230,962 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans