This release is a pre-release and may not be stable for production use.
Field Service - Sales
The module integrates the Field Service application with the Sales one and allows you to sell products that generate field service orders.
Table of contents
Installation
To install Field Service and have the mapping features, you need to install GeoEngine.
Please refer to the installation instructions available at: https://github.com/OCA/geospatial/tree/12.0/base_geoengine
Configuration
Products must be configured properly in order to create field service orders upon sale order confirmation.
The field service tracking of a product defines how it generates a field service order if the product is sold via sale order.
To configure a product that generates a unique field service order on each sale order line:
Go to Sales > Catalog > Products
Create or select a product
Set the Field Service Tracking to ‘One FSM Order per Sale Order Line’
Select the FSM Order Template that will be used for creating FSM Orders when a Sale Order is confirmed with this product
To configure a product that generates a unique field service order for an individual sale order:
Go to Sales > Catalog > Products
Create or select a product
Set the Field Service Tracking to ‘One FSM Order per Sale Order’
Select the FSM Order Template that will be used for creating FSM Orders when a Sale Order is confirmed with this product
To setup a sales territory:
Go to Field Service > Master Data > Locations
Create or select a location
Go to the Sales tab and select the sales territory
Usage
Go to Sales
Create a new Quotation/Sale Order
Set the FSM Location to be used
On a Sale Order Line, select a product configured for field service orders
Confirm the Sale Order
Field Service orders linked to SO lines are created
- When a Field Service order is completed, the quantity delivered for its
linked sale order line will be updated to the quantity ordered, indicating this line is ready for invoicing.
Known issues / Roadmap
Provide a mapping between an address and the branch and use it to set the pricelist of a new partner
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
Open Source Integrators <https://opensourceintegrators.com>
Steve Campbell <scampbell@opensourceintegrators.com>
Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
Wolfgang Hall <whall@opensourceintegrators.com>
Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>
Brian McMaster <brian@mcmpest.com>
Raphaël Reverdy <raphael.reverdy@akretion.com>
Clément Mombereau <clement.mombereau@akretion.com>
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 maintainers:
This module is part of the OCA/field-service project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-fieldservice-sale 12.0.2.5.2.99.dev14
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 |
|---|---|---|---|---|
| odoo12_addon_fieldservice_sale-12.0.2.5.2.99.dev14-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_fieldservice_sale-12.0.2.5.2.99.dev14-py3-none-any.whl |
Release files / odoo12_addon_fieldservice_sale-12.0.2.5.2.99.dev14-py3-none-any.whl
| Download URL | odoo12_addon_fieldservice_sale-12.0.2.5.2.99.dev14-py3-none-any.whl |
|---|---|
| Size | 83.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
caeb2d9d227e2498cc87c4bd7645cd5f03c01e7c478ca09e4f1eafb372d9fdc0
|
|
BLAKE2b-256 checksum How to use checksums |
08495c4b4402e9fa0099864fc87e1e9fecb1dfa249deaceadee89a8a23ce62c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo12-addon-fieldservice-sale 12.0.2.5.2.99.dev14
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.
