Return Merchandise Authorization Management - Link with MRP Kits
This module enables RMAs for kits, wich isn’t compatible with the base modules. In the backend side, we can return separate component while in the frontend side, customers can return the whole kit and the proper RMAs will be generated.
Table of contents
Usage
To use this module, you need to:
Make a a sale order with a kit on it and deliver its components.
Go to the portal view for the order and launch the RMA wizard.
You’ll see a line for the kit.
There will be a limit of kits to return that should much the number of kits delivered.
Once you validate the wizard with the number of kits to deliver, you’ll have as many RMAs as components those kits have with the proper quantities for each one.
If you refund the components, the kit in the sale line will be used as the reference.
Known issues / Roadmap
We compute the kits from the original demanded quantity in the sale order. If this quantity was to change, we could loose the right components per kit reference. So this should be very present. Also, v12 has a very poor support for delivered quantities, that is very improved in v13 with the introduction of the link to the BoM line in the stock moves. That approach could lead to errors as well, as the BoM line could change in the future loosing again the original components per kit reference. Anyway, is to be considered in that version to use the same rules so they fail for the same reasons.
Some extra features would be nice to have:
Add actions constraints to disallow actions on single components.
Show kit components in the portal wizard.
Allow to make an RMA directly from a kit product.
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
-
David Vidal
Michael Tietz (MT Software) <mtietz@mt-software.de>
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 maintainer:
This module is part of the OCA/rma 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 odoo14-addon-rma-sale-mrp 14.0.1.1.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 |
|---|---|---|---|---|
| odoo14_addon_rma_sale_mrp-14.0.1.1.0-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_rma_sale_mrp-14.0.1.1.0-py3-none-any.whl |
Release files / odoo14_addon_rma_sale_mrp-14.0.1.1.0-py3-none-any.whl
| Download URL | odoo14_addon_rma_sale_mrp-14.0.1.1.0-py3-none-any.whl |
|---|---|
| Size | 46.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
78d92f0cdd7a832cba5e8d2cb27bd1dc97809a13697edf40176f2330f0550541
|
|
BLAKE2b-256 checksum How to use checksums |
de790ab9d25769f0766d3b91b474b095ac54592cbab74145cd0a86ee201e3fb9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo14-addon-rma-sale-mrp 14.0.1.1.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.
