Microsoft Dynamics NAV/AX Implementation – Russian ERP Market

In this small article we will be giving you highlights on Microsoft Navision and Axapta implementation, customization, tuning and reporting in Moscow and on Russian ERP/MRP market in general. We suggest this information to IT directors of multinational corporations with connection to Russia, Kazakhstan, Central Asia. Recently – in September 05 Microsoft Business Solutions renamed Microsoft Great Plains, Navision and Axapta into Microsoft Dynamics GP, Microsoft Dynamics NAV, Microsoft Dynamics AX, following the directions of Project Green. We will be discussing localization, government reporting, language translation.

o Localization. Microsoft has two ERP products for Russia and CIS – Microsoft Dynamics NAV – Navision and Microsoft Dynamics AX – Axapta. Microsoft Dynamics GP is not localized and is not available in Russia from Microsoft Business Solutions Moscow. You can purchase the license from MBS Partner in US and implement Microsoft Great Plains in Russia, but you will face government reporting issues

o Language. Both – Microsoft Navision and Microsoft Axapta have interfaces translated into Russian and to some extent you can have multilanguage version, the reason we are rising multilanguage issues – in order to control your subsidiary in Russia you should have at least English interface and reporting.

o Government Reporting. Russian tax reporting is somewhat relatively conservative and the regulation here is rather strict. Also, tax inspectors assume that you use standard chart of account and do transactions on the General Ledger level, following accounting transactions prescribed rules.

o Chart of Accounts & Transactions. Standard chart of accounts has enumerated codes for accounts and geared toward manufacturing accounting. Again – accounting code prescribes you do transactions in General Ledger. The regulation would be not an impediment, if you are manufacturing company and tune your manufacturing ERP / MRP module to use codified and state-approved accounts/transactions. However if you are service business, especially high-tech oriented – the code is a pain for you, because Sales Order Processing or Service modules are typically designed under the assumption of accrued accounting, without posting your profit and expenses through “goods in production” type of accounts.

o Cash Based Accounting. Technically you can use either one: cash based or accrued methods. However, the accounting code was designed with the idea of the cash method.

o Implementation Partner. For the company, having headquarters in the US/Europe, consulting company selection is important question. Technically implementation should be done in Moscow, but the implemented ERP should be “consolidated” into Corporate ERP, an so – the communication between consulting company and your headquarters based IT and Finance department should be very efficient.

We encourage you to analyze your alternatives. You can always appeal to our help, give us a call: Russia: (095) 918 3314, Germany: (0177) 8349 806, USA 1-866-528-0577 or 1-630-961-5918, help@albaspectrum.com

Thanks To : restaurant accounting software

Published August 29, 2010 – 5:55 am Categories: great plains accounting software | Comments Off

Tagged , , , , , |

E-Commerce Microsoft Dynamics GP Great Plains Web Development

Microsoft Great Plains ecommerce architecture: website with Sales Order Processing and Microsoft Dynamics GP as accounting back office. Highlights to automatic invoices posting, inventory item allocation

Technically you can start from scratch and purchase webstore, however typically customers have to use evolutionary approach to their ecommerce strategy. If you have your existing ecommerce website, you next step to link this specific ecommerce (often developed inhouse) with your ERP application. Former Great Plains Dynamics/eEnterprise and currently Microsoft Dynamics GP has broad number of installation across the US and you may not have another option, but work with you existing MRP – Great Plains.

o eConnect. In the past budget was an issue to purchase eConnect, so you might be designing or purchasing simple stored procedures, helping you send Sales Order or invoice from ecommerce web site to Great Plains. Our recommendation is – when eConnect became available – do not invent the wheel and utilize it in you ecommerce web integration. The most elegant way is to call XML web services interface of eConnect

o Beyond eConnect. If you want complete automation, when posting of SOP invoice is done automatically (upon the credit card payment), then you need to call portions of Microsoft Dynamics GP internal logic, which is currently the realm of Microsoft Great Plains Dexterity, where you need to know Dex architecture, sanscript, GP tables, etc. Instead of investing in dex learning, you may decide to purchase Dexterity Posting Server

o Some eConnect restrictions. Old Great Plains modules are out of eConnect scope, such as Invoicing module (do not confuse – Sale Order Processing or SOP is automated in eConnect). Plus do not expect third party modules to be in standard eConnect, however ISV companies might have eConnect extension, automating their third party modules

o Auto Posting Server. Supported and distributed by Alba Spectrum it uses so-called Great Plains Dexterity source code programming – it calls GP posting logic when your batch is ready for posting

Please feel free to call us: 1-866-528-0577, 1-630-961-5918, help@albaspectrum.com or skype: albaspectrum

Related : sage accpac certified management accountant program

Published August 27, 2010 – 12:18 pm Categories: great plains accounting software | Comments Off

Tagged , , , , , , , , |

Microsoft Great Plains: Large Scale Implementation


Image : http://www.flickr.com

Microsoft Business Solutions Great Plains, Navision, Axapta, Solomon and CRM are coming up to satisfy ERP needs for large corporation, including multinationals. In this article we will be describing Microsoft Great Plains as the MRP platform, fitting to multiple industries and business niches: aerospace, defense, textile, pharmaceutical, healthcare, constructions, mining, services, distributions & logistics, wholesale & retail, public sector, chemicals, oil & gas, finance, brokerage, etc. We’ll try to give you orientation and set realistic expectations if you are CIO for large publicly traded company and looking for reasonably budgeted solution.

o Technical versus Functional implementation. The trend of our new post-recession era is biased toward technical implementation. If you look back to 1990th Clinton golden days – when we would say huge number of CPA-oriented businesses were realizing and implementing mid-size and large accounting applications. Today – accounting department team is comfortable with generic ERP interface and needs minimal training. Usually we train IT people and they in turn provide Great Plains interface and reporting training to the end users, or end users attend online training to get advanced skills in the application interface.

o Technical Customization & Modification. Well – if you remember old-good-days SAP, PeopleSoft, JDEdwards, Oracle ERP systems implementation – you would agree that they required a lot of programmers and developers participation. The same is applicable if you look at Microsoft Great Plains – however we need to make some remarks, related to our new time. First of all – Developers are mow concentrated in the development centers, dispersed across the USA and especially internationally in so-called offshore zones: India, Philippines, Brazil, Russia, Ukraine. We are not talking about China here, because Great Plains is not very popular over there. So, normal situation should be when your have nation-wide consulting company here in the States with regional project managers and Great Plains Dexterity, VBA/Modifier, Integration Manager, eConnect, Crystal Reports, VB.Net and C#.Net developers in Sao Paulo, Moscow or Manila.

o Remote Support. Nowadays technology tries to move us toward the ideal world when you as end-user in Denver could be supported by consultant or developer in Brazil through web session, remote desktop connection, VPN, Skype, VOIP, or other tool. The only requirement is fast internet connection from your and technician side – which is catching up very quickly.

o Multinationals. Multinational corporation has to deal with the following issues: taxes (VAT, GST, Sales Taxes), customs fees, tax filing rules, local chart of accounts regulations (France, Russia), localizations – ERP application should be localized – all the screens should be in local language: Chinese, Spanish, Portuguese, Russian, French, German, Polish. Microsoft Great Plains is localized for South America, UK, Canada, France, Germany, Poland, Middles East (Arabic language support), Australia, New Zealand, South Africa, Nigeria and central Africa

Good luck with implementation, customization and integration and if you have issues or concerns – we are here to help! If you want us to do the job – give us a call 866-528-0577 or 630-961-5918! help@albaspectrum.com

See Also : payroll accounting software certified management accountant program

Published August 26, 2010 – 10:18 am Categories: great plains accounting software | Comments Off

Tagged , , |

Microsoft Dynamics GP Data Conversion – Overview for Consultant

You are not alone when you are switching or migrating from Accpac, MYOB, MAS 90, QuickBooks, or even legacy in-house made accounting ERP application to Microsoft Great Plains. This is typical situation and from time to time majority of midsize or small businesses should come through this. Do not be overwhelmed with potential problems expectation, relax, think about your options and ways to go. In this small article we would like to give you some orientation on the possible steps to undertake and pitfalls. First you should think and explore data conversion possibilities and their classification:

o Setup. Consider transferring existing setup features from your legacy application to GP. In GP we have clear concept of setup files (compared to master records, work, open and historical records). The scope if setup is usually limited to company name, users and their access rights to your GP companies, Modules settings: GL, AR, AR, SOP, POP, IV, UPR. Please try to be patient, before you burst with emotions let’s us give you the argument – setup is typically built into the heart of the MRP architecture, this is why you should not expect it to be transferred by the wizard

o Master Files. Customers, Vendors, Employees, GL Accounts should be migrated – no doubt about it. You are the judge – if the number of your customers is 50 or so – you may simply to have somebody of your employees to manually key them in. If this is not the case (you have 50 thousand customers), then GP integration manager module is needed or if this is too expensive you may have your GP consulting partner to use SQL scripts to bring master records over to GP

o Work Transactions. GP has concept of work, open and historical transactions, when operator enters invoice it is in so-called work status, when you post it – it is in open status and then you move it to history when your review open files longevity. When you are migrating from legacy ERP – it is good approach to “post” or transform to equivalent of open or historical status all your legacy transactions prior to migration to GP

o Beginning Balances. This is very reliable and old accounting wisdom – start your new ERP with new accounting period and all you need to do is enter General Ledger beginning balances for the period

o Keep old system for historical inquiry. This will allow you to avoid painstaking historical data migration. In GP historical data is often considered as participating is such decision making scenarios as perpetual inventory cost revaluation, multicurrency transactions: Canadian Dollar/Euro

o Historical Transactions Migration. First idea is to avoid this – until it is absolutely required. If you can not avoid it – think this way – I can allow GL historical data migration – it typically doesn’t participate in future business logic (revaluations, multicurrency, etc), If you absolutely need GP history in modules, such as SOP – consider this approach first. You enable historical financial periods, move transactions through IM and post them to history. If you think this is impractical – if you have 100 millions records to be re-posted in history – then you rescue to SQL scripting. In SQL scripting you should expect new discovery (meaning problems, reported to you from you GP partner, typically meaning going over budget and things line that)

Related : great plains accounting software

Published August 26, 2010 – 3:38 am Categories: great plains accounting software | Comments Off

Tagged , , , , |

eCommerce development for Microsoft Great Plains: accoutrement and highlights for programmer

Microsoft Business Solutions Great Plains, former Great Plains Software Dynamics and eEnterprise was designed in earlier 1990th as ERP, which can be easily transferable to the winning Database and OS platform and it was originally available on Mac and PC – Mac OS and Microsoft Windows respectively. Graphical platforms battle is pretty much over and now with eCommerce demands, we should look at Great Plains Dynamics tables structure:

o Naming Convention. Great Plains was designed to be ready to move to the winning database platform and probably this is why we see this a bit complicated naming convention in place: SOP10100, RM00101, IV00101 – these are samples: SOP header, Customer master, Inventory master. First – we see module prefix: SOP – Sales Order Processing, RM – Receivables management, IV – Inventory control, etc., then 0 stays for the master files, 1 – so-called work files (before transaction being posted), 2 – open files (after transaction is posted) and 3 – historical files (when you close the year in General Ledger – transactions are moved from open to history files). So as you see – logic is present and structured, but it is not friendly to the developer, who never seen and worked with Great Plains Dynamics.

o Tables Groups. Great plains was designed to first serve mid-size businesses and then with the availability of third party modules – the intention was to compete on corporate ERP market with Oracle, PeopleSoft, SAP and others big players. This is why we see the whole cluster of tables to store, say Sales Invoice: SOP Header, SOP Lines, SOP Distribution, RM Key file, etc.

From the Forms side (or screens) you can see more human-readable names: SOP Entry, RM_Customer_Maintenance, POP_Entry or the like. But these legacy Great Plains Dexterity names do not help eCommerce developer – only probably as the reference on which table works with specific screen.

Let’s take a look at the tools available:

o eCommerce – together with eOrder, and other eXXX products it should be considered as legacy and phase out product, based on Microsoft eCommerce server and ASP technology, today Microsoft has new paradigm – .Net and ASPX World

o eConnect – was specially created for eCommerce developers, who integrate Microsoft Great Plains with eCommerce web interface. This tool covers a lot of Great Plains objects creation and retrieving functionality, however it does have restrictions, because it was not intended as replacement to Great Plains Dexterity shell. For example – if you create Orders in SOP via Web interface/eConnect – it is difficult manipulate these orders (transfers to Invoices, backorders, reallocations, etc.). Another issue with eConnect – developers are kind of used to the fact that Microsoft provides free SDK to its products, Microsoft CRM for example has freely downloadable Microsoft CRM SDK. For eConnect you have to pay license and be on Microsoft Business Solutions annual support to get version upgrades. Also if you are ISV and develop your GP integration to your customers – you have licensing issue with Microsoft.

o Custom SOP/AR stored procedures. Microsoft Business Solutions partners in their practice usually have several Great Plains integration projects implemented where integration is realized on the stored procedures level and transactions are created and manipulated in Great Plains SOP. So – you may end up seeking this type of help

Good luck with implementation, customization and integration and if you have issues or concerns – we are here to help! If you want us to do the job – give us a call 866-528-0577 or 630-961-5918! help@albaspectrum.com

Recommend : great plains frx

Published August 24, 2010 – 10:09 pm Categories: great plains accounting software | Comments Off

Tagged , , , , , , , , , |

Microsoft Great Plains Implementation FAQ – Financial Setup, Conversion, User Training

Microsoft Dynamics GP ERP implementation process is similar to other mid-market accounting and MRP products: GP partner selection and sales cycle, business processes mapping, customization design if required, reports. Then you go to the actions: Microsoft Dynamics GP software licenses purchase, GP installation, initial data conversion and beginning balances, business specific users training. If your company is large business, you may consider switching GP for one or several business entities as a pilot project with the plan to turn all your departments and units to Microsoft Great Plains in the short future. We will not be covering business processes mapping scenarios in this small article and will try to give you technical side of the implementation

1. Great Plains Installation. You should plan for appropriate Server hardware, SQL Server 2005 installation (including planning for data and log files separation on different drives). Then you go ahead with GP server installation – we certainly understand and confirm, that GP Utilities installation Wizard is very intuitive, however, GP is not small business accounting application, so it is powerful and at the same time sensitive to options chosen. This is why we strongly recommend you to invite GP consultant to do installation and overall implementation job

2. Data Migration. The best approach is to leave old ERP data in your old system and make fresh start in Microsoft Dynamics GP. If this is not possible, then consider migrating Chart of Accounts, Customers, Vendors, Employees, and entering beginning GL balances (this last step manually). This recommended data migration should be done via GP Integration Manager, as it validates Great Plains Dynamics business logic and doesn’t allow data inconsistency.

3. GP Modules Setup. Each module: General Ledger, Inventory Control, Sales Order Processing, Receivables Management, Payables Management, Payroll and others requires opening setup screen and coming through the required fields setup there. One of the most important setup decisions is Posting Accounts setup – this is done on the company setup level

4. User Training. First of all – you should be aware that Microsoft is in the process of synchronizing its ERP applications user interface with the one in Microsoft Office and Microsoft Outlook – meaning that if your users are very good and intuitive with Microsoft Office products, they should be ready to do GP discovery. Saying this, we have to admit that GP user training is needed, as MS Office interface unification, leading to users intuition is just the top level

5. Frequently Asked Questions. Software Licenses – you can purchase these from MBS partners only. To get new user licenses or modules – you will need to be enrolled in Microsoft Dynamics GP annual enhancement program. Migration from old versions: 5.5, 6.0, 7.0, 7.5 – if you are on Pervasive SQL or Ctree, then you need migration tool, please contact your MBS partner. Version upgrade – current version is 10.0 and one-step migration path exists for 8.0 SP5 and 9.0 SP2

6. Reporting. You can consider industry tools, such as Crystal Reports, Microsoft SQL Server Reporting Services (SRS), MS Excel, or even Microsoft Access Reports, if you are comfortable with Access. Very important reporting hint – consider creating report logic in MS SQL Server stored procedure or view and not expect the magic from reporting tool Wizard.

7. Beyond the generic implementation. Customization – please review eConnect, Microsoft Dexterity, GP SDK, SQL Stored Procedures, Modifier with VBA. Integration – please start with Integration Manager, then think about eConnect programming, SQL direct scripting. EDI or Electronic Document Interchange – this is popular SQL scripting routine, it is often resolved via XML feed. If you represent lager corporate entity and need major integration project, we will be happy to help you.

Tags : restaurant accounting software small business financial services forensic accounting jobs

Published August 23, 2010 – 5:31 pm Categories: great plains accounting software | Comments Off

Tagged , , , , , , |

Great Plains Automatic Batch Posting Overview

If you know Microsoft Dynamics GP architecture, Dexterity business logic, you probably realized that standard Great Plains Integration tools, such as Integration Manager, eConnect, which are typically deployed in eCommerce integration scenarios, allow you create only so-called work transactions: SOP Invoice is the most popular transaction type. Work transaction is placed to the batch to be saved for future review and posting by GP user. It is probably impractical to try posting batches through Dexterity from scratch programming, as you will spend a lot of hours just to getting through Dex programming learning curve, plus you will need Dexterity so-called source code to dive deep enough for finding the way to trigger batch posting programmatically. In this article we are describing Posting Server product:

1. Triggering batch for posting. As being eConnect C# or VB.Net developer you have an instrument to create transaction, place it into the batch (and save by doing that). Next, you should just place this batch record into posting queue table – this is custom table, where posting server monitors new records

2. Dexterity engine. The flexibility of this approach relates to the fact that posting server calls Dexterity posting procedure and so, it is pretty reliable in version upgrade, as posting procedures are one of the core functionalities of GP

3. Posting batches in almost all modules. As posting is done by Dexterity engine, it is typically unified for all the GP modules and so, posting server doesn’t have modules limitation. Some restrictions apply, usually for third party add-ons to standard GP

4. Integration Manager. If you plan to deploy IM, then you should plan to populate queuing table with additional programming – simple SQL stored procedure will do the job

5. Sales Order fulfillment. If you are intermediate party or reseller, you can post batches in both Sales Order Processing module as well as in Purchase Order Processing, where you order from your vendors. In this case posted Sales batch will trigger posted Purchasing batch.

Friends Link : computerized accounting software

Published August 22, 2010 – 1:29 pm Categories: great plains accounting software | Comments Off

Tagged , , , |

Implementing New Business Management Software – 7 Ways to Make it Smooth and Seamless

As a very small business or a business just getting started, you might be using an entry level accounting system where the investment in training and configuration is minimal because the product is fairly easy to use. Often these systems are ideal until your business begins adding more users and your business processes become more complex than what the system can support.

When a small business decides to implement a new accounting or business management system, it cannot shut its doors or stop day-to-day responsibilities to install, configure, and test a new system. Also, it cannot expect to start using a new system without investing time to consider potential improvements to existing business processes or train end users and migrate historical data.

This is where the role of your solution provider or consultant is critical. Top solution providers efficiently transition you from your old system to your new system with minimal downtime for your staff. In addition, your solution provider will continue supporting the solution for you as your business grows and evolves.

When choosing a new system, your choice of a solution provider should carry as much weight as the product itself. Here are a few things to look for when choosing a solution provider:

1. Understands Your Business and System Needs

A software provider should understand your business and business processes to interject which processes can be more efficient. The provider should listen to you, give good examples of how the system should work, and ask good questions, not just about software, but also how your people work, who they are, their skill sets, and how they would use the application.

2. Exhibits Exceptional Knowledge About Their Product(s)

It is a must for your software provider to thoroughly understand the functionalities, capabilities and intricacies of their solutions and coherently explain those to your end users so you optimize your investment and use the business management system to its fullest potential for your organization.

3. Knowledge of Other Products and Solutions

A good solution provider makes sure you understand what you are looking for and know ahead of time what the expected returns and benefits will be. If you do not know what you need to do well versus what a business management system does well, you can get trapped into buying a system because of something it does that is not important to you. System selection prepares the client for the sales cycle, gets their information together, and allows them to quickly eliminate inappropriate systems.

4. Proven Approach to Implementing

Entry level accounting systems can often be implemented by following the software vendor’s checklist. However, mid-level systems require more planning and testing because there are many different configuration options to make it adaptable to your business processes. The top solution providers have developed and can explain to you their approach to implementing the system. The approach should include options for functional design, pilot testing, data migration planning, a cut-over strategy and ongoing support.

5. Communication

When evaluating systems, many businesses are first introduced to a salesperson and may not have the opportunity to assess the communication skills of the consultants who will eventually be assigned to the project. A top solution provider will have an approach for communicating with the client regarding project status and budgets. Also, your solution provider is often preparing deliverables to you, including procedures documentation, end user training guides and more – a top solution provider can provide sample documents that demonstrate their ability to communicate in these areas.

6. System Cut-Over

When your company starts using the new business management system, your comfort level must be established by the solution provider. That can take anywhere from 30 days to six months, depending upon the client and how significant the changes are in IT and business processes. During this time, your solution provider should still pay attention to you, check in to make sure things are working the way they were expected, and provide any additional support and training your end users need.

7. Ongoing Support

Many businesses begin realizing a positive return on their investment in a new system within the first 12 to 18 months. The project and your relationship with your solution provider should not end there. As your business grows and evolves, you want some assurance that your solution provider is always looking after your business – recommending improvements to business processes, assessing new modules or tools and their impact on your business, or offering user groups where you can interact and share ideas with other end users. The top solution providers make these and other services available to you for as long as you own the system.

Visit : government accounting software peachtree accounting software

Published August 22, 2010 – 7:30 am Categories: great plains accounting software | Comments Off

Tagged , , , , , |

Microsoft Moves to Small Business Accounting/Retail Market – Stakes and Thoughts

In this small article we will be looking at the new opportunities for Microsoft Small Business Server specialists, but rather look at the global business strategy and possible ways of future ERP modules standardizing and interoperability. This is important to get into consideration for midsize and large corporate business IT decision makers. Let’s look at the chronology and possible future development.

o Great Plains Software acquisition. When Microsoft took leading position on the operating system market and released stable and reliable Windows 2000 Server, the next logical step would be getting into ERP market. Microsoft decided to try midsize market, and the reason is probably this – it is wise to create small accounting as the extension to Microsoft Office, not to purchase existing small application. However if you plan to try midmarket – you better purchase something established with broad client base. Developing midsize package from scratch might deplete all the resources. As the stake on Great Plains was high – Microsoft formed business systems subdivision – Microsoft Great Plains Business Solutions, later on Great Plains name was taken off and now we see Microsoft Business Solutions.

o Navision Software Acquisition. There are multiple opinions among the MBS partners. Considering the fact that Navision Attain had strong clientele in Europe, and the fact that currently MBS promotes Navision on the majority of emerging markets: East Europe, Russia, Brazil – the point of view that Microsoft got very large pool of clients in Europe and one of the goals of Navision acquisition was geographic expansion.

o Axapta. Navision Software was indeed very robust and it was one of the Danish software “dragons” (in the good sense of this word), the other nice company was MacHanza. We would like here to credit Danish ERP vendors. Axapta was new product on the moment of acquisition and it is rich-functionality ERP and so – a rival to SAP, Oracle Financials, PeopleSoft

o Small Business Manager/Small Business Financials. This was natural way of downsizing the functionality of Great Plains Dynamics/Microsoft Great Plains to gain small business market. Small Business Financials is Great Plains Dexterity written accounting package. You see similar marketing moves from SAP and Oracle sides.

o Small Business Accounting 2006. It took Microsoft about four years to feel itself comfortable on the ERP market before it decided to create its own small business package, targeted to take over market share from QuickBooks, MYOB, PeachTree. Small Business Accounting 2006 is really nice application, which is excellently integrated with Microsoft Office/Microsoft Outlook. Microsoft is right – majority of Windows users spend their computer time in Microsoft Outlook and Microsoft Excel. And it create accounting application, allowing you to do 50% of work from Microsoft Outlook directly

o Microsoft POS. As you know that there are several thousand small retail businesses in the USA, using just one cash register and these folks have to use a lot of small Retail Management applications, which are competing on this market for a long time. And it is a good momentum to take over this unreliable and turbulent market offering cheap and solid rock solution, working with POS devises. Please, take into account that Microsoft has another high-end Retail Management system – Microsoft RMS, which can automate midsize and huge retail stores and chains.

o Market is taken over? Well – the last flint of Microsoft Small Business Accounting and Microsoft POS give customer an option to stay in Microsoft framework from the company inception till going public as a large corporation. This fact would be very difficult to ignore for such folks out there on the market as BestSoftware, SAP, Oracle, Sun.

Related : restaurant accounting software computerized accounting software accpac accounting software

Published August 21, 2010 – 4:09 am Categories: great plains accounting software | Comments Off

Tagged , , , , , |

Great Plains Automatic Batch Posting Overview

If you know Microsoft Dynamics GP architecture, Dexterity business logic, you probably realized that standard Great Plains Integration tools, such as Integration Manager, eConnect, which are typically deployed in eCommerce integration scenarios, allow you create only so-called work transactions: SOP Invoice is the most popular transaction type. Work transaction is placed to the batch to be saved for future review and posting by GP user. It is probably impractical to try posting batches through Dexterity from scratch programming, as you will spend a lot of hours just to getting through Dex programming learning curve, plus you will need Dexterity so-called source code to dive deep enough for finding the way to trigger batch posting programmatically. In this article we are describing Posting Server product:

1. Triggering batch for posting. As being eConnect C# or VB.Net developer you have an instrument to create transaction, place it into the batch (and save by doing that). Next, you should just place this batch record into posting queue table – this is custom table, where posting server monitors new records

2. Dexterity engine. The flexibility of this approach relates to the fact that posting server calls Dexterity posting procedure and so, it is pretty reliable in version upgrade, as posting procedures are one of the core functionalities of GP

3. Posting batches in almost all modules. As posting is done by Dexterity engine, it is typically unified for all the GP modules and so, posting server doesn’t have modules limitation. Some restrictions apply, usually for third party add-ons to standard GP

4. Integration Manager. If you plan to deploy IM, then you should plan to populate queuing table with additional programming – simple SQL stored procedure will do the job

5. Sales Order fulfillment. If you are intermediate party or reseller, you can post batches in both Sales Order Processing module as well as in Purchase Order Processing, where you order from your vendors. In this case posted Sales batch will trigger posted Purchasing batch.

Recommend : compare quickbooks fixed asset accounting software

Published August 20, 2010 – 8:25 pm Categories: great plains accounting software | Comments Off

Tagged , , , , |