How to Schedule Crystal Reports Around Working Days and Month-End

Imagine finance receiving its close report on the fourth working day of each month. A schedule for the fourth calendar day works in some months, but a weekend or holiday can move it ahead of the completed close.

Ask what “working day” means for this reporting team. It may exclude weekends, local holidays or company closure days. That definition should be part of the calendar rather than an adjustment someone remembers each month.

Also agree which figures the report should contain. Running in November does not automatically mean the report selects October’s completed accounts.

Your existing Crystal Server or BusinessObjects scheduling environment may already offer the recurrence and calendar facilities you need. A script can calculate business dates too, but someone must maintain its holiday rules and check the next runs.

CRD documents weekday schedules, a specified working day of the month, monthly patterns such as the last Thursday, and custom calendars. An exception calendar identifies dates when the job should not run.

Those controls schedule execution. An exception calendar prevents a run on excluded dates; do not assume that it also moves the job to the next working day. Use an explicit custom calendar when holiday-adjusted dates need to be specified, and verify the resulting run dates.

Relative date parameters determine the period the report selects, while a separate readiness condition handles a close that finishes late.

The CRD scheduling guide explains the recurrence choices.

Select the finance report, configure its previous-month parameters and choose the intended destination. Then set the working-day or monthly recurrence that represents the reporting agreement.

Review the start date, execution time and relevant custom or exception calendar. Check the scheduled host’s time-zone settings against the time finance expects; do not assume a time written in a job description establishes the configured zone.

Inspect the next dates across an ordinary month, a weekend boundary and a holiday period. Use controlled runs to check the selected accounting period as well as the date the report arrives.

A correct working-day calculation cannot confirm the ledger is closed. If the close varies, agree how finance signals completion and whether the reporting job should wait, alert or follow another approved response.

CRD event-based scheduling can use configured conditions for readiness. Combine that with the reporting calendar deliberately, rather than describing a later clock time as proof that the data is complete.

Finance should receive the intended month’s report on the agreed business day, with a clear response when the figures are not ready.

Explore CRD scheduling with your next few month-end dates and real holiday exceptions.