Project:
View Revisions: Issue #36621 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0036621: It is possible to use UOM conversions of other clients in some callouts. | ||
Revision | 2017-08-07 15:20 by markmm82 | ||
Description | It is possible to use UOM conversions of other clients in some callouts. UOM conversions can be defined with different rates according the client using them. For instance, for a client one Bag can be defined as 100 Kg, but to other client one Bag could be 100.25 Kg. Currently, some callouts are using the multiplyRate and divideRate of SL_Invoice_Conversion_data.xsql, these methods are not taking into account the session's client and it is causing that can be used incorrect conversions. It is necessary to filter by client when searching for UOM conversions to avoid use an incorrect conversion. You will find this bug in the following callouts: - SL_CreateFromMultiple_Conversion - SL_CreateLines_Conversion_UOM - SL_GlobalUse_Conversion - SL_InOut_Conversion - SL_Internal_Consumption_Conversion - SL_Inventory_Conversion - SL_Invoice_Conversion - SL_Movement_Conversion - SL_Order_Conversion - SL_Production_Conversion - SL_SequenceProduct_Conversion |
||
Revision | 2017-08-07 15:08 by markmm82 | ||
Description | It is possible to use UOM conversions of other clients in some callouts. UOM conversions can be defined with different rates according the client using them. For instance, for a client one Bag can be defined as 100 Kg, but to other client one Bag could be 100.25 Kg. Currently, some callouts are using the multiplyRate and divideRate of SL_Invoice_Conversion_data.xsql, these methods are not taking into account the session's client and it is causing that can be used incorrect conversions. It is necessary to filter by client when searching for UOM conversions to avoid use an incorrect conversion. |
Copyright © 2000 - 2009 MantisBT Group |