Dynamics GP Warehouse Management System Reporting

In earlier publications we already covered such topics as comparisons between External WMS and Warehouse Management extensions for Great Plains, so if you are in WMS software licenses purchase research mode, please see earlier articles.  In this publication we assume that you are on Dynamics GP WMS extensions and all the reporting is based on Great Plains tables and data flow
1. Barcode Labels.  Typically you print barcode labels while receiving new merchandise or restocking existing items.  In WMS extensions for GP it is in POP Purchase Receipts (exposed via WMS to barcode scanning).  There are several options to print labels.  First one is this – consider Dynamics GP ReportWriter custom report which looks at the items received via POP Purchase Receipt with restriction by dates, where you change the font to be the one barcoding compliant.  Second, more elegant in our opinion (but probably requiring some Crystal Report designer help) is to create stored procedure with parameters (POP Purchase Receipt from/to or date from/to), where you pull all the items received with quantities and Crystal Report prints labels based on Items ID and Quantity received.  Please, note that such report is probably too difficult for Crystal Report Wizard, and you will need SQL Stored Procedure – this approach (SQL procedure) is recommended as it gives you more control in possible future changes in Barcode Labels printing logic.  Microsoft SQL Server Reporting Services should give you the results, similar to Crystal Reports
2. Order Fulfillment Report.  In WMS you typically post Invoices allocated via barcoding on the warehouse floor.  Consider Sales Transactions History report in detail (which also could include unposted documents, if you think this is required).  Here you can filter by document number (where numbering schema could be set to be distinguished for WMS documents, for example have the prefix WMS in the numbering convention), Document Date and Customer ID.  If this report is not covering your specific requirements, you can modify it in Dynamics GP Report Writer.  In the case when you need really custom reporting logic, this report (or any one available in Reports.dic) could be customized in Microsoft Dexterity
3. Items Quantities available in each warehouse and across the company.  Consider Inquiry Inventory->Item Stock.  If this inquiry doesn’t make your life easier, please review Reports->Inventory Purchase Receipts, Stock Status, Historical Stock Status
4. Custom WMS reporting.  Obviously here you have full control over linking various tables in Dynamics GP in your SQL Stored Procedure or View, but these reports require Great Plains Programmer time.  Sometimes WMS customers have EDI, ecommerce integration scenarios, or when reporting should pull the data from heterogeneous DB platforms, such as Oracle, IBM DBII, MS Access, Pervasive SQL (formerly known as Btrieve), Ctree, MySQL/PHP
5. Great Plains Dexterity Reporting.  Dexterity was the original architecture for Great Plains Dynamics, introduced in earlier 1990th.  Microsoft Dexterity has unlimited control in Dynamics GP customizations and reporting.  If you tried Crystal Reports, Report Writer, SSRS, please review Dexterity as the last resort (or maybe natural next step)
6. How to request help?  Please call us 1-866-528-0577, 1-630-961-5918 or email us help@albaspectrum.com  We are helping businesses locally in Michigan: Saint Joseph, Benton Harbor, Holland, Kalamazoo, Muskegon, Grand Rapids, Ludington, South Haven, Grand Haven; Illinois: Chicago Downtown, Naperville, Aurora, Bolingbrook, Schaumburg, Downers Grove, Lisle and other areas of Chicagoland; Southern California: Los Angeles, San Diego, Orange County; Houston Texas.  We are serving you USA, Canada, Mexico nationwide and this is our preferred method of service – via web sessions, short visits onsite and following remote support