D365FO

  Dynamics 365 -Project Management- Project Operations: Helps plan, estimate, schedule and track projects. -Sales : Helps to track contacts, leads , marketing lists, campaigns, service cases and opportunities. https://docs.microsoft.com/en-us/dynamics365/sales/overview -Marketing: With using Sales, Customer Insights, Teams and other products helps decision making. https://docs.microsoft.com/en-us/dynamics365/marketing/overview -Customer Service: Customer Service for customers. https://docs.microsoft.com/en-us/dynamics365/customer-service/overview -Field Service: Helps deliver on-site services for customers. https://docs.microsoft.com/en-us/dynamics365/field-service/overview -Finance: Decision making of financial insights. https://dynamics.microsoft.com/en-gb/finance/overview/ -Supply Chain Management: Manage Supply Chain processes for all inventory related transactions. https://dynamics.microsoft.com/en-us/supply-chain-management/overview/ -Intelligent Order Management:C oordinate,...

   I were in a meeting yesterday of Tech Talk 2 days ago and I found that very useful if you have too many transaction to proceed.    This is a pretty new feature.  Was available in 10.0.25 but with 10.0.29 enabled with all instances. Can be enabled in feature management.    As a setup, first you have to set the  batch reserved capacity level parameter under batch global settings. There are 4 capacity type to be selected. 1.No reserved capacity – Default 2.Low reserved capacity –  %10 3.Medium reserved capacity – %15 4.High reserved capacity –  %25    You can not reserve full capacity.    Then on the batch groups, you define priority. Can see the weigh of the priorities. 1. Low: 5% 2. Normal: 10% 3. High: 15% 4. Critical: 30% 5. Reserved Capacity: 40%  Links: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/priority-based-batch-scheduling#set-the-batch-reserved-capa...

  Before to start the balance migration, be sure that all the master data is in the system like bank accounts, GL accounts, vendors , customers and their posting profiles. Also need at least one journal to be able to post the transactions. You may use a separate journal to be used once or can use one of which are already defined and to be used while balance upload journal will stay forever in the system and can not be deleted. But you may restrict by to add a user group , so that users will not see in the future as a solution. Also may require a separate journal o use a separate voucher series for balance upload but that also can be managed by to change the original journals number sequence as well. One daily journal will be enough but it depends on the implementation type while if assets are going to be uploaded or vendor invoices for balance upload need to be reported as invoices in transactional level.     While modules are used in D365FO, module related accounts ...

     What we should understand is Cost Management Module is just a module for calculation. So before this module is used, data in the system must be ready and correct. And for data to be correct, we have to setup the system correctly and train users.     In this blog I would like to explain the key points that needs to be controlled before to run the the inventory closing. I assume that the closure is done monthly basis. Before the postings 1. Train users how to process the transactions 2. Train users on which reports to use on daily, weekly and month end basis. It is very important to control the system while there is time for the month end. Not wait till the month end for controls. 3. Prepare a document/process flow of month end closure. 4. Setup item related setups correctly. (Which cost method to be used, price lists, inventory dimensions) Before to run closure: 1. Control the production orders  at the month end, all the status must be in "Ended" s...

  We have the new release of D365FO. 10.0.27 has only couple features to be released but some of them were really needed one like the customer aging report performance and bank reconciliation cancelling. Can find the list of details in the link.  https://docs.microsoft.com/en-us/dynamics365/finance/get-started/whats-new-changed-10-0-27

 There are various tiers are used in D365 F&O but each tier has its own purpose. First you have to know, the purpose of the environment.  In this blog I'll be summarizing this for you. Tier 1 and 2 depends on how you would like to do your implementation. If you want to use an environment you want to manage for security purposes, you use Tier 1 but in this case, you should know that you may not be able to use some functionalities like Warehouse mobile apps etc. Tier 1: VHD , Customer Managed Environments, Development Environments Tier 2: Microsoft Managed standard offer environments, UAT, Integration, Testing Environment,Golden Config, Pre Production Tier 3: Microsoft Managed additional environments, UAT, Integration, Testing Environment Tier 4: Microsoft Managed additional environments, Performance Testing Tier 5: Microsoft Managed additional environments, Performance Testing Also selecting a tier is depending on the user and transaction counts. There is offered counts tha...

  This question is usually asked and I see this question again couple of days ago in the community forum. So rather than to give an answer that has been explained technically, I would like to give that my answer for this question.  1. Newness:  While it is a Microsoft product, innovation is everywhere. The team is open for new technologies and improvements. 2. Documentation:  Has a huge documentation , in which is updated and is easy to understand. 3. User Support:  Supports users with the ticketing system. 4.  Project Support:  It is not only the programme that you but but also guides on how to process your project. Microsoft also cares on the project to success. This is why you can use Success by design documentations and LCS tools to decide your project models and processes. 5. Reporting Tools:  There are various reporting tools that you can use within or outside of the programme. For internal use, I can give example of standard queries, SSRS r...