|
Hi Paul, I presume you meant to say "LLCC - Last Date" on ILI, instead of LLOC (which is the location code). >From what I remember on V405.CD, this field is only updated if you process any cycle count transactions thru (INV515), and this date indicates the last time cycle count transaction was made. this theory is applicable for existing ILI records. (update mode). However, when a record is added for the first time in ILI by any other means (new receipts or Mass location transfer etc..), then this field is updated with the date of such transaction and then stays unchanged until a cycle count. you may find it in ITE (Transactions effect maintenance) table - Filed name: TCC='Y' Hope this helps.. Rgds. Rizley. bpcs-l-request@xxxxxxxxxxxx Sent by: bpcs-l-bounces@xxxxxxxxxxxx 31/10/2003 02:00 Please respond to bpcs-l To: bpcs-l@xxxxxxxxxxxx cc: Subject: BPCS-L Digest, Vol 1, Issue 794 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. Last Move Date: lloc field in file: ILI (Paul LaFlamme) 2. Re: Last Move Date: lloc field in file: ILI (sally.bosman@xxxxxxxxxxxxxxx) 3. Re: Re: Last Move Date: lloc field in file: ILI (sally.bosman@xxxxxxxxxxxxxxx) 4. Re: Re: Re: Last Move Date: lloc field in file: ILI (sally.bosman@xxxxxxxxxxxxxxx) 5. Re: Re: Re: Re: Last Move Date: lloc field in file: ILI (sally.bosman@xxxxxxxxxxxxxxx) 6. Re: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI (sally.bosman@xxxxxxxxxxxxxxx) 7. Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI (sally.bosman@xxxxxxxxxxxxxxx) 8. Re: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI (sally.bosman@xxxxxxxxxxxxxxx) 9. Re: Re: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI (sally.bosman@xxxxxxxxxxxxxxx) 10. Re: Re: Re: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: (sally.bosman@xxxxxxxxxxxxxxx) 11. Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in (sally.bosman@xxxxxxxxxxxxxxx) 12. Re: Last Move Date: lloc field in file: ILI (David Gibbs) 13. BPCS CimPath (Janet Talalai) 14. Re: BPCS CimPath (Mike Ozanne) ---------------------------------------------------------------------- message: 1 date: Wed, 29 Oct 2003 15:28:32 -0500 from: "Paul LaFlamme" <laflammep@xxxxxxxxxxxxx> subject: Last Move Date: lloc field in file: ILI Hi everyone, here's a strange one. We're running V4.05CD and use the LLOC field on several reports. The LLOC field exists in ILI - Item Inventory Location file and is supposed to be the last move date. This doesn't seem to be the case. In many locations, a really old date exists in the field and it is not changed when adjustments are made to the location. Other items of the same type and class are stored in this particular location and the Last Move Date is updated when inventory is adjusted in or out. Anyone know what process updates that field and why it may not be working for some items? Thanks, Paul ------------------------------ message: 2 date: 29 Oct 2003 20:33:49 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Last Move Date: lloc field in file: ILI I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 3 date: 29 Oct 2003 20:37:39 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Last Move Date: lloc field in file: ILI I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 4 date: 29 Oct 2003 20:48:36 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Re: Last Move Date: lloc field in file: ILI I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 5 date: 29 Oct 2003 20:58:48 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 6 date: 29 Oct 2003 21:00:37 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 7 date: 29 Oct 2003 21:13:44 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 8 date: 29 Oct 2003 21:15:40 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 9 date: 29 Oct 2003 21:30:41 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: ILI I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 10 date: 29 Oct 2003 21:45:56 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Re: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in file: I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 11 date: 29 Oct 2003 22:00:40 -0000 from: sally.bosman@xxxxxxxxxxxxxxx subject: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Last Move Date: lloc field in I will be away from my desk until Wednesday 5th November, 2003. If you require an immediate response to your communication, please contact Clare Holtham at clare.holtham@xxxxxxxxxxxxxxx Regards Sally Bosman ------------------------------ message: 12 date: Wed, 29 Oct 2003 17:22:39 -0600 from: David Gibbs <david@xxxxxxxxxxxx> subject: Re: Last Move Date: lloc field in file: ILI At 02:33 PM 10/29/2003, you wrote: >I will be away from my desk until Wednesday 5th November, 2003. If you >require an immediate response to your communication, please contact Clare >Holtham at clare.holtham@xxxxxxxxxxxxxxx I've caught this folks ... it won't continue. david ------------------------------ message: 13 date: Wed, 29 Oct 2003 08:13:49 -0500 from: Janet Talalai <JTalalai@xxxxxxxxxxxxxxx> subject: BPCS CimPath Hello. We have been using the BPCS Cimpath system for quite some time now to collect shop floor labor. When a user scans a shop order/operation, the bar code reader has been very slow in processing the users request and move on to the next question or prompt. We have heard that the previous IT manager did something on the PC, maybe clear some data from a folder/file. Would anyone have any idea on this? Does this folder/file sound familiar? USR/TRANS/TDCTRANS???? The PC that is running CimPath is using Client Access for DOS. Thanks. Janet Talalai Philadelphia Mixers Corporation Programmer/Analyst MIS Dept 717.832.8838 <mailto:jtalalai@xxxxxxxxxxxxxxx> jtalalai@xxxxxxxxxxxxxxx ------------------------------ message: 14 date: Thu, 30 Oct 2003 10:57:39 +0000 from: Mike Ozanne <mozanne@xxxxxxxxxxxxxxxxxxxxxxxxx> subject: Re: BPCS CimPath At 08:13 29/10/03 -0500, you wrote: >Hello. > >We have been using the BPCS Cimpath system for quite some time now to >collect shop floor labor. When a user scans a shop order/operation, the >bar code reader has been very slow in processing the users request and move >on to the next question or prompt. We have heard that the previous IT >manager did something on the PC, maybe clear some data from a folder/file. > > >Would anyone have any idea on this? > >Does this folder/file sound familiar? USR/TRANS/TDCTRANS???? > >The PC that is running CimPath is using Client Access for DOS. The BPCS part of the equation will read from a member in the NIN file in your BPCS file library. What you need to do is establish the train of events that populates that member. A typical train of events is. Scanner reads barcode and writes data to a PC file, this could be anything from a txt or prn file to an SQL database file. A process is triggered on your PC which reads this file and transfers it to your AS/400, the data will be written to a workfile or maybe a DATAQ. An As/400 process will be triggered which will validate the data, add anything else that CIM needs and write the NIN member record. From the sound of things there would seem to be a glitch with either step one or two. Could be a full log or transaction file, or maybe a disk or memory space problem. ------------------------------ _______________________________________________ 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 1, Issue 794 **************************************
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.