Nurosoft Incoming Toleranceby Nurosoft Consulting https://nurosoft.id
• Purchase (purchase)
• Invoicing (account)
|Lines of code||101|
|Also available in version||v 11.0 v 13.0|
NUROSOFT INCOMING SHIPMENT TOLERANCE LIMIT
By default, Odoo doesn't have a quantity check on Good Receipts against Purchase Order.
With Nurosoft Incoming Shipment Tolerance Limit,
the system will trigger a blocking message if qty received is over a predefined maximum limit.
Configuration: Set Incoming Shipment Tolerance %
- Go to Inventory > Configuration > Settings > Set tolerance %
- The incoming shipment tolerance % allows the system to check if qty received > Max Limit. The tolerance does not check if qty received < Min Limit.
- Ex. Tolerance = 10%, Purchased qty = 10 units
- Max Limit = Purchased qty * (1 + tolerance %) = 11 units
- Min Limit = Purchased qty * (1 − tolerance %) = 9 units (System does not check if qty received < 9 units)
Warning on Incoming Shipment Tolerance Limits:
- Fill out the qty received (Done qty) on receipt
- If user validates the receipt, then the system will check qty received (Done qty) against qty purchased (Demand qty) and its maximum tolerance %
- The system will trigger the following blocking message if qty received (Done qty) is over the maximum limit (Demand qty + tolerance %). Only certain users have access to override this blocking message as explained in part 3.
- Configuration: Settings > Users & Companies > Users > Select user to configure > Tick "Confirm Tolerasi Incoming Shipment"
- Users with "Confirm Toleransi Incoming Shipment" access rights will have access to override the overlimit blocking message and validate receipt:
- A confirm button will appear on the blocking message
- Clicking on the confirm button will allow users to validate the receipt.
For any questions or custom development contact us at firstname.lastname@example.org
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 (see the COPYRIGHT file). 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
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.