|
Hey Kevin, Thanks for the information... I think this file may work for what we need. Thanks to all for your input and help! Regards, Dave Zoll BlueWave Consulting, Inc. -----Original Message----- From: bpcs-l-bounces+dzoll=bluewaveconsulting.net@xxxxxxxxxxxx [mailto:bpcs-l-bounces+dzoll=bluewaveconsulting.net@xxxxxxxxxxxx] On Behalf Of washburnccinc@xxxxxxx Sent: Monday, May 22, 2006 11:37 AM To: bpcs-l@xxxxxxxxxxxx Subject: Re: [BPCS-L] BPCS 6.0.02 Kit Processing Dave, Have you looked at the KAO file yet? Caution because the records do not stay in the file forever. Kevin Washburn -----Original Message----- From: David J. Zoll <DZoll@xxxxxxxxxxxxxxxxxxxxxx> To: 'SSA's BPCS ERP System' <bpcs-l@xxxxxxxxxxxx> Sent: Sun, 21 May 2006 13:49:24 -0400 Subject: Re: [BPCS-L] BPCS 6.0.02 Kit Processing Kevin, I understand those values... thanks... but here is the situation I want to define: Say that Item "A" and Item "B" are Kits. They both share a component "C". If both Items "A" and "B" are on the order, this will mean that "C" could be on the order twice. I want to be able to track the specific "C" item line back to "A" or "B" depending on which it belongs. I didn't know if BPCS stored a line value anywhere that says this line belongs to that line... type of thing. Regards, Dave Zoll -----Original Message----- From: bpcs-l-bounces+dzoll=bluewaveconsulting.net@xxxxxxxxxxxx [mailto:bpcs-l-bounces+dzoll=bluewaveconsulting.net@xxxxxxxxxxxx] On Behalf Of WASHBURNCCINC@xxxxxxx Sent: Saturday, May 20, 2006 9:37 PM To: bpcs-l@xxxxxxxxxxxx Subject: Re: [BPCS-L] BPCS 6.0.02 Kit Processing Look at the LCPNT field in the ECL. The parent line should have a "P" and the component lines will have a "Y". Regular line items have an "N". The components should be in sequence right after the Parent Record. Hope that helps Kevin Washburn
As an Amazon Associate we earn from qualifying purchases.
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.