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!!!!! 

Hello everyone, in this series of Blog, we are going to learn about the Advance warehouse management in D365.  What is Advance Warehousing Process?  The day-to-day transactions in the advanced warehouse are a bit different than in a normal warehouse. Workers in the advanced warehouse use mobile devices to move stock from one location to another. Here location doesn’t mean just the location, we can move it from one warehouse to another. So, instead of sitting in one place, workers can move around the warehouse to pick up or put the stock. In Advance warehouse management, the visibility of the stock is very clear. Workers can see where the stock is in the warehouse and in what quantity. This results in Streamlined warehouse operations, reduced inventory carrying costs, and thus improvement in customer satisfaction through faster and more accurate order fulfillment.  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 an item 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: Product Information Managementà Dimension and Variant Groupsà Storage Dimension Groups.  In the Storage dimension group, activate the “Use warehouse management process.”   Once you activate the use warehouse management process, the Location, Inventory Status, License Plate will be automatically activated.   2. Reservation hierarchy   Path: Warehouse Management à Setupà Inventoryà Reservation Hierarchy.  A reservation hierarchy helps delay specific reservation details until after you’ve placed an order. This hierarchy relies on item-related factors like inventory status and license plate for storage and tracking. While it’s essential to have site, warehouse, and inventory status information during the ordering process, certain details like location can be added after making reservations. For instance, the warehouse management system can identify the best locations for picking based on this reservation hierarchy.   3. Unit sequence groups Path: Warehouse Management à Setup à Warehouse à Unit sequence groups.  Unit sequence group is mandatory setup which works when dealing with movement of material. Now take one example: If the Unit sequence group is mentioned as Each and Box, then While making product receipt from a Purchase Order, mobile device will show the options to receive the materials in two different units which are Each and Box.  Here based on my scenario, I have mentioned the default unit for Purchase orders and Transfer Order as Box.  Now, the Item is ready to use in Advance Warehouse process.  That’s it for this blog!!  How to use this item in actual transaction will be discussed going forward in the blog series.  Keep learning!!!!!  Next in the Blog series:  How to create Warehouses in Advance warehouse management in D365.  How to create Locations in Advance warehouse management in D365. 

Introduction In this blog, we’ll be looking into creating a new environment for D365 Finance and Operations or D365 Commerce. Pre-requisites References Configuration Go to Microsoft Dynamics Lifecycle Services and log in with your account. If you select D365 Commerce, you get the following screen. If you select D365 Finance and Operations, you get another screen where you have to specify whether the project is an actual implementation or just for evaluation after which you get the same screen as below. Once the Project is created, we get the following screen. From here, we click on the hamburger menu at the top and then click on Cloud Hosted Environments. Click on Add to create a new environment. If you get the below pop-up asking to configure an Azure Connector, please refer to my blog – “Configure an Azure Connector in LCS”. Once, you have an Azure Connector configured, you can click on Add again and get the following pop-up. After selecting the Application and Platform version, you’ll get the option to select the environment topology. DEMO – A demo environment includes only Microsoft demo data. You can use a demo environment to explore default features and functionality. DEVTEST – A DevTest environment is for development or build. You can use this environment for development or build. Then we get another pop-up to select the environment topology. After that is selected, we decide the environment name and the size of the VM that is to be used for this environment. You can read more about VM sizes here – VM sizes – Azure Virtual Machines | Microsoft Learn Once we click on Next we get the last pop-up after which the environment gets deployed. Once we click on deploy, it takes about 6-8 hours to deploy the environment after which it’ll be available in the cloud-hosted environments section. If, for some reason, you try to create an environment with the latest platform and application version and that deployment fails, you can try to create an environment one platform/application version below that. Conclusion Thus we saw how to create an environment in LCS for either D365 Finance and Operations. Happy Coding!

In Dynamics 365 Finance and Operations (D365 F&O), the use of batch numbers is a common practice to manage and trace items with specific characteristics. Batch numbers are typically assigned to groups of items produced or received together, allowing for better control, tracking, and compliance with industry regulations. In this blog I will explain how to solve the expiration date issue while registering a Batch and Serial number tracked product. In the above screenshot you can see that the Batch Number 23010-CM-000088 has been assigned for my Item P-000014. Here, the Expiration Date is 08-04-2023. Now if I try to register this Item with the same Batch Number, I will get the Batch Number Expiration Date being past the Required Date error. Now to solve this error go to Inventory Management>Enquiries and Reports>Tracking Dimensions>Batches. Now on the Batch Number page go to Reset Tab then under the Reset tab click on Reset Shelf-Life Dates. The next step is to select the New Expiration Date and then Click Ok. This will Update the Expiiration Date of that Batch Number. In the above screenshot you can see that the Expiration Date has been changed. Now we will be able to register the Item. Here, you can see that now I am able to register the Item successfully. That’s it for this blog. Hope this helps you! Thank You!

Hello Everyone!!! In this blog I will explain the Quarantine Management process in Dynamics 365 Supply Chain Management.  Here the Product was first received in the Main warehouse and then it was moved to Quarantine Warehouse for further inspection as the Product failed to clear the Quality Test. In this blog I will explain a scenario where the Products should be directly received in the Quarantine Warehouse for inspection and after final inspection it turns out that all the products fail the inspection so, a few products will be scrapped and the rest will be returned back to vendor. What is Quarantine Management? The quarantine management process in D365 aims to effectively manage and control quality issues, ensuring that only items meeting the required standards are released for use or distribution. The quarantine management process in Dynamics 365 is a systematic approach to handling items that are suspected of having quality issues or non-conformities. When an item is flagged for quarantine, it is physically segregated from the regular inventory and moved to a designated quarantine location. The quarantined item undergoes thorough inspection and testing to assess the extent of the quality issue. Based on the evaluation, decisions are made regarding the item’s disposition, which may include repair, return to the vendor, or scrapping. If the item is repairable, necessary actions are taken to rectify the identified issues. In cases where the vendor is responsible, the item can be returned for resolution. Once the necessary actions are completed, and the item meets the required quality standards, it is released from quarantine and reintegrated into the regular inventory for use or distribution. This process ensures that only items meeting quality criteria are allowed for further processing, while mitigating the risk of non-conforming products entering the supply chain Let’s start with the setups first: Step 1: Map the Quarantine Warehouse to the Main Warehouse. For that the Pathway is: Go to Inventory Management>Set Up>Inventory Breakdown>Warehouses. Step 2: The next step is to Enable the “Quarantine Management” parameter in the Item Model Group Quarantine Management Process: The below Purchase Order CM-PO-0000137 has been received in the Quarantine Warehouse as per the setup, hence a Quarantine Order CM-0000142 with 9 quantities has been created. Now if I go to the Quarantine Orders page, I can see that a new Quarantine Order has been created. The below screenshot shows the Transactions that took place after the Product Receipt was posted. After Inspection it was found out that 5 quantities were damaged, 4 quantities were to be returned back to the Vendor which means that all the 9 quantities failed to pass the Quality Inspection. So, what I will do is Scrap the 5 quantities and return back the 4 quantities to the Vendor by creating a Purchase Return Order.  Now I will split the Quarantine Order CM-0000142 into 2 separate Quarantine Orders. For that I will use the Split function which is available at the Top of the screen under the Functions Tab. In the above image you can see that I have split the Quarantine Order CM-0000142 into 2 different Quarantine Orders that is CM-0000143 and CM-0000144 for further processing. Now let’s begin the further processing. To scrap this order, I will use the Scrap functionality. To Scrap this order, click on Function and then select Scrap. Here, you can see that the Quarantine Order CM-000143 has been ended as it has been scrapped. 2.  Return the Items back to vendor: Now in order to return the Items back to vendor I will first the Invoice the existing Purchase Order which is CM-PO-0000137. Then I will receive the Items from the Quarantine warehouse to the W3 warehouse. Below you can see that I have invoiced the purchase order CM-PO-0000137. Now let’s receive the items from the Quarantine Warehouse to the Central Warehouse, for that I will use the Arrival Journal. As you can see that a New Arrival Journal has been created. Validate and Post the Journal. Vendor Return Process: After posting the Journal create a New Purchase Order with the type as Return Order.  For that go to Procurement and Sourcing>Purchase Orders>All Purchase Orders. Then select the Vendor to whom the Items will be returned and select the Purchase Type as Return Order. Enter the Site and Warehouse from which the Items will be returned back to the Vendor. Then enter the RMA number provided by the Vendor and then Click OK. Click on the Purchase Order line, select Credit Note, choose the specific invoice, input the quantity as a negative value, and then click OK. In my case the Invoice Number was 311711, so I will select that and then click OK. Then proceed with the normal purchase order processing which will be Product Receipt and Invoicing. After Invoicing the Return Order aa credit note will be  created which will be  deducted from the Vendor Balance. The below screenshot represents the On hand List before and after posting the Return Order Invoice. In the above screenshot you can see that the On hand Quantity changed from 26 to 22 since 4 quantities have been returned back to vendor. That’s it for this blog. Hope this helps you! Thank You!

In financial management, the accurate recording and reconciliation of transactions within the general ledger stand as paramount tasks. Microsoft Dynamics 365 Finance and Operations, a comprehensive enterprise resource planning (ERP) solution, offers a feature known as General Ledger Adjustments. This feature, often overlooked or misunderstood, plays a pivotal role in addressing critical challenges associated with ledger adjustment entries due to environmental issues or data corruption. The recent discovery of the General Ledger Adjustments feature within the feature management workspace prompted a deeper exploration. However, upon enabling this feature, it became apparent that Microsoft aims to streamline and systematize a fundamental problem-solving process. Reflecting on past experiences, various challenges related to ledger adjustments surfaced: Traditionally, when encountering such issues, the path forward often involved engaging Microsoft support to delve deeper into the problem. While Microsoft proficiently identifies the root cause and initiates steps to address it in future product updates, the immediate concern revolves around rectifying the existing corrupted or missing data. The suggested workaround typically involves manual journal entries. However, this process traditionally unfolds through email communications, leading to potential discrepancies or misunderstandings regarding the specifics—such as the nature of the journal entries, relevant dates, or designated journals. The introduction of the General Ledger Adjustments feature within Microsoft Dynamics 365 Finance and Operations appears as a structured attempt to address these challenges within the system itself, streamlining and formalizing the process that was previously conducted through ad hoc communications. Enabling General Ledger Adjustments: In this section, Microsoft Dynamics 365 Finance and Operations provides an interface where recommended journal entries for data correction are populated based on identified discrepancies or issues within the system. Users are presented with suggested adjustments, and based on their discretion and analysis, they can decide to create a journal entry directly from this interface. Note: Creating a journal entry from this interface generates a “Daily” type of journal within the General Ledger, facilitating a more organized and systematic approach to handling the necessary corrections or adjustments. In conclusion, this feature signifies a proactive step towards enhancing the efficiency and accuracy of managing ledger adjustments within the Microsoft Dynamics 365 Finance and Operations ecosystem.