jem-odoo
e38ed7c780
We want to break the dependency between stock and purchase for our furtur developpement. For more modularity, a new bridge module 'purchase_stock' is created. This commti move part of business code, views, data, ... related to stock management from purchase into purchase_stock without changing any feature. Task #47927
32 lines
1.2 KiB
XML
32 lines
1.2 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<!-- Purchase-related subtypes for messaging / Chatter -->
|
|
<record id="mt_rfq_confirmed" model="mail.message.subtype">
|
|
<field name="name">RFQ Confirmed</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="res_model">purchase.order</field>
|
|
</record>
|
|
<record id="mt_rfq_approved" model="mail.message.subtype">
|
|
<field name="name">RFQ Approved</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="res_model">purchase.order</field>
|
|
</record>
|
|
<record id="mt_rfq_done" model="mail.message.subtype">
|
|
<field name="name">RFQ Done</field>
|
|
<field name="default" eval="False"/>
|
|
<field name="res_model">purchase.order</field>
|
|
</record>
|
|
|
|
<!-- Sequences for purchase.order -->
|
|
<record id="seq_purchase_order" model="ir.sequence">
|
|
<field name="name">Purchase Order</field>
|
|
<field name="code">purchase.order</field>
|
|
<field name="prefix">PO</field>
|
|
<field name="padding">5</field>
|
|
<field name="company_id" eval="False"/>
|
|
</record>
|
|
|
|
</data>
|
|
</odoo>
|