Sales Orders from Eviden Automotive EDI Not Reflected in Item Net Requirements (D365 F&O)

(2) Share

Report

Posted on by Sangeeta - IT Syste...

Hello everyone,

We’re working on an automotive EDI integration in Dynamics 365 Finance & Operations (F&O) with implementation support from EDI partners.

We are using automotive contracts to create sales order in D365 and the sales order are being successfully created in D365 from automotive contracts. However, we’ve found that these EDI-created sales orders are not being considered in the Item Net Requirements calculation (MRP). And we are running planning optimization. However, EDI sales orders are working with old legacy master planning. So there is something in the palnning optimization.

Issue details:

Sales orders appear normally in D365 (status: Open order).
However, they do not show up in the Net Requirements form for the relevant items.
Manually created sales orders do appear as expected.
MRP is running correctly for other demand sources (manual orders, etc.).
EDI sales orders are created through an integration/middleware process handled by Eviden, which uses D365 APIs or data entities to create/insert orders.

Questions / What we’re trying to understand:

Are there any specific flags, fields, or statuses that must be set on sales orders for them to be recognized by the planning optimization / Net Requirements engine?

Could the issue be related to the origin of the sales order (e.g., not fully initialized in D365 tables, missing ReqTrans linkage, or unposted confirmation)?
Has anyone faced similar behavior with EDI automotive integrations in D365 F&O — where orders were excluded from net requirements?
Any recommendations for troubleshooting steps.

Environment:

D365 Finance & Operations

Industry: Automotive manufacturing / supply
Problem type: MRP not recognizing EDI-created sales orders

Thank you in advance for any insights or guidance!

Categories:

Dynamics 365 Supply Chain Management

I have the same question (0)

All responses (7)

Answers (1)

Suggested answer

André Arnaud de Cal... 303,667 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Sangeeta,

Can you tell us how the sales order lines are created? Is this through a custom import class? What coding is used for creating the lines?

For each sales order line you create, it should also create a record in the inventory transactions. These are used for the master planning calculation. Can you check if behind each sales order line there is also an inventory transaction record created?

Was this reply helpful? Yes No
Sangeeta - IT Syste... 36 on at

Like (0)

Report
Copy link

Link copied!

Hi @André Arnaud de Calavon,

Thanks for your reply!

Sales lines are created through Automotive contract. I am not sure but I think EDI is creating through data entities.

And also I checked that each sales line has the corresponding inventory transaction.

But I found that there is no sales line(generated through contract) available in ReqTrans table.

Was this reply helpful? Yes No
Suggested answer

Danny Bilodeau 4,934 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi Sangeeta,

Very well documented question, thank you for that.

In addition/complement to André's suggestion, you should check the Order type, if your EDI sales order are coming in as 'Sales Journal', they would excluded from planning (no transactions).

What's bizarre is that you say it worked with Legacy Master Planning. Once they are in D365, it should not matter the manner in which the sales order are created, so something is causing the transactions (if there are) to be ignored.

To my knowledge, unposted confirmation does not matter but that could be easily enough confirmed.

What comes to mind:

- Sales order Header : Order type "Journal"

- For a Warehouse with "Manual coverage" enabled.

- Item with Item coverage "manual" (overriden?)

- Product Lifecycle State excludes item from Planning

- Missing data on sales line:

Missing Dimension with "Coverage Plan by..." (look at Storage Dimension or Tracking Dim Gp)

If Product Master, missing Production dimension (style, size...)

When you update Net Requirements for the Item, do you have any error message?

Was this reply helpful? Yes No
Guy Terry 28,965 Moderator on at

Like (1)

Report
Copy link

Link copied!

Aside from the other suggestions here, please check the Exclude from master planning toggle on the Sales order lines

Was this reply helpful? Yes No
Sangeeta - IT Syste... 36 on at

Like (0)

Report
Copy link

Link copied!

Hello @Danny Bilodeau,

Thank you so much for your suggestions.

I have already checked those settings. And I am using same item with the same settings for creating both, manual order and through EDI contract. But they still behave differently. Also, we are not getting any errors while generating net requirements.

Hi @Guy Terry Thanks for the suggestion, but it's also turned off.

Was this reply helpful? Yes No
André Arnaud de Cal... 303,667 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Sangeeta,

In this case, it would be really beneficial to know what exact logic is used to create the order lines. It is using standard Dynamics 365 options, like calling a data entity or is it a customization where some logic is not included? Who did create the integration? Is that an own customization or is it part of the EDI solution?

Was this reply helpful? Yes No
Verified answer

Sangeeta - IT Syste... 36 on at

Like (4)

Report
Copy link

Link copied!

Hello everyone,

Thank you so much for your kind responses! We were finally able to identify the root cause and resolve the issue.

We did trace the net requirements scenario.

While tracing the net requirements scenario, we discovered that four specific validations must be set to "Yes" for sales orders to be included in the calculation.

What solved the problem:

1. Enable the required feature

Go to System administration → Feature management and enable “Ignore specific transaction types using Planning Optimization.”
Once this feature is active, the below four validation settings become visible in the master plan.

2. Update the master plan settings

Set all four validations to "Yes". After doing this, the sales order started appearing correctly in the net requirements.

In our case, “Include retail sales order” was set to "No", since we don’t use retail sales orders. Interestingly, turning it on still resolved the issue—though we’re not entirely sure why it’s required when retail isn’t in use.

Hope this helps someone facing a similar situation!

1 people found this reply helpful.

Was this reply helpful? Yes No