+- Oracle Forum - The Knowledge Center for Oracle Professionals - Looking Beyond the Possibilities (http://www.oraerp.com)
+-- Forum: Oracle Applications (http://www.oraerp.com/forum-39.html)
+--- Forum: Oracle Tutorials, Articles, eBooks, Tools & Tips (http://www.oraerp.com/forum-12.html)
+--- Thread: Smart Receipts concept in Oracle Fusion (/thread-72384.html)
Smart Receipts concept in Oracle Fusion - Gordon Victor - 05-24-2017
There are four rules:
• Customer recommendation Threshold - The qualifying percentage necessary to add customer information to a receipt. If the calculated score for a customer account number is above this threshold, then the AutoApply process adds this customer information to the receipt. The system will provide recommended matches if it does not find a match within the threshold.
First, the system uses references with a payment to disposition the payment – this value is meant to be used when you are only getting customer information with the payment and will be used to determine the match percentage to assign a customer to the payment. The system will not do both customer and transaction matching, they are mutually exclusive – you either match the customer or the transactions. Most scenarios would be transaction based.
• Minimum Weighted Threshold) - The qualifying percentage necessary to define the relative importance of customer, transaction and amount matches when deciding the final match score. If the calculated score for one or more transactions is above this threshold, the AutoApply process recommends the transactions for receipt application, in order of the highest percentage match.
NOTE: The minimum match threshold must be less than the customer recommendation threshold and the combined weighted threshold.
If the value being evaluated does not exceed the threshold, a recommendation will be created for the user to review. But, think about values that could be recommended that only have a 5%, if the system presented this low of a value, there would be too many recommendations to be useful, so we establish a minimum.
• (Combined Weighted Threshold) - The qualifying percentage necessary for the AutoApply process to apply a receipt to a transaction automatically. This percentage is the sum (always 100%) of the qualifying percentages defined for the supplied customer information, transaction information, and actual transaction amount that is considered for receipt matching.
It is combined weighted matches because you can set percentages to weight what to evaluate, for example I can match partially on the values provided and partially on the amount. If this is set to 90%, then a resulted matched weight of 90% will result in the system automatically applying it. This is similar to the customer minimum, but for transaction based matching.
• (Days of closed Invoices Threshold) - Determines which closed transactions to include in the AutoMatch process. All transactions that were closed on or before the number of days provided as the threshold value are considered for application or recommendation.
This can be used if the customer suspects the payment may relate to a closed invoice. The invoice could have been adjusted, paid by another payment etc. The system will not only look for open items to evaluate, it will also look at closed items. If the customer does not suspect closed invoices, it should be set to 0 as it will take more time to process.