× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Mark:
I too have seen the multiple pick confirm problem when a user bypasses the
detail confirmation screens.  EWR is just a working pick file and so is
transient in nature.  I would suspect the session disconnect and the mass
pick confirm may be coincidental, but in case it is an "undocumented
feature"  you will want to audit ECH, ECL, ECS, BBH, BBL, IIM, IWI, ILI, ITH
so you can see what data has been processed and what programs did the
processing.  If you need help with this feel free to contact me via this
list and I'll walk through the steps for you.
Martin Foglesong
Senior Technology Consultant
Verona, Inc.
PO Box 4094
Lancaster, PA 17604-4094
Phone: (717) 664-4292
Fax: (888) 256-3772
Mobile: (717) 951-8230
mfoglesong@xxxxxxxxxxxxxx


-----Original Message-----
From: bpcs-l-bounces@xxxxxxxxxxxx [mailto:bpcs-l-bounces@xxxxxxxxxxxx]On
Behalf Of bpcs-l-request@xxxxxxxxxxxx
Sent: Thursday, January 15, 2004 1:00 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: BPCS-L Digest, Vol 2, Issue 7

Send BPCS-L mailing list submissions to
        bpcs-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.midrange.com/mailman/listinfo/bpcs-l
or, via email, send a message with subject or body 'help' to
        bpcs-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
        bpcs-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of BPCS-L digest..."


Today's Topics:

   1. Pick Confirmation (Richards, Mark)
   2. Re: Pick Confirmation (Small Blue)


----------------------------------------------------------------------

message: 1
date: Thu, 15 Jan 2004 08:50:57 -0500
from: "Richards, Mark" <richarma@xxxxxxxxxxxx>
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





------------------------------

message: 2
date: Thu, 15 Jan 2004 15:51:48 -0000
from: "Small Blue" <sally.bosman@xxxxxxxxxxxxxxx>
subject: 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.
>
>




------------------------------

_______________________________________________
This is the SSA's BPCS ERP System (BPCS-L) digest 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.



End of BPCS-L Digest, Vol 2, Issue 7
************************************



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.