We’re pleased to introduce a new capability for Dynamics 365 Finance and Operations archive with Dataverse long-term retention: parallel processing for archive jobs. This enhancement allows the Archive job scheduler to run multiple archive jobs at the same time, dramatically reducing the time required to archive high volumes of transaction data across legal entities. 

The challenge: Sequential bottlenecks 

Previously, archive jobs within the same scenario were processed sequentially. For organizations operating across dozens of legal entities—each with millions of transaction records in General Ledger, Sales Orders, or other scenarios—this approach created a bottleneck, and archiving could take days or even weeks to complete. 

For example, a multinational organization may have 50–200+ legal entities, each containing one fiscal year of General Ledger transactions. Archiving one legal entity data at a time delays storage optimization, increases SQL Server load, and slows the movement of data into long-term retention in Dataverse. 

The solution: Use Job criteria key partition to enable parallel processing 

Parallel processing introduces the Job Criteria Key—a partition identifier you set when you build the archive job contract. The job criteria key tells the archive job scheduler which archive jobs operate on independent data sets. This allows them to run simultaneously without conflict. 

How it works 

1. Define the partition key — When you build the archive job contract, set the criteria key (typically the legal entity) that represents the data partition. 

2. The scheduler identifies parallel candidates — The archive job scheduler detects that jobs with different criteria keys target non-overlapping records. 

3. Jobs run concurrently — Rather than waiting in a queue, archive jobs for different partitions execute in parallel. 

The zero-overlap guarantee 

The job criteria key depends on one critical invariant: when multiple archive jobs run within the same scenario, each job with a different job criteria key must process a completely distinct set of records with zero overlap. 

For example, if you run two Sales Order archive jobs at the same time—one with job criteria key “USMF” and another with “DEMF”—the records archived by the USMF job must not overlap with those archived by the DEMF job. This is why DataAreaId is a natural choice for many scenarios: it inherently partitions data by legal entity. 

Monitoring parallel jobs 

You can monitor archive jobs running in parallel from the Archive with Dataverse long term retention workspace in Dynamics 365 Finance and Operations. Each job shows its criteria key value, making it easy to confirm which partitions are being processed concurrently. 

Join the private preview 

Parallel processing for archive jobs is currently available in private preview. If you’d like to try this capability in your environment, we’d be happy to have you participate. 

Submit your request to join the private preview 

By joining the preview, you’ll get early access to parallel archive job execution. You’ll also have an opportunity to provide feedback that helps shape the final release. The preview is open to all Dynamics 365 Finance and Operations customers and partners.

The post Support Parallel Processing for Archive Jobs in Dynamics 365 Finance and Operations appeared first on Microsoft Dynamics 365 Blog.

Introduction 

In fast-paced, complex supply chain environments, ensuring product quality throughout the journey from supplier to customer is more critical than ever. We’re excited to address this with a powerful new feature in Microsoft Dynamics 365 Supply Chain Management Landed Cost module, enabling quality control for goods in-transit orders. 

Addressing a Critical Gap in Supply Chain Management 

Traditionally, quality control measures in supply chain management focus on initial stages of production and receipt of purchase orders at their final destination. We see a growing need for more comprehensive quality assurance processes covering all phases, including the in-transit phase. Now, businesses can conduct quality checks on goods while they are in transit. This new feature ensures product integrity throughout the entire supply chain journey. 

How it works 

The quality control for goods in-transit feature is seamlessly integrated into the Dynamics 365 SCM framework. Here’s how it enhances the supply chain process: 

Setup of Goods in transit order in Quality associations: Businesses can now define goods in-transit order as a new quality association type with pre-defined event blocking approach.  This proactive measure ensures any potential quality issues can be identified and addressed before the goods reach their final destination.

Automatic Quality order creation: During the Goods in-transit order registration/receive operation, depends on the previous step’s configuration, the corresponding quality order will automatically create to reflect the quality control.

Order control and release: Depending on the configuration, the quality order completeness will block the downstream business operation if it’s not passed. This control makes it easy for businesses to adopt and implement without significant changes to their current quality control processes for Goods in-transit order.

Benefits of Quality Control for Goods In-Transit

While the enhanced return receiving process in Dynamics 365 SCM represents a significant leap forward, transparency is key. We have multiple planned backlogs coming soon, such as:

Implementing quality control for goods in-transit offers several significant advantages:

• Enhanced Supply Chain Reliability: By ensuring quality at every stage, businesses can significantly reduce the risk of receiving defective or non-compliant goods.
• Cost Efficiency: Early detection of quality issues minimizes the need for costly rework or returns, leading to substantial cost savings.
• Regulatory Compliance: The feature supports compliance with various regulatory standards, ensuring that products meet all necessary legal requirements.
• Improved Customer Satisfaction: Delivering high-quality products consistently enhances customer trust and satisfaction, ultimately driving business growth.

Conclusion

The introduction of quality control for goods in-transit orders in Microsoft Dynamics 365 SCM represents a significant advancement in supply chain management. It empowers businesses to ensure product quality at every stage of the supply chain, from production to final delivery. By adopting this feature, companies can enhance their supply chain integrity, reduce costs, comply with regulatory standards, and deliver superior products to their customers.

Stay tuned for more updates as we continue to innovate and expand the capabilities of Microsoft Dynamics 365 SCM to meet the evolving needs of the global supply chain.

Call to action

Enable the feature: Turn on the Landed cost module and related features for your system – Supply Chain Management | Dynamics 365 | Microsoft Learn

Learning Article:   Quality orders – Supply Chain Management | Dynamics 365 | Microsoft Learn

The post Enhancing Supply Chain Integrity: introducing quality control for goods in-transit orders in Dynamics 365 SCM  appeared first on Microsoft Dynamics 365 Blog.

Editor Denis Conway

Introduction

In the relentless pursuit of customer-centric excellence, optimizing our return process emerges as a pivotal strategy for both customer satisfaction and operational prowess. This blog exploration delves into Dynamics 365 SCM Warehouse Management’s transformative role in enhancing customer return receiving process, showcasing a strategic framework that promises elevated customer experience and operational efficiencies.

Elevating Standard Processes

In the traditional realm of return management, the issuance of a Return Material Authorization (RMA) order has been the cornerstone. This process, while effective, faces challenges in scenarios where the reason for return is not immediately apparent. Our executive journey begins with understanding the standard RMA process and its limitations.

This current sales return approach with RMA order, while effective in many respects, introduces potential delays and customer frustration due to its structured and sometimes rigid procedures. The complexity of documentation, especially in unplanned return scenarios, coupled with communication gaps and limited automation, poses challenges. Additionally, as businesses scale, the classic RMA order process may face scalability concerns, raising questions about its ability to efficiently handle increased volumes of return requests. Addressing these limitations is crucial for executives aiming to optimize return management processes, enhance customer satisfaction, and ensure operational resilience. The previous return system does not support the creation of return labels that is a must have for many industries, such as e-commerce. 

Enhanced processes in customer return receiving

In the innovative landscape of our enhanced customer return receiving process within Dynamics 365 SCM, the traditional requirement for a pre-existing Return Material Authorization (RMA) order has been reimagined. In the new way of enhanced customer return process, we can pre-generate return data, create return labels that can be shipped in a shipment and used for seamless return of items. If items need to be returned, customers now have the flexibility to initiate returns seamlessly through two distinct scenarios: the ‘Blind Return’ and ‘Return Details,’ eliminating the upfront necessity of an RMA order.

Blind Return Scenario: In the ‘Blind Return’ scenario, customers can initiate return requests without disclosing specific details initially. We will still need to have a customer number to assign (it can be a dummy customer) to the return order and the item numbers, but we do not need to have an issued return order number. This approach caters to situations where the reason for return may not be immediately apparent or where customers prefer a swift and straightforward process. By bypassing the need for upfront details, this streamlined approach accelerates the return initiation phase, enhancing the overall customer experience.

Return Details Scenario: Alternatively, the ‘Return Details’ scenario allows customers to provide comprehensive information about the return from the outset. This more structured approach is ideal for situations where a detailed explanation of the reason for return, return until date or additional information is available. It facilitates smoother and more informed return processing, using pre-generated RMA-number included on the return labels, enabling the receiving team to address customer needs with precision and efficiency.

Crucially, what sets this enhanced process apart is the automation that follows these customer-initiated returns. In the subsequent stages, the system intelligently generates the necessary RMA order automatically in the background. The post-return generation of the RMA order streamlines the process, combining customer convenience with the structured documentation needed for efficient internal processing. As we evolve in our commitment to customer-centric operations, this innovative approach sets the stage for a more agile, responsive, and efficient return management process. In the image below, we can see an illustration of the return receiving process:  

Conclusion

In the executive suite, strategic decisions are paramount. The enhanced customer return receiving process in Dynamics 365 SCM Warehouse Management is not merely a feature; it’s a strategic tool that aligns our organization with the demands of modern business. As we navigate the complexities of customer interactions and operational excellence, let us leverage this innovation to propel our brand into the forefront of customer-centric leadership.

More details

Learning article can be found at:
Sales returns – Supply Chain Management | Dynamics 365 | Microsoft Learn,
Receive unannounced sales returns – Supply Chain Management | Dynamics 365 | Microsoft Learn.

Welcome to join Yammer group at: Dynamics 365 and Power Platform Preview Programs : Dynamics AX WHS TMS

The post Elevating Customer Returns receiving experience with Dynamics 365 SCM Warehouse Management  appeared first on Microsoft Dynamics 365 Blog.

Introduction:

Microsoft Dynamics 365 F&O Supply Chain Management is a powerful enterprise resource planning (ERP) system that offers a range of modules to help businesses manage their operations. One of the modules available is the landed cost module, which helps businesses to calculate the total cost of a product, including all the additional costs incurred when importing goods from overseas. One of the key functions of the landed cost module is the over and under delivery tolerance function, which helps businesses to manage their costs and avoid unexpected expenses.

What is the over and under delivery tolerance function?

The over and under delivery tolerance function is a feature within the landed cost module that allows businesses to set tolerance levels for quantity of goods received. This means that if the actual quantity of goods received and total purchase order amount falls within or outside the tolerance levels set, over/under delivery transactions and different follow up documents will be generated to reflect the additional costs or savings.

Why is the over and under delivery tolerance function important?

The over and under delivery tolerance function is important because it allows businesses to manage their costs more effectively. By setting tolerance levels, businesses can avoid unexpected expenses that can arise when they receive a lower quantity of goods than expected. At the same time, if the business receives a higher quantity of goods than expected, they can benefit from the savings and adjust the landed cost calculation accordingly.

The over and under delivery tolerance function also helps to improve supplier relationships. By setting tolerance levels and communicating them to suppliers, businesses can ensure that their suppliers are aware of the expected quantity of goods and are able to meet those expectations. This helps to build trust between the business and its suppliers, which can lead to more reliable and consistent supply chains.

Business processes flow

Main process logic:

1. When purchase order is received, system check the received line total amount compare with order total amount, if the purchase order total amount difference is larger than amount tolerance, system will process below two cases.
   • Over delivery case: the received order line quantity is larger than order quantity. Over/under transaction is created, and one Purchase Order will be automatically created.
   • Under delivery case:  the received order line quantity is smaller than order quantity. Only over/under transaction is created, no follow up document created automatically, need manual process.
2. If the purchase order total amount difference is smaller than amount tolerance, system will further compare received line quantity difference with percentage tolerance.
3. When the received line quantity difference is larger than percentage tolerance, system will process below two cases:
   • Over delivery case: the received order line quantity is larger than order quantity. Over/under transaction is created, and one Purchase Order will be automatically created.
   • Under delivery case:  the received order line quantity is smaller than order quantity. Only over/under transaction is created, no follow up document created automatically, need manual process.
4. When the received line quantity difference is smaller than percentage tolerance, system will process below two cases:
   • Over delivery case: the received order line quantity is larger than order quantity. Over/under transaction is created, and movement journal will be automatically created.
   • Under delivery case:  the received order line quantity is smaller than order quantity. Only over/under transaction is created, and movement journal will be automatically created.

How to setup over and under delivery tolerance?

Item over/under tolerance groups

The over and under tolerances can be accessed through the menu path:

Landed Cost Setup > Over/under setup > Item over/under tolerance groups.

You can set the tolerance groups for the group products that have same tolerance.

The value of this form will be used in:

Released Product > Purchase > Over/under tolerance group field.

Vendor over/under tolerance groups

You can group together vendors that regularly over-deliver or under-deliver. You can then set the over/under tolerance per group. The vendor over and under tolerances can be accessed through the menu path:

Landed Cost > Setup > Over/under setup > Vendor over/under tolerance groups.

The value of this form will be used in:

Vendor > Miscellaneous details > Over/under tolerance group field.

Over/under tolerances

You can set the tolerance in terms of different product / vendor dimensions. The over and under tolerances can be accessed through the menu path:

Landed Cost > Setup > Over/under setup >Over/under tolerances.

Below demo data belongs to legal entity: USMF.

Account code:

• All: Applies to all vendors.
• Table: Applies to specific vendor which selected in field ‘Account relation’, in above first record there will be US-101.
• Group: Applies to all vendors in the vendor tolerance group which selected in field ‘Account relation’.

Item code:

• All: Applies to all products.
• Table: Applies to specific product which selected in field ‘Item relation’, in above first record there will be A0001.
• Group: Applies to all products in the Item tolerance group which selected in field ‘Item relation’.

Amount tolerance: The amount tolerance applies to the entire purchase order, calculation logic is:

In the above first record there will be 200 USD tolerance for purchase order from vendor US-101.

Percentage tolerance:

The percentage tolerance applies to each purchase order line, calculation logic is:

In the above first record there will be 3% tolerance for product A0001 when purchased from vendor US-101.

Conclusion:

The over and under delivery tolerance function is a valuable feature within the Dynamics 365 landed cost module. By setting tolerance levels for the quantity of goods received, businesses can manage their costs more effectively and avoid unexpected expenses. At the same time, this feature helps to build stronger relationships with suppliers, which can lead to more reliable and consistent supply chains. If you are using Dynamics 365 for your business, it is worth exploring this feature to see how it can help you to optimize your business processes with landed cost module.

Not yet a Supply Chain Management customer? 

Take a guided tour.

The post Introduction to Over/Under tolerance feature during goods in transit process appeared first on Microsoft Dynamics 365 Blog.