community-data-files
community-data-files copied to clipboard
OCA
[IMP] uom_unece: Change unit code from C62 to PCE
According to https://www.gs1us.org/resources/data-hub-help-center/unit-of-measure-codes C62 means one while PCE means piece. I think PCE is correct as for example dozen is encoded as DPC meaning dozen piece.
Hi @astirpe, @alexis-via, some modules you are maintaining are being modified, check this out!
Please follow commit message guidelines: https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#commit-message
Please follow commit message guidelines: https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#commit-message
Thanks Pedro for reminder. Need to remind this once for all.
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Is there an option to support multiple codes for the same item?
As we can encounter the situation that we receive an document for
partner A with code H87 And partner b with C62
Both seems valid. As it may take a long time for partners to migrate from the "old" to "new" code.
@bosd I agree with you, the real topic is "how can he have 1 code for generation (C62) and several codes for import (C62, PCE, H87)". I don't have great ideas on this at the moment, but it's definitely the problem to tackle.
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.