|
the # transaction gets logged whenever a cost is changed via CST100 cost maintenance. typically this is material cost standards. most other costs are generated via CST600 (load cost standards from routings) and CST500 (cost roll up). when these programs are run they generate the mfg cost standards from the routings and then roll them up. i change to any of the following fields (this may not be a complete list) will cause these programs to generate different cost standards lot size order policy set-up time run time set up labor rate run labor rate b/m qty per scrap factor (?) effectivity dates one other thing that you could do would be to write a query that save the cost stds. then after the cost roll ups, compare the new standards to the prior standards. it will tell you what changed, but not why it changed. but you should be able to track down any significant changes while it is still fresh. but this takes time and a lot of investigative work. >>> lopeze@xxxxxxxxxxxxxxxxx 12/07/04 10:14AM >>> Hi, A manager came to me and asked me if there's a way to know who made a change to the costs and I told him let me see... so, the first thing I thought was, if I go to the CMF table I might know that but for my surprise that table doesn't have the last change user, then I went to the ITH and made a SQL query to get all records within the last two months with transaction type "#" and it did return some records which is ok... however I was expecting more records so I removed the transaction date filter and again it didn't return me the expected records... so I'm wondering if there's a table where I can get that information... any help will be very appreciated Thank you, Eduardo Lopez Windows/Web Developer Tyco Plastics & Adhesives +1 (619) 424-4244 (US) +52 (664) 647-4359 (Mexico) lopeze@xxxxxxxxxxxxxxxxx <mailto:lopeze@xxxxxxxxxxxxxxxxx> Confidentiality Notice This transmission (including any attachments) contains information which is confidential and is intended solely for the individual or entity named above. Any interception, copying, distribution, disclosure or other use of this transmission or any information contained in it is strictly prohibited, and may be subject to criminal and civil penalties. If you have received this transmission in error, please immediately send a mail to lopeze@xxxxxxxxxxxxxxxxx <mailto:lopeze@xxxxxxxxxxxxxxxxx> , delete the transmission from all forms of storage and destroy all hard copies. Thank you Notificación de Confidencialidad Esta transmisión (incluyendo cualquier anexo) contiene información que es confidencial y es pensada solamente para el individuo o entidad nombrada arriba. Cualquier interceptación, copiado, distribución, exhibición o cualquier otro uso de esta transmisión o cualquier información contenida en este esta terminantemente prohibida, y puede estar sujeto a penas criminales y civiles. Si usted ha recibido esta transmisión por error, por favor envié inmediatamente un correo a <mailto:lopeze@xxxxxxxxxxxxxxxxx> lopeze@xxxxxxxxxxxxxxxxx, borre la transmisión de todas las formas de almacenaje y destruya todas las copias en papel. Gracias. _______________________________________________ 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. Delivered-To: cdoe@xxxxxxxxxxxxxxxxxxxxx
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.