PurchaseAP Data Model
Last Edit: December 1, 2017 the alpha360 team
The main table of the PurchaseAP Entity is the bPurchaseAP table - every bPurchaseAP record is related to one and only one bBusinessDocument record.
This is done with a one to one relation between the bBusinessDocument record and a bPurchaseAP record - here the PK is the bBusinessDocument.sBusinessDocumentPK field and the FK is the bPurchaseAP.sBusinessDocumentFK field.
To implement this type of relation in the Analysis:
This data model is built from the Universal Business Document Model
The bPurchaseAP has the following important data:
The bBusinessDocument has the following important data:
Every bBusinessDocument record has a [1,1]->[0,n] relation to a bBusinessObject record.
At the end, this record - the bBusinessObject record - gives the bPurchaseAP record all its functionality (numbering, defaults, print forms) including its specific Business Object Role.
The bPurchaseAP table currently supports the following Business Objects Roles:
The alpha360 supports one Payment distributed to many different CashBooks (or Cash Accounts) - the bBusinessDocument_CheckLine stores these "different payments" - note here that each record is related to the bBusinessDocument record.
The alpha360 supports one check Payment distributed to many different Checks - the bBusinessDocument_CheckLine stores these "different check payments" - note here that each record is related to the bBusinessDocument record.
next -> Purchase Transactions
Copyright 2017 - computerplus