Project:
View Revisions: Issue #38207 | [ All Revisions ] [ Back to Issue ] | ||
Summary | 0038207: API change is required due to solution of issue 38163 | ||
Revision | 2018-03-23 09:25 by aferraz | ||
Description | The fix of issue 38163 causes an API change due to some changes in the database functions. 1- C_INVOICELINETAX_ROUNDING: 1.1 - Removed the "p_linefrom" as it is always using its default value (0) and the condition (and line > p_linefrom) where it is used is always true. 1.2 - Added the new "p_stdprecision" parameter to use the standard precision of the document currency to round the taxes correctly when searching for the tax line adjustment that stays closest to the original amount. 2- C_INVOICELINETAX_ROUNDING_AMT: 2.1 - Removed the "p_linefrom" as it is always using its default value (0) and the condition (and line > p_linefrom) where it is used is always true. 3- C_INVOICETAX_ROUNDING: 3.1 - Created the new "p_stdprecision" parameter to use the standard precision of the document currency to round the taxes correctly when searching for the tax line adjustment that stays closest to the original amount. 4- C_ORDERLINETAX_ROUNDING: 4.1 - Removed the "p_linefrom" as it is always using its default value (0) and the condition (and line > p_linefrom) where it is used it is always true. 4.2 - Created the new "p_stdprecision" parameter to use the standard precision of the document currency to round the taxes correctly when searching for the tax line adjustment that stays closest to the original amount. 5- C_ORDERLINETAX_ROUNDING_AMT: 5.1 - Removed the "p_linefrom" as it is always using its default value (0) and the condition (and line > p_linefrom) where it is used it is always true. 6- C_ORDERTAX_ROUNDING: 6.1 - Created the new "p_stdprecision" parameter to use the standard precision of the document currency to round the taxes correctly when searching for the tax line adjustment that stays closest to the original amount. |
||
Revision | 2018-03-22 20:58 by aferraz | ||
Description | The fix of issue 38163 cause an API change due to some changes in the database functions. The main changes need to be approved: 1- C_INVOICELINETAX_ROUNDING: 1.1 - Removed the "p_linefrom" as it is always using its default value (0) and the condition (and line > p_linefrom) where it is used it is always true. 1.2 - Created the new "p_stdprecision" parameter to use the standard precision of the document currency to round the taxes correctly when searching for the tax line adjustment that stays closest to the original amount. 2- C_INVOICELINETAX_ROUNDING_AMT: 2.1 - Removed the "p_linefrom" as it is always using its default value (0) and the condition (and line > p_linefrom) where it is used it is always true. 3- C_INVOICETAX_ROUNDING: 3.1 - Created the new "p_stdprecision" parameter to use the standard precision of the document currency to round the taxes correctly when searching for the tax line adjustment that stays closest to the original amount. 4- C_ORDERLINETAX_ROUNDING: 4.1 - Removed the "p_linefrom" as it is always using its default value (0) and the condition (and line > p_linefrom) where it is used it is always true. 4.2 - Created the new "p_stdprecision" parameter to use the standard precision of the document currency to round the taxes correctly when searching for the tax line adjustment that stays closest to the original amount. 5- C_ORDERLINETAX_ROUNDING_AMT: 5.1 - Removed the "p_linefrom" as it is always using its default value (0) and the condition (and line > p_linefrom) where it is used it is always true. 6- C_ORDERTAX_ROUNDING: 6.1 - Created the new "p_stdprecision" parameter to use the standard precision of the document currency to round the taxes correctly when searching for the tax line adjustment that stays closest to the original amount. C_INVOICELINE_TRG2 and C_ORDERLINE_TRG2: It is needed to pass the new "p_stdprecision" parameter to use the standard precision of the currency to round the taxes correctly when the C_INVOICELINETAX_ROUNDING/C_ORDERLINETAX_ROUNDING function is called to avoid a mutant trigger issues in Oracle. |
Copyright © 2000 - 2009 MantisBT Group |