26.05.2016, 18:11 | #1 |
Участник
|
stoneridgesoftware: Knowing When to Create a New Company or Company Dimension Entities in Dynamics NAV
Источник: https://stoneridgesoftware.com/knowi...-dynamics-nav/
============== When considering how to introduce new entities in Dynamics NAV, such as companies or divisions, etc., there are a number of factors that should be taken into consideration. Sometimes, the right solution is to create a new company in NAV; other times, the better solution may be to create a new dimension instead. Main points to consider for adding new dimension entities in Dynamics NAV:
Accounting As a rule of thumb, if the new entity has a unique federal ID number, you should first consider a separate company in NAV. While it is possible to successfully implement multiple FEIN entities in the same NAV company, the other variables need to be strongly in favor of the single company model. The reason for this usually boils down to accounting, specifically the balance sheet. Master Data & Subledgers If you will need the ability to produce a balance sheet for the new entity, independent of the other entities in the database, the single company model starts to become challenging. In concept, you can create a new dimension in NAV, (ex: “COMPANY”), within an existing company in the database, and use that to segregate transactions and report an independent balance sheet. In reality, you will need very good dimension rules on your G/L accounts and independence in the master data. The master data includes your customers, vendors, bank accounts and items. Because the balances for those areas reside in the balance sheet, it is critical that related transactions are segregated completely. Often, customers, vendors, and banks are unique between entities – or can minimally be managed separately. As an example, you may have a customer with which two different entities do business, but you would never expect to send an invoice or receive a cash receipt common to both entities. Therefore, a common customer could still have completely segregated history and allow per-entity reporting. Likewise, vendors and banks seldom require co-mingled transactions. On the other hand, sharing the common master records themselves, but with segregated histories, is an argument in favor of a new dimension rather than a new company. The exception to the master data rules is often inventory. If the same part numbers are available and used in multiple entities, the balances will not be consistently maintained by a dimension – “COMPANY” or other. This prevents running a per-entity balance sheet that truly balances within the entity. If part numbers are not common across the entities, we can potentially address the balance sheet segregation requirements through setup rules alone. Currencies & External Integrations If we pass the first three tests above, then there are four more considerations to address. The first of these is currency. If the base currency in the new entity is different, then it should be represented by a new company in NAV – always. Likewise, if external integrations require NAV companies rather than a dimension, we must comply. An example would be separate web stores where the connection from NAV inherently presumes no more than one web store per NAV company. Security & Intercompany Workflow The final two considerations are security and interplay requirements between entities. If you need users to be limited to one entity, with hard limitations, a separate company is recommended. There are some tools that can help segregate security by a dimension, but they are imperfect for this purpose and require a good deal of planning and ongoing management. Counter to the security argument for multiple companies is the integration argument for a single company. If many workflows require movements (documents, inventory, etc…) or allocations across companies, then the single company model is favored. Intercompany tools exist in NAV, but the workflows are often significantly simpler if both entities reside in one NAV company. In conclusion, the answer is seldom simple. You should plan on a dialogue with your partner and a pros/cons review of the variables described here. This exercise will inform your knowledge of the possibilities and allow you to make the most appropriate decision for your business. Источник: https://stoneridgesoftware.com/knowi...-dynamics-nav/
__________________
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору. |
|
|
Опции темы | Поиск в этой теме |
Опции просмотра | |
|