A contextual database is typically a database hosted by the company intended to deliver contextual data such as prices, rebate, sizes, codes, etc.
When you "calculate" data according to a context, you may need to interface QDV7 databases with your own databases. This is not to be confused with database publishing in which you simply publish your own databases to QDV7 users. (A specific tool exists for this purpose.)
Let's say you have a database named Schneider Electric in which you have some 300,000 different references. When you sell these referenced articles, you want to have a price which depends on the context (Country, Kind of business, etc.). Such a database could appear as follows:
Country |
Reference |
Cost per unit |
Currency |
USA |
01109 |
85,07 |
USD |
USA |
01225 |
53,96 |
USD |
USA |
03204 |
83,93 |
USD |
USA |
03220 |
51,84 |
USD |
USA |
03243 |
48,05 |
USD |
UNITED KINGDOM |
01109 |
46,20 |
GBP |
UNITED KINGDOM |
01225 |
27,56 |
GBP |
UNITED KINGDOM |
03204 |
41,25 |
GBP |
UNITED KINGDOM |
03220 |
28,36 |
GBP |
UNITED KINGDOM |
03243 |
22,25 |
GBP |
In the QDV7 database we have all references, descriptions, unit, family, etc. but here, the country is part of the context. When we import an article, we pass the list of global variables (including the country) to the QDV7 database which queries
QDV7 comes with a program (an assembly) whose source is provided in the \SDK directory. You can freely adapt this program to interface your own data. An example shows also in the Overhead Sheets of Sales in the Multi-languages sample.