[13.0][MIG] Module l10n_br_sale_stock #1786
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…l10n_br_sale_stock module to accomodate to the increased modulrity in OpenERP 7 where sale modules doesn't force you to install the stock module aymore
…r_account e l10n_br_account
…br_crm, l10n_br_data_base, l10n_br_data_zip e l10n_br_sale_stock
…stock e corrigido métodos onchange do objeto stock.picking
…emo nos arquivos __openerp__.py de todos modulos da localização
…sale_stock, removido chave 'demo' duplicada no l10n_br_sale_stock/__openerp__.py
… fiscais e copia-la nos documentos fiscais, corrigido copia de observações de posições fiscais por linhas
…ento fiscal a partir do picking, postado códigos para manter modularidade.
… de alertas no log e futura internacionalização dos termos da localização
…n_br_sale_stock module
…module, preserving all orginial on_change signatures
… to fake web_context_tunnel behavior
…ing test invoice from delivery
…aturar um picking que já foi faturado
…br_sale and works wether l10n_br_account_service is installed or not
…t so it can be shared bewteen products and services. You need to change the ir_model_data id of this fiscal category by SQL to update your database
…r_account so it can be shared bewteen products and services. You need to change the ir_model_data id of this fiscal category by SQL to update your database" This reverts commit 5296355.
…ing depending of Product Stock Valuation defined.
…move and account.move.line and the name of method to Create Invoice in sale.order was changed.
…cessary to get the main Fiscal Operation from Sale Order to used in creation of Stock Picking.
|
Vou fechar essa PR porque nós da Akretion não temos interesse em finalizar esse PR na 13.0. já tem PR equivalente na 14.0. Pode ser reaberto se alguém se garante para terminar o trabalho na 13.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migration l10n_br_sale_stock module #725, depends migration of modules l10n_br_stock_account #1784 .There are error "Unbalanced Journal Entries" when create invoice, the ideia is solve the problem in v14, this PR make the basic migrations and create the versions history because v13 in theory not will be used, will be just an passage version, if someone want use v13 should will make the backports from v14.
Migração do modulo l10n_br_sale_stock, depende da migração do l10n_br_stock_account e tem o erro, já relatado em outros PRs na criação da Fatura/Invoice de "Entradas não Balanceadas", as outras implementações do modulo estão funcionando:
o botão de "Criar Fatura" quando selecionada a "Politica de Criação de Fatura" como "Stock Picking" e o Pedido de Venda não tem Serviços some, para forçar o usuário a criar a fatura no Stock Picking
e os dados Fiscais e Impostos estão sendo copiados do Pedido de Venda para o Stock Picking
esse PR faz as migrações básicas e mantém o histórico de versões, facilitando um possível "backport", porque a v13 em teoria não será usada, será apenas uma versão de passagem, se alguém quiser usar a v13 deverá fazer os "backports" da v14.
cc @renatonlima @rvalyi @marcelsavegnago @mileo