You cannot change the item number on an order line (ECL) after picking. The
IPP carries order #, line #, and item # and your pick slip provides specific
info to the warehouse as to which items (lots and containers) a user is to
pick from which locations (if you're using allocations then this info is in
ELA - also keyed by order #, order line, and item #). The new item should
be added to the order as a new order line which may then be pick released
successfully. If the old line is no longer valid, it may be closed, but
very few other changes should be made since data integrity will be impacted.
Hope this helps,
[mailto:bpcs-l-bounces+bpcs=easolutions.net@xxxxxxxxxxxx] On Behalf Of
Sent: Tuesday, August 12, 2008 3:58 AM
To: BPCS ERP System
Subject: [BPCS-L] BPCS Pick release process
When an order is Pick Released it creates an IPP record and the order
and line status are set to Ready for Pick Confirm.
If the item number is changed then the order and line statuses
are set back to Ready to Pick Release, but the IPP record from the first
Pick Release still exist in the file.
When the user tries to Pick Release the order again, it appears
to the user that this works; however, the status flags continue to be
set at Ready for Pick Release and the user cannot do Pick Confirm.
We need to determine:
a. How should this work?
b. Should the flag status stay at Ready for Pick Confirm and should
the existing IPP record be updated?
c. Should the flag status be reset to Ready for Pick Release and
the IPP record deleted?
d. What needs to be change so that this works correctly?
CGI c/o COTT
T: (022) 28291421 x261
F: (022) 28291818
Link: 978-946-3400 x8827/x8828
CONFIDENTIALITY NOTICE: Proprietary/Confidential Information belonging
to CGI Group Inc. and its affiliates may be contained in this message.
If you are not a recipient indicated or intended in this message (or
responsible for delivery of this message to such person), or you think
for any reason that this message may have been addressed to you in
error, you may not use or copy or deliver this message to anyone else.
In such case, you should destroy this message and are asked to notify
the sender by reply mail.
[mailto:bpcs-l-bounces+neeraj.sarougi=cgi.com@xxxxxxxxxxxx] On Behalf Of
Sent: Monday, August 11, 2008 6:13 PM
To: BPCS ERP System
Subject: Re: [BPCS-L] RAR Downstream
Then you can query file PGMREF to find all the pgms that reference file
RAR (or any other file).
The WHFUSG filed in PGMREF will tell you whether a pgm is using the file
for Input/Output or Update.
Hope this helps,
Colin Hadley.> Date: Sun, 10 Aug 2008 10:03:33 -0500> To:
bpcs-l@xxxxxxxxxxxx> From: macwheel99@xxxxxxxxxx> Subject: [BPCS-L] RAR
Downstream> > We're 405 CD on V5R1 long gone off OSG.> > We have BPCS
tech support, but management not authorize call them unless > emergency.
Instead I get string of challenges to figure out.> > Latest: A/R to be
handled by another system outside of BPCS to get its info > from BPCS
billing process, such as A/R invoice register, then invoice input > to
RAR file, after cut-off date, to be deleted. Invoices prior to cut-off >
date to be processed old way. SIL invoice file remain intact, since it >
used in massive followup to support customer service inquiry, and price
increase analysis.> > I can write program to mass delete RAR on
invoices after cut-off date. My > concern is unintended consequences
downstream, so that I can have > alternative arrangements in place
before they needed, instead of end-fiscal > time discovering mountains
of problems. !
Other than invoices awaiting > customer payments, and where we apply
credit debit memos, where else does > BPCS use RAR file data? I don't
use XRF because in 405 CD its security > corrupts.> > For example, do
ACR230 customer ranking and SAL300 sales history get info > from RCM
customer master, which in turn from summarization of RAR? Where > in
shipping billing cycle are SSH SSD history totals populated with latest
sales?> > I desire to know what else will be zapped due to RAR mass
deletions, > because it relies on RAR content, so we can evaluate which
of that we can > live without, and which needs some replacement system.>
-> Al Macintyre> Never Knowing enough about BPCS> > > -- > This is the
BPCS ERP System (BPCS-L) mailing list> To post a message email:
BPCS-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,>
> or email:
BPCS-L-request@xxxxxxxxxxxx> Before posting, please take a moment to
e archives> at http://archive.midrange.com/bpcs-l
.> > Delivered-To:
Get more from your digital life. Find out how.
As an Amazon Associate we earn from qualifying purchases.