Required Apps |
•
Manufacturing (mrp)
• Inventory (stock) • Purchase (purchase) • Invoicing (account) |
Included Dependencies | Show |
Lines of code | 7446 |
Technical Name |
mrp_planning_engine_availability_check |
License | See License tab |
Website | http://www.openvalue.cloud |
Required Apps |
•
Manufacturing (mrp)
• Inventory (stock) • Purchase (purchase) • Invoicing (account) |
Included Dependencies | Show |
Lines of code | 7446 |
Technical Name |
mrp_planning_engine_availability_check |
License | See License tab |
Website | http://www.openvalue.cloud |
MRP Planning Engine Availability Check
The “MRP Planning Engine Availability Check” tool supports the customer promise delivery date
determination in Customer Request for Quotation process by taking into account the projected stock
quantity compared to customer requested quantity at all BoM’s level.
The MRP Parameter attributes, the main master data involved in MRP Planning Engine run, are considered.
The lead time, the cumulative lead time along the overall BoM and the decoupled lead time for are
calculated also.
The critical path is shown to have an immediate overview where procurement issues can be faced.
The tool consists of two main sections:
· BOM explosion
· Availability Check Result
Two printouts are available also:
· BoM Explosion report to provide an overview of all BoM structure with its main procurement attributes
· Availability Check report to list all quantities figures related to a component’s replenishment
In detail, we have as follows:
BOM Explosion section
![]() |
BOM is exploded till the final level and the requested quantity is calculated for all the components.
For each component, its main procurements attributes are provided:
· Product Type, to distinguish between storable products and consumables and serviced
· MRP parameter indicator to check whether the MRP parameter master data has been created
· Make product, so its procurement is achieved internally by executing a production order
· Buy product, so a purchase order has to be created for its procurement
· Subcontracting product, so a subcontracting purchase order has to be created for its procurement
· Reorder point replenishment model related to the MRP type Reorder Point
· Lead Time calculated according the supply method
· Cumulative lead Time taking into account the lead time of BoM’s components
· Decoupled Lead Time taking into account the buffer stock due to a reorder point
· Critical path indicator
The critical path for calculating the decoupled lead time is pointed out in red color.
Availability Check Result section
![]() |
All components’ requirements are summarized, i.e. components in different BoM level are listed in only one
row with all its requirements summarized. The storable products are reported only.
For each item the following stock quantities are provided for the selected location (its children are taken into account also):
· Requested Quantity based on BOM explosion
· On hand Quantity
· Available Quantity, i.e. the projected stock quantity
· Free to Use Quantity, i.e. the on hand stock minus the reserved one
· Incoming Quantity, i.e. all incoming goods movement are summarized
· Outgoing Quantity, i.e. all issue goods movements are considered
· Forecast Quantity, achieved as the “Free to Use” quantity minus requested quantity
The forecast report is available also for checking the projected stock over the time and to trigger a manual
replenishment also.
Component’s shortage is pointed out in red color, i.e. the forecast quantity is negative so the requested
production is not feasible and procurement has to be activated.
BOM Explosion Report
![]() |
Availability Check Report
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software. You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module