Automotive

Purpose

Automotive, also referred to as BE-Automotive in older documents, extends Microsoft Dynamics 365 Business Central with automotive and logistics-oriented process components. In daily operation, this mainly means that you steer call-offs, automotive sales and purchase orders, loading units, transport data, EDI messages, mobile scanning processes, and Logistics Supply Chain in one connected workflow.

Business Value

• You see which work areas in Automotive belong together from a business perspective and in which sequence they are typically used.
• You recognize which pages are informative only and which pages actually control operational processing.
• You can place sales, purchasing, shipping, loading units, LSC, workflow, and EDI inside one shared end-to-end process.
• You can recognize how mobile processes and electronic sales labels complement several main processes as cross-cutting topics.
• You can guide new users and key users more quickly to the functionally correct detail pages.

Typical Process Model

graph LR;

%% Nodes
A[Inbound call-offs or EDI messages]
B[Automotive Sales Order or Automotive Purchase Order]
C[Plausibility, release, and operational lines]
D[Loading units, packaging, and warehouse logic]
E[Goods receipt or production or goods issue]
F[Sales Transport Data and shipping documents]
G[Invoice or credit memo or history]
H[Workflow and event messages]
I[Logistics Supply Chain]
J[EDI Setup, partners, and message monitoring]

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==> D
D ==> E
E ==> F
F ==> G
C ==> H
D ==> I
A ==> J

%% Classes
class A btProcessTitle
class B,C,D,E,F,G,H,I,J btProcessActive

Process overview from the service description

The service description also maps the end-to-end flow as one connected process picture across purchasing, planning, production, warehouse, and sales. This complements the Mermaid model above with a role-based operational view.

Click to enlarge

Key interpretation from this source:

• Delivery call-offs, detailed call-offs, and production-synchronous call-offs drive the sales side of execution.
• Purchasing and production run supply and planning streams in parallel and converge in warehouse stock.
• Goods issue is functionally tied to transport data, labels, and downstream shipping documents.
• Invoice and credit processing should be read as an integrated part of the same process chain, not as a detached finance-only flow.

Real work areas in the solution

How the solution components work together

Automotive core logic

The functional core of Automotive is the automotive sales and purchase order logic. These documents bring together plant, unloading point, reference numbers, item numbers, call-off mode, progress counters, packaging references, and pricing logic so that later call-off and shipping steps can work reliably.

Operational control in sales

In sales, the main operational hub is Automotive Sales Order. From there, you create delivery call-offs, detailed call-offs, or production-synchronous call-offs, review open detail lines, control transit quantities, and prepare shipment through Sales Transport Data.

Operational control in purchasing

In purchasing, Automotive Purchase Order acts as the operational framework order. From there, you create delivery call-offs, review delivery history and detailed-call-off information, and later connect the order with warehouse receipt, invoice, and archive status.

Packaging, loading units, and LSC

Loading-unit logic and Logistics Supply Chain are not isolated side topics. They directly affect purchasing, sales, warehouse, and production. Packaging structure, ownership, movements, QA, and backflush should therefore always be read as part of the complete process.

Mobile execution and electronic labels

Mobile processes and Electronic Sales Labels are cross-cutting topics. Mobile scanning processes directly affect warehouse, production, and inventory execution. Electronic labels connect Business Central with external platform logic, infrastructure, and physical display. Both remain stable only if business release, technical integration, and operational control steps fit together.

EDI, workflow, and audit trail

EDI and workflow form the cross-process communication and control layer. EDI connects call-offs, delivery notes, transports, and invoices with external partners. Workflow and event pages make visible where the process was violated or where a business decision is still pending.

Recommended reading path for new users

1. Start with Setup and master data so that global parameters, mandatory fields, and technical prerequisites are clear.
2. Deepen Pack structure management early when items, packaging materials, and process steps need to be controlled not only by quantity but by package structure.
3. Add Mobile processes, BE-Mobile Fusion, and legacy MDE and Electronic Sales Labels early when scanner processes, infrastructure, or electronic displays are part of the project.
4. Then move into Sales and call-off processing or Purchasing and order processing, depending on the role.
5. Add Loading units and empty returns and Logistics Supply Chain when the process includes packaging, warehouse handling, or production.
6. Use Workflow and event messages and EDI interface as soon as monitoring, deviations, or external communication become relevant.
7. Use Process catalog as the cross-process view of the main end-to-end workflows.
8. Review Migration analysis: legacy help vs. new documentation when you want to secure migration coverage from the legacy help content.

Result

• You can position Automotive as one connected solution instead of a loose collection of menus.
• You know which areas should be read first and which detail pages should be deepened afterward.
• You have a reliable orientation for sales, purchasing, loading units, LSC, mobile, ESL, workflow, and EDI.