Microsoft Dynamics GP Sales Order Processing Module in eCommerce and Warehouse Management 0
Before you decide on purchasing and implementing new Corporate ERP application, we assume you do your homework, including reading various reviews and user’s opinions. This publication is intended to give you some initial info on Microsoft Dynamics GP, sometimes also referred by its historical name – Great Plains Dynamics, we will give you high lights on Sales Order Processing (SOP) module: settings, transactions, its openness to customization, integration, reporting and how it might be involved in ecommerce and warehouse management scenarios. We tried to be reasonably technical (your IT department, programmers, report designers) and at the same time understood on the controller level or even business owner:
1. General functional review. SOP gives you the power to automate your sales cycle, starting with Quote, then working all the way through negotiation (including hold options, where quote price negotiation might be blocked by Sales director) and transforming Quote to Sales Order (or directly to Invoice, if Order fulfillment is not a concern). Order allows you to pick and pack items (or possible find replacement parts). Order also has Allocation feature (also often referred as Fulfillment in WMS lexicon). There is also Backorder mechanism, allowing you to order missing parts from suppliers. When Order is fulfilled – it is transformed into Invoice. Sales Document has access to Inventory items, plus in some cases you may use Service items (they do not require allocation, but you can still track Quantities Sold in reporting and inquiries) or even so-called non inventory items (simply free style text on the SOP document lines). Returns are also entered in SOP transaction entry form
2. SOP Settings. Here you specify defaults, such as site ID (or default warehouse to allocate or pick items against the SOP transaction: Sales Order or Invoice). In data entry defaults you specify such parameters, as what to do in the case
