Features

• Each dictionary presents data grouped by business function
• Presents common baseline information from the VISUAL database, hiding more detailed and esoteric data
• All data has been denormalized and therefore does not require linking tables
• Columns have been renamed to present a clear, intuitive understanding of their function
• Column descriptions are available within the eDictionary
• Codes used in the database are decoded into easily understood terms
• Future changes to the VISUAL database are automatically remapped in your existing reports by using an updated eDictionary
• Utilizes an ODBC connection to the VISUAL database

What does eDictionary do?

• Selects and joins together the necessary tables
  Retrieving information from the VISUAL database almost always involves more than one table.  These tables must be linked together so that the corresponding rows are matched up.  This would be a simple process if there were always one row in each table that matches another row.  This is rarely the case, however.  Typically there can be several rows in one table that match a single row in another.  For example, there can be any number of alternate contacts for a customer.  To make matters worse, there can also be no rows in a table to match.  An example here would be when a customer has no alternate contacts.  eDictionary has done this linking for you.
• Decodes database fields
  When you make a selection from radio buttons or combo boxes, the text that you see on the screen is typically not stored in the database.  Most of these settings are stored as codes.  For example a status selection of "Closed" is actually stored in the database as "C".  Most of these are fairly simple, however there are exceptions.  For example "Yes" maybe stored as a "Y", however "No" maybe stored as an "N" or simply a null.  eDictionary has decoded these fields into clear English.  Since you may want the codes for formula writing, we have supplied those too.
• Common data is given with details hidden
  The VISUAL database is quite vast.  There are hundreds of tables, and thousands of columns.  Fortunately the average person writing reports will only need a tiny subset of these.  Working with the database directly forces you to wade through the tables and columns that are of no interest.  This is difficult since so many of the names are similar.  It is not always apparent which tables/columns to use.  eDictionary presents common baseline information.  System related tables and the more esoteric functionality are hidden, giving a clear and concise listing of data to choose from.
• Friendly names and explanations
  The tables and columns in the VISUAL database all make use of underscores and abbreviations.  eDictionary renames these to be more English like names.  Where the names are not self explanatory, an online help popup window is available.
• Resolves field inheritance
  VISUAL Enterprise™ makes use of defaults in many places.  For example, in Customer Order Entry the field Desired Ship Date is in the header, line detail, and delivery schedule.  If the delivery schedule ship date is blank (or no delivery schedule exists) then the line ship date is used.  If the line ship date is blank, then the header ship date is used.  Many users assume that the database is populated the same way.  That is, they will retrieve the appropriate default date from the delivery schedule, line detail or header records.  This is not the case, however.  The database is populated with literally what is keyed in.  It is up to the user to determine if a date is null and then go the other tables to pull the appropriate date.  eDictionary does this for you. When you select a field that has defaults, the inheritance of that field is automatically performed for you.
• Isolates report definitions from the database
  Since eDictionary is a meta-layer that isolates your reports from the VISUAL database, only this meta-layer needs to be modified when database changes are made.

Data Views Provided

• Quoting
  The focal point for this dictionary is the quote.  Detail is presented down to quote detail.  This data group is limited to quote information since a quote can be generated without a customer or work order.
• Sales
  The focal point for this dictionary is the Customer Order.  Detail is presented down to delivery schedules.  Information is also available about the customer.
• Inventory
  The focal point for this dictionary is the inventory transaction.  Detail is presented down to the part.  Information is also available about the warehouse and location.
• Purchasing
  The focal point for this dictionary is the Purchase Order.  Detail is presented down to delivery schedules.  Information is also available about the Vendor.
• Work Orders
  The focal point for this dictionary is the Work Order, Engineering Master or Quote Master.  Detail is presented down to material level.
• Receiving
  The focal point for this dictionary is the receiver.  Detail is presented down to the delivery schedule.  Information is also available about the associated purchase order.
• Shipping
  The focal point for this dictionary is the Packlist.  Detail is presented down to the delivery schedule.  Information is also available about the bill of lading.
• General Ledger
  The focal point for this dictionary is accounts with balances.  Detail is presented down to the accounting period.
• Receivables
  The focal point for this dictionary is the invoice.  Detail is presented down to the invoice line.  Information is also available about the promise payment and customer.
• Payables
  The focal point for this dictionary is the voucher.  Detail is presented down to the payable line.