Al,

Yes you are right.
I checked our files and # transactions are only created when records are
changed via CST100.
We do not refer to these # transactions in our procedure for changing
Standards.

Thanks and Regards,
Vincent




                                                                                
                                                      
                      Alister Wm                                                
                                                      
                      Macintyre                To:       "SSA's BPCS ERP 
System" <bpcs-l@xxxxxxxxxxxx>                                
                      <macwheel99@sigec        cc:                              
                                                      
                      om.net>                  Subject:  Re: What is a # 
transaction?                                                 
                      Sent by:                                                  
                                                      
                      bpcs-l-bounces@mi                                         
                                                      
                      drange.com                                                
                                                      
                                                                                
                                                      
                                                                                
                                                      
                      22/01/2004 19:20                                          
                                                      
                      Please respond to                                         
                                                      
                      "SSA's BPCS ERP                                           
                                                      
                      System"                                                   
                                                      
                                                                                
                                                      
                                                                                
                                                      




We are on 405 CD
We see # when CST100
We do not see # when CST500 CST600 rollup changes standard cost
Is there some system parameter that turns on/off this feature that perhaps
we missing?

The record looks to me like it is showing the NEW cost.
To find the OLD cost, find prior # on same item, unless recently had copy
into simulated costs.
Correct ?

  you wrote:
>This transaction is created when the value in the Standard Cost or any
>other Cost Bucket is changed via CST100/CST500/CST600.
>It's merely an indication that the Std was changed on that date. It has no
>other effect.
>
>Regards
>Vincent
>
>
>"Paul LaFlamme" <laflammep@xxxxxxxxxxxxx>
>Sent by: bpcs-l-bounces@xxxxxxxxxxxx
>22/01/2004 14:12
>Please respond to "SSA's BPCS ERP System"
>
>
>         To:     <BPCS-L@xxxxxxxxxxxx>
>         cc:
>         Subject:        What is a # transaction?
>
>
>Hi!
>
>Version 4.05cd.
>
>I found a # transaction in INV300 - transaction history. The description
>of the transaction is Cost Adjustment. Anyone know what puts that out
>there?
>
>Thanks,
>
>Paul




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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.