Inventory aging report storage

This article explains how to run the Inventory aging report in Dynamics 365 Supply Chain Management and make the results available as both a form and a chart. The Inventory aging report helps analyze inventory value based on the age of stock, supporting cost management and inventory control.

Key Functionality

• Inventory aging report: Calculates the aging of inventory items according to inventory transactions and costing methods.
• Output presentation: Results can be viewed in a detailed form and as a chart for visual analysis.
• Storage of results: Report results and details are stored for reference, analysis, and audit purposes.

How to Use Inventory Aging Report Storage

1. Run the Inventory aging report:

   • Access the Inventory aging report via the Cost management module.
   • Configure filters such as date range and item groups to tailor the data.

2. View the stored report output:

   • After running, the output is saved in a storage table.
   • Review the stored data using the Inventory aging storage details form.

3. Analyze data visually:

   • Use the Inventory aging storage chart to view inventory value distribution by aging periods.
   • This graphical view aids in quickly identifying inventory items with aging concerns.

Entities Involved

Benefits

• Improved visibility on inventory valuation over time.
• Easier identification of slow-moving or aging inventory.
• Ability to retain historical inventory aging reports for auditing and management decisions.
• Supports better cost management and supply chain optimization.

Additional Notes

• The aging process aligns with costing methods configured in the system.
• The report and storage feature is particularly useful for financial controllers, inventory managers, and supply chain analysts.

For more detailed instructions and technical information, see the original Microsoft documentation.

Original article:
https://learn.microsoft.com/en-us/dynamics365/supply-chain/cost-management/inventory-aging-report-storage

Deferred processing of warehouse work

This article explains the deferred processing functionality for warehouse work put operations in Dynamics 365 Supply Chain Management, which improves warehouse efficiency by allowing staging and scheduled processing of put-away work.

Overview

• Deferred processing refers to postponing the actual completion of warehouse put operations until a later time, rather than executing them immediately.
• This feature enables warehouse workers to stage or prepare goods before final put-away, optimizing labor and equipment utilization.
• Deferred put processing is particularly useful in scenarios with bulk put operations or when organizing warehouse layout requires staging locations.

Key Concepts

• Warehouse work put operations: Tasks related to placing inventory into storage locations after picking or receiving.
• Work processing policies: Control how and when put operations are processed.
• Deferred put processing: A work processing policy option that defers completion of put operations and processes them in batches via scheduled tasks.

How Deferred Put Processing Works

1. Warehouse workers perform put operation staging without immediately closing the warehouse work.
2. Work put lines are held in a deferred state.
3. A system batch job or scheduled task runs to process these deferred put lines and complete the put operations.
4. This batch processing consolidates multiple put lines, providing efficiency gains.

Setup and Configuration

To enable deferred processing of warehouse put operations:

1. Configure a Work Processing Policy:

   • Navigate to Inventory management > Setup > Warehouse management > Work processing policies.
   • Create or edit a policy.
   • Set the Work deferred put processing parameter to Yes.

2. Assign the Policy to Relevant Warehouses or Work Types:

   • Assign the work processing policy where deferred processing is desired.

3. Setup Batch Job for Deferred Processing:

   • The system uses the WHSWorkDeferredPutProcessingTask batch job to process deferred put operations.
   • Schedule or run this batch job at required intervals to complete staging operations.

Benefits

• Improves warehouse task assignment flexibility.
• Enables consolidating put operations, reducing travel and handling time.
• Better aligns with staging processes or when space constraints require temporary put locations.
• Supports high-volume warehouses with complex put routing.

Related Elements

For detailed steps and examples, refer to the official documentation.

Original article:
https://learn.microsoft.com/en-us/dynamics365/supply-chain/warehousing/deferred-put

Set up a mobile device menu item for moving items by template

This article explains how to configure a mobile device menu item that enables warehouse workers to register item movements using predefined movement templates in Dynamics 365 Supply Chain Management.

Key points

• The mobile device menu item allows users to process item movements efficiently by leveraging movement templates.
• Movement templates specify logic and parameters for common warehouse item movements such as moving inventory from one location to another.
• This setup is part of the Warehouse Management module focusing on mobile device-enabled operations.
• The configuration requires steps within the system to create the menu item, associate it with a movement template, and deploy it to the mobile device UI.

Step-by-step setup process

1. Create or identify a movement template

   • Movement templates define parameters for standard item movements in the warehouse.

2. Create a mobile device menu item

   • Navigate to the warehouse management mobile device menu configuration.
   • Create a new menu item.
   • Select the menu item type that supports movement by template functionality.

3. Configure the menu item

   • Set the template that the menu item should use for item movements.
   • Define necessary parameters such as warehouse, work templates, etc.

4. Add the menu item to a mobile device menu

   • Incorporate the new menu item into an existing or new mobile device menu.

5. Deploy the menu to users

   • Synchronize or deploy the updated menu to warehouse workers’ devices.

6. Test the movement registration

   • On the mobile device, verify that workers can initiate item movements using the configured menu item and template.

This configuration streamlines the process for warehouse workers to move items by reusing defined templates, reducing manual input and errors.

For detailed configuration fields and examples, please refer to the full Microsoft documentation.

Original article link:
Set up a mobile device menu item for moving items by template - Supply Chain Management | Dynamics 365

Bills of materials and formulas

This article explains the role and structure of Bills of Materials (BOMs) and formulas in Microsoft Dynamics 365 Supply Chain Management. BOMs and formulas are key to defining products and their variants, specifying the components, raw materials, and subassemblies needed for production.

Key Concepts

• Bill of Materials (BOM): A structured list detailing the components (items or materials) required to manufacture a product or product variant. BOMs can be used for discrete manufacturing, process manufacturing, and other production types.
• Formulas: Used mainly in process manufacturing to define production recipes, including ingredients, quantities, and production instructions.
• Product Variants: Different configurations of a product can have different BOMs/formulas.
• Versions: BOMs can have multiple versions for revisions or changes over time.

BOM Components

• Lines: Each line represents a component in the BOM, including quantity, unit of measure, and item details.
• Subassemblies: BOM lines can reference other BOMs, allowing nested BOMs.
• Phantom BOMs: Temporary BOM assemblies that do not exist as physical inventory items but group components logically.

Usage Highlights

• BOMs and formulas are used by production control for scheduling, picking materials, and tracking production.
• They aid in cost estimation, inventory management, and quality control.
• Integration with engineering change management supports controlled updates.

Functional Areas Covered

• Defining and maintaining BOMs/formulas
• Managing BOM versions and effective dates
• Using BOMs in manufacturing processes
• Integration with product and inventory management

For more detailed technical data, parameter descriptions, and process flows, refer to the official documentation.

Official Article Link

Year-end Close

This article explains the setup requirements and procedural steps for executing the general ledger year-end close process in Dynamics 365 Finance. It includes guidance on defining year-end close templates that streamline closing activities.

Overview

The general ledger year-end close process in Dynamics 365 Finance involves closing the financial books for a fiscal year, ensuring all transactions are posted and summarized, and preparing the system for the new fiscal period. This process helps maintain data integrity and accurate financial reporting.

Key Components

• Year-End Close Templates: Predefined templates that automate sequences of closing activities and help standardize the year-end close process.
• Fiscal Calendars and Periods: Proper setup of fiscal calendars and accounting periods is required to ensure accurate closing.
• Ledger Setup: Ensure ledger and financial dimensions are correctly configured for closing.

Setup Steps

1. Define Fiscal Calendars and Periods

   • Establish the fiscal year and its accounting periods in the system.
   • Verify the status of periods to control transaction postings during and after closing.

2. Configure Year-End Close Templates

   • Create templates with sequences of tasks to automate closing operations.
   • Templates may include tasks like financial data validation, transaction posting, balance rollovers, and report generation.

3. Assign Templates to Ledgers

   • Link the year-end close templates to relevant ledgers.
   • Configure task parameters specific to the ledger requirements.

Running the Year-End Close Process

1. Pre-close Validation

   • Verify that all financial transactions for the year are posted.
   • Ensure no open batches or unposted journals remain.

2. Execute Year-End Close Template

   • Run the predefined template which executes closing tasks in order.
   • Tasks could include:
     • Closing open fiscal periods
     • Transferring balances to retained earnings
     • Resetting account balances for the new fiscal year
     • Generating closing reports

3. Review Close Results

   • Check for warnings or errors.
   • Review generated reports and journal entries.
   • Confirm that balances have correctly rolled over.

4. Open New Fiscal Period

   • Enable posting in the new fiscal year.
   • Notify relevant users that the ledger is ready for new transactions.

Best Practices

• Always back up financial data before starting the year-end close.
• Use test environments to validate templates and closing procedures.
• Communicate timelines and responsibilities across finance teams.
• Perform closing tasks during off-peak hours to minimize system impact.

Additional Resources

• Detailed guide on fiscal calendars and period setup.
• Step-by-step instructions on creating and managing year-end close templates.
• Troubleshooting common issues during year-end close.

Reference:
Year-end close - Finance | Microsoft Learn