Supply chain | Supply Chain Management, Commerce

Inbound ASN

(0) Share

Report

Posted on by dynamicsnewb96

190

I am trying to configure Inbound ASN. I am using the composite data entity Inbound ASN V2. However, if I do not include WHSInboundLoadPackingStructureCaseEntity and WHSInboundLoadPackingStructureCaseLineV2Entity while importing the entity I keep getting error.

Information loaded
'Inbound ASN V2_WHSInboundLoadPackingStructureLineV2Entity' entity mapping has completed successfully
'Inbound ASN V2_WHSInboundLoadPackingStructureEntity' entity mapping has completed successfully
'Inbound ASN V2_WHSInboundShipmentHeaderEntity' entity mapping has completed successfully
'Inbound ASN V2_WHSInboundLoadHeaderEntity' entity mapping has completed successfully

Cannot delete the parent entity 'Inbound ASN V2_WHSInboundLoadPackingStructureCaseEntity' if child entity Inbound ASN V2_WHSInboundLoadPackingStructureCaseLineV2Entity' exists, first delete the child entity and then try again

File does not contain the required data for entity: 'Inbound ASN V2_WHSInboundLoadPackingStructureCaseEntity'

How to resolve this error? Is caseentity mandatory for ASN?

I have the same question (0)

All responses (11)

Answers (0)

dynamicsnewb96 190 on at

Like (0)

Report
Copy link

Link copied!

<?xml version="1.0" encoding="utf-8"?>

<Document>

<WHSInboundLoadHeaderEntity TRACTORNUMBER="0000101">

<WHSInboundShipmentHeaderEntity VENDORSHIPMENTID="VendASN_01" VENDORADDRESSCOUNTRYREGIONID = "USA" VENDORADDRESSSTREET = "123 Coffee Street" VENDORADDRESSSTATEID = "WA" VENDORADDRESSCITY = "Redmond" VENDORADDRESSZIPCODE = "98052">

<WHSInboundLoadPackingStructureEntity LICENSEPLATENUMBER="LP_ASN_001">

<WHSInboundLoadPackingStructureLineV3Entity PURCHASEORDERNUMBER="00000176" ITEMNUMBER="A0001" QUANTITY="1" UNITSYMBOL="ea" />

</WHSInboundLoadPackingStructureEntity>

</WHSInboundShipmentHeaderEntity>

</WHSInboundLoadHeaderEntity>

</Document>

docs.microsoft.com/.../import-asn-data-entity

This is not working

Was this reply helpful? Yes No
Suggested answer

YY Lim 960 on at

Like (0)

Report
Copy link

Link copied!

Hi, could you share how do you create this import entity, I am using the same one on contoso without any problem?

Please check the import project is it correct? When you create import project, you need to upload it with the xml format that you are going to import which in your example above is the xml without these 2 case and case line entity

<WHSInboundLoadPackingStructureCaseEntity>

<WHSInboundPackingStructureCaseLineV3Entity>

Was this reply helpful? Yes No
dynamicsnewb96 190 on at

Like (0)

Report
Copy link

Link copied!

I am also using it in Contoso and using xml-attribute. Can you share your xml?

also which version are you using?

YY Lim

Was this reply helpful? Yes No
YY Lim 960 on at

Like (0)

Report
Copy link

Link copied!
Is the same on the link you provided, example 1.

The environment version is 10.0.28

Was this reply helpful? Yes No
dynamicsnewb96 190 on at

Like (0)

Report
Copy link

Link copied!

Hmmm, the only difference is I am at 10.0.24

Was this reply helpful? Yes No
YY Lim 960 on at

Like (1)

Report
Copy link

Link copied!

I don't have 10.0.24 environment to test now, but it is end of service already, perhaps you should update and test in latest version.

Was this reply helpful? Yes No
dynamicsnewb96 190 on at

Like (0)

Report
Copy link

Link copied!

YY Lim Do you have any documentation on Outbound ASN? I am trying to test it but nothing gets generate when I click on "Send ASN"

Was this reply helpful? Yes No
YY Lim 960 on at

Like (0)

Report
Copy link

Link copied!

I don't have any documentation on this, if you don't get anything you need from docs, perhaps you could request from Microsoft from the support or maybe some tech talk around this area if there is any.

Was this reply helpful? Yes No
Jupke 48 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Were you able to find a solution for this issue ?
We are running into the same error and are not able to use the xml without the 'case' child entities.

Thanks for you reply

Kind regards,

Jurgen van Zeeland, jzeeland@aptean.com

Was this reply helpful? Yes No
Suggested answer

Tendor11 5 on at

Like (0)

Report
Copy link

Link copied!

Hi all,

We had the same error on the new Inbound ASN V3 data entity, and the only solution was to go the Data Management -- Data entities -- Filter on the Inbound ASN V3 -- Select Manage and Related Data Projects.
Then Delete all the Import/Export projects that related to the Inbound ASN V3 entity.

After doing this, recreate a new project and reselect and map an XML file without the WHSInboundLoadPackingStructureCaseEntity or WHSInboundLoadPackingStructureCaseLine entities. The mapping should be done without any errors.

All the best,

Tendor.

Was this reply helpful? Yes No