The , Account Receivable (AR) and Accounts Payable (AP) modules in AX are very similar to one another. On one hand, you have customers and sales orders and on the other hand, you have vendors and purchase orders. The examples in this chapter are only from the AR module, but switching the example to AP should not be a problem for you at this point.
As you will see from the entity schema in the next section, the similarities between the tables on the different sides are taken to a common level using a table map in the in Application Object Tree (AOT). This enables you, as a developer, to write one class that can easily handle both AR and AP at the same time, as you can reference the table map instead of having two classes—one class to reference the AP tables and another class to reference the AR tables.
The entity schema shows how the base data in the AR and AP modules relate to one another. It also shows that the fields that are common in the AR and AP modules are put into maps to enable one piece of code to refer to the map and have it work for both the AR and the AP modules.
Again, this schema is very simplified as there are many more fields and other entities that also relate to the tables in the schema.
The following table gives a brief description of each of the tables shown in the preceding entity schema:
The transactions entity schema shows how the customer and vendor transactions link to settlement tables and the ledger transactions, and how all of these tables relate to the ledger dimensions. The following shows a transaction entity schema:
The following table gives a brief description of each of the tables shown in the preceding transactions entity schema: