Microsoft Business Solutions Great Plains has several options to enable web ordering. Traditionally Great Plains Dynamics/eEnterprise had eOrder – this is ASP pages based ordering application, enabling you to place or retrieve your Sales Order Processing (SOP) Sales Orders over the web. There were several drawbacks however with eOrder. You should be the customer in Great Plains company database to be able placing the orders. Also if you were planning to customize eOrder – you could only do cosmetic style changes only – if you wanted to alter scripts on the ASP pages – then you would have very serious eOrder upgrade issues. Upgrade simply wipes out your custom scripts and you had to reapply your customization to new version enriched ASP pages. Instead of following the way to move eOrder to ASPX or .Net platform – MBS introduced eConnect, enabling web designer to “connect” eCommerce site to Great Plains backend. This is very elegant module and solution, however we are hearing a lot of complaints from developers on eConnect restrictions.
• SOP Invoice posting. It is not enabled in eConnect. However you should probably first understand the architecture of Microsoft Great Plains. Order takers supposed to enter Sales Order and submit it (place in the batch and save) to the manager for approval (taking off transfer/print/post holds). eConnect enables you to create or update Great Plains objects, but it doesn’t allow you to process them (post) – this would open a gap in the security/approval cycle.
• Order Transfer. Again – this is similar problem to the invoice posting. Both Order and Invoice could be subject to holds and approvals. eCommerce logic might need partial or full order transfer to invoice or even backorder, based on the item availability status.
Why would you then need to purchase eConnect? Maybe just go ahead and program the connection in SQL stored procedures? The answer is – eConnect allows you to allocate items in