| Microsoft Dynamics GP has a set of SDK and | | | | lines |
| programming tools to enable business logic | | | | 3. Modification technique. You actually never change |
| customization for software developers. You can utilize | | | | original GP tables; instead you add your new custom |
| Extender, VBA with Modifier, direct SQL scripting as | | | | tables and link them one-to-one with GP original tables. |
| well as eConnect object calls from Microsoft Visual | | | | In the case of Sales header table, you link your custom |
| Studio C# or VB projects. However if the modification | | | | table by these two fields: SOPTYPE and SOPNUMBE |
| should be seamlessly integrated in Great Plains user | | | | - Sales document type and Sales number respectively |
| interface, you should consider Microsoft Dexterity tool. | | | | 4. Typical modifications in business logic. Imagine - you |
| Regardless of the tool, you need to understand which | | | | have return and you would like to associate it with |
| GP objects should be modified and where to find their | | | | invoice. Custom logic may have custom screen, where |
| description: | | | | you select invoice number and click Create Return |
| 1. Great Plains Tables description. You can install | | | | button. The logic copies all the items and qty from |
| Microsoft Dynamics GP SDK or Software | | | | chosen invoice and creates reversing return. This is |
| Development Kit, which has comprehensive overview | | | | one of the typical scenarios, where your business has |
| of GP tables and their relations. If you work closely | | | | special automation requirements, not available in GP or |
| with GP users, you can get tables snapshot in GP | | | | any other generic ERP application. The example |
| interface: Microsoft Dynamics GP->Tools->Resource | | | | above is very good candidate to be considered and |
| Description->Tables. | | | | implemented in Great Plains Dexterity |
| 2. SOP tables, often participating in modification. GP | | | | 5. Additional Considerations. As we are talking about |
| design distinguishes work, posted and historical tables. | | | | mid-size MRP application, where Great Plains |
| In the case of Sales Order Processing module you | | | | Dynamics GP belongs, altered business logic is not a |
| see Sales Work Documents: SOP10100 - Sales | | | | five minutes change. GP objects model is relatively |
| header and SOP10200 - Sales lines tables (to name | | | | complex, plus if you decide on Dexterity programming |
| key tables, there are other tables as well, outside of | | | | - it requires several years of extensive software |
| the scope of this article); and historical tables: | | | | development to get enough under your belt to consider |
| SOP30200 - Sales header and SOP30300 - Sales | | | | learning curve to be finally behind. |