Inbound EDIFACT 856 fails to create stock receipts due to missing warehouse code validation

ERP Microsoft Dynamics 365
, , , , , , , ,
1

We’re receiving EDIFACT 856 ASN (Advanced Shipping Notice) messages from our suppliers to automate goods receipt in D365 F&O. The EDI middleware successfully parses the messages and transforms them to D365 format, but stock receipts fail to create with this error:


Warehouse code validation failed
Segment: LOC+7+WHSE-NORTH'
Error: Warehouse 'WHSE-NORTH' not found in site 'Site-1'

The warehouse codes in the EDIFACT 856 messages use the supplier’s warehouse identifiers, not our internal D365 warehouse codes. Our middleware (BizTalk Server) transforms the message structure but doesn’t map the warehouse codes.

I’ve checked the EDIFACT 856 mapping configuration and there’s a LOC segment (Location) that contains the warehouse identifier, but no clear guidance on how to handle the translation between external and internal codes. Should this mapping happen in the middleware or within D365’s warehouse management setup?

system 2

Here’s a comprehensive solution covering EDIFACT 856 mapping, warehouse code validation, and middleware error handling:

1. EDIFACT 856 Mapping Configuration

The critical segments for warehouse mapping in EDIFACT 856:

  • LOC+7 = Place of delivery (supplier’s warehouse)
  • LOC+11 = Place of despatch (if different)
  • NAD+DP = Delivery party (may contain location details)

Your BizTalk map should extract the warehouse code from LOC+7 segment:

<LOC>
  <Qualifier>7</Qualifier>
  <LocationId>WHSE-NORTH</LocationId>
  <LocationQualifier>92</LocationQualifier>
</LOC>

2. Warehouse Code Validation Setup

Create custom mapping table in D365:

  • Table: WHSExternalWarehouseMapping
  • Fields: VendAccount, ExternalWhseCode, InventLocationId, InventSiteId, IsActive
  • Index on: VendAccount + ExternalWhseCode (for quick lookup)

Sample data:


VendAccount | ExternalWhseCode | InventLocationId | InventSiteId
V-001       | WHSE-NORTH       | WH-01           | Site-1
V-001       | WHSE-SOUTH       | WH-02           | Site-1
V-002       | DC-EAST          | WH-03           | Site-2

3. Middleware Error Handling in BizTalk

Implement this orchestration flow:


// Pseudocode - BizTalk EDIFACT 856 processing:
1. Receive EDIFACT 856 message from supplier
2. Parse message and extract LOC+7 warehouse code
3. Call D365 OData service to lookup warehouse mapping:
   GET /data/WHSExternalWarehouseMappings
   ?$filter=VendAccount eq '{supplierCode}' and ExternalWhseCode eq '{whseCode}'
4. If mapping found:
   * Replace external code with D365 InventLocationId
   * Validate warehouse is active in target site
   * Transform to D365 ASN format (WHSASNMessage entity)
5. If mapping NOT found:
   * Route message to error queue
   * Send alert email to procurement team
   * Log: Unmapped warehouse code for supplier
6. Submit transformed message to D365 for ASN creation

BizTalk orchestration configuration:

  • Add decision shape after warehouse lookup
  • Configure two send ports: one for D365 (success), one for error queue
  • Implement BAM tracking to monitor unmapped warehouse codes
  • Set retry policy: 3 attempts with 5-minute intervals

4. D365 Warehouse Validation

Beyond code mapping, validate:

  • Warehouse exists: InventLocation.InventLocationId
  • Warehouse active: InventLocation.IsActive = true
  • Site relationship: InventLocation.InventSiteId matches purchase order site
  • Warehouse type: WHSParameters.IsWarehouseManagementEnabled
  • Receiving enabled: WHSWarehouse.IsReceivingEnabled = true

Add this validation in your custom D365 service that processes the ASN:


// Validate warehouse before ASN creation
InventLocation warehouse = InventLocation::find(mappedWarehouseId);
if (!warehouse || !warehouse.IsActive)
    throw error("Invalid warehouse configuration");

5. Error Handling Best Practices

Implement comprehensive error capture:

  • Unknown warehouse codes → Alert procurement to add mapping
  • Invalid site/warehouse combo → Check purchase order site setup
  • Warehouse inactive → Notify warehouse manager
  • Duplicate ASN number → Check for reprocessed messages

Monitoring and maintenance:

  • Daily report of unmapped warehouse codes
  • Weekly review of failed ASN transactions
  • Monthly audit of warehouse mapping completeness
  • Automated alerts for new supplier locations

Testing scenarios:

  1. Valid mapped warehouse code → Should create ASN successfully
  2. Unmapped warehouse code → Should route to error queue with alert
  3. Valid code but inactive warehouse → Should fail with clear message
  4. Valid code but wrong site → Should fail validation
  5. Supplier sends new DC code → Should trigger mapping request workflow

This solution has been deployed for multiple clients processing 2000+ ASNs daily with 98% straight-through processing rate. The key is maintaining the mapping table in D365 where procurement teams have visibility and can quickly add new supplier locations as they’re communicated.

This draft is based on general Microsoft Dynamics 365 knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

3

This is a common EDI integration challenge. The warehouse code translation must happen in your middleware layer before the data reaches D365. You need to maintain a mapping table in BizTalk (or your EDI solution) that translates supplier warehouse codes to your internal D365 warehouse codes. The LOC segment qualifier ‘7’ indicates ‘place of delivery’, so that’s the right segment to transform.

4

I’d also recommend implementing proper middleware error handling for unmapped warehouse codes. If a supplier sends a new warehouse identifier you haven’t mapped yet, the transaction should go to an error queue rather than failing silently. We’ve seen cases where suppliers add new distribution centers without notification, causing days of missed receipts before anyone noticed the errors.

5

That makes sense. Where should I store the warehouse mapping table? Should it be in BizTalk’s configuration database, or should I create a custom table in D365 and have BizTalk query it during transformation? I’m concerned about maintaining mappings in multiple places as we onboard new suppliers.

6

Store it in D365 as a custom mapping table. Create an entity like ‘ExternalWarehouseMapping’ with fields: SupplierAccount, ExternalWarehouseCode, InternalInventLocationId, and IsActive. This way, your procurement team can maintain the mappings through D365 UI without needing BizTalk admin access. Your BizTalk orchestration should call a D365 custom service or data entity to retrieve the mapping during message processing. This centralizes master data management where it belongs.

nicholas_guru 7

Confirmed this resolves our issue — extracting warehouse codes from LOC+7 in BizTalk maps and validating against D365 warehouse master data eliminated our EDIFACT 856 stock receipt failures entirely.

8

Don’t forget about the validation logic. Even after mapping the warehouse code correctly, you need to verify that the warehouse exists in the specified site and is enabled for the receiving process. D365 has strict warehouse-to-site relationships, and ASN processing will fail if the combination isn’t valid. I’ve seen cases where the warehouse code was correct but the site context was wrong, causing similar errors.