In Sage X3, there are several ways to build reports, whether using the in-build query tools or deploying external crystal reports in the application server folder.

External crystal reports provide so much freedom of design choices to the developers to build complex reportings for client’s requirement. However, when working on a Live production environment, access to the application server often raises security concerns from the client side so to make modifications on reports in such cases we need to use Sage X3 crystal report connector.

For this we’re referencing following paths and screenshots below:

Administration addons: All > Administration > Utilities > Installation > Crystal report connector
Users: All > Setup > Users > Users (GESAUS)
Report dictionary: All > Development > Script dictionary > Reports (GESARP)

New Stuff: Implementing and Support Electronic Data Interchange

Fig. 1 – Crystal Report Connector addon

-To begin with we should be having a proper version of SAP Crystal Reports software which is compatible with the addon, most widely used are 2013 and higher editions.
-Once the software requirement is completed, then as shown in Fig. 1 we need to navigate over to the Administration utilities path to download the Crystal Report Connector. Follow the on-screen instructions and complete the addon setup.

Fig. 2 – User parameters

-Now we need to navigate over to Users (GESAUS) setup to configure our development user for report development. For this under the selected user, we need to jump into the Development parameters as shown in FIg. 2.

Fig. 3 – Setting DEVCRY to Yes

-After setting the Report development parameter (DEVCRY) to Yes as shown in Fig. 3, we are all set for development.

Fig. 4 – Transfer Option in Report Dictionary

-Now head over to the Reports dictionary (GESARP) and for the respective report, under the report grid when we click on the 3 dot action button we get a list of options showing the Transfer button as shown in Fig. 4.

Fig. 5 – Status Change

-Once we click the transfer button the Status on the grid for the report changes to Transfer request as shown in Fig. 5 and we can click on Save button to start the transfer request from server. Follow the prompts and the system should automatically open the Crystal Reports with the report file.

Fig. 6 – Sandbox status options

-Once we’re done taking the backup of the file and making the modifications, we can Commit back the local report file to the server using the same process as shown in Fig. 6.

This way we can make use of Sage X3 Crystal Reports Connector addon to work on report development without access to the server.