The Day End process can be a complex and confusing part of Horizon. This is especially true with the addition of SMS messages to the process. This troubleshooting section provides you with a step-by-step approach to determining if there is a problem with your Day End configuration for SMS messaging.
If you are having problems, you should first go through the troubleshooting for the SMS processor (see SMS Processor Troubleshooting).
If the Horizon Day End process would not generate a particular day end notice were SMS not enabled, then when SMS is enabled, the corresponding SMS notice will not be generated either.
The parameters required to generate a Day End SMS notice are in addition to the parameters required to generate a regular Day End notice.
Day End troubleshooting is divided into the following sections:
• | General Day End Troubleshooting |
• | Overdue Notice Troubleshooting |
• | Hold Notice Troubleshooting |
• | Pre-Overdue Notice Troubleshooting |
General Day End Troubleshooting
Check all of the following things, regardless of the type of SMS notice to be generated:
1. | Ensure that the type of notice has been enabled in the sms_control table of Horizon. |
Check the system default and the exceptions areas of the table.
Ensure that the checkbox for the desired notice type is selected. For example, Enable SMS Pre Overdue Notice, Enable SMS Overdue Notice, or Enable SMS Hold Notice.
For more information, see Enabling SMS messaging.
2. | Ensure that the borrower has opted in to receive the desired SMS notice. |
Verify this in the borrower record, in the SMS notice area. The borrower only receives SMS messages for the notice types that have been selected.
For more information, see Editing Borrower Records for SMS.
3. | Verify that the phone type is sms-enabled. |
For more information, see Enabling SMS for a phone type.
4. | Make sure that the DeSMS (Generate Day End SMS Notices) process has been set up to run in Day End. |
The DeSMS processs should run after DeOverdue (Day End Set Overdues) and before DeTcPhone (Generate Telephone Messaging Notices) and DeNotices (Generate Notices).
To specify this, go to Administration > Table Editor > menu. Move Generate Day End SMS Notices from MDESave to MDayEnd. Use the Option No field to control the sequence placement of each process in the list.
For more information, see Enabling the SMS day end process.
5. | Check the burb table to ensure that the borrower does not have a pcr (Phone Correction Requested) block. |
If the borrower has a pcr block, no SMS notices will be generated for that borrower.
6. | Check dayend_activity to see if there was an error for DeSMS. |
To do this, go to Administration > Day End Processes > Day End Activity Log.
Overdue Notice Troubleshooting
For overdue notices, check the following:
1. | Check the burb table for the borrower to ensure that there is an od block for an item. |
2. | Check the od block in the burb table for the last "noticeX" block where X is the notice number. |
Verify that the notice_print flag is set to 0 (meaning, printed).
No additional notices will be sent to the borrower if the last notice has not been printed.
For information about how to print notices, see the Circulation User's Guide.
3. | Verify that it is time to generate the next SMS overdue notice by checking the circ_privilege_code table. |
You must check the following variables based on either the item's location or the circ location, depending on the selection specified in the matham table's Circ Settings by property:
a. | First Notice Delay - The system generates the first notice when the current date is greater than or equal to the value of the date in the od block plus the delay specified here (currentDate >= (odBlockDate + firstNoticeDelay)). |
b. | Notice Interval - The system generates the next notice when the current date is greater than or equal to the value of the date of the last notice sent plus the delay specified here (currentDate >= (previousNoticeSentDate + noticeInterval)). |
c. | Maximum Number of Notices - The system stops sending overdue notices when the maximum number has been reached. |
Note: If you make any changes to the Circ Privilege Codes, you must restart Horizon before continuing.
For additional information about the Circ Settings by property, see "Setting Up Circulation Privileges and Parameters" the Circulation Setup Guide or "Setting Up Circulation Privileges Tracking" in the System Administration Guide.
4. | Ensure that the item has not been overdue for too long and automatically set to "Lost". |
In the location table, check the value for Overdue To Lost (Days). Compare this with the overdue date of the item.
5. | Compare the item number in the burb table with the item number in the item table to verify that it is still a valid item. |
6. | Compare the borrower number in the burb table with the borrower number in the borrower table to ensure that the borrower is still valid. |
7. | Compare the item number, item status, and borrower number in the burb table with the same information in the item table. |
If the values do not match, the system will not generate an SMS overdue notice for this item.
8. | Ensure that the item status is o (out). |
If the status is not "out", the system will not generate an SMS overdue notice for this item.
9. | Check the burb table to see if the odsms# (where # is the notice number) or odsmsF block is being generated for the borrower. |
If the system generates the block for the current session of the Day End process, the problem is probably not the SMS Day End process.
10. | The notice text must be set up in the block table. |
For more information, see Configuring the SMS overdue notification blocks
For hold notices, check the following:
1. | Check the burb table for the borrower to ensure that there is an hnsms block when the requested item is filled. |
If hnsms is not generated, check the troubleshooting steps detailed in General Day End Troubleshooting .
All the parameters that would affect the appearance of a non-SMS hold notice must be configured correctly in order for SMS hold notices to work.
2. | Compare the item number, item status, and borrower number in the burb table with the same information in the item table. |
If the values do not match, the system will not generate an SMS hold notice for this item.
3. | Ensure that the item status is h (On hold). |
If the status is not "on hold", the system will not generate an SMS hold notice for this item.
4. | Verify that the hold request has not expired. |
To check this, go to Dayend run date > Request Hold Until Date.
5. | Check the hnsms block in the burb table. |
Verify that the notice_print flag is set to 0 (meaning, to be printed).
No additional SMS hold notice will be sent to the borrower if the notice_print flag is set to 1 (meaning that an SMS hold notice was already sent).
6. | The notice text must be set up in the block table. |
For more information, see Configuring the SMS hold notification block
Pre-Overdue Notice Troubleshooting
For pre-overdue notices, check the following:
1. | Verify that it is time to generate the SMS pre-overdue notice for the borrower. |
The system generates SMS pre-overdue notices for any item due date that matches all of the following conditions:
– | Pre-Overdue Day in btype is not NULL. |
– | Item due date is greater than or equal to the Day End run date (itemDueDate >= dayEndRunDate). |
– | Item due date is greater than the value of the last pre-overdue date in the sms_control table plus the Pre-Overdue Day in btype (itemDueDate > (lastPreoverdueDate + preoverdueDay)). |
– | Item due date is less than or equal to the value of Pre-Overdue Day in btype plus the Day End run date (itemDueDate <= (preoverdueDay + dayEndRunDate)). |
2. | The notice text must be set up in the block table. |
For more information, see Configuring the SMS pre-overdue notification block
© 1998-2017 Sirsi Corporation