Backflushing not working in Epicor 10.0.700.3 - help please

#ygrps-yiv-1561271377 P.ygrps-yiv-1561271377b1e7fd89-0279-4ffe-a16a-1f1bcba0d537 { MARGIN:0cm 0cm 0pt;} #ygrps-yiv-1561271377 LI.ygrps-yiv-1561271377b1e7fd89-0279-4ffe-a16a-1f1bcba0d537 { MARGIN:0cm 0cm 0pt;} #ygrps-yiv-1561271377 DIV.ygrps-yiv-1561271377b1e7fd89-0279-4ffe-a16a-1f1bcba0d537 { MARGIN:0cm 0cm 0pt;} #ygrps-yiv-1561271377 TABLE.ygrps-yiv-1561271377b1e7fd89-0279-4ffe-a16a-1f1bcba0d537Table { MARGIN:0cm 0cm 0pt;} #ygrps-yiv-1561271377 DIV.ygrps-yiv-1561271377Section1 { }

This is a bug speak with Epicor support.
It has been corrected in .4 and 10.

I had to clean this up at one site where jobs fed other jobs and they were also using CoPart factors. 

The issue is a timing problem the auto receive occurs before the back flush and labour costs apply.

Sent from my iPhone

On 28 Feb 2016, at 03:12, jsavastio@... [vantage] <vantage@yahoogroups.com> wrote:

 


 

The problem is that the full cost of the parts are not reflected as the part is auto received to stock.  Labor and burden missing on the first receipt when backflushing labor. Seems the quantity receipt to stock is occurring prior to backflushing the labor of prior operations.

 

 

Significant variances are being created from manufacturing jobs (MFG-VAR).

 

We are set up as follows:

 

Labor & Material Backflushing.

 

Average Cost environment.

 

MES “Report Quantity” on last operation. Last Operation is marked final.

 

“Auto-Receive”, on last operation.

 

The MES reporting of “quantity only” occurs as the parts are being manufactured. In the department where the costing with backflushing doesn’t work, we report quantity over a period of time as the parts are being manufactured.  

 

Last operation was set up with a production standard. I have read postings in this forum that if last operation is a quantity only, the operation should not have a production standard.

 

It has been suggested to add a dummy operation such as “inspect” should be added to the MOM with  a count only, auto receive and   without production standards. Any thoughts on if this will work?  Or why backflushing is not working?

J Savastio

 



Stephen Edginton (Beng) | Solutions & Technical Director

Mobile:  +44 7734 858415
DDI:  +44 121 314 1179
Main:  +44 (0) 121 314 1170
Web:  www.dotnetit.co.uk

Dot Net IT Limited, One St Kenelm Court, Steel Park Road, Halesowen, B62 8HD, United Kingdom.

DotNetIT

Epicor Platinum Partner

Epicor Alliance Partner


 

The
problem is that the full cost of the parts are not reflected as the part is
auto received to stock.  Labor and burden
missing on the first receipt when backflushing labor. Seems the quantity receipt
to stock is occurring prior to backflushing the labor of prior operations.

 

 

Significant
variances are being created from manufacturing jobs (MFG-VAR).

 

We
are set up as follows:

 

Labor
& Material Backflushing.

 

Average
Cost environment.

 

MES
“Report Quantity” on last operation. Last Operation is marked final.

 

“Auto-Receive”,
on last operation.

 

The
MES reporting of “quantity only” occurs as the parts are being manufactured. In
the department where the costing with backflushing doesn’t work, we report quantity
over a period of time as the parts are being manufactured.  

 

Last
operation was set up with a production standard. I have read postings in this
forum that if last operation is a quantity only, the operation should not
have a production standard.

 

It
has been suggested to add a dummy operation such as “inspect” should be added
to the MOM with  a count only, auto
receive and   without production standards. Any thoughts on
if this will work?  Or why backflushing
is not working?

J
Savastio