web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / Hardik’s Dynamics Dojo / Understanding TransChildTyp...

Understanding TransChildType and TransChildRefId in InventTrans

Views (6)
HardikPatel523 Profile Picture HardikPatel523 184

Understanding TransChildType and TransChildRefId in InventTrans — The Hidden Links Behind Inventory Transactions

In Microsoft Dynamics 365 Finance and Operations, the InventTrans table records every inventory movement in the system.
Whenever inventory changes, a transaction is created here, for example:
  • Purchase receipts
  • Sales issues
  • Production consumption
  • Inventory movements
But sometimes an inventory transaction is linked to another document in the system.
This relationship is captured using two fields:
  1. TransChildType
  2. TransChildRefId
These fields help Dynamics identify which document the transaction is associated with.

TransChildType — What Kind of Document Is Linked

TransChildType tells the system what type of document the transaction is linked to.
Examples include references like:
  • Picking list journal
  • Inventory journal
  • Other inventory-related postings


Instead of storing detailed information, Dynamics stores a type indicator that identifies the document category.
In simple terms:
TransChildType answers the question: “What type of document is this transaction linked to?”

TransChildRefId — The Actual Document(Reference) ID

If TransChildType describes the type, then TransChildRefId stores the actual document identifier.
For example:

No Open picking list journal linked:


Open picking list journal linked, for total quantity:



Open picking list journal linked, for partial quantity:


Same fields exists in related tables for relation:


So these two fields together identify both the document type and the specific document.

Important Behavior — Transaction Cannot Be Closed

One important thing to know about these fields:
If TransChildType and TransChildRefId are populated on an InventTrans record, the system treats the transaction as linked to another process or document.

Because of this relationship:
The transaction cannot be closed while this reference exists.

You may get error’s like - 
  1. “The production has lines in Picking list journal that must be posted first.”
  2. “The quantity cannot be reduced. The number of inventory transactions on order is too low because the quantity or part of it is referenced by an output order or a production order or is marked against other transactions.”
  3. “Inventory dimensions cannot be changed for the transactions because the latter is controlled by the inventory reference ……”
The system expects the linked document or process to be completed or cleared before the transaction can be closed.
This helps maintain data integrity and traceability in inventory flows.

Final Thoughts

At first glance, InventTrans looks like a simple list of inventory movements.
But fields like TransChildType and TransChildRefId reveal that transactions are often connected to other inventory documents.
Understanding these fields helps developers:
  • Trace inventory relationships
  • Debug inventory postings
  • Investigate warehouse transactions
And most importantly, it explains why sometimes an inventory transaction refuses to close — because it is still linked to another document.

Comments