The following views exist in the database:
v_Company_AllFields
v_Contact_AllFields
v_PayExport_AllFields
v_PaymentsReceived_AllFields
v_Placement_AllFields
v_PurchaseInvoice_AllFields
v_PurchaseOrder_AllFields
v_Requirement_AllFields
v_SalesInvoice_AllFields
v_Task_AllFields
v_Timesheet_AllFields
Due to the nature of the recruitment industry, each child view inherits the fields from its parent so for example the v_Requirement_AllFields view contains both v_Contact_AllFields because each requirement is linked to a primary client contact, and also v_Company_AllFields because each requirement is with a client company.
This ‘hierarchy’ of dependencies becomes very complex when dealing with for example a sales order, which is inherited from one or more timesheets, each of which is inherited from a placement derived from a requirement with links to both a client contact and company.