8000 [FW][IMP] purchase: THD feedback about UBL format & alternative upload by fw-bot · Pull Request #13340 · odoo/documentation · GitHub
[go: up one dir, main page]
Skip to content

[FW][IMP] purchase: THD feedback about UBL format & alternative upload #13340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

[FW][IMP] purchase: THD feedback about UBL format & alternative upload #13340

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
[IMP] purchase: THD feedback about UBL format & alternative upload 
X-original-commit: ea3e194
  • Loading branch information
@Felicious
Felicious committed May 12, 2025
commit caa8e04c2b3dcfeb75d34dbdbeec3e04e7e3b32b
29 changes: 20 additions & 9 deletions content/applications/inventory_and_mrp/purchase/advanced/edi.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,19 @@ In Odoo, a *purchase order* (PO) can be exported as an XML file and imported as
into another Odoo database, removing the need for manual entry of products, quantities, prices, and
other key information.

The workflow in this document describes how buyers and sellers exchange data directly between their
Odoo databases. As an alternative, sellers can receive a PDF version of the request for quotation
(RFQ) by email and :ref:`upload it directly in their Sales dashboard
<purchase/advanced/rfq-upload>`. **This method is simpler** but does not use the XML-based exchange
described in the document.

.. note::
Exported XMLs follow the `Order-X schema <https://fnfe-mpe.org/factur-x/order-x/>`_, a standard
commonly used in European countries. When exchanging data between two Odoo databases, this schema
remains compatible.
Exported XMLs follow the `UBL schema
<https://docs.peppol.eu/poacc/upgrade-3/syntax/Order/tree/>`_. When exchanging data between two
Odoo databases, this schema remains compatible.

However, implementing custom developments for software that does not support the Order-X schema
may introduce additional complexity.
However, implementing custom developments for software that does not support the UBL schema may
introduce additional complexity.

Roles and configuration
=======================
Expand All @@ -31,9 +37,12 @@ configurations.
Buyer database
--------------

The buyer database is responsible for creating and confirming purchase orders. Prerequisites include
:ref:`installing <general/install>` the **Purchase** app and adding vendors (the sellers in this
workflow) as :doc:`portal users <../../../general/users/portal>`.
The buyer database is responsible for creating and confirming purchase orders. Prerequisites
include:

#. (required) :ref:`installing <general/install>` the **Purchase** app
#. (optional) adding vendors (the sellers in this workflow) as :doc:`portal users
<../../../general/users/portal>`.

Seller database
---------------
Expand All @@ -48,7 +57,7 @@ Buyer's process
---------------

To begin, the buyer (in their database) navigates to the :menuselection:`Purchase` app to create a
request for quotation (RFQ).
:abbr:`RFQ (request for quotation)`.

Set the :guilabel:`Vendor` to the portal user representing the seller, and :guilabel:`Confirm` the
:abbr:`RFQ (request for quotation)`. Doing so converts it into a :doc:`purchase order
Expand Down Expand Up @@ -92,6 +101,8 @@ file.
.. example::
:download:`XML file <edi/P00017.xml>` for PO00017

.. _purchase/advanced/rfq-upload:

Upload file
~~~~~~~~~~~

Expand Down
0