DDMRP Adjustment
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): pending to implement
Table of contents
Usage
To plan buffer adjustments act as follows:
Click on Inventory > Demand Planning > Create Buffer Adjustments.
In the popup window fill the Period and Date Range Type to perform your planning.
Check the boxes of the Factor to Apply in which you are interested.
Select the DDMRP Buffers where to apply this factors.
Under the title Sheet you will see a generated sheet in which you can fill the values for each period.
Click Validate to confirm your planning and the system will end up showing you the newly created DDMRP adjustment records.
Known issues / Roadmap
Implement new factors
Reuse existing factor and modify them instead of always creating new ones.
Add small graph view in buffer form as a way to overview DAFs.
Changelog
13.0.1.0.0 (2020-07-02)
Standard migration to v13.
11.0.1.1.0 (2019-02-01)
Refactor data model to reduce complexity. Functionality unchanged.
11.0.1.0.0 (2018-08-01)
Start of the history
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Lois Rilo <lois.rilo@forgeflow.com>
Jordi Ballester <jordi.ballester@forgeflow.com>
Akim Juillerat <akim.juillerat@camptocamp.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainers:
This module is part of the OCA/ddmrp project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo13-addon-ddmrp-adjustment 13.0.1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo13_addon_ddmrp_adjustment-13.0.1.4.0-py3-none-any.whl | Python 3 | none | any | Details for odoo13_addon_ddmrp_adjustment-13.0.1.4.0-py3-none-any.whl |
Release files / odoo13_addon_ddmrp_adjustment-13.0.1.4.0-py3-none-any.whl
| Download URL | odoo13_addon_ddmrp_adjustment-13.0.1.4.0-py3-none-any.whl |
|---|---|
| Size | 34.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
238797ad3b03f4ba2ab3285e4d6d90f65911f20732d74250a43ddba7ea453ea5
|
|
BLAKE2b-256 checksum How to use checksums |
88a65bdae264352db720fe90ebeb91927b981098742fedb434725e08e9e59753
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo13-addon-ddmrp-adjustment 13.0.1.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
