Ported Reports
Start with the report lifecycle walkthrough for data preparation, rendering, delivery, memory use, and cleanup across engines.
Ice Porter converts Report Builder definitions to a target report format. PPJ supplies the runtime adapter that receives application data and implements supported SAL reporting calls. Conversion, runtime support, and the reporting vendor's own capabilities are separate concerns.
| Target | Converted format | Integration |
|---|---|---|
| Crystal Reports | .rpt | SAP reporting runtime and a compatible PPJ adapter. |
| List & Label | .lst with schema data | combit's reporting component and PPJ data delivery. |
| Reporting Services | .rdlc | Local ReportViewer processing of data supplied by PPJ. |
| Stimulsoft | .mrt | Stimulsoft reporting runtime and a compatible PPJ adapter. |
Crystal Reports and ReportViewer are separate dependencies, not components of the .NET runtime itself. Confirm the supported engine version, runtime, architecture, and deployment requirements for the selected PPJ adapter.
Reporting Abstraction
PPJ reporting is exposed through ISalReport. The report filename and configured default engine determine which implementation is used. See Reporting Support and General. Selecting another engine does not convert a report definition into that engine's format.
Validation Before Acceptance
Use the same input data to compare original and converted reports. Check record counts, group totals, running-total resets, nulls, dates, rounding, page breaks, headers, footers, and empty results. Test print and each required export format separately; preview alone does not establish correct pagination or output.
Include large reports and concurrent web requests. Measure data preparation and rendering independently. Browser download/printing and server-side printer access are different workflows.
Deployment
Deploy report definitions, schemas, images, fonts, the adapter, and engine dependencies as a consistent set. Confirm runtime and designer redistribution terms with the vendor for the edition in use. Historical examples in these chapters do not establish current licensing or version support.