Allow to extend DDMRP App to be able to apply Adjustments for dynamically altering buffers for planned or anticipated events. This include:
- Demand Adjustment Factor (DAF): is a manipulation of the ADU input within a specific time period. The system will look for existing DAFs when computing the ADU for each buffer and apply them. The system will also explode the resulting increase in demand of parent buffers to all their children buffers using the BoM.
- Lead Time Adjustment Factor (LTAF): manipulates the Decoupled Lead Time for an individual part or group of parts (buffer profile, same partner...) to adjust for a planned or known expansions of LT.
- Zone Adjustment Factor (ZAF): Adjustment done to any of the zones of the buffer to modify the ordering size and frequency (green), demand coverage (yellow) or safety (red).
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets you temporarily adjust DDMRP buffer calculations for planned events, using demand, lead time or zone factors. Adjustments are dated, applied automatically to the buffer's ADU, decoupled lead time and green/yellow/red zones, and can be exploded down to component buffers.
This module extends the DDMRP (Demand Driven MRP) app so planners can temporarily change how a buffer is calculated during a known or expected event, without editing the buffer itself.
You create adjustments in a new Buffer Adjustments screen (menu under the demand planning menu). Each adjustment targets a buffer and a period, either by picking a Date Range or by entering manual start and end dates, and chooses one of five factor types: Demand Adjustment Factor, Lead Time Adjustment Factor, Red, Yellow or Green Zone Adjustment Factor. The value must be positive, and a period is mandatory.
When buffers are recalculated, active adjustments are applied automatically: demand factors multiply the average daily usage, lead time factors multiply the decoupled lead time, and zone factors multiply the green, yellow or red zone quantities (which also updates the top of green and top of yellow). Demand factors that are not yet active are exploded through the bill of materials to buffered components, creating extra demand lines with dates shifted by the cumulative lead time.
On the buffer form you get buttons showing the applied factors (for example DAF, parent DAF, RZAF, YZAF, GZAF) that open the related adjustments or the demand allocated to components. A scheduled job refreshes this parent-originated demand. Adjustments are company-specific.
Depends on
Required by other modules
Menus it adds
Models and fields (3)
- stock.buffer · extends an existing modeldaf_text, gzaf_text, rzaf_text, yzaf_text, daf_applied, pre_daf_adu, gzaf_applied, rzaf_applied, yzaf_applied, parent_daf_text, extra_demand_ids (Extra Demand), parent_daf_applied, count_ddmrp_adjustment_demand
- ddmrp.adjustment · new modelvalue, date_end (End date), buffer_id (Buffer), company_id, date_start (Start Date), product_id, location_id, date_range_id (Date Range), adjustment_type, manual_date_end (End Date (Manual)), manual_date_start (Start Date (Manual))
- ddmrp.adjustment.demand · new modeldate_end (End date), buffer_id (Apply to), company_id, date_start (Start date), product_id, extra_demand, product_uom_id (Unit of Measure), buffer_origin_id (Originated from), product_origin_id (Origin Product)
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 7 confirmed, 2 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/ddmrp.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0You can create and manage buffer adjustments from Inventory \> Demand Planning \> Buffer Adjustments.
To create adjustments in bulk using a 2D matrix wizard, install the companion module ddmrp_adjustment_matrix.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.