Diego.ruiz: Categorize and tag

2022-09-02T12:53:16Z

Categorize and tag

CarlosRuiz: CarlosRuiz moved page NF9.1 Extending CommissionCalc to NF9 Extending CommissionCalc

2021-12-25T12:03:37Z

CarlosRuiz moved page NF9.1 Extending CommissionCalc to NF9 Extending CommissionCalc

CarlosRuiz at 12:00, 25 December 2021

2021-12-25T12:00:22Z

Diego.ruiz: Created page with "='''Feature:''' Custom Commission calculations= '''Goal:''' Extensibility '''Developer:''' Diego.ruiz '''Feature Ticket:''' [https://idempiere.atlassia..."

2021-12-21T17:51:45Z

Created page with "='''Feature:''' Custom Commission calculations= '''Goal:''' Extensibility '''Developer:''' Diego.ruiz '''Feature Ticket:''' [https://idempiere.atlassia..."

New page

='''Feature:''' Custom Commission calculations=

'''Goal:''' Extensibility

'''Developer:''' [[User:Diego Ruiz|Diego.ruiz]]

'''Feature Ticket:''' [https://idempiere.atlassian.net/browse/IDEMPIERE-5119 IDEMPIERE-5119]

'''Description:'''
The core commission feature works well but it is limited. Usually, every company has a different way of calculating commissions. The goal of this ticket is to make the process that calculates the commission extensible, in a way that every implementation has the flexibility to mix their own rules with iDempiere ones without having to copy the whole class.

==Development==
To extend the CommisionCalc process that is run when clicking "Generate Commission". You need to extend CommissionCalc from your custom class and in your Process factory return your custom class when the class name = ""org.compiere.process.CommissionCalc"".

Methods that you can override within your custom class.

'''doIt''': In case you want to do something completely different.

'''setStartEndDate:''' Sets the start and end date to parse the documents from which the commission will be calculated.

'''createCommissionRun''': In case you want to set special values to the created commission run

'''getCommissionRunDescription:''' If you want to set a special description to the created commission run. By default, the description is set to Start date - End Date - Currency symbol

'''getCommissionCalculationSQL''': This is the method that defines the SQL statement used to create the commission line details.

'''getPaymentCommissionSQL, getOrderCommissionSQL, getInvoiceCommissionSQL:''' Defines the SQL statement to set in the commission lines details based on Payment, Order, Invoice respectively. The query by default sets the columns in this order: Currency ID, Commission Amt, Qty, C_OrderLine_ID, C_InvoiceLine_ID, Reference, Info, Date. If you change this order, you need to override the createDetail method as well.

'''createDetail:''' Creates the commission detail based on the SQL query created with the methods explained above.

==Example==
Let's say your company has a rule for commissions where the commission for sales orders is calculated based on the margin (sales price - purchase price) and not on the total.

''The explanation of where to get the purchase price is out of the scope of this guide and it will be assumed that there's a CUSTOM_PurchasePrice column in C_OrderLine that contains the purchase price of the selected product.''

In this case, all you need to do is create a class like this to override the getOrderCommissionSQL with the right amount:<syntaxhighlight lang="java">
public class CUSTOM_CommissionCalc extends CommissionCalc {

protected String getOrderCommissionSQL() {
StringBuilder sql = new StringBuilder();
if (m_com.isListDetails())
{
sql.append("SELECT h.C_Currency_ID, l.LineNetAmt - (l.CUSTOM_PurchasePrice*l.QtyOrdered) AS Amt, l.QtyOrdered, ")
.append("l.C_OrderLine_ID, NULL, h.DocumentNo,")
.append(" COALESCE(prd.Value,l.Description),h.DateOrdered ")
.append("FROM C_Order h")
.append(" INNER JOIN C_OrderLine l ON (h.C_Order_ID = l.C_Order_ID)")
.append(" LEFT OUTER JOIN M_Product prd ON (l.M_Product_ID = prd.M_Product_ID) ")
.append("WHERE h.DocStatus IN ('CL','CO')")
.append(" AND h.IsSOTrx='Y'")
.append(" AND h.AD_Client_ID = ?")
.append(" AND h.DateOrdered BETWEEN ? AND ?");
}
else
{
sql.append("SELECT h.C_Currency_ID, SUM(l.LineNetAmt-(CUSTOM_PurchasePrice*l.QtyOrdered)) AS Amt,")
.append(" SUM(l.QtyOrdered) AS Qty, ")
.append("NULL, NULL, NULL, NULL, MAX(h.DateOrdered) ")
.append("FROM C_Order h")
.append(" INNER JOIN C_OrderLine l ON (h.C_Order_ID = l.C_Order_ID) ")
.append("WHERE h.DocStatus IN ('CL','CO')")
.append(" AND h.IsSOTrx='Y'")
.append(" AND h.AD_Client_ID = ?")
.append(" AND h.DateOrdered BETWEEN ? AND ?");
}
return sql.toString();
}

}
</syntaxhighlight>

[[Category:New Features|D]]
[[Category:New Features v9.1|D]]
[[Category:New Features Development]]
[[Category:Developer documentation]]

← Older revision		Revision as of 12:53, 2 September 2022
Line 75:		Line 75:
	[[Category:New Features Development]]		[[Category:New Features Development]]
	[[Category:Developer documentation]]		[[Category:Developer documentation]]
		+	[[Category:HowTo]]
		+	[[Category:Updated2022]]

← Older revision	Revision as of 12:03, 25 December 2021
(No difference)

@@ Line 72: / Line 72: @@
 [[Category:New Features|D]]
-[[Category:New Features v9.1|D]]
+[[Category:New Features v9|D]]
 [[Category:New Features Development]]
 [[Category:Developer documentation]]

NF9 Extending CommissionCalc - Revision history

Diego.ruiz: Categorize and tag

CarlosRuiz: CarlosRuiz moved page NF9.1 Extending CommissionCalc to NF9 Extending CommissionCalc

CarlosRuiz at 12:00, 25 December 2021

Diego.ruiz: Created page with "='''Feature:''' Custom Commission calculations= '''Goal:''' Extensibility '''Developer:''' Diego.ruiz '''Feature Ticket:''' [https://idempiere.atlassia..."