As you can see, ERP systems have been implemented in businesses that require tight integration with existing or legacy systems, warehouse management, automation of shipping and receiving operations, barcode scanners (Symbol wireless and standalone) inventory order fulfillment. increase.
One direction is the implementation of so-called supply chain management (e.g. Radio Beacon) integrated with Microsoft Great Plains. Another solution that's inexpensive and suitable for medium-sized warehouses - use a third-party custom module for Microsoft Dynamics GP and work with a customization partner to tailor custom parts for your unique warehouse operations. This small article provides an overview of the light barcode functionality available in Great Plains.
• Custom logic for order processing (SOP). Scanning barcodes is generally similar to typing characters on the keyboard itself. It makes sense to improve your SOP logic to automate processes such as order fulfillment and shipping. In this case, for example, you should be able to charge more than you ordered. A simple prompt screen in Great Plains should only let you decide whether to override or not.
• Barcode – Item number. You should probably be able to see these two side by side. We recommend storing the mapping in a custom table. • Serial/lot number. Lot numbers often need to be associated with a specific larger unit of measure. B. Each roll (of fabric/fabric) with slightly different yardages or meters (using a new batch number or serial number). Variable length should be concatenated with lot number in parallel with standard unit of measure logic
• Technology. Microsoft Dynamics GP's customization technology is the same as Microsoft Dexterity 5-10 years ago or the Great Plains Dexterity before it. Customizations come in the form of chunks (files with a .CNK extension) that are built into the Great Plains workstation when the application is first launched, and then into custom dictionary files.
(DYNAMICS.DIC is the core functionality, CUSTOM.DIC is the customization dictionary, etc.). Dexterity uses Scanscript coding and has the Microsoft Dexterity IDE. In some cases, you can use the Microsoft Great Plains Modifier (DYNAMICS.VBA) to extend your Dexterity customizations with SQL stored procedures and VBA scripts, but if you're talking about the default Great Plains client application, We recommend using Dexterity. If you plan to deploy a web interface, you should consider newer technologies such as eConnect.
• SQL tables. For SOP, you should read SOP10100 - Sales Document Header, SOP10200 - Sales Document Detail. You should also read tables IV00101 - Inventory Item Master and IV00102 - Item Quantity Master.
• Microsoft RMS integration. If you sell at the retail level and want to integrate your transactions in Great Plains, you need the Microsoft Dynamics GP - MS RMS integration module. In our case we use it at the AR/SOP/POP level, then post the transaction in Great Plains and send it to GL.
