RMA disposition in 809

Yahoo Archive
1
Hi,

We experienced the same issue that Vishal described below. It was a
bug that Epicor was aware of in May 2006 and they sent us a
patch/fix that did not work so we had to manually correct these
duplicates. Epicor told us that the general ledger would not be
affected (only quantities duplicated) and so no cost adjustment
would be needed. However, we are now experiencing $ reconciling
issues and I'm wondering if the general ledger was affected?

Did anyone on this board have the same issue?

Thanks,

Vanessa


--- In vantage@yahoogroups.com, "Vishal Mehta" <vishy65@...> wrote:
>
> We are on 809 and are observing that there is a bug in Disposition
of returns. When we disposition to Stock and assign different
warehouse ( FG) ( returns are received in MRB warehouse); system is
doubling inventory in warehouse returns were received ( MRB) and not
moving to destination warehouse.
>
> Is anyone else facing this issue ? According to Epicor support ;
its not an issue and its specific to our DB .
>
> Vishal
>
> [Non-text portions of this message have been removed]
>
2
We are on 809 and are observing that there is a bug in Disposition of returns. When we disposition to Stock and assign different warehouse ( FG) ( returns are received in MRB warehouse); system is doubling inventory in warehouse returns were received ( MRB) and not moving to destination warehouse.

Is anyone else facing this issue ? According to Epicor support ; its not an issue and its specific to our DB .

Vishal

[Non-text portions of this message have been removed]
3
Are you multi-plant?

--- In vantage@yahoogroups.com, "Vishal Mehta" <vishy65@...> wrote:
>
> We are on 809 and are observing that there is a bug in Disposition
of returns. When we disposition to Stock and assign different
warehouse ( FG) ( returns are received in MRB warehouse); system is
doubling inventory in warehouse returns were received ( MRB) and not
moving to destination warehouse.
>
> Is anyone else facing this issue ? According to Epicor support ; its
not an issue and its specific to our DB .
>
> Vishal
>
> [Non-text portions of this message have been removed]
>
4
No, we are single plant.

Vishal


To: vantage@yahoogroups.comFrom: mhow@...: Tue, 12 Sep 2006 21:24:46 +0000Subject: [Vantage] Re: RMA disposition in 809




Are you multi-plant?--- In vantage@yahoogroups.com, "Vishal Mehta" <vishy65@...> wrote:>> We are on 809 and are observing that there is a bug in Disposition of returns. When we disposition to Stock and assign different warehouse ( FG) ( returns are received in MRB warehouse); system is doubling inventory in warehouse returns were received ( MRB) and not moving to destination warehouse.> > Is anyone else facing this issue ? According to Epicor support ; its not an issue and its specific to our DB .> > Vishal > > [Non-text portions of this message have been removed]>



[Non-text portions of this message have been removed]
5
We are considering installing 809, but we also use RMA's and return to
different warehouses and bins. Is anyone doing that successfully?



Thanks for you help.





<http://www.coldjet.com>

Michelle de la Vega

Business Applications Manager

Cold Jet, LLC

455 Wards Corner Road

Loveland, Ohio 45140

513-716-6400

513-831-1209 FAX

Celebrating 20 Years of Dry Ice Technology and Innovation

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Vishal Mehta
Sent: Tuesday, September 12, 2006 4:37 PM
To: vantage@yahoogroups.com
Subject: [Vantage] RMA disposition in 809



We are on 809 and are observing that there is a bug in Disposition of
returns. When we disposition to Stock and assign different warehouse (
FG) ( returns are received in MRB warehouse); system is doubling
inventory in warehouse returns were received ( MRB) and not moving to
destination warehouse.

Is anyone else facing this issue ? According to Epicor support ; its not
an issue and its specific to our DB .

Vishal

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]