Skip to main content

Purchase Representatives will be the point of contact for RFQ's and PO's

Project description

Beta License: AGPL-3 OCA/purchase-workflow Translate me on Weblate Try me on Runboat

This module makes the field Purchase Representative in Purchase Orders default to the user doing a procurement to overcome the known flaw of Odoo user in the transaction when using SUPERUSER_ID.

Table of contents

Usage

Just set the Purchase Representative in the Purchase Order header. Then when sending the RFQ/PO to the vendor the Purchase Representative will be the contact person (email from and reply to).

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

  • ForgeFlow

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/purchase-workflow 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 odoo14_addon_purchase_representative-14.0.1.0.1.dev6-py3-none-any.whl.

File metadata

File hashes

Hashes for odoo14_addon_purchase_representative-14.0.1.0.1.dev6-py3-none-any.whl
Algorithm Hash digest
SHA256 fdfe573f416a39985a633add60f65305c460d091655ccc140993f1a545874776
MD5 33bc50e3ee0f7f1bcb097fc9f551c1b5
BLAKE2b-256 83f6258ccd5f6381f515563cfd151de9866a69abed2635d52e921538e71a82b8

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