DM501 – Using the Composite Inbound ASN V3 Entity in D365FO: A Step-by-Step Guide to Create Inbound Loads via Data Projects (Part-1)

Series Introduction

This article is Part 1 of 4 in the Automatic Inbound ASN Series, where we explore key Data Management operations in Dynamics 365 Finance & Operations (D365FO). You can find the complete series below:

📌 DM501 – Using the Composite Inbound ASN V3 Entity in D365FO (Current Article)
📌 DM502 – Converting Excel Data to XML for Inbound ASN V3
📌 DM503 – Securing Data Management Projects in D365FO
📌 DM504 – Automating Inbound Load Creation in D365FO

Introduction

In this article, we will walk through the process of using the Inbound ASN V3 entity in D365FO to create inbound loads. Key topics include configuring the data entity, preparing XML templates, setting up Data Management projects, and importing data for load creation.

The Inbound ASN V3 (Advance Shipment Notice) entity in Dynamics 365 Finance and Operations is used to automate and streamline the process of receiving shipments from suppliers. It allows businesses to create inbound loads based on shipment details provided by the supplier, ensuring the correct quantities and products are expected and received.

Use Case

• Supplier sends shipment data: Suppliers send shipment details like products, quantities, and delivery dates in an electronic format.
• Inbound load creation: Using the Inbound ASN V3 entity, this shipment data is imported into D365FO to create an inbound load. The system can automatically recognize what products are being delivered and prepare the warehouse for receipt.
• Accurate and efficient receiving: By using the ASN V3 entity, companies can automate the creation of these loads, reducing manual entry and ensuring more accurate inventory tracking. It helps in managing large volumes of shipments and improving the overall efficiency of the supply chain.

Breakdown of Inbound ASN V3 data entity: Child Entities

Note: Case details are optional and can be disregarded if not required. For our use case, we will not be utilizing case details. Please be aware that Microsoft frequently updates the Inbound ASN composite entity, having done so four times already. Ensure you are working with the latest version of the entity.

Step 1: Prepare Inbound ASN Template

1. Create Project

• Prepare data project and download template

• Find download package and access entity format file.

• Amend ‘Inbound ASN V3’ template and prepare your own template with required data for your business to create inbound load.

Note – For simplicity, I am using use case of organization with minimum information without packing structure case data as below.

<?xml version="1.0" encoding="utf-8"?>
<Document>
    <WHSINBOUNDLOADHEADERENTITY LOADID="Load123" />
    <WHSINBOUNDSHIPMENTHEADERENTITY SHIPMENTID="Load123" DELIVERYTERMSCODE="" />
    <WHSINBOUNDLOADPACKINGSTRUCTUREENTITY LICENSEPLATENUMBER="LP123" />
    <WHSINBOUNDLOADPACKINGSTRUCTURELINEV3ENTITY ITEMNUMBER="ABC" PURCHASEORDERNUMBER="PO123" PURCHASEORDERLINENUMBER="1" QUANTITY="1" UNITSYMBOL="ea" />
</Document>

• Save this data as Master Inbound ASN V3.xml entity

Step 2: Prepare Data management Import project (But do not Import data)

1. Create Import Project

• Prepare data project

• Save Data project but do not import data,

Step 3: Run and Test

1. Prepare Purchase orders – I have 3 Purchase orders with one line each

2. Prepare XML file to data project

• Inbound Load ID: IB1234
• License Plate: LP1234

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Document>
    <WHSINBOUNDLOADHEADERENTITY LOADID="IB1234" />
    <WHSINBOUNDSHIPMENTHEADERENTITY SHIPMENTID="Load123" DELIVERYTERMSCODE="" />
    <WHSINBOUNDLOADPACKINGSTRUCTUREENTITY LICENSEPLATENUMBER="LP1234"/>
    <WHSINBOUNDLOADPACKINGSTRUCTURELINEV5ENTITY ITEMNUMBER="IP001" PURCHASEORDERLINENUMBER="1" PURCHASEORDERNUMBER="CPO015291" QUANTITY="5" UNITSYMBOL="ea"/>
    <WHSINBOUNDLOADPACKINGSTRUCTURELINEV5ENTITY ITEMNUMBER="IP002" PURCHASEORDERLINENUMBER="1" PURCHASEORDERNUMBER="CPO015292" QUANTITY="10" UNITSYMBOL="ea"/>
    <WHSINBOUNDLOADPACKINGSTRUCTURELINEV5ENTITY ITEMNUMBER="IP003" PURCHASEORDERLINENUMBER="1" PURCHASEORDERNUMBER="CPO015293" QUANTITY="3" UNITSYMBOL="ea"/>
</Document>

3. Upload file using Data management Project

• We will leave initial mapping in place
• Select Import Project and click Run

• Upload and import file

• Wait for successful data import

4. Verify Import

• Inbound load

• Packing Structure

In the upcoming article, I will demonstrate how to create an XML template from an Excel file, providing a guide for end users who may not be familiar with XML coding.

Expand Your Knowledge: See More Data Management Blogs