Skip to main content

MRP Production Request

Mature License: AGPL-3 OCA/manufacture Translate me on Weblate Try me on Runbot

This module extends the functionality of Manufacturing to allow you to use Manufacturing Request (MR) as a previous step to Manufacturing Orders (MO).

Some of the benefits you can obtain are:

  • Allow managers to review what is going to be manufactured.

  • Better control of manufacturing calendar.

  • Manage big requirements splitting them in batches.

  • Know your bottleneck component in advance and only schedule what you really can build.

Table of contents

Configuration

To configure a product to automatically generate Manufacturing Requests from procurements instead of directly create manufacturing orders you need to:

  1. Go to the products that you want them to trigger manufacturing requests.

  2. Go to the Inventory tab.

  3. Check the box of a manufacture route and the box of Manufacturing Request.

Usage

To use this module, you need to:

  1. Go to Manufacturing > Manufacturing Requests.

  2. Create a manufacturing request or open a existing one (assigned to you or created from a procurement).

  3. If you click on Request approval button the user assigned as approver will be added to the thread.

  4. If you are the approver you can either click on Approve or Reject buttons.

  5. Rejecting a MR will cancel it and propagate this cancellation to destination moves.

  6. Approving a MR will allow you to create manufacturing orders.

  7. You can manually set to done a request by clicking in the button Done.

To create MOs from MRs you have to:

  1. Go to approved manufacturing request.

  2. Click on the button Create Manufacturing Order.

  3. In the opened wizard, click on Compute lines so you will have a quantity proposed for creating a MO. This quantity is the maximum quantity you can produce with the current stock available for the components needed in the source location.

  4. Use the proposed quantity or change it and click on Create MO at the bottom of the wizard.

NOTE: This module does not restrict the quantity that can be converted from a MR to MOs. It is in hands of the user to decide when a MR is ended and to set it to Done state.

Known issues / Roadmap

  • Take into account workstations.

  • Take into account consumable products.

Changelog

11.0.1.0.0 (2018-09-13)

  • [MIG] Migration to v11. 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 smashing it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Eficent

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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 maintainer:

lreficent

This module is part of the OCA/manufacture project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Metadata

Release files for odoo11-addon-mrp-production-request 11.0.1.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo11-addon-mrp-production-request 11.0.1.0.1
File Interpreter ABI Platform Actions
odoo11_addon_mrp_production_request-11.0.1.0.1-py2.py3-none-any.whl Python 2, Python 3 none any Details for odoo11_addon_mrp_production_request-11.0.1.0.1-py2.py3-none-any.whl

Release files / odoo11_addon_mrp_production_request-11.0.1.0.1-py2.py3-none-any.whl

Download URL odoo11_addon_mrp_production_request-11.0.1.0.1-py2.py3-none-any.whl
Size 275.5 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
1e598bd67eee363a4908899050f75734d3d2dedf40777356a08c54d1f9e96e98
BLAKE2b-256 checksum
How to use checksums
587eb30b45dd875cafc986fd918cb9400e3adfff2a4249cc86bc7d955e576f61
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3

Security for odoo11-addon-mrp-production-request 11.0.1.0.1

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page