Purchase Transactions

First of all there is no single table or entity for Purchase transactions !!!

What we mean with the term Purchase Transactions are the records created in the following tables:

• iInventoryTransaction
• gPartyTransaction,

when a Business Document - from the Purchases area - is posted.

The iInventoryTransaction table

This is the main table for the Inventory transactions.

PurchaseOrders, Shipments and Invoices from Purchases "create these transactions" when they are posted - they use data from the bBusinessDocument_ProductLine table.

You can find more information about the iInventoryTransaction table here .

The gPartyTransaction table

This is the main table for all Party transactions - it includes Debits and Credits for Customers and Suppliers.

Invoices and Payments from Purchases "create these transactions" when they are posted - they use data from the bPurchase and/or the bPurchaseAR, bBusinessDocument_CashLine, bBusinessDocument_CheckLine tables.

To speed up queries this table is not 100% relational.

Please note that there are NO tables that SUM Debits and Credits for Customers or Suppliers - if needed, this information is "calculated on the fly" by queries.

Another important design decision is to keep the Credits and Debits for Customers and Suppliers together, in one table - the gPartyTransaction table. This way we can "relate" Debits and Credits for a Party that come from the Sales or the Purchase area - this info is kept in the gCrossPartyTransaction table.