http://wavelet.asia/customer-portal/?p=7741
After creating a main credit control scheme, you need to create rules. Rules define what should happen between certain periods of time. For example, invoices that are outstanding for the first 30 days, are okay, but if it is longer than 30 days. you may not create any more invoices for the customer to whom the outstanding invoice belongs to. You will need to create 2 rules to recreate this scenario. The first rule specifies the time period for which it is okay for an invoice to remain outstanding, and the second rule specifies the time period for which an outstanding invoice must fall into to block that customer from having more invoices created in its name.
The Screen
Description of the screen above follows:
1. Credit Terms Control Code: Enter an existing credit terms main code. If it exists, it will load all rules that belong to that scheme.
2. Code: Enter a code for your credit terms rule. Should not be more than 100 characters.
3. Name: Enter a name for your credit terms rule. Should not be more than 1000 characters.
4. Description: Add a short description to your credit terms rule. Should not be more than 5000 characters.
5. Action: Currently there are only 2 actions: normal and block_invoice. These should be self-explanatory. More actions may be added in the future, such as warning the user, but still allowing invoice creation.
6. Date Start Set: This set of fields will help define the starting point of the date range to determine if the current date falls within the rule date range. This is calculated by taking an invoice's transaction date, and replacing the date's individual elements with the values specified in the corresponding fields.
For example:
The diagram above shows 0 for Year, 0 for Month and 0 for Day. Let's say the current date is 13 April 2009. The invoice's transaction date currently being tested is 26 March 2009. Placing a 0 in any of these fields means to leave the current date values alone, it will not set the respective date values with any new value. To create the starting point of the the rule date range, we set Year 0 to 2009 = 2009, Month 0 to March(03) = March, and Day 0 to 26 = 26. Therefore, the starting point of the exception date range is 26 March 2009. You should not set more than 31 for Day field and 12 for Month field. Setting the value to 40 tells the system to use the last day of that particular month (30 for April, 31 for May, 28 or 29 for Feburary depending on leap year conditions).
7. Date Start Add: This set of fields will help define the starting point of the rule date range. This is calculated by adding the specified values to the previously-modified date. For example, using the previously-modified date of 26 March 2009, we add Year 0 to 2009, Month 2 to March(03) = May(05), and Day 1 to 26 = 27. This brings the final starting point of the exception date range to 27 May 2009. If the values specified in the Day and Month field would bring the value to more than the upper limit of the Month/Day field (based on month's maximum days), it will adjust the Year and Month portions accordingly. Setting the value to 40 tells the system to use the last day of that particular month (30 for April, 31 for May, 28 or 29 for Feburary depending on leap year conditions).
8. Date End Set: This set of fields help define the ending point of the rule date range. It works the same way as Date Start Set. In the previous example, the invoice date (26 March 2009) will be modified to 31 December 9999.
9. Date End Add: This set of fields also help define then ending point of the rule date range, in the same way as Date Start Add. In the previous example, 31 December 9999 will be modified to 31 December 9999 (no change, since all the fields are set to 0).
We now have a date range for the NEXT-BLOCK rule, from 27 May 2009 to 31 December 9999, based on the transaction date of one particular invoice whose transaction date is 26 March 2009. If the current date does not fall into this range (e.g. 13 April 2009), then the rule's action (e.g. block_invoice) does not take place. If the current date actually falls into this range (e.g. 30 May 2009). then the rule's action takes place. In this case, since this invoice has fallen into the NEXT-BLOCK rule's date range, it will stop all new invoices from being created for this customer, until this invoice (and all other invoices) which activate this rule have been settled and are no longer outstanding. All outstanding invoices for a certain customer will have to go through all the rules that belong to this credit control scheme, and if any of those invoices fall into a certain rule's date range, those rules' actions will take place.
NOTE: please be careful when creating rules, ensure that date ranges for each rule do not overlap each other. Complications may occur and will result in the function not working correctly.
10. Save/Cancel: Save a new rule, save changes to an existing rule or cancel any changes.
11. Edit/Remove: Edit or delete an existing rule.
As a side note, calculations for setting and adding modifications to the dates will always follow this rule: apply the set portions first before applying the add portions. Then apply year first, then month, then day.
Learn how to define a new scheme here.
The Screen
Description of the screen above follows:
1. Credit Terms Control Code: Enter an existing credit terms main code. If it exists, it will load all rules that belong to that scheme.
2. Code: Enter a code for your credit terms rule. Should not be more than 100 characters.
3. Name: Enter a name for your credit terms rule. Should not be more than 1000 characters.
4. Description: Add a short description to your credit terms rule. Should not be more than 5000 characters.
5. Action: Currently there are only 2 actions: normal and block_invoice. These should be self-explanatory. More actions may be added in the future, such as warning the user, but still allowing invoice creation.
6. Date Start Set: This set of fields will help define the starting point of the date range to determine if the current date falls within the rule date range. This is calculated by taking an invoice's transaction date, and replacing the date's individual elements with the values specified in the corresponding fields.
For example:
The diagram above shows 0 for Year, 0 for Month and 0 for Day. Let's say the current date is 13 April 2009. The invoice's transaction date currently being tested is 26 March 2009. Placing a 0 in any of these fields means to leave the current date values alone, it will not set the respective date values with any new value. To create the starting point of the the rule date range, we set Year 0 to 2009 = 2009, Month 0 to March(03) = March, and Day 0 to 26 = 26. Therefore, the starting point of the exception date range is 26 March 2009. You should not set more than 31 for Day field and 12 for Month field. Setting the value to 40 tells the system to use the last day of that particular month (30 for April, 31 for May, 28 or 29 for Feburary depending on leap year conditions).
7. Date Start Add: This set of fields will help define the starting point of the rule date range. This is calculated by adding the specified values to the previously-modified date. For example, using the previously-modified date of 26 March 2009, we add Year 0 to 2009, Month 2 to March(03) = May(05), and Day 1 to 26 = 27. This brings the final starting point of the exception date range to 27 May 2009. If the values specified in the Day and Month field would bring the value to more than the upper limit of the Month/Day field (based on month's maximum days), it will adjust the Year and Month portions accordingly. Setting the value to 40 tells the system to use the last day of that particular month (30 for April, 31 for May, 28 or 29 for Feburary depending on leap year conditions).
8. Date End Set: This set of fields help define the ending point of the rule date range. It works the same way as Date Start Set. In the previous example, the invoice date (26 March 2009) will be modified to 31 December 9999.
9. Date End Add: This set of fields also help define then ending point of the rule date range, in the same way as Date Start Add. In the previous example, 31 December 9999 will be modified to 31 December 9999 (no change, since all the fields are set to 0).
We now have a date range for the NEXT-BLOCK rule, from 27 May 2009 to 31 December 9999, based on the transaction date of one particular invoice whose transaction date is 26 March 2009. If the current date does not fall into this range (e.g. 13 April 2009), then the rule's action (e.g. block_invoice) does not take place. If the current date actually falls into this range (e.g. 30 May 2009). then the rule's action takes place. In this case, since this invoice has fallen into the NEXT-BLOCK rule's date range, it will stop all new invoices from being created for this customer, until this invoice (and all other invoices) which activate this rule have been settled and are no longer outstanding. All outstanding invoices for a certain customer will have to go through all the rules that belong to this credit control scheme, and if any of those invoices fall into a certain rule's date range, those rules' actions will take place.
NOTE: please be careful when creating rules, ensure that date ranges for each rule do not overlap each other. Complications may occur and will result in the function not working correctly.
10. Save/Cancel: Save a new rule, save changes to an existing rule or cancel any changes.
11. Edit/Remove: Edit or delete an existing rule.
As a side note, calculations for setting and adding modifications to the dates will always follow this rule: apply the set portions first before applying the add portions. Then apply year first, then month, then day.
Learn how to define a new scheme here.