Thai Localization - Government Purchase Agreement
There are 2 type of procurement, 1) with agreement document and 2) without agreement document.
This module allow creating agreement as reference to procurement process when required.
Table of contents
Usage
To use this module:
Go to Purchase > Orders > Blanket Orders.
Create a new purchase agreement (blanket order)
Choose between: - Agreement: Allows the creation of an agreement. - No Agreement: Does not allow the creation of an agreement.
Confirm purchase agreement
Click New Quotation for create new quotation and create invoice plan (if any)
If the PO Type is set to Agreement, Quotation can’t confirm without agreement document. - Go to Agreements > Operations > Agreements to create an agreement.
Select RFQ in agreement, The partner details will be automatically pulled from the RFQ.
Access the Invoice Plan tab, which will now be visible, to apply the invoice plan for the installment.
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
Contributors
Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>
Pimolnat Suntian <pimolnats@ecosoft.co.th>
Maintainers
This module is maintained by the OCA.
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.
Current maintainer:
This module is part of the OCA/l10n-thailand project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo-addon-l10n-th-gov-purchase-agreement 16.0.1.0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo_addon_l10n_th_gov_purchase_agreement-16.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_l10n_th_gov_purchase_agreement-16.0.1.0.0.2-py3-none-any.whl |
Release files / odoo_addon_l10n_th_gov_purchase_agreement-16.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_l10n_th_gov_purchase_agreement-16.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 29.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
00476d1da678354df876b1b5ea9ddc8dbaf640a3b5ef6ea9f56acf4efbf2d556
|
|
BLAKE2b-256 checksum How to use checksums |
8b463ce0e6fdf6ed63fb733b49c4d8bfcc5a9ff1a32605c5c2a7e7a9bf20183b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo-addon-l10n-th-gov-purchase-agreement 16.0.1.0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.