• # How do the overdue intervals in tab32 work?

• Article Type: General
• Product: Aleph
• Product Version: 20, 21, 22, 23

Description:
Can you please explain how exactly the intervals (col. 5 and 6) from tab32 are calculated in overdue jobs p_cir_50, p_cir_51 and p_cir_52?

Resolution:
1) For the 1st letter the system checks line with col. 4 = 00 and compares the interval between the overdue date** of the item and current date (= interval A) with the interval B defined in col. 5 (non-requested items) and col. 6 (requested items). If interval A (number of days since due days) is higher(!) than interval B (defined in tab32) the first overdue letter is printed.

** The overdue date is the z36_due_date + 1.

2) For the 2nd, 3rd,.. letter the system checks line with col. 4 = 01, 02, ... (01 for 2nd notice, 02 for 3rd notice and so on) and compares the interval between date of the last letter of the item and current date (= interval A) with the interval B defined in col. 5 (non-requested items) and col. 6 (requested items). If interval A (number of days since last letter) is higher(!) than interval B (defined in tab32) the next overdue letter is printed.

So if for example you want to define:
- The 1st letter should be printed on next day right after the due date of the item.
- All upcoming letters should be printed in a weekly interval
you may define this:

!
! 1 2 3 4 5 6 7 8
!!!!!-!!-!!-!!-!!!-!!!-!-!!!!
HIL 01 ## 00 000 000 O 0080
HIL 01 ## 01 006 006 O 0081
HIL 01 ## 02 006 006 O 0082

• Article last edited: 10/8/2013