LEARN CRYSTAL REPORTS

SAP Crystal Server API or CRD API: Which Approach Fits?

Use SAP Crystal Server’s developer interfaces when your application should work with reports in that server. Use the CRD API when it should start and monitor saved CRD reporting jobs.

Compare responsibility for execution, output, delivery and recovery, so the monthly statement remains manageable after the first successful request.

  
Your reporting task

Start with what the application must deliver

Imagine a development team adding a monthly statement feature. One proposal connects the application to SAP Crystal Server; another calls CRD to start a saved reporting job. Both can sound like “using an API,” but the reporting environment behind the request shapes the work your team will maintain.

Define the required result first. Does a user need an immediate document in the browser, or should a completed statement be prepared and sent to an approved destination? Does the same work also run every month without a user request?

These questions expose the responsibilities that matter after the first successful demonstration.

Compare the complete requirement

Include parameters, database connections, output protection, distribution, monitoring and the person who will support failures.

  
Your options

Decide which reporting service owns the job

SAP Crystal Server keeps reports in its repository and provides scheduling, instance history and developer interfaces. SAP lists Java, .NET and Web Services SDKs. That can suit a team already managing its reports, users and permissions there.

Choose the interface documented for your installed SAP Crystal Server version and the operation you need. Verify execution, parameters and the output path together. Personalized automated publishing has a separate Concurrent Sessions (CS) licensing requirement; SAP’s Crystal Server guidance explains that distinction.

The CRD API works with the CRD reporting environment. A saved schedule can hold report execution and destination instructions while the application starts and monitors the job. The application still owns business authorization and how its users see the outcome.

Follow the statement all the way through

A successful request is only useful when the right statement reaches its approved destination. Compare both reporting services against that complete handoff.

  
Put it into practice

Evaluate the same statement with each approach

Use one representative RPT and reporting period in both evaluations. Agree the statement content, the person allowed to request it and the destination where its completed output should appear.

For SAP Crystal Server, demonstrate the report operation through its supported interface and show how the application identifies the resulting instance. Include its output destination or retrieval path instead of stopping at a successful server response.

For CRD, prepare the statement schedule and prove it runs correctly before using the API. Confirm the API Service, authenticate, request the saved schedule and retain the asynchronous execution reference. Then check the final file where the statement workflow expects it.

The CRD service setup guide and the execution workflow establish that starting point.

CRD API Service configuration for application requests

Use a realistic report

Include the subreport, connection type or output requirement that makes your workload distinctive. A trivial sample may hide the deployment work.

  
Keep it dependable

Compare the work after the first successful request

Discuss how each design handles a changed recipient, an unavailable database and a response that times out after execution begins. The useful comparison includes support ownership and the evidence available for recovery.

Keep cost and development effort specific to your environment. A claim that one approach always takes days and another minutes would obscure the actual dependencies.

Developer reference: contracts and deployment boundaries

For SAP Crystal Server, verify the installed version’s supported SDK, authentication, report operations and user permissions. For CRD, verify the API Service, client authentication and documented schedule operations. A request written for one product is not interchangeable with a request for the other.

CRD is Windows-hosted even when a client calls it from another platform. Executing a schedule does not establish an embedded viewer or automatic file-download endpoint. Retain the specific run reference and verify output rather than treating request acceptance as completion.

Include a controlled failure

Ask each prototype to explain a failed statement and recover an uncertain request. That reveals responsibilities a successful export will not.

  
Your next step

Choose the approach your team can operate

The right route leaves the development and reporting teams with clear ownership of the monthly statement. It should fit both the user-facing feature and the recurring work behind it.

Use the Crystal Reports API comparison with your tested report and deployment requirements.

Contributors:

Christian Ofori-Boateng

Christian Ofori-Boateng

CEO, ChristianSteven Software