Can Crystal Reports Run After a File Arrives or Database Data Changes?

Imagine a warehouse report timed for six each morning. The order import normally finishes earlier, but on busy days it runs late. The supervisor receives an incomplete picking list and asks for another copy.

Moving the report later solves today’s delay without establishing whether tomorrow’s import will be finished. A completion signal gives the workflow something more meaningful to wait for.

For this example, the import writes a record containing the completed business day. The reporting job can then start for that day, rather than treating any database change as permission to send the picking list.

SAP Crystal Server provides file, schedule and custom events. A completed-file signal or a preceding server job can therefore support a native dependency. A database condition that identifies newly ready orders is a more specific requirement.

A maintained application can also detect completion and request the report. That may be the clearest route when the application already owns the import’s status.

CRD’s Event-Based scheduling guide documents file and database conditions, including matching-record behavior. It can start an existing schedule when the criteria are met. The rule you configure determines the meaning of the event; CRD does not infer whether the import is complete.

Prepare the picking-list job and prove its report and destination first. Choose the intended business-day parameter and deliver to a controlled folder or test mailbox.

Add the Event-Based schedule and configure the file or database condition that represents completion. For a database query, return the intended completion records and a stable identifier. Limit the polling window if the process is only relevant during warehouse operating hours.

Plan what makes the event stop qualifying. A completion record left unchanged may keep matching. CRD’s documented new-record and matching-record choices serve different needs; choose the behavior and any processed-marker update deliberately.

Test a late import, an ordinary completed import and an already handled completion record. The supervisor should receive a picking list for the loaded day, without another copy on every check.

If the import application supplies the start request, retain its business-day and batch identifiers alongside the CRD execution reference. That gives operations one way to connect the incoming orders with the delivered document.

The picking list should arrive because the orders are ready, with an understandable response when they are late or the report fails. Start with one completion signal everyone involved can explain.

Use event-triggered CRD automation to evaluate that handoff. The Crystal Reports automation overview connects event checks with the wider delivery workflow.