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 :
Supply chain | Supply Chain Management, Commerce
Unanswered

deferent warehouse info

(0) ShareShare
ReportReport
Posted on by 108

hello

A Purchase Order (PO‑000005105) was created and confirmed with warehouse JDSFR, and the Product Receipt was also posted into JDSFR as expected.

However, the system created inventory transactions and on‑hand quantities in MKSFR instead of JDSFR.

 

Expected Behavior:

When a PO is created, confirmed, and product‑received in warehouse JDSFR, the on‑hand inventory and inventory transactions should remain in JDSFR.

 

Actual Behavior:


  • PO header/line warehouse: JDSFR
  • PO confirmation: JDSFR
  • Product Receipt Journal: JDSFR
  • Inventory on‑hand: MKSFR
  • Inventory transactions: MKSFR
  • Batch number created from receipt: 260310‑PO‑000005105
  • Lot ID: HLES‑2309213
  • Inventory dimensions for the Lot ID show warehouse MKSFR
  • Item Default Purchasing Warehouse: MFOPW
  • Vendor Default Warehouse: none


  •  

Impact:

The item physically should received in warehouse JDSFR but incorrectly posted and shown as available in warehouse MKSFR

 

Problem Statement:

There are no known transfer orders, no movement journals, and no WMS processes that would move the inventory to MKSFR.

This appears to be unexpected behavior in inventory posting logic or warehouse override during batch/lot handling.

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    303,657 Super User 2026 Season 1 on at
    Hi 7asan,
     
    This is the first time, I hear or read about such issue. In case you specify a warehouse, it will be set via the Inventory dimension on both the PO line as well as the related inventory transaction.
    Is the InventDimID on the PO line and the inventory transaction the same or different? In case it is different, it might be caused by a customization, or data manipulation. Are you aware of customizations or data corrections?
     
    Is this issue happening on only one PO or all POs? Do other documents (e.g. sales order) also have this issue? 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Supply chain | Supply Chain Management, Commerce

#1
Mallesh Deshapaga Profile Picture

Mallesh Deshapaga 227

#2
Laurens vd Tang Profile Picture

Laurens vd Tang 193 Super User 2026 Season 1

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 120 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans