Effective task management is essential in the field of enterprise resource planning. Administrators could designate particular batch servers to a batch group with more flexibility prior to Microsoft Dynamics 365 for Finance and Operations (D365FO) introducing “Priority Based Scheduling”. This capability was not merely about enhancing capacity but also about controlling and limiting it. The Problem of Overutilization Recently, our team encountered a significant challenge. We had 98 tasks, all marked with a “normal” scheduling priority, that were able to execute simultaneously. Given that more than 98 tasks were available, all of them entered the executing state at the same time. This situation led to a 100% Database Transaction Unit utilization over a prolonged period, which is far from ideal. Such a high utilization rate can strain the system, leading to performance issues and potentially impacting other operations. In the past, this kind of issue could have been mitigated. The older batch group mechanism allowed us to limit the number of batch servers assigned to a batch group, thereby controlling the number of parallel tasks. Unfortunately, with the shift to “Priority Based Scheduling,” this direct control seemed to have been lost, leading to the problems we recently faced. Discovery of Batch Concurrency Control With the release of version 10.0.38 PU63, a new feature called “Batch Concurrency Control” caught my attention. This feature reintroduces the ability to limit or throttle the number of parallel tasks in a specific batch group. Had we been aware of this feature earlier, and had the users selected the correct batch group in their request forms, we could have limited the number of parallel tasks to a manageable number, such as 10. This would have prevented the processing from adversely affecting other users and maintained overall system performance. Activating and Utilizing the Feature After activating the “Batch Concurrency Control” feature, you will notice a new field in the batch group settings. This field is crucial for managing task concurrency effectively. Understanding the Help Text The maximum number of tasks that can run in parallel at a time for Batch Jobs in this Batch Group. This setting should be set to zero if concurrency control is not required. To completely stop all batch jobs in this Batch Group, set the value to -1. It’s important to remember that using this feature on batch jobs with more than 5000 concurrent tasks that are prepared to run could have a negative effect on batch scheduling performance. This explanation is vital. Setting the value to zero means no concurrency control, while setting it to -1 halts all batch jobs in the group. However, caution is advised against using this feature for batch jobs with more than 5000 concurrent tasks, as it could degrade the performance of batch scheduling. Implementing the Feature in Our Workflow In our operations, we now actively use this feature to manage the number of available tasks per batch group. This approach mirrors our previous strategy, where we selected only a few batch servers for a specific batch group. By doing so, we can effectively throttle the tasks and ensure a balanced load across the system. Conclusion The introduction of “Batch Concurrency Control” in Microsoft Dynamics 365 for Finance and Operations has provided us with a much-needed tool to manage and control task execution within batch groups. By setting appropriate limits, we can prevent system overloads, maintain performance, and ensure a smoother operation. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com 

Introduction: Ensuring user security is a crucial aspect in Dynamics 365 for Finance and Operations. To access or utilize the features of Dynamics 365 F&O, a user must have a role assigned to them. Without a role, the user will be unable to perform any actions within the system. Access levels and business processes for a particular role are determined by the duties and privileges associated with that role. In this blog post, we will explore two recently introduced features that simplify the process of comprehending and setting up customized security roles within Dynamics 365: security diagnostic and security configuration tools. Defining terms used in Security: Security Roles: – Security roles in Dynamics 365 define how users can access different modules. – The system comes with pre-defined security roles that can be assigned to users. A user has the ability to possess multiple security roles. – Data security policies can only be applied by the administrator to limit user access to data. – To gain access to Finance and Operations, it is mandatory for users to be assigned to at least one security role.  – Security roles correspond to company responsibilities and contain a set of duties required to carry out functions. Duties: – Duties correspond to tasks of a role and are part of a business process. – They are composed of privileges necessary for performing an action. – Duties can be assigned to multiple security roles and help reduce fraud and detect errors. – Segregating duties is important for regulatory compliance such as SOX and IFRS. – Default duties are provided, and administrators can modify or create new duties. Privileges: – Privileges are unit action sets that correspond to system functions. – They specify the level of access required to perform a job or complete an assignment. – Privileges refer to specific permissions granted to application objects such as UI elements and tables. – Default privileges are provided, and administrators can modify or create new privileges. Permissions: – Permissions are required for accessing functions in Dynamics 365. – Access levels are grouped for permissions to tables, fields, forms, or server-side methods. – Permissions include any tables, fields, forms, or server-side methods accessed through the entry point. Security Configuration Tool: The Security Configuration Tool is a useful tool for administrators as it enables them to create and manage security roles, duties, and privileges.  The Security Configuration Tool is a feature in Dynamics 365 that offers various benefits to users. Here are some of the benefits: Display Entry Point Permissions: The tool enables administrators to display entry point permissions for a given role, duty, or privilege. Test Security Role is a useful feature that allows users to check if a security role, duty, or privilege has been newly created or modified, without having to create a separate test user account.  Non-Permanent Changes: Changes made in the Security Configuration Tool are not permanent and must be published to take effect. Data Export/Import: Changes can be saved as a data export file that can be imported into desired environments. Full Hierarchy View: Users can access the tool by going to System Administration > Security > Security Configuration and have a full hierarchy view of roles, duties, privileges, and entry point security assignments. Duplicate Existing Roles: Users can duplicate existing roles, duties, and privileges. Various Options: The tool offers several options for performing against the currently selected role/duty/privilege, including undo/redo customizations, creating new roles, showing all levels, deleting roles, duplicating roles, copying roles, viewing permissions, and displaying the audit trail. To add a new role in Dynamics 365 with the Security Configuration Tool, you can follow these easy steps: Step 1: Select the ‘Roles’ tab and click ‘Create new’ to create a new role in Dynamics 365. Step 2: Enter the name of the new role using a different naming convention so that it is easily identifiable. Step 3: To add a new duty to a role, highlight it, go to the Duties column, and select Add references. All duties (and customs if created) will be available in the list. Step 4: You can select certain tasks, and their corresponding privileges, to be available in a role. If needed, users can remove certain tasks from the role. Step 5: To modify object permissions, go to the Privileges section. Dynamics 365 has different access levels, such as Read, Update, Create, and Delete, that determine a user’s level of access to a particular record or record type. Security roles have three types of access levels: Unset, Grant, and Deny. Step 6: Any modifications made in the user interface must be published before they are implemented. This list shows all the changes that are not yet published. Security Diagnostic Tool: The Security Diagnostic Tool is a unique feature of Dynamics 365 that empowers individuals with a security administrator or system administrator role to conduct an assessment on any form to identify the roles, duties, and privileges required to accomplish a task.  The tool provides numerous advantages to its users, including: To use the Security Diagnostic Tool, simply follow these steps: go to the Option tab, then select Page Options, and finally, click on Security Diagnostics.  This will automatically run the tool for you. Remember that the Security Diagnostic Tool is available on any form.  After the tool runs, it will generate a comprehensive list of all the roles, duties, and privileges related to that particular form.  This enables administrators to quickly identify any gaps in security and make necessary adjustments to ensure the protection of the system and its data. Conclusion: In conclusion, Dynamics 365 for Finance offers a reliable and secure role-based security system that guarantees that users have access to only the data that is necessary for them to carry out their tasks. The security roles, duties, privileges, and permissions collaborate to create a comprehensive security system that is effective.  Moreover, the security diagnostic and configuration tools make it simpler to comprehend and customize security roles in Dynamics 365. We hope you found this … Continue reading Security Roles in D365 Finance and Operation →

In the world of retail and commerce, managing sales returns efficiently is a critical aspect of customer satisfaction and operational excellence. In this blog, let’s explore how the sales return process works in Dynamics 365 Finance and Operations (D365FO) and explore how businesses can leverage the capabilities of this robust ERP system to streamline and enhance their return management. In this part, I will walk you through the standard process. Please keep in mind that the steps and setups may vary based on the business requirement. Let’s consider a scenario wherein we have sold 10 quantities to the customer and amongst them 3 quantities get damaged during transit. So now the customer wants to return those items back to us. So, lets create a Return Order, to do that go to Sales and Marketing>Sales Return>All Return Orders. Create a New Return Order. The RMA number is generated automatically based on the Number sequence set up. Tip: In order to generate the RMA Number manually you can enable the Manual number sequence parameter in the RMA Number Sequence set up. For this scenario, I have enabled the Manual Parameter. The next step is to Enter the Customer Details, Site, Warehouse, Return Reason Code and RMA Number. Then click OK. Now to add the line item on the Return Order line there are two ways to do it: For now, I will go with the Find Sales Order function. To use that go to the Return Order fast tab in that under the Return Tab click on the Find Sales Order button. The next step is to select the Sales Order Invoice for which the Return Order will be Created.   Based on my scenario the system has automatically taken the quantity as 3. In the above screen shot you can see that a New Return order is created with the Negative line quantity. Return Order processing: There are two ways to process a Sales Order Return: 1.Credit Only: In the credit-only process, the customer’s account is credited without the need for replacing or returning the item. Here, the Sales price is credited to the Customer deducting the charges. 2.Physical Return: The Physical Return process involves the Return of Item to the customer. Here during registration, a Disposition Code is assigned which determines the Sales Return process for that particular Item. To keep this simple and easy to understand I will go ahead with Credit Only process in this part. But for this we will first need to create a Credit Only Disposition Code. For that go to Sales and Marketing>Set Up>Returns>Disposition Codes. In that Click New and create a New Credit Only Disposition Code. Now the next step is to Register the Return order for that on the Return order lines click Update Line then under that click on Registration. Then select the Credit Only Disposition Code and click OK. Then Confirm the Registration. As I click on the Confirm Registration button a New Sales Return Order is created with the same quantity and same customer on the All-Sales Order page. The next step is to Invoice the Sales Return Order. After Invoicing the Sales Return Order, in the below screenshot you can see that the Return status of the order is changed to Invoiced. This completes the Credit only sales return order process. Maintaining customer satisfaction and operational efficiency in Sales and Marketing involves effectively managing sales returns. Dynamics 365 Finance and Operations (D365FO) simplifies this task, whether you opt for a credit-only strategy or handle physical returns. By leveraging D365FO’s powerful features, businesses can ensure precise and efficient return management, enhancing both customer relations and operational excellence. Stay tuned for the next section, where we’ll dive into the Physical Return process. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com 

Introduction:  As a business owner, you might have come across a situation where you want to upgrade your current systems with renowned ERP solutions available on the market. One of the ERPs you would consider is Microsoft Dynamics. However, even choosing this would require a lot of brainstorming from all decision-makers because Microsoft Dynamics comes with two ERP platforms, i.e., Dynamics 365 Business Central and Dynamics 365 Finance & Supply Chain. I assume this brainstorming itself would have probably landed you on this article. Let’s dive into the key differences and use cases for each platform. Hopefully, by the end of the article, you will be able to make a decision and choose the right platform for your business.  Below are the key factors differentiating Dynamics 365 Business Central and Dynamics 365 Finance & Supply Chain: Company Size: When determining company size, the usual factors that are considered are revenue and employee count. The definition of which can change based on the country you are located in. Here, for reference, we would consider the following: – Revenue: a. SME: Having revenue between 0 and 1 billion USD. Business Central is ideal for this size of company. b. Large companies: Having revenue above 1 billion USD. Finance and Operations is the ideal platform for large organizations. – Employees: a. SME: having employees between 0 and 500. b. Large companies: having more than 500 employees. Number of Entities: If your company has multiple legal entities in multiple geographical locations across the world,a. Business Central is ideal for companies with a single legal entity or multiple legal entities in the same country. Business Central allows you to create and manage individual products and accounts for each legal entity; however, it cannot be managed centrally. b. Finance and supply chain are ideal for companies with multiple legal entities across the world. Finance & Supply Chain allows you to manage products and accounts centrally and release them centrally to each legal entity across the world. Business Operations: Does your company have streamlined and simple operations? a. Business Central can handle operations for companies with streamlined and simplified operations that do not require very detailed data capture or sophisticated reporting. b. Finance & Supply Chain captures detailed data, covers a lot more processes than Business Central, and hence can provide robust and detailed reporting. Future Growth: It is also important to consider what the growth plans are for your company. If you currently have 2–3 legal entities, you may be tempted to go with Business Central, as it comes with low implementation and operating costs, ease of use, and faster implementation timelines. However, ERP projects are not done frequently, and it is important that you consider future organizational plans. Let’s say you intend to expand over the next three to five years into multiple different geographical areas. You should think about finance and supply chain as your organization’s go-to platform since this will be a big, long-term investment. You might want to consider the following factors while making the decision: – Licensing: a. Since finance and supply chain are for large companies, they come with a minimum licensing requirement of 20 licenses. b. Business Central is perfect for small and medium-sized businesses (SMEs) because it only requires one license and has no minimum licensing requirements. – Implementation timelines:a. Finance and Supply Chain has a typical implementation timeline of 6 months or more, considering the size of the implementation and global rollout.b. Business Central can be up and running in 3–6 months.    Conclusion:  Choose Business Central if: You’re an SME seeking an easy-to-use, all-in-one solution with a lower upfront and operating cost.  Choose D365 Finance & Operations if: You’re a large enterprise requiring extensive functionalities, deep customization, and global capabilities.  We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction: Businesses in the digital age depend on cloud platforms and ERP systems integrating seamlessly. Dynamics 365 Finance & Operations (F&O) and azure integration is one such potent combination. Numerous advantages, such as improved scalability, agility, and data-driven decision-making capabilities, are made possible by this integration. The step-by-step instructions for connecting Azure with Dynamics 365 F&O will be provided in this blog. Steps to achieve the goal: Step 1: Setting up Azure Services a. Create an Azure account: Sign up for an Azure account if you don’t have one already. b. Provision Azure resources: Set up the required Azure resources such as virtual machines, databases, storage accounts, and other services according to your needs. Below are few links to create azure account. https://learn.microsoft.com/en-us/answers/questions/433827/how-to-get-an-azure-account-without-credit-card https://azure.microsoft.com/en-in/free/students Step 2: Configure Azure Active Directory (AAD) a. Click on New on the App Registration page. Set the name and set the type like below screenshots. b. Once you click on Ok button you would get notification like below. c. Now go to API Permission and click on Add permission d. Select Dynamics ERP e. Select Delegated Permission f. Select all permission and then click on Add Permission g. After selecting this permission again add permission on the screen this time selected Application Permission. h. Now we have to generate client secret value. Just select Certificates and secret. i. You will see the below screen where you can generate a new client secret j. Once you click on new you will see below screen where you can set the date to which this secret key would be valid. Max validity is 2 years. k. This is how the secret value would look like just copy Value. l. Now copy the Directory ID and Application ID Step 3: Connect Azure Services to F&O a. Go to Finance and Operations and serach globally Azure Active Directory/Microsoft Entra ID b. And then click on New and add your client id over here and set User ID as Admin. Please Note you should have the admin access right if not this won’t work. Conclusion: Azure integration with Dynamics 365 Finance & Operations empowers businesses to streamline processes, unlock data insights, and achieve operational excellence. Next blog would be how to connect standard API on postman and perform get and post function. Stay tuned! We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Client Requirement: Financial Reporting Year Change from Jan-Dec to Apr-March The last financial year is January2021 to December2022. Client has the requirement to change the year to April to March. The transition year needs to be from January 2023 to March 2024. In Microsoft D365 F&O, fiscal calendar can be of 15months, however, ledger calendar cannot be more than 12 months. Solution: 1.  Ledger calendar can be shorter than 12 months. 2. We need to do two-year end close process: a. For January 2023 to December2023 – 12 months b. For January 2024 to March 2024 – 3 months 3. Client can have regular financial year from April 2024 to March 2025 onwards. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Hello everyone, in this series of Blog, we are going to learn about the Advance warehouse management in D365.  In this blog we will learn about the basic setups required for the Advanced Warehouse Management process. These setups may vary depending on the business scenarios. As a continuing blog from https://www.cloudfronts.com/blog/advance-warehouse-management-item-creation-part-1/ and https://www.cloudfronts.com/blog/advance-warehouse-management-warehouses-and-locations-in-microsoft-d365-fo-part-2/, this is will be a part 3 of the series. The following are the setups that we need to configure:  Load:  The loads are useful when we group multiple shipments. So, you can consider load as an object that will be used to transport the material.  Path:   Warehouse Managementà SetupàLoadà Load Templates  I have created two containers here as a load. One is a 20 ft container, and the other is a 40 ft container.  Location Directives:  The Location Directive plays a significant role in inventory movement in advanced warehouses. Location Directives are the set of rules which define the pick and put, Counting, License Plate building, Status change and Quality check etc. for individual warehouse or group of warehouses.  For my current scenario, I will create location Directive for a Purchase Order transaction. In further blogs I will write about other transactions as well.  Select the Work Order type as Purchase Order.  Select the work type as “Put.” For the receipt location, I have mentioned the default receipt location in the warehouse master.  For default receipt location, Go to Warehouse managementà Setupà Warehouse à Warehouses.  Select the default receipt location from the Drop down.  Select the Warehouse for which this “Put” rule going to work. You can group the warehouse and select the warehouses to work similar to the rule.  In the lines I have mentioned the from Quantities and to quantities.  For location directive action, I am using “Only fixed locations for the product.” By this, the system will ask for the location while Putaway operation in the Purchase Order.  Now, the Loads and location directives are ready to use in Advance Warehouse process.  That’s it for this blog!!  How to use these Loads and location directives in actual transaction will be discussed going forward in the blog series.  Keep learning!!!!!  Next in the Blog series:  How to create Work Classes and Work Templates in Advance warehouse management in D365.  How to set up Worker in Advance warehouse management in D365. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

In D365 Finance and Operations, managing transfer orders is a crucial aspect of maintaining efficient inventory operations. However, there may be instances where you need to cancel a transfer order shipment due to various reasons such as changes in demand, inventory discrepancies, or operational adjustments. In such cases, it is essential to understand the process of cancelling the transfer order shipment to ensure accurate inventory management and smooth operations. Here are the steps to cancel the transfer order shipment in D365 Finance and Operations: Go to Inventory Management>Out Bound Orders>Transfer Order. Here, I have already created the Transfer Order which is in Created State. Here, I am transferring the Items from (Warehouse W1 to Warehouse W2). The next step is to ship the Transfer Order. In the below screenshot you can see that the Transfer Order has been Shipped. As the Transfer Order is shipped the following Transactions are posted. Now to Cancel the Transfer Order Shipment. In the Transfer Order tab click on Transfer Order History which is under the View Action tab. Here you can see the Transfer Order Shipment. Select that and then click on the Cancel Button from the top of the screen. By clicking this the system will automatically reverse the Transaction. You will see that a Reverse entry is posted with negative quantity and there will be a right tick under the Cancelled Shipment column. Now if I go to Transactions, I can see that the entry has been reversed and the Transfer Order status has been reverted back to Created. Note: The Transfer Order which has been received cannot be Reversed by this process. Transfer Orders which are only in Shipped state or transfer orders where in Shipment has been sent can only be cancelled or Reversed. Depending on your system configuration you may need to manually adjust the Inventory. That’s it for this blog! Hope that helps, thank you for reading!!

In inventory management, there often arises a need for flexibility, especially when dealing with orders that exceed current stock levels. Dynamics 365 Finance and Operations offers a solution to this challenge through enabling physical negative inventory.   This functionality allows organizations to create sales orders even when inventory levels are insufficient, catering to scenarios where a stock may be incoming or when manufacturing units are involved.  Purpose of Physical Negative Inventory:  Some organizations encounter situations where they must fulfil customer orders despite lacking sufficient inventory on hand. This could be due to various reasons such as pending stock arrivals or the need to initiate manufacturing processes upon order placement.   Enabling physical negative inventory facilitates the creation of sales orders under such circumstances, ensuring business continuity and customer satisfaction.  Process to Enable Negative Inventory:  Enabling physical negative inventory involves configuring settings within Dynamics 365 Finance and Operations. This can be achieved through the following steps:  Navigate to Inventory Management > Setup > Inventory > Item Model Group.  Within the Item Model Group, allow for physical negative inventory.  For further insights into this process, refer to our previous blog post on https://www.cloudfronts.com/blog/d365-enterprise/d365-finance-operations/physical-negative-inventory-dynamics-365-operations/ can provide additional guidance.  Necessary Steps to Manage Physical Negative Inventory:  Once physical negative inventory is enabled, it’s essential to adopt proper procedures for its management to maintain accuracy and efficiency.   • Ensure Availability of Physical Inventory during Shipment: Before shipping any items, verify the presence of physical inventory in stock. Only proceed with the shipment if the required items are physically available.  • Transfer Stock if Necessary: If the required stock is not available at the shipping warehouse but exists in the main warehouse, initiate a transfer process to move the items accordingly and receive that in a shipping warehouse.  • Periodic Inventory Closing: Implement regular inventory closing procedures to ensure accurate inventory valuations.  Issues Faced by Organizations if Proper Procedures Are Not Followed:  Failure to comply with the proper procedures can lead to various issues, including:  Invalid Cost Value of Items: This can result in an inaccurate inventory valuation, subsequently affecting main accounts and profit estimation.  In conclusion, by following these steps, organizations can effectively manage physical negative inventory within Dynamics 365 Finance and Operations, ensuring smooth operations and accurate inventory valuations.  We hope you found this article useful and if you would like to discuss anything you can reach out to us at transform@cloudfonts.com 

Hello everyone, in this series of Blog, we are going to learn about the Advance warehouse management in D365.  In this blog we will learn about the basic setups required for the Advanced Warehouse Management process. These setups may vary depending on the business scenarios. For a Warehouse to work in an Advance warehouse scenario, there are some prerequisites that we need to do first. The following are the setups that we need to configure:  Path: Inventory Management Inventory Breakdown Warehouses.  Click on New. Enter the warehouse and Warehouse name.  Most importantly, for warehouse to work in a advanced warehouse scenario, we have to enable the “Use warehouse management processes”.  For advanced warehouse management, the location plays an important role for better inventory visibility and item tracking. For this, we need to do multiple setups as per below.  In the location type, I have mentioned four main locations. These are Baydoor, Floor, receiving and User.  These locations will increase or decrease as per business scenarios.  Recv: This location I am using primarily for entry of the goods/items in the warehouse.   Floor: This location I am using for storing the goods/items in the warehouse.  Baydoor: This location I am using for exit of the goods/items from the warehouse.  User: This location I am using for default. This user location will be used in the Warehouse management parameter, in User Location profile.  Location formats are used as the naming system by which we can create the unique and consistent names for different locations within the warehouse.  Here, I have mentioned the length as 1.   The location profiles will be used for connection between location type, Location formats and the locations. The location profiles are very important setup because the location capacity can be mentioned here. Also, how the inventory is stored in the location, and how the inventory is getting accessed is also dependent on the location profiles.  Here, I have enabled User license plate tracking, allow mixed items, Allow mixed inventory statuses, Allow mixed inventory batches.  Click New. Select warehouse from the drop-down menu. Enter location name as per requirement. Select the Location profile ID from the drop-down menu.  We can add as many locations as we want.  Now, the warehouse and locations are ready to use in Advance Warehouse process.  That’s it for this blog!!  How to use these warehouses and locations in actual transaction will be discussed going forward in the blog series.  Keep learning!!!!!