Setup and fundamentals on Product Documentation

Setup and master data

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes the business and technical foundation for Automotive based on the current AL code. The focus is a practical implementation sequence so that call-offs, automotive orders, EDI messages, loading-unit processes, and optional Logistics Supply Chain scenarios work together reliably.

Before You Start

Microsoft Dynamics 365 Business Central and the required Automotive licenses are installed.
The current app build is designed as a cloud solution. Plan the setup for SaaS or an equivalent cloud operating model.
The dependent app BE-terna Barcode Service is installed and technically available because label and barcode scenarios rely on it.
The base master data for items, customers, vendors, shippers, warehouse locations, countries, units, and delivery terms is prepared or available for migration.
You have decided whether optional scenarios such as EDL/Consi, Q-status, mobile data entry, or Logistics Supply Chain are part of the first project scope.

How this fits into standard Business Central

In setup, Automotive does not replace the BC foundation. The solution extends standard master data and standard parameters with automotive mandatory fields, VDA logic, EDI parameters, and transport- and packaging-related rules. For users, it is therefore important to separate two views clearly:

System requirements and administration

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page complements the general setup guidance with prerequisites and the administrative baseline. It describes the licensing and operating prerequisites, explains how barcode components should be understood, and outlines the administrative functions for record types, keys, and XML-based import and export.

1. Check system requirements carefully

Automotive can only run reliably when product licensing, app status, and technical supporting components fit together. The legacy documentation explicitly distinguishes between on-premises and cloud scenarios.

Setup wizard and parameter tabs

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page deepens the central Automotive setup. It complements the overview page with the assisted setup sequence, the business meaning of the most important parameter groups, and the points that are often missed in SaaS projects for barcode, EDI, and document output.

When this page is useful

during first-time implementations or when rebuilding a company setup
during go-live preparation when call-offs, EDI, and shipping must work reliably end to end
during troubleshooting when processes start but fail on mandatory values, number series, or transmission types
in cloud projects where barcode and PDF output work differently from older on-premises installations

Recommended sequence

Start assisted setup and initialize the base data.
Complete countries, units, and currencies with the VDA-related additional values.
Refine Automotive Setup in General, Sales, Purchasing, and document output.
Finish EDI Setup including number series and transmission type.
Only then maintain customers, vendors, items, packaging, locations, and references in detail.
Validate barcode, label output, and archiving with a real end-to-end test.

How to use the Automotive Setup Wizard correctly

The wizard is the fastest entry point, but it does not replace a full project configuration. It creates standard data and checks whether the absolute minimum for automotive messaging already exists.

Barcode service in SaaS and Universal Code

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes service-based barcode generation in SaaS and Universal Code scenarios. It shows which fields in BE-Code Setup matter and how to validate the connection so that labels and reports can generate barcodes reliably later.

Why this setup is required

In a SaaS environment there is no local barcode-font installation and no classic DLL call. To generate barcodes anyway, a web-API-based service connection is required.

In addition, this setup model has become relevant for current on-premises scenarios in the context of Microsoft’s Universal Code direction. In practice this means:

Process catalog

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This process catalog brings together the main end-to-end workflows of Automotive with direct reference to the real working pages in the solution. It helps you read the product not only by menus, but by operational process steps that can be transferred into a reliable target process.

Context

The basic configuration, master data, and global automotive parameters are described on Setup and master data.
The Overview page positions the solution inside Cross-Industry Solutions.
The cross-cutting topics Mobile processes, BE-Mobile Fusion, and legacy MDE and Electronic Sales Labels complement several of the following main processes.

Prerequisites

Customers, vendors, shippers, items, warehouse locations, and references are prepared.
The global automotive setup is fully maintained.
Number series, VDA codes, and barcode scenarios are aligned before the first test.
Mobile endpoints, scanner profiles, or ESL platform and network connectivity are prepared when these scenarios are part of the process.

How to use this catalog

Each section describes one complete work sequence from preparation to business evidence.
The named pages and actions are the real anchor points where users control the process in Automotive.
Use this catalog as a process view and jump from here into the matching detail page when you need field-level or exception-level depth.
Cross-cutting topics such as mobile or ESL complement several main processes and are therefore also deepened on dedicated topic pages.

Process Catalog

Process Receive call-offs and build automotive orders In sales, the operational process runs through Automotive Sales Order, Plausibility Check, call-off actions, and the review of released documents. +

Start in Automotive Sales Order and first review order type, order subtype, plant, unloading point, customer item no., our item no., and the contract or order reference.
Use Plausibility Check before forwarding new call-off data. Pay special attention to price finding, progress counters, date logic, and the Method Release DCO behavior.
Use Create Delivery Call Off, Create Detailled Call Off, or Create Production Synchron Call Off depending on the scenario. PAB and JIT/JIS scenarios belong only in appropriately prepared orders.
After every release, review Released Delivery Call Off, Released Detailed Call Off, and Open Detailed Call Off so that open lines, quantities, and dates remain visible.
Move the order into shipping or production only after quantities to ship, transit quantities, and special logic such as EDL or BMW JIS are business-wise plausible.

Process Control purchasing call-offs and framework orders In purchasing, Automotive Purchase Order, Delivery Call Offs, Purchase Call Off, and Purch. Det. Call Off carry the main business process. +

On Automotive Purchase Order, first maintain the mandatory basics: Order Type, our item no., vendor reference, plant, unloading point, Contract Start, Contract End, Automotive Location Code, Usage, and Shipment Sequence.
Use Release as a deliberate control point before running Create Call Off. This confirms that contract data, pricing logic, packaging reference, and location are aligned from a business perspective.
After call-off creation, open Delivery Call Offs and then Purchase Call Off to validate old and new call-off number, delivery history, delivery interval, packaging reference, TCQ Received, and release-related information.
Use Purch. Det. Call Off for questions around Forecast Horizon, Key of Critical Stock, Consumption Point, TCQ Difference, transmission data, and receipt history.
Before warehouse receipt or later posting, always review Vendor Shipment No. and Vendor Shipment Date so that inbound processing remains traceable to the supplier document.

Process Secure shipping, shipper data, and transport documents Between goods issue and outbound EDI, Sales Transport Data is the key working page for carrier, vehicle, target arrival, and shipment evidence. +

From Automotive Sales Order, first trigger the operational shipment flow, for example through warehouse-related follow-up documents or Create Warehous Outbound Request.
In Sales Transport Data, complete Shipment Load Reference No., Customer, Carrier Transfer Date, Carrier Transfer Time, Delivery Date expected, Delivery Time expected, Carrier ID, and the vehicle data.
Maintain shipping and packing costs in the Shipping/Packing Cost Sub part in a functionally understandable order. Use inserts between existing lines deliberately when additional costs should not simply be appended at the end.
Maintain Delivery EDI, Group Message No., EDI Partner No., weights, and dangerous-goods status productively only when the corresponding shipping logic is functionally approved.
Use Packaging Structure, Print Label, Post, Post and Print, and Create Transport Advice (VDA4933) only after transport case, packaging materials, and shipping documents are fully aligned.
After shipment, review the relation between order, transport, Posted Sales Shipments, and later invoice so that no gap remains in the document flow.

Process Manage loading units, empty returns, and ownership logic The core pages LE Account Keeper, LE Empties Movement, and LE Account provide the operational evidence for ownership, movements, and open balances. +

Maintain account-holder relations first on LE Account Keeper so that customer, vendor, or other partner is linked correctly to the loading-unit account.
Record and post movements through LE Empties Movement only when location, movement direction, and account holder are clear from a business perspective.
Use the print action on movement documents deliberately as operational evidence for external partners or internal reconciliation.
Review open balances and periods in LE Account so that deviations become visible before inventory or balance settlement.
Always align ownership, packaging structure, and EDI context together when loading units are part of a customer or vendor process.

Process Use Logistics Supply Chain for goods receipt, warehouse, production, and goods issue LSC is controlled operationally through LSC Setup, Quality Assurance Activity, and Production Backflush and extends classic document logic with package- and warehouse-oriented processing. +

Start with LSC Setup and verify that locations, item flags, optional quality fields, and process-relevant switches really match the intended workflow.
Use Quality Assurance Activity as the working page for controlled QA decisions inside the material flow. Separate standard cases from QA exceptions so that rework remains traceable.
Use Production Backflush only after production reference, consumption logic, item identification, and feedback behavior have been fully tested.
Before go-live, test handovers between LSC, loading-unit logic, and classic sales or purchasing documents in complete end-to-end scenarios, especially when mobile, lot, or subcontracting variants are planned.
Keep reversal and correction procedures clearly separate from standard processing so that operational ownership and audit evidence do not get mixed.

Process Run mobile warehouse, production, and inventory processes reliably Reactor/BE-Mobile Fusion or legacy MDE directly affect operational documents and therefore need clear process boundaries, setup, and testing. +

Decide first whether the mobile process will run through Reactor or BE-Mobile Fusion or through an existing legacy MDE. Without that decision, menus, devices, and responsibilities become inconsistent.
Align endpoint, company, permissions, barcode or regex logic, and the affected warehouse, production, or inventory process together.
Maintain mobile settings per process area deliberately so that goods receipt, picking, feedback, or inventory do not accidentally share the same operating paths.
Test at least one complete flow per mobile process with a real scan, posting, and proof in the web client.
In hybrid operation, users, devices, and process boundaries between the current mobile solution and legacy MDE must remain documented and controlled.

Process Secure electronic labels as an integration process Electronic Sales Labels connect Business Central, external platform logic, access points, and physical labels. Business approval and visual checks are therefore part of the process. +

First define which item, price, quantity, or status information should be displayed electronically and which data source is leading.
Set up label assignment, layout, location reference, and update triggers in a controlled pilot area before scaling wider.
Check network approvals, access points, and radio coverage not only technically but directly at the planned usage locations.
Test at least one complete change case from Business Central to the visibly updated physical label.
Define how wrong displays, delayed updates, or unassigned labels are detected and handled operationally.

Process Exchange EDI messages and protect history EDI Setup, partners, message types, and the inbound or outbound message pages form the operational chain for incoming and outgoing communication. +

Start with EDI Setup and verify number series, paths, web-service integration, partner logic, and filename rules before productive messages start running.
Maintain EDI Partner and Partner Lines so that partner identifiers, direction of communication, and technical handover model match the real setup exactly.
Use Message Types to keep the allowed functional message types and their default setup transparent.
Control inbound traffic through Inbound Messages using actions such as Import Messages, Check Message, Process Message, and Reprocess Message.
Control outbound traffic through Outbound Messages using Send Message, Update Delivery Status, Test Mode, and status review so that converter behavior remains traceable.

Process Control special flows and settlement logic reliably Porsche time-slice, pearl-chain, PUS, and credit-note or payment-advice handling follow a dedicated process pattern and should be managed as one explicit process block. +

For time-slice and pearl-chain scenarios, use explicit cut-off timing and sequence context as fixed control points.
Ensure PUS and PSA data is carried consistently from detailed call-off and order subtype through goods issue, labels, and shipment EDI.
Keep sequence release, packaging order, and shipment release synchronized so no business break appears in execution.
For credit-note and payment-advice processing, maintain a complete document chain per shipment; in particular follow the one-invoice-per-shipment rule.
Separate standard flow and special flow in training, monitoring, and incident analysis so exceptions do not blur the core process.

Process Handle deviations through workflow and event control Event Codes, Error Codes, Event Messages List, and Links make business deviations visible and connect them to the affected process. +

Maintain Event Codes and Error Codes so that function reference, escalation logic, and the business meaning of the message stay understandable for users.
Use Event Messages List as the operational work queue. The page starts with unhandled messages by default and is therefore suited for daily review and processing.
Use Links to connect events directly with orders, call-offs, or other follow-up objects so that the root cause remains attached to the affected document.
Define clearly which messages are warnings only and which ones require processing. Fields such as May Be Ignored should be used deliberately, not as a blanket setting.
Review workflow and event rules regularly so that productive messages create value instead of noise.

Result

You can place the main Automotive processes as real work sequences inside the solution.
You can see which pages and actions actually control the respective business process.
You have a reliable base for expanding training material, test cases, and detail documentation by process area.

Migration analysis: legacy help vs. new documentation

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page documents the cross-check between the legacy help portal (automotive.help.be-terna.com) and the new Automotive documentation. The goal is to make information gaps transparent and keep them actionable as a remediation backlog.

Data basis

Crawl of German-language legacy help pages.
Structure and content comparison against the current Automotive tree in this Hugo documentation.
Focus on process completeness, special scenarios, mobile execution, and screenshot evidence.

Cross-check result

Area	Legacy pages	Legacy scope (words)	New pages	New scope (words)	Initial assessment
Setup	8	9915	6	4551	Needs deeper coverage
Sales	7	9967	5	3731	Needs deeper coverage
Purchasing	5	3255	3	2044	Partial deepening needed
Workflow	3	771	2	771	Largely stable, review structure
Loading units	6	1470	4	2205	Stable to improved
LSC	24	39092	7	7007	Largest depth gap
EDI	3	3779	4	2961	Moderate depth gap
Glossary	1	633	1	647	Stable

Note: Word count is a depth indicator, not a quality verdict. The key criterion is whether process variants, exception paths, and control steps are fully documented.