Planning: Dynamics GP System in .NET Render barcode data matrix in .NET Planning: Dynamics GP System

Planning: Dynamics GP System use none none maker toinsert none with none USS-93 Now that yo none none u have put together your business requirements, you should plan out the details of your Dynamics GP system. In this chapter, we will go over the second implementation planning phase and focus on the following topics: How many companies to set up in Dynamics GP Integration with other systems General Ledger account framework and account format Numbering schemes for master records Fiscal year and period setup Users and security planning Sales and purchase tax setup Additional setup considerations including shipping methods, payment terms, credit cards, posting setup, and multicurrency. Companies in Dynamics GP A critical none none decision that is very difficult to change after implementation is whether or not to have multiple companies in Dynamics GP. Sometimes there is no question, as there is only one company or there are clearly separate entities. However, often there are multiple legal entities, branches, or subsidiaries that may require separate accounting records and procedures, but also share customers or inventory items.

There is no limit on the number of companies you can setup in Dynamics GP. Each company created becomes a separate SQL Server database and behaves autonomously, save for a few shared characteristics global to the entire Dynamics GP installation, such as system users, currency setup, and exchange rate tables..

Planning: Dynamics GP System There are s none none ituations when separate companies are clearly recommended in Dynamics GP: If accounting records must be kept in different functional currencies to conform to local requirements When using Dynamics GP Payroll and there are different Federal ID Numbers If there are entities that have different fiscal periods Some types of businesses require separate accounting books to be kept to comply with various federal and state regulations. If the requ irement is simply to keep separate General Ledger accounts for each separate entity, this is fairly easy to accomplish within one Dynamics GP company. In some situations, there is no right or wrong answer as to whether to have one or multiple companies, the following sections will discuss the benefits of the two approaches in more detail..

Benefits of having one company in Dynamics GP The benefit s of having one company in Dynamics GP are as follows: Initial company setup is faster: Even if there are different General Ledger accounts for multiple entities within one company, there are significant time savings in only having one Dynamics GP company to set up. Ongoing maintenance and support are simpler: Multiple companies add ongoing incremental time, and thus cost, to maintenance and support. Even though many maintenance tasks can be automated, monitoring and support is simpler for a single company database.

Any changes, service packs, or additional products installed may need to be performed separately for each company. Upgrades will typically take less time for one large company database than multiple smaller ones. Less storage space is needed: Having multiple databases in SQL Server increases the storage space needed because each separate database will have some duplicated overhead.

Also keep in mind that each additional company will require added capacity for backups. This benefit may not be so important anymore, with storage being much more affordable than it has been in the past, but it is still something to consider..

[ 52 ]. 3 . Yearly proc none none essing is faster: Yearly closing for various modules only has to be done once if there is one Dynamics GP company. Other yearly company-specific tasks, such as creating new fiscal years and yearly budgets, will take less time with one company. Reporting is simpler: Typically creating reports for one company takes significantly less time.

There are no built-in multiple-company reports in Dynamics GP. Ability to share vendors, customers, and inventory items: Dynamics GP does offer an Intercompany module, but it is fairly limited. For example, there is no way in Dynamics GP to sell an inventory item from one company to a customer in another company.

(There are third-party add-on products that can help with this.) Imports and integrations with other systems may be simpler: Typically, imports and integrations with other systems are more straightforward to set up and maintain with only one Dynamics GP company. Availability of additional products or modules is not limited: There may be some modules or products that will not support multiple Dynamics GP companies easily.

Having one company will obviate any concerns about this..
Copyright © . All rights reserved.