Problem definition:
In the table "account.invoice" the outgoing and incoming invoices are saved. By using the field type: "OUT" or "IN" we can define which kind of invoice is been inserted.

Normally within the outgoing (customer) invoice you have 1 type (Sales).
At the incoming (supplier) invoice you have 2 kinds of invoices:
1) Invoices of goods (saleable products)
2) Invoices of costs (insurrance etc)

At each tyoe of invoice your administration department has different demands. E.g. at "cost" (2) invoices you want the field "analytic accounting" to be required. Otherwise at the goods invoice your do not want the field "analytic accounting" being required.

But if you make a payable list your want to have all vendors with invoices due to date. So logic is the retain the information out of the same table (account.invoice).

Possible solution:
To make two (sub)menus:

• Invoices of Goods (view a, masterview)
• Invoices of Costs (view b)

Every menu has his own view. And here is the problem!
We would like to have 1 basic view that has every change. Form that view we will make a inherted view for the menu items.
But we cann't inherted a view because 1 is always the masterview.

A adjustment in view b == adjustment in view a.
The (sub)menu's have there own windows.action.

So we thaught to solve the problem with a second model based on account.invoice, but this turns out to add a table in the DB. That is not what we want because of centralisation of data, also the working of other modules is in danger. Therefore we would like to put the data in one table, but with predefined requirements, specialised views.

Question:
How do you make a second view for a menu that inherted a basic view. Whereby the menu is for the user (interface) a different form, different requirements, show/hide fields.

PS: we are using V7.

Thank you in advance....