• Subject: Re: Units of Measure problems in 405CD
  • From: Bill Robins <BillZBubb@xxxxxxxxxxxx>
  • Date: 13 Jul 99 08:06:23 PDT


We had problems with U/M conversions also.  Take a look at the statements
affected by BMR 42343.  What I did was restore the code it commented out AFTER
the line it added in, thus rendering the BMR void.

The commodity code problem was introduced partially by 19597 in INV920.  Look
for the following code:

     C**         THQUM     MULT IUMCN     WRK002 309H   
A1d  C*          REVQTY    MULT IUMCN     WRK002 309H   
A1a  C                     Z-ADDREVQTY    WRK002 309H   
     C           WRK001    MULT WRK002    PSTAMT 309H  
     C                     ELSE                        
     C           PECST     MULT CCNVFC    PSTAMT 309H  
A1a  C                     MULT REVQTY    PSTAMT    H  

The pertinent lines are the "A1d" (line deleted) and "A1a" (line added), (I
included the others to help you locate the relevant code.


KLChilds@aol.com wrote:
well.....several......we have run into problems with journal entries created 
by the inventory sub system dealing with unit of measure conversions, 
problems with commodity codes reversing the debits and credits, and a few 
others....anybody else had these kind of problems ??

Get your own FREE, personal Netscape WebMail account today at 
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com.
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: dasmussen@aol.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 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].