17.0 mig l10n ec delivery note

[jorge-luis-dev]

Migration of Delivery Note module

[celm1990]

/ocabot migration l10n_ec_delivery_note

[celm1990]

@jorge-luis-dev please rebase your branch to fixes issues relates to taxes

[sabiduriainformatica]

Dear Jose Luis

In a delivery note made from sales, the invoice field should be set with the invoice number or allow this invoice number to be selected before authorizing said guide in the SRI.

[franklingerman]

Dear Jose Luis
The field should be set with the invoice number or allow this invoice number to be selected before authorizing said guide in the SRI.

[celm1990]

@jorge-luis-dev
Before the migration process, the user could fill the invoice_id field into wizard at this line

l10n-ecuador/l10n_ec_delivery_note/wizard/wizard_input_document_number.bak.py

Line 65 in 2cc2a3e

invoice_id=self.invoice_id.id,

And is used here

l10n-ecuador/l10n_ec_delivery_note/models/stock_picking.py

Line 149 in 2cc2a3e

"invoice_id": self.env.context.get("invoice_id", False),

However, in the migration process, this wizard is no longer used, so the 'invoice_id' field is never filled in the delivery note. Please review this. If the sale order has an invoice, pass this record to the delivery note.

NOTE: @sabiduriainformatica @franklingerman This depends on the invoice policy from the product's configuration. You can deliver before creating the invoice and create the invoice later, so this scenario is complicated.

NOTE 2: Picking does not have a direct relation with the invoice, so we will only try to obtain the invoice from the sale order. Other alternative is add dependency to this module https://github.com/OCA/stock-logistics-workflow/tree/17.0/stock_picking_invoice_link what do you think?

[eduxworks]

Lo he probado me parece genial tu aporte.

[rvjaraj]

Probado y Aprobado

Como sugerencia agregar el motivo en el modelo stock.picking