Transaction Reversal errors - something about a contract?

(0) Share

Report

Posted on by Oceanfish26

624

D365 10.0.12

In my prod environment, I have a GL transaction I receive an error when I attempt to reverse it.

"Voucher number GJE000144, transaction type Ledger journal, and account number 9040-PCI-CO-201 can't be reversed."

I have two trace files one from a similar GL transaction which I am able to reverse, and one from this error. When I compare them, I find the error trace file has these extra calls in the call stack to TransactionReversal::parmContract, the good GL transaction reversal does not.

I have submitted this to Microsoft, and they do not know what is causing this.

Can someone offer any advice?

FAQs:

No, we do not have Mass reversals for multiple documents enabled

No, we do not have Revenue Management module enabled

No, we are not using the Project module

No, we are do not have any worker/vendor/customer contracts in D365

I have the same question (0)

All responses (9)

Answers (1)

Suggested answer

Ramit Paul 22,797 Most Valuable Professional on at

Like (0)

Report

Hi,

Do you use ISV solution for contracts? any ISV product?

What is you journal entry? ledger to ledger?

How important is to reverse it, you may also consider this by a manual entry?

Can this be reproduced?

Was this reply helpful? Yes No
Suggested answer

Junaid Idrees on at

Like (0)

Report

Hi Oceanfish26

Thanks for specifying the FAQ details for more clarity.

Can you please share that transaction entry Debit and Credit side or if you can send screen print of it, that would be sufficient.

Any idea if anyone enabled any new feature from feature management screen? Did you checked any other GL transaction by doing reversal just to troubleshoot and reproduce the issue.

Was this reply helpful? Yes No
Oceanfish26 624 on at

Like (1)

Report

I checked in Features and nothing was recently added.

Was this reply helpful? Yes No
Martin Dráb 237,805 Most Valuable Professional on at

Like (0)

Report

What about debugging it (after copying the database to a non-production environment)?

Was this reply helpful? Yes No
Oceanfish26 624 on at

Like (0)

Report

That's where I'm at now. I just wondered if anyone knew what this was before I dove into debugging.

Was this reply helpful? Yes No
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (1)

Report

Hi Oceanfish26,

You can do all of what has been suggested but I wonder whether it wouldn't be easier to create a manual correction line?

From your screenshot I can identify a voucher with two lines only and it should not take much time to post a corrective voucher.

Wouldn't that be the faster and easier workaround?

Best regards,

Ludwig

Was this reply helpful? Yes No
Oceanfish26 624 on at

Like (1)

Report

Thanks, but I've kept back some details to keep my question, and answer, hopefully succinct. The bigger issue is, this happens on many other Ledger Journal transactions as well - and, in sandbox I can reverse the very same transaction. Its def. a functional problem, more than just a single corrective voucher. But thanks for the idea. Another FAQ, its not a closed period.

Was this reply helpful? Yes No
Suggested answer

Junaid Idrees on at

Like (0)

Report

I agree what Martin suggested, debug it on non production environment to find the root cause as you are facing issue on other ledger transactions as well.

Was this reply helpful? Yes No
Verified answer

Oceanfish26 624 on at

Like (1)

Report

I solved the issue without debugging. I realized they had performed a Year End Close, which when done becomes a checkpoint in the code to prevent reversals. Only net new transactions can be performed in the YEC date range, then another YEC can be executed.

Was this reply helpful? Yes No