|
we're on version 6.1.2. i cannot find where the THLIN field is populated using standard BPCS transactions. the only place where i think it could be is if you use the generate work order from customer order / line option, which we do not use. we have orders where we get the same part number on multiple lines, usually with different ship dates. i need to track various inventory transaction back to the customer order / line. what i've done is to use the comments field to include the line number. the comment field is available on the INV500 screen. then we have a data base trigger program that runs every time an ITH record is created. it scans the comments field, which does get populated on ITH, and if it finds a valid line number it then populates this into the ITH record being created. this is not a perfect solution, but with some discipline it pretty much works. chick doe barton instrument systems >>> rkonda@xxxxxxxxx 03/19/03 11:54AM >>> Hello Everybody We've an application calling INV500B1 to post a stock transation with a transaction effect similar Adjust, so we've to control the line number in ITH File. We tried to use the fields that populate THLIN or THRSEQ, but bacause of transaction effect, the INV500B1 program doesn't populate this Fields. Does Anybody have a suggestion how field use in DS into INV500B1? We're 6004MM. Thanks in advance. Renato _________________________________________________________ Voce quer um iGMail protegido contra vfrus e spams? Clique aqui: http://www.igmailseguro.ig.com.br _______________________________________________ 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.
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.