Sync lot/sn in intercompany transactions
by CLuedoo https://www.cluedoo.com/shop/licclusetsnl0039-sync-lotsn-in-intercompany-transactions-7129$ 100.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Sales (sale_management) • Invoicing (account) • Discuss (mail) • Inventory (stock) |
| Lines of code | 219 |
| Technical Name |
cds_intercompany_sync_transfer_lot |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/licclusetsnl0039-sync-lotsn-in-intercompany-transactions-7129 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Sales (sale_management) • Invoicing (account) • Discuss (mail) • Inventory (stock) |
| Lines of code | 219 |
| Technical Name |
cds_intercompany_sync_transfer_lot |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/licclusetsnl0039-sync-lotsn-in-intercompany-transactions-7129 |
ODOO'S FUNCTION
Standard Odoo prevents you from validating a receipt during inter-company transactions (like moving goods from a Sales Order to a Purchase Order) if your Lots or Serial Numbers are set to be company-dependent.
CLUEDOO'S FUNCTION
CLuedoo resolves inter-company tracking roadblocks by offering two key features:
1️⃣ Cross-Company Validation: Seamlessly sync Lots/Serial Numbers and successfully validate receipts during inter-company transactions, even when the Lot/SN is configured as company-dependent.
2️⃣ Smart Consistency Warnings: Whenever you change the name of a Lot/SN, the system immediately triggers a warning reminding you to update its counterpart across all related companies to keep your records perfectly aligned.
CONFIGURATION |
|
|
1. Go to Settings > Enable Inter-Company Transactions in all the companies that you want to sync transactions.
e.g., My Company (San Francisco) and My Company (Chicago)
|
|
|
2. Create a product
tracked by Lots/Unique Serial Number
|
|
|
3. Click the
On Hand
smart button to update the stock with lot/sn.
|
|
|
Note that the lot/sn has to be company-dependent.
|
|
USAGE |
|
|
1. Create a
Sales Order
from one company to another and add the product >
Confirm
e.g., From My Company (San Francisco) to My Company (Chicago) |
|
|
2. A Purchase Order will be automatically created in the receiving company. |
|
|
3. Go to the Delivery > Assign the lots/sn to the product > Validate |
|
|
4. Confirm the Purchase Order > Access its Receipt > The lots/sn are automatically synced and you can validate the transfer. |
|
|
5. Go to
Lots / Serial Numbers
>
Group by Product
|
|
|
Note: If you change the name of a lot/sn, a warning appears to remind you to change the name of its counterpart in all related companies as well. This warning is non-blocking , it is purely informational. |
|
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