Distinguishing between concepts in Microsoft Dynamics AX 2012: amount vs. quantity
This is the first blog entry of an ongoing series that I will offer periodically to share distinctions between concepts that we apply frequently in Microsoft Dynamics AX and that I receive questions about.
In this blog entry, we take a closer look at how we apply the concepts named amount and quantity in the product.
We apply the concept amount when we need to represent something that cannot be counted or that is indivisible. More specifically, we use the term amount to represent a definite magnitude of currency, a quantity of currency, or an indefinite magnitude of an uncountable substance or quality.
We apply the concept quantity when we need to represent something that can be counted or that is divisible. More specifically, we use the term quantity to represent an exact measure of some countable operational or financial characteristic that is represented by a number.
Term challenge
In the sentences that follow, insert the term that accurately completes each sentence.
To see if you applied the terms as we have, click the link in each sentence. Each link will take you to the Microsoft Dynamics AX glossary entry for the highlighted term, which shows you which term we have applied – amount or quantity.
- A kanban is a signal that communicates a requirement for a/an ___________ of product.
- A consolidated invoice is a vendor invoice that documents a sum of product ____________ and a monetary ____________ from more than one referenced vendor invoice.
- Balance is the ____________ of economic resource required to bring opposite economic resource flows to a state of equilibrium.