Microsoft Great Plains is ideal for Crystal Reports design. Microsoft is staking on Crystal Reports for its Microsoft Business Solutions Products. We have many requests from our clients to help them with Crystal Report design for Great Plains. We would like to educate our potential clientele to help their own IT resources in Crystal Reports design.
If you are developer who is asked: how do we extend Great Plains ReportWriter with somewhat more sophisticated – read this and you will have the clues on where to look further.
1. Great Plains Tables Structure – first of all you need to know the tables to link. Launch Great Plains and go to Tools->Resource Description->Tables. Find the table in the proper series. If you are looking for the customers – it should be RM00101 – customer master file. If you need historical Sales Order Processing documents – they are in SOP30200 – Sales History Header file, etc.
2. Create ODBC connection to GP Company database. Use the same technique as when you create standard ODBC connection for GP workstation – but change default database to targeted company database.
3. Consider SQL Views – if you don’t want complex links in Crystal Report itself or if you need unionization from several companies – SQL view is the answer.
4. Consider SQL Stored Procedures. Sometimes you can not pull the data in one view – you need temporary tables to be created and the final query should be based on these temp tables – this is when you need stored procedure.
5. Call Crystal Report from GP Screens via VBA/Modifier – if the user wants to call Crystal report for example - printing Invoices in GP and do it from SOP Entry window – you can use Modifier and VBA to call Crystal Reports engine.
6. Create SQL Query to probe the data – we always recommend tuning your query and see that you are getting adequate results – in any case – Crystal Report is just a nice tool to show the results of your query.
