Re: Backflushing Issue

If this component has back-flushed in the past for this Parent item, on
this route, and no route overrides were made on the work order, I would
check to see if and Job Logs or IPG Dumps were printed.  This could
identify that a record lock may have occurred that crashed the update.
SYS/21, does not always end the job for a record lock. It prints a Dump
or Job Log and continues.


-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx
[mailto:system21-bounces@xxxxxxxxxxxx] On Behalf Of Jim Kerr
Sent: Wednesday, February 28, 2007 12:58 PM
To: 'System 21 Users'
Subject: Re: [SYSTEM21] Backflushing Issue

I would check the Route Operation definition. Make sure the "Reporting
Type"
on the operation is set to "2" to signify a "Backflushed Operation". 
 

-----Original Message-----
From: system21-bounces@xxxxxxxxxxxx
[mailto:system21-bounces@xxxxxxxxxxxx]
On Behalf Of Bill.Geissinger@xxxxxxxxxxxxxxxxx
Sent: Wednesday, February 28, 2007 7:27 AM
To: system21@xxxxxxxxxxxx
Subject: [SYSTEM21] Backflushing Issue

I have a user who did Item Booking for a particular item recently and
had 
a backflushing issue. 

When going into the Inventory Movements Inquiry they noticed that some
of 
the parts in the routing backflushed and some didn't.  The interesting 
thing is that previous booking and subsequent bookings have worked just 
fine.  It's just this one particular instance that this problem
occurred.

Does anyone have any ideas what might have happened or what the problem 
is?  I hate these once in a great while issues because it usually ends
up 
being a user created problem.



_______________________________________________
This is the System 21 Users (SYSTEM21) mailing list
To post a message email: SYSTEM21@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/system21
or email: SYSTEM21-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/system21.