accounting distributions uncomitted tax

(0) Share

Report

Posted on by CRSW

625

Hello

I do have a purchase order with about 25 lines for the same item with different delivery dates.

Now I received the items for 3 lines (confirmed delivery dates on the PO are 17.03., 21.04. 19.05)

When I try to post the journal today it fails with error "Transaction date is not part of an open fiscal period, or you do not have the necessary user rights"

I am sysadmin so its not the user rights and transaction date should be today (or am I wrong) and the current period is open

It seems to be a problem with the accounting distribution for uncommitted tax. On the PO the distribution on each line is done with accounting date = date of the ordercreation (March, 19, 2019) so posting the WMSJournal today occurs an error because of the uncommitted tax posting from accounting distribution because the accouting date is March, 19th 2019 which is in closed period
How can fix the problem to post my journal? (and the tax)

I have the same question (0)

All responses (12)

Answers (1)

Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi,

Have you checked that your periods are all open and that there is no module access restrictions for the different periods in place?

Best regards,

Ludwig

Was this reply helpful? Yes No
CRSW 625 on at

Like (0)

Report

Hi Ludwig

Question to me is more Why is a PO line, posted, lets say today, having an accounting date in 2019. This seems to be wrong to me. Or not? If I receive goods today I have to do the accouting with todays date not with a date 2 years ago. In the end its not only financial value for the goods I received today posted in 2019 it will be tax as well.

Period for 2019 is closed is it should be in my opinion

Best regards

Chris

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello Chris,

Can you double check whether

(a) All periods in 2019 are really put on hold and

(b) whether you regularly run an inventory close

If you follow (a) and (b) on a regular basis then you should not be able to backdate transactions.

Best regards,

Ludwig

Was this reply helpful? Yes No
CRSW 625 on at

Like (0)

Report

Hi

(a) yes all periods in 2019 are on hold

(b) good question I have to ask cause I do not know

To me it's still the question why would I backdate a transaction. To me it's still like. The delivery date for PO line is in March 2021, I received good in March2021, the invoice from the vendor will be in March 2021 so to me there is no sense to backdate it to May2019.

In the end to me, if I post it in the May 2019, Inventory value is calculated wrong, tax is posted wrong and so on.

Is it really correct to post with backdate in 2019?

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi CRSW,

If you regularly run an inventory close then backdating is not possible and the problem is gone.

Fully agree with you that backdating things - especially for multiple years - is probably not the best practice :-)

Cheers,

Ludwig

Was this reply helpful? Yes No
CRSW 625 on at

Like (0)

Report

Hi

So it's quite good that I am not that stupid. Thought I got s.th. wrong.

In the case here the periods are on hold and as I could the see an inventory closing is done for the periods in 2019.

So why does the PO have OPEN positions with accounting date on accounting distribution somewhere in 2019 and tries to post with this old accounting date?

How can fix this and second how can we avoid this behaviour happening again?

Was this reply helpful? Yes No
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hi CRSW,

Can you share some screenshots about those old and open positions?

Also, can you let us know the build number of your AX2012 application?

Many thanks,

Ludwig

Was this reply helpful? Yes No
CRSW 625 on at

Like (0)

Report

Here you can see the PO with the 3 Positions I want to post the WMS Journal for

The accounting distribution for the 3rd last line (2nd last looks the same and last line has only the "Original" in distribution

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

Hello CRSW,

The 3 lines that you shared in the second screenprint seem to be caused by a line update that has been made. This usually happens if a change is made to a line and after the PO is reconfirmed.

This does, however, not explain the error message that you see.

I had a short look at LCS and the available hotfixes there.

That is because in the past there were a couple of problems related to those distributions.

Can you check whether one of those hotfixes applies to your environment?

If this does not bring you forward then the next step might be debugging the issue with the help of a developer.

Best regards,

Ludwig

Was this reply helpful? Yes No
CRSW 625 on at

Like (0)

Report

Maybe you have an idea how I can modify the accounting distribution in this ca (partly invoiced Purchase order with 3 open lines)

When I try to call the accounting distribution or post a new confirmation I always get the error with the accounting date

(for the pics I just modified the return value to today by code)

Was this reply helpful? Yes No