Skip to main content

Sale Order Sequence by Operating Unit

Project description

Odoo Community Association

Sale Order Sequence by Operating Unit

Beta License: AGPL-3 OCA/operating-unit Translate me on Weblate Try me on Runboat

This module use to define sequence of Sale Orders by Operating Unit.

Table of contents

Configuration

You can change the default sequence by the one of your choice going to Settings > Technical > Sequences & Identifiers > Sequences, and editing the record Sale Order of ….

You will only have access to that section if your section has Technical features permission check marked.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

  • Ecosoft

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/operating-unit project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distributions

No source distribution files available for this release.See tutorial on generating distribution archives.

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

File details

Details for the file odoo_addon_sale_operating_unit_sequence-16.0.1.0.0.7-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo_addon_sale_operating_unit_sequence-16.0.1.0.0.7-py3-none-any.whl
Algorithm Hash digest
SHA256 32434e6f147049655bb65d8b528a148d784e7301fbebaf5a093b816fa1bd728a
MD5 5b1020bb4feebc722c48ef7b0f5c492b
BLAKE2b-256 5048e71d765f20c374d8e660123be47e26f9d6b518ef81c24f84d21270fa7bee

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page