Problem Note 45136: SAS® Marketing Automation scheduling fails to create an entry for the first month when there are fewer than 31 days in the first month
SAS Marketing Automation enables you to schedule a campaign or communication execution to recur once each month. In order to schedule the recurrence for the last day of each month, you enter 31 as the date. If you then begin recurring from the current month and that current month has fewer than 31 days, that first month's execution is skipped.
For example, this problem occurs in the following circumstance:
- You create a schedule in June for a recurring campaign.
- You set the execution date to be the 31st day of each month.
- You set the recurrence to start in the current month, June.
The expected behavior in this instance is for the campaign to execute the 30th day of June. However, the first execution of the campaign would be the 31st day of July. Every subsequent month in the scheduled recurrence works as expected. Execution occurs the 31st day of August and then on the 30th day of September, and so on.
If you use Platform LSF to schedule campaigns or communications, you can correct this problem by rescheduling the first occurrence in the LSF calendar.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Marketing Automation | Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows XP 64-bit Edition | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows 2000 Advanced Server | 5.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Datacenter Server | 5.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Server | 5.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows 2000 Professional | 5.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows NT Workstation | 5.1 | | 9.1 TS1M3 SP4 | |
Microsoft Windows Server 2003 Datacenter Edition | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Enterprise Edition | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows Server 2003 Standard Edition | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Microsoft Windows XP Professional | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Windows Vista | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Windows Vista for x64 | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
64-bit Enabled AIX | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
64-bit Enabled HP-UX | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
64-bit Enabled Solaris | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
HP-UX IPF | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
Linux | 5.1 | 6.1 | 9.1 TS1M3 SP4 | 9.3 TS1M2 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2012-04-03 09:12:48 |
Date Created: | 2011-12-14 08:53:50 |