"THREAD" Unit of Measure Requirements

(5) Share

Report

Posted on by JE-20081519-0

3,549

Hi:

We know that Business Central can forecast finished good sales in EACH, yet, conduct supply planning for their raw materials in Purchase Orders or Work Orders in FEET.

We also know that -- for some finished goods -- sales quotes and sales orders are created in EACH, yet, Business Central can consume their raw material in INCH.

Some of those finished goods are in INCH but, also, are measured in THREADS where you thread one end (TOE), thread both ends (TBE), or Plain end (PE = no threading).

The demand for these different THREADS and lengths have to be summed in INCH, which is converted into FEET of replenishment requirements for any ¾-inch finished goods.

Can Business Central, out of the box, handle these THREAD requirements? If so, how?

Thanks!

John

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (2)

Verified answer

CA Vijay Krishna 180 on at

Like (4)

Report
Copy link

Link copied!
Yes It can be acheived through out of box functionality but not natively UOM as threads are not predefine UOM , before please try to follow this 6 steps and check

Step 1: Define Units of Measure (UOM)
Path: Item Card → Related → Item → Units of Measure

On the Item Card for your raw material (e.g., Pipe ¾-IN), set the Base Unit of Measure to INCH.

Add additional UOMs:

EACH = e.g., 36 INCH (if one finished good uses 36 inches).

FEET = 12 INCH.

Any other needed conversion.

Step 2: Configure Item Variants for THREAD Types
Path: Item Card → Navigate → Item → Variants

Create variants for the same item:

Variant Code = TOE (Thread One End).

Variant Code = TBE (Thread Both Ends).

Variant Code = PE (Plain End).

Step 3: Use Item Attributes (Optional, for reporting)
Path: Item Card → Navigate → Attributes

Create an Attribute called Thread Type.

Assign values: TOE, TBE, PE.

Link the attribute to the variants.

Step 4: Link to Production BOM or Routing (if manufacturing thread ops)
Path: Manufacturing → Production BOM → Lines
Manufacturing → Routings

If threading is a consumption/material difference, make separate BOMs for TOE/TBE/PE variants.

If threading is a process step, add a routing operation (e.g., Threading Machine = 1 min per end).

Assign routing to the variant.

Step 5: Forecast & Demand Planning
Path: Planning → Demand Forecast or Sales Orders / Quotes

Enter demand in EACH (finished goods).

System converts EACH → INCH.

Planning Worksheet converts INCH → FEET (raw material).

THREAD variant ensures that demand is separated (TOE vs. TBE vs. PE), but total length is rolled up for replenishment.

Step 6: Planning Worksheet
Path: Planning → Planning Worksheet

Run Calculate Plan.

BC aggregates demand across sales/forecast.

Replenishment requirements will show in FEET, while still respecting variant (TOE/TBE/PE).

Below is the Flow Process of UOM in Business Central.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Nimsara Jayathilaka. 4,950 Super User 2026 Season 1 on at

Like (6)

Report
Copy link

Link copied!

Hi

Business Central can handle the complex requirements of different units of measure, such as EACH, FEET, INCH, and THREAD types, out of the box. It achieves this by allowing users to set a base unit of measure per item and define alternate units with precise conversion factors. This ensures seamless conversion and aggregation of demand across units like THREAD lengths converted to FEET for replenishment planning. The system also supports rounding precision to avoid conversion errors, making it fully capable of managing multi-unit demands and supply planning without customization.

So, Business Central can natively manage THREAD requirements and supply planning across mixed units by configuring units and conversions properly on the item cards

https://community.dynamics.com/blogs/post/?postid=9e5080b3-e58b-f011-b4cc-0022482e2e9d

Thanks

Nimsara

2 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Sahan Hasitha 2,683 on at

Like (6)

Report
Copy link

Link copied!

hi

different units of measure such as EACH, INCH, and FEET can be managed out of the box by properly setting up the Base Unit of Measure and defining conversions in the Item Units of Measure table. For example, if the base is INCH, the system can automatically convert sales demand entered in EACH into INCH, and then into FEET for purchasing or replenishment planning. When supply planning is run, Business Central consolidates all demand into the base unit and then translates it into the purchasing or production unit, ensuring consistency across sales, purchasing, and manufacturing. The challenge arises with THREAD requirements such as TOE, TBE, or PE, since “threading” is not a unit of measure in Business Central. The standard approach is to manage these differences using Item Variants or separate items, especially if threading changes the stock, cost, or process. In this way, demand for threaded and non-threaded goods can still be summed in INCH, converted into FEET, and then proposed as supply in planning. Therefore, Business Central can handle these requirements natively through careful unit of measure setup, while THREAD-specific handling is best managed through variants or item design.

4 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Pallavi Phade 5,420 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Namaste John

Business central can handle multiple unit of measures . In item card , there are three unit of measures .

Base unit of measure will be considered for inventory repoting and it gets posted in item ledger enties .

Sales Unit of Measure for Sales , Purchase unit of Measure for Purchases,planning . If its blank , system considers base unit of measure for transaction

This is how item unit of measure with measurement works

There are multiple UOM's and the corresponding conversions . THis below matrix plays an important role

1 PC = 10 KG

Output and stock will be measured in Base unit of measure in item ledger entry

If you feel this could help , please verify the answer

Regards

Pallavi Phade

1 people found this reply helpful.

Was this reply helpful? Yes No
Verified answer

Rishabh Kanaskar 6,219 Super User 2026 Season 1 on at

Like (8)

Report
Copy link

Link copied!

Business Central can support this scenario by using a combination of item units of measure and production BOM or routing setup. Each item can be defined with a base unit of measure, such as feet, and additional units of measure, such as inch or each, can be added with conversion factors. Sales orders and forecasts can then be entered in the unit of measure that the customer uses, such as each or inch, while the system automatically converts them into the base unit for planning and replenishment.

For threading requirements like TOE, TBE, or PE, Business Central does not have a native threading attribute field. This requirement can be addressed by setting up separate item numbers for each threading type or by using item variants if the threading is the only differentiator. Demand from all variants can then be aggregated through planning worksheets, which generate production or purchase orders in the base unit of measure.

This setup allows the demand for different thread types and lengths to be entered in their respective units, summed automatically in the base unit, and converted into replenishment requirements in feet.

A walkthrough:

> Item 1000 is set up with base unit of measure Feet.
> Additional units of measure are set up: Each = 2 Feet, Inch = 0.0833 Feet.
> Three item variants are created: 1000-TOE, 1000-TBE, 1000-PE.

> Sales Order 1 requests 10 Each of 1000-TOE. System converts this to 20 Feet demand.
> Sales Order 2 requests 36 Inch of 1000-TBE. System converts this to 3 Feet demand.
> Sales Order 3 requests 5 Feet of 1000-PE directly.

Planning Worksheet sums demand to 28 Feet and creates a single purchase order or production order for 28 Feet of Item 1000.

Thanks

Rishabh

5 people found this reply helpful.

Was this reply helpful? Yes No