Microsoft DynamicsFree referencePDF, Excel, Word exportMicrosoft Dynamics 365 Finance and Supply ChainDiscrete Manufacturing

D365 Finance and Supply Chain Data Entity Reference for Manufacturing

Choosing the right data entity is the first decision in any Dynamics 365 Finance and Supply Chain data load or integration. This reference groups the entities manufacturing projects touch most, with what each carries and the traps that cost consultants time.

Download:

Area	Entity (label or OData name)	What it carries	Consultant note
Product	Released products V2 (ReleasedProductsV2)	Released product master: item number, product type, units, groups	Most common item load. Legal-entity specific. Pair with the product master entity first.
Product	Products V2 (EcoResProductV2Entity)	Shared product master, product dimensions and search names	Load before released products. Not company specific.
Product	Released distinct products	Released products for distinct (non-variant) items	Use for simple item loads when no product variants are needed.
Product	Product categories / category hierarchy entities	Category hierarchies and assignments for products	Hierarchy must exist before assigning products to categories.
Product	Item coverage (per-item coverage settings)	Item coverage: coverage group, min and max, lead times by item and site	Required for master planning to behave per item. Check the entity name in your version.
BOM	Bill of materials headers (BillOfMaterialsHeaders)	BOM header: BOM number, name, approval and active flags	Load headers before lines. Approve and activate through the import or after.
BOM	Bill of materials lines (BillOfMaterialsLines)	BOM component lines: item, quantity, unit, line type, scrap	Watch line type (Item, Vendor, Pegged supply) and the constant scrap fields.
BOM	Bill of materials versions	BOM versions with date and quantity validity and site	A version links a BOM to an item, site and validity window.
Routes	Route headers and route operations entities	Route header and operations: operation number, resource requirement, times	See the Data entities form for the exact public names in your version.
Routes	Operations (operation master) entity	Operation definitions referenced by routes	Load operations and resource groups before routes.
Resources	Resources and resource groups entities	Work centers, machines, labor resources and groups	Resources need calendars and capabilities assigned to be schedulable.
Resources	Calendars and calendar working times	Working time calendars used for scheduling	Master scheduling and shop floor dates depend on them.
Production	Production order headers (ProductionOrderHeaders)	Production order header: item, quantity, status, dates, BOM and route	Used for integration and migration of open orders. Status transitions need care.
Production	Production order BOM and route lines entities	Production order component and operation lines	Consult the Data entities form for names. Posting changes to inventory is not an entity import.
Production	Production order picking list / route card journals	Journals that consume material and report operations	Journal entities have posting implications. Test in a non-production environment.
Inventory	Inventory on-hand entity	Read access to on-hand by dimensions	For reads, prefer the on-hand API over bulk entity export when volume is high.
Inventory	Inventory journal headers and lines	Counting, movement and adjustment journals for opening balances	Typical opening balance load. Posting is a separate step.
Inventory	Warehouses and sites entities	Sites, warehouses and locations	Dimension values must exist before inventory is loaded.
Procurement	Purchase order headers V2 (PurchaseOrderHeadersV2)	Open purchase orders header	Vendor and delivery terms must exist. Check currency and legal entity.
Procurement	Purchase order lines V2 (PurchaseOrderLinesV2)	Purchase order lines	Use received quantity carefully when migrating partially received orders.
Procurement	Vendors V2 (VendorsV2)	Vendor master	Party record is created with the vendor. Watch vendor groups and payment terms.
Sales	Sales order headers V2 (SalesOrderHeadersV2)	Sales order headers	Order of load: customers, items, then orders.
Sales	Sales order lines V2 (SalesOrderLinesV2)	Sales order lines	Delivery dates and reservations influence master planning.
Sales	Customers V3 (CustomersV3)	Customer master	Group, currency and payment terms must be present.
Finance	Main accounts (MainAccounts)	Chart of accounts main accounts	Shared across legal entities that use the same chart.
Finance	Legal entities (LegalEntities)	Company list with identifiers	Use dataAreaId values when filtering OData across companies.
Finance	General journal entities	Ledger journal headers and lines	Used for opening balances. Validate dimension formats in advance.
Cost	Item prices and cost entities	Standard cost, price and trade agreement style records	Standard cost activation is a separate step in costing versions.
Quality	Quality order and test entities	Quality associations, tests and results	Availability depends on enabled modules and features.
Admin	Number sequences entities	Number sequence definitions	Do not overwrite live sequences during a cutover rehearsal.

Entity names and exact public collection names vary by version and enabled features. Always confirm in Data management > Data entities (filter by module) before building an integration or a data project.

Map your D365 entities to a migration plan

Send us your entity list and we will review the load order and validation risks. Optional, the reference is free without it.

Optional. The tool and every export work without this. No spam.

How to use this reference

Search by area (Product, BOM, Routes, Production, Inventory) or by a term such as 'lines'. The consultant note column flags load order and posting behavior. Treat the names as a starting point, then confirm the exact entity in Data management > Data entities, where you can filter by module, see whether an entity is OData-enabled and review its staging table and target fields.

Search a term, then export the matches to Excel for your mapping workbook
Confirm each name in the Data entities form of your environment
Check the 'Is public' and OData properties before building an integration
Note legal-entity scope before you design the load per company

Load order for a manufacturing data project

Entities depend on each other. A typical order is: legal entities, calendars, sites and warehouses, units and groups, products and released products, resources and operations, routes, bills of materials and versions, item coverage, vendors and customers, then open orders and opening inventory. Loading in a different order creates avoidable validation errors, such as a BOM line referencing an item that is not yet released to the legal entity.

Data entities, OData and the integration choice

A data entity is a denormalized view over several tables. It can be used in the Data management framework (import and export through staging) and, when public, exposed as an OData collection. For high-volume reads, recurring data export or the data lake style options are usually better than paging OData. For writes with business logic, entity imports run the same validation as the form, which is slower but safer than direct table writes.

Common mistakes

The usual errors are loading a company-specific entity into the wrong legal entity, importing BOM lines before the header is approved, assuming an entity name from a previous version, and treating posting journals like simple master data. Document the entity, the sequence number in the data project and the owner of each load in your cutover plan.

Frequently Asked Questions

Where do I find the exact data entity name in D365?

Open Workspaces > Data management, then the Data entities tile. Filter by module, search by label, and check the entity name, staging table and whether it is public. The public collection name is what an OData URL uses, and it can differ from the label.

What is the difference between ReleasedProductsV2 and ProductsV2?

The shared product (EcoResProductV2Entity) is company independent and holds the product master. Released products are the per-legal-entity record with units, groups and item model data. Load the shared product first, then release it to the legal entity.

Can I import production orders through data management?

You can, through the production order entities, and projects do it for open work in progress. Status, reservations and inventory postings need careful design, so most teams migrate open orders at a defined status and test in a sandbox before any production load.

Do entity names change between versions?

Yes. New versions are added with a V2 or V3 suffix and older ones are deprecated over time. Features also change which entities are available. Always verify against your environment instead of copying names from older documentation.

If you want these entities queried by plain language over your own D365 data, with the query shown and role security respected, we can scope that with you.

Talk to an Expert Explore More Free Tools

Related Tools

Microsoft Dynamics

More Microsoft Dynamics tools

See all

Back to All Tools