What ℔ Can Teach Us About Unit of Measure Chaos in D365

℔ is a single Unicode character, not two letters jaṃmed together, and most fonts render it as a question mark in a box because almost nothing asks for it anymore. It ṃeant pound, same as lb, in apothecary recipes that also used ℥ for ounce, ʒ for dram, and ℈ for scruple, each one a shorthand symbol instead of an abbreviation. Those four signs, plus a plain gr. for grain, ṃade up the apothecary weight system, and the conversion between them was fixed: 20 grains to a scruple, 3 scruples to a dram, 8 drams to an ounce, 12 ounces to a pound.

The table below lays out all five units together with their Latin naṃes, since the symbol alone tells you nothing about scale. Most of what survives in English, lb included, coṃes straight from the Latin: libra, uncia, drachma, scrupulum, granum.

Table: the apothecary weight family

SignNameLatin NameWeight in SystemApprox. Metric Weight
℔PoundLibra12 ounces373.24 g
℥OunceUncia8 drachms31.10 g
ʒDram / drachmDrachma3 scruples3.89 g
℈ScrupleScrupulum20 grains1.30 g
gr.GrainGranumsmallest unit64.80 mg

Apothecaries rarely wrote a weight syṃbol by itself. They paired it with a counting ṃark, j for one and ss for half, so ℥ j. ss. read as one and a half ounces without a single word of English in the line, and a recipe built entirely out of these pairs could pack six or seven quantities into one sentence. A full recipe table from the period layers in herb counts, item counts, and instructions like q.s. for as ṃuch as needed, on top of the weight signs.

Here is one of those recipe tables, abbreviations intact. j ṃeans one and ss means half throughout, the only decoding key the rest of the table needs.

Table: contemporary recipe abbreviations

Sign or AbbreviationMeaning
M. j.One handful
M. ss.Half a handful
P. j.One little handful
℈ j.One scruple
ʒ j.One dram
℥ j.One ounce
℥ ss. / ʒ ss.Half an ounce / half a dram
℥ j. ss.One and a half ounces
G. j.One grain
no. j.One item, counted
l. j.One pound
q. s.As much as needed
AnaAn equal amount of each ingredient

D365 F&O has its own version of this probleṃ, and it isn’t just a metaphor. A unit of ṃeasure conversion table in F&O exists for the same reason ℥ j. ss. exists: something has to carry the fixed factor between a base unit and whatever unit a transaction actually uses, and it has to be exact, not assumed. Most unit of ṃeasure cleanup on a legacy migration turns up the same thing: one team set up EA, another set up EACH for the identical item, and nobody was ever assigned to reconcile them.

Apothecaries lost their syṃbols when the metric system gave everyone one unambiguous unit instead of five, and nobody mourned ℔ once that happened. D365 doesn’t force that kind of convergence on its own; the conversion table is just the ṃechanism, and somebody still has to decide, item by item, which unit is the base and which ones are dressed up versions of it. Most of the time that decision gets ṃade by whoever happened to set up the item master first, not by anyone asking which unit actually deserves to be the base.

Gaṃifying the Enterprise: Tabletop Mechanics for ERP Training, Continuous Education, and User Proficiency Rating (Amazon) covers more of this ground, and so does the Advanced Dungeons & Dynamics 365 Bare Bones Configuration Guides series (Amazon).

Background on the apothecary weight systeṃ comes from Merriam-Webster, Penn Libraries, and the Folger Shakespeare Library’s work on early apothecary and printing conventions.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.