Problem Note 61464: A project defined via monthly run-frequency might not be executed when running an alert-generation-process job in SAS® Financial Crimes Monitor
 |  |  |  |  |
In SAS Financial Crimes Monitor, you can define the monthly run-frequency via the option "The order day of every month" on the project level. The order can be First through Fifth. The day can be Sunday through Saturday. However, the monthly run-frequency dates are incorrect by one week in the fcm_job_calender database table. As a result, your project is not executed on your desired date when you run the Alert Generation Process batch job.
Example: In SAS Financial Crimes Monitor, your project has the run-frequency "The First Monday of every month". However, in the fcm_job_calender database table, the entries are pointing to the second Monday of every month. The correct value should be Nov 6th, 2017. However, in the database table, the value is Nov 13th, 2017. Similarly, the correct value should be Dec 4th 2017, but in the database table, the value is Dec 11th, 2017.
There are no errors or warnings to indicate a problem.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Financial Crimes Monitor | Microsoft® Windows® for x64 | 6.2 | |||
| 64-bit Enabled AIX | 6.2 | |||||
| 64-bit Enabled Solaris | 6.2 | |||||
| HP-UX IPF | 6.2 | |||||
| Linux for x64 | 6.2 | |||||
| Solaris for x64 | 6.2 | |||||
A fix for this issue for SAS Financial Crimes Monitor 6.2 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/R38.html#61464| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2017-12-04 11:47:01 |
| Date Created: | 2017-11-28 09:27:10 |