link

If you company is small or mid-size special products or materials exchange broker, you probably have custom in-house made exchange application. Nowadays exchange is done over the internet, so you might have advanced web-based exchange application. Microsoft Business Solutions Great Plains could play the role of the backend: accounting, sales and purchasing ordering, backordering, allocation, collection. In this case we expect tight integration between your exchange application and Great Plains. In this small article we consider industry / market niche specifics and the ways to realize these requirements:

• Exchange Transaction. Exchange transaction usually has two parts: Sales and Purchasing. This transaction should be translated into Great Plains as Sales Order in Sales Order Processing (SOP) and Purchase Order in Purchase Order Processing (POP). Assuming that you have web developers and C#, VB.Net programmers, you can deploy eConnect Distribution – this is Software Development Kit with sample codes, you can create or modify Great Plains objects, such as Sales Order, Customer record, Purchase Order, Vendor record. One warning about eConnect – it is designed based on general ERP application principles: you can create work transaction only – you can not post transaction, this is left for the Great Plains user

link

Welcome to WordPress. This is your first post. Edit or delete it, then start blogging!