Navigation:  IDIQ Contracts > Contract Databases

Principe

QDV7 features a function of  type Extraction Transformation Loading, that loads data from the basic estimate to databases:

▪a database whose sets are the WBS tasks

▪a linked article database (rows not coming from a manufacturer database), in addition to the regular manufacturer databases, to monitor all the costs

▪an optional contract database whose articles are the WBS tasks.

 

QDV7 builds these databases by crossing preexisting databases with the WBS (or WBS package) and, for the Linked articles database, the Minutes (an excerpt with the option 3):

The option number refers to the first column of the second table in the hereunder "Procedure" section.

The regular manufacturer databases are depicted with a gear.

 

ETL Parameterisation

The forced selling prices can be brought

A.by the set database (option 1)

B.by the contract database (options 5 and 7, or option 6).

Therefore the options 1 and 7 are incompatible.

The ETL function turns the WBS into a set database (3 panes) with the following contents:

QDV7 compensates the absence of missing reference and structure fields (selection 8) at task level by inserting therein the item number (on 4 digits for the structure field).

 

Appearance of the package set after insertion in the view of Minutes (in a default task) according to the options:

 

The linked database contains:

▪the virtual articles (rows not coming from a manufacturer database)

▪the Minute rows whose reference was void, provided they feature a cost/time by unit

▪the sets not coming from a set database, collapsed and flattened.

 

Unless you have unchecked the option 4, the Minutes without quantity nor cost per unit are NOT enrolled in the set database or the linked database. The set headers in this case are still enrolled.

QDV7 assigns the COF –<rank> reference to the two first categories and to the sets whose header is limited to a title. COF stands for Call-OFf (Contract).

Without the option 3, the database enrolls also Minute rows with a native database and replaces the latter with the linked articles database.

 

In the contract database, the costs are hidden.

 

Preparation of Databases

To create an empty .grp file meant to host the set database, refer to How to Create an Empty Database of Sets.

To create the empty .qdb files meant to host the linked articles database and the contract database, refer to How to Create & Manage the Databases.

You can also empty an existing database by keeping in the hereunder dialog box the 'Empty database first' box checked. Otherwise,the sets and articles are appended to the database. The articles of the costs database are overwritten in any case.

- Emptying a database does not erase a previously edited structure.

- If the grp file has not been just created, check, in the Field Manager, that the added free fields IDs are WITHOUT _.

 

Option 1: insert the 'Take the forced selling price' and 'Forced selling price per unit' special columns. (Refer to Créer des champs libres à comportement personnalisé)

Procedure

To define the ETL, click Automation>Create Database>Build: