Finance | Project Operations, Human Resources, ...

Application of Returns Issue

(0) Share

Report

Posted on by NCOPP

Post upgrading to GP 2018, a client is now experiencing the following:

1. Applying a return to an invoice does result in the amount of the return being applied... HOWEVER

2. The document reference on the allocation shows as the invoice document number AND

3. The return is not closed out to future use.

It would appear that the allocation is failing - except there is no error thrown.

I have not seen anything like this reported, but am hoping that perhaps someone can point me toward what to examine in the tables to see if there is an issue. The installation does have customization and the transactions are being sent in using eConnect.

Thank you,

- Nick

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Andrea Melroe 3,437 on at

Like (0)

Report
Copy link

Link copied!
Thank you for using Dynamics Communities. This is Andrea, and I will assist with your question today.

I have seen problems with allocations occur when users use eConnect to bring transactions into the system with ‘currency’ information (because currency data exists in the CM00100 or the IV00105) when Multicurrency is not marked as registered (Microsoft Dynamics GP >> Tools >> Setup >> System >> Registration).

I have some questions for you:

Are you talking about Returns in Purchase Order Processing, or in Sales Order Processing?

Are you registered for Multicurrency?

Do you have currency data in the CM00100 and/or the IV00105 table?

If you test hand keying a return manually in GP, does the same problem occur?

If you disable your customization, and you use eConnect to bring in a return, does the same problem occur?

If you disable your customization, and you hand key the return manually in GP, does the same problem occur?

The answers to these questions should help to hone in on the cause.

Andrea Melroe | Sr. Technical Advisor | Microsoft Dynamics GP

Was this reply helpful? Yes No
NCOPP 92 on at

Like (0)

Report
Copy link

Link copied!

Hi Andrea,

Thank you so much for the response. I apologize for the delay in getting back to you. I am working through some of the questions you posed. Please allow me to answer the ones I can right now.

1. These are returns in Sales Order Processing

2. We do have values in both the CM00100 and IV00105 tables.

3. I asked that a manual return be entered and applied and IT DOES result in the same problem.

4. Multicurrency Management is checked - enabled if I understand correctly.

Thanks,

- Nick

Was this reply helpful? Yes No
NCOPP 92 on at

Like (0)

Report
Copy link

Link copied!

As a follow-up to this issue:

After upgrading to GP 2018, this issue began...

Upon applying a return to an invoice, the following occurs:

1. The return remains open and the amount available remains unchanged.

2. The distributions from the applied return sit in RM10101 as posted, but with a posting status of work

3. The invoice is paid and closed

4. The is an apply record in RM30201 but the APFRDCNM is the invoice document # itself and not the return.

I believe the issue lies in #4 above. Somehow the wrong document # is getting set into the "from" document, which I have to assume prevents the proper closure and decrementing of available funds on the return itself.

Given this has been going on for some time now, and the invoices sit in history, I'm looking for a solution to:

1. unapply the payments and reopen the invoices

2. I'm guessing a necessary customization is causing this issue although it has not been identified where and that is not something I have access to. I'm wondering if I can write a process leveraging the MSSQL procs and at least get the returns applied properly through current seeing as history needs to be fixed.

Any help is appreciated. Thanks.

- Nick

Was this reply helpful? Yes No
Suggested answer

Andrea Melroe 3,437 on at

Like (0)

Report
Copy link

Link copied!

Hi Nick,

If you’re still seeing this problem, I’d recommend you open a support case for further assistance so we can help you dig into what’s occurring. To determine the cause and resolution, we’d need to be able to review the data on the backend in detail, and likely gather logs (dex.sql, script log, and sql trace) of the issue occurring to determine where the problem is stemming from. That’s not something we’d be able to do within the forums platform.

If you’re intereseted in opening a case, you can do so here: Microsoft Dynamics Support

I hope this helps!

Was this reply helpful? Yes No