Financial Products in Font

Generator PDF 417 in Font Financial Products

The aim of this table is to hold the different products the company sells. From bank accounts to life insurance, all products will be held here. This table will be used when producing statements and creating transactions when the user s balance changes for example, when buying further shares: Financial Product ID (K): This is a unique identifier. Financial Product Name: This is the name of the product, such as checking account, share, loan, and so forth. Frequency of Payment: For each product, this indicates how often payments are collected for those products that require it, such as a loan, a regular savings account, and so on.

This table will hold customer details, such as the customer s products and balances. To clarify and reiterate, there will be items currently within this table that will no longer reside within it once we normalize the data. For example, you will see an attribute for Account Numbers for Each Product. When we proceed through normalization, you will see how attributes such as this are moved: Customer ID (K): This is a unique ID for each customer. Financial Product Balance: This is the current balance of each product. Title: This is the customer s title (Mr., Ms., etc.). First Name: This is the customer s first name. Last Name: This is the customer s last name. Address: This is the customer s address. Account Numbers for Each Product: This is the account number of each product the customer owns. Financial Products Details: This contains details of each financial product the customer owns.

This table will hold the details of each stock share, such as its current price and its price history: Share Price ID (K): This is a unique ID for each share. Share Name: This is the name of the share. Current Price: This is the current price of the share. Previous Price: This contains previous prices of the share. Price Date: This is the date the price was set at this level. Stock Market Ticker ID: This is the ID for this share on the stock market.

This table will hold the details of each financial transaction that takes place for each product. Financial Transaction ID (K): This is a unique ID for each financial transaction. Customer ID: This is the customer s unique identifier, as defined in the Customers section earlier. Date of the Transaction: This is the date the transaction took place. Financial Product: This is a link to the financial products table. Amount: This is the amount the transaction is for. Debit/Credit: This flag denotes whether the transaction is a debit or a credit.

At this point, we have a first draft of the logical tables and attributes, but there are still no relationships between these tables. There is one more piece of information that we need to know, which concerns information not recorded, as it won t be included within this database. The example database will not hold every item of information that is required to make the system complete. This is to keep the example simple and to avoid having extra tables that will not be used within the book s exercises. However, there may be other times when you may wish to implement only some of the tables for example, when performing a viability study (in other words, when you re building part of a system to prove the viability of an idea). Or perhaps there are third-party tools available that can fill in the gaps. For example, a system might use an external addressing system, and instead of holding all customer addresses within the system, it may use a cross-reference ID. A table could also exist to hold all of the financial transactions for products not covered where specialized tables are required, such as for company pension plans. Next, let s move on to consider relationships between the tables in the database.