Product Data Model

Main Entity

• Product Entity - a complex entity

Basic Table

• gProduct table

Every Product Entity has one and only one gProduct record associated with it.

A general and simplified graph of the Product Data Model

What type of information does the gProduct table store?

The gProduct table has general information about a Product Entity, like the Name, the ProductID, the Barcode etc.

Some of this information can be found in string or number fields in the table and other information can be found in dimension tables, directly related to the gProduct table.

There is also other information about the Product Entity, stored in other tables, that is not directly related to the gProduct table - more on this in the Sales and Purchases functional areas.

Dimension tables directly related to the gProduct table

There are 3 types of dimension tables directly related (or connected) to the gProduct table:

1. The [1,1] -> [0,n] related dimension tables

A paradigm for this type of relation is the gProduct -> gManufacturer relation (see the image above)

• Every gProduct has one (and only one) relation to a gManufacturer record.
• This relation is constructed by a link (or constraint) that is of type [1,1] -> [0,n] and uses the gProduct.sManufacturerFK and gManufacturer.sManufacturerPK fields as linking fields.
• In Relational theory terms, we could say that the gProduct.sManufacturerFK is a FK and the gManufacturer.sManufacturerPK is a PK in the above relation.

2. The [0,n]-> [1,1] related dimension tables

A paradigm for this type of relation is the gProduct -> gProductPackage relation (see the image above)

• Every gProduct can have many (or no) relations to a gProductPackage record - in the end this just means that a Product Entity can come in many different packages (or no packages).
• This relation is constructed by a link (or constraint) that is of type [0,n]->[1,1] and uses the gProduct.sProductPK and gProductPackage.sProductFK fields as linking fields.
• In Relational theory terms, we could say that the gProductPackage.sProductFK is a FK and the gProduct.sProductPK is a PK in the above relation.

3. The [0,1]-> [0,n] related dimension tables

A paradigm for this type of relation is the gProduct -> gConsignmentTrade relation (see the image above)

• Every gProduct can have one (or no) relation to a gConsignmentTrade record.
• This relation is constructed by a link (or constraint) that is of type [0,1] -> [0,n] and uses the gProduct.sConsignmentTradeFK and gConsignmentTrade.sConsignmentTradePK fields as linking fields.
• In Relational theory terms, we could say that the gProduct.sConsignmentTradeFK is a FK and the gConsignmentTrade.sConsignmentTradePK is a PK in the above relation.

List of tables related to the gProduct table

• gManufacturer - link [1,1] -> [0,n]
• gUOM - link [1,1] -> [0,n]
• gProductGroup- link [1,1] -> [0,n]
• gProductClass- link [1,1] -> [0,n]
• gProductPriceList- link [1,1] -> [0,n]
• gProductPosting - link [1,1] -> [0,n]

• gProductPackage- link [0,n] -> [1,1]
• gSerialNumber - link [0,n] -> [1,1]
• gLotNumber - link [0,n] -> [1,1]

• gConsignmentTrade- link [0,1] -> [0,n]

Products and TAXES

Every gProduct in the alpha360 project is always related to one and only one record in the gProductPosting table.