Re: Pick Confirmation

Hi Mark,

I am currently working for a client who also uses Pick confirm as opposed to
Ship confirm.

I have never seen a situation like this after a session crash, usually it is
just a matter of resetting the in use flag and a few files for the order
that was being processed at the time.  However, I have seen a situation
happen where all allocated orders for a warehouse have been confirmed
because a user has pressed F6 from the first screen (ORD570D1-01) - but none
of the files got corrupted.  Is it possible that this has happened on your
system?

In our case we took away the F6 functionality!  This is in V6.0.02 MM which
I think is the same.

I don't know if this helps you ... it may give you something to consider.

Sally

Director - Small Blue Ltd
www.smallblue.co.uk
Tel:  +44 (0) 1737 824246
----- Original Message ----- 
From: "Richards, Mark" <richarma@xxxxxxxxxxxx>
To: <bpcs-l@xxxxxxxxxxxx>
Sent: Thursday, January 15, 2004 1:50 PM
Subject: Pick Confirmation


> 1. We are on 6.1.2MM.
> 2. We do not use ship confirmation.  We use pick confirmation (creates
> the B transactions, BBH/BBL records etc..).
> 3. During pick confirmation a user lost connectivity.
> 4. Shortly afterwards another user, pick confirming one order, shipped
> 159 orders!  We had to adjust inventory, issue credits, etc.
>
>
>
> We are currently tracing the job stream (EWR, etc.) but wondered if anyone
> else has had this problem.  If so, what files did you find that were
> corrupted?
>
>
>
> This is not the first time this has occurred and I want to put into place
an
> SOP (what to cleanup in BPCS and how to process the orders that were in
the
> midst of being pick confirmed) to address this issue if it occurs again.
> Any input is appreciated.
>
>
>
> Thank you.
>
>
>
>
>
> Mark
>
>
>
> _______________________________________________
> This is the SSA's BPCS ERP System (BPCS-L) mailing list
> To post a message email: BPCS-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/bpcs-l
> or email: BPCS-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/bpcs-l.
>
>