Setup and master data
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:
- Standard BC view for countries, units, currencies, number series, items, customers, vendors, shippers, and warehouse locations as the functional base.
- Automotive view for the Automotive Setup Wizard, Automotive Setup, EDI Setup, VDA fields, transport numbers, packaging structure, and optional LSC or loading-unit logic.
| Standard BC object | Extension in Automotive | Why this matters to users |
|---|---|---|
| Countries or regions, units of measure, and currencies | VDA country of origin, trade preference, VDA unit-of-measure code, and VDA ISO key | Without this base data, the setup wizard cannot be completed cleanly. |
| Items, customers, vendors, shippers, and warehouse locations | Automotive fields for references, plant, unloading point, EDL/Consi, packaging logic, and transport | The master data remains standard BC master data, but is later enriched with industry-specific mandatory values. |
| Number series | Numbering for automotive orders, transports, and inbound or outbound EDI messages | Clean numbering is a prerequisite for traceability and document flow. |
| Assisted Setup in BC | Automotive Setup Wizard | The wizard is the guided entry point into Automotive setup, but it does not replace the maintenance of the actual master data. |
| Warehouse locations, journal templates, and batches | Logistics SMART, LSC, automatic EDI posting, and barcode-related processes | Without the right warehouse and posting base, later follow-up processes may start, but will not run reliably. |
graph LR; %% Nodes A[BC master data] B[Automotive Setup Wizard] C[Automotive Setup] D[EDI Setup] E[Items partners and locations] F[Sales purchasing LE and LSC processes] %% Flow A -.- B linkStyle 0 stroke:#ffffff B ==> C B ==> D C ==> E D ==> E E ==> F %% Classes class A btProcessTitle class B,C,D,E,F btProcessActive
Keep this in mind in daily work: if mandatory values are already missing in the BC base master data, later automotive setup will not solve that problem.
Recommended Implementation Sequence
graph LR; %% Nodes A[Check product base and dependencies] B[Run the Automotive Setup Wizard] C[Complete mandatory country unit and currency data] D[Maintain Automotive Setup] E[Complete EDI Setup] F[Maintain items partners and packaging logic] G[Enable LSC or Logistics SMART only if needed] H[Finish barcode printing and go-live checks] %% Flow A -.- B linkStyle 0 stroke:#ffffff B ==> C C ==> D D ==> E E ==> F F ==> G G ==> H %% Classes class A btProcessTitle class B,C,D,E,F,G,H btProcessActive
1. Check the Product Base and App Dependencies
First verify that the correct BC version, the Automotive app, and its dependent apps are active. The current code refers in particular to BE-terna Barcode Service, the Reactor platform core, and further technical components. In practice this means one thing above all: barcode and label scenarios are part of the planned cloud setup, not a later add-on.
2. Run the Automotive Setup Wizard First
The code provides an Automotive Setup Wizard as an assisted setup. This wizard is registered in Guided Experience and is intended for typical roles such as Business Manager, Accountant, and Order Processor.
The wizard performs three important initial steps automatically:
- It initializes the automotive base data.
- It creates the EDI base data.
- It creates a default object for a pseudo loading-equipment scenario.
In addition, the wizard enforces three business minimum checks before you can finish cleanly:
- at least one country or region with VDA country of origin and trade preference
- at least one unit of measure with VDA unit-of-measure code
- at least one currency with VDA ISO key
Run this step deliberately early. If these minimum values are missing, later setup can still be maintained in parts, but not used reliably.
3. Prepare Base Master Data
Create items, customers, vendors, shippers, warehouse locations, countries, units, and delivery terms before you maintain automotive-specific settings. Many automotive fields depend directly on this master data and cannot otherwise be maintained completely or correctly.
Complete in particular the values that the setup wizard later checks explicitly:
- countries or regions with country-of-origin and preference logic
- units of measure with VDA UoM code
- currencies with VDA ISO key
4. Maintain the Central Automotive Setup
The Automotive Setup page controls the global base parameters of the solution. The following topics are especially important:
| Area | Field or topic | Meaning |
|---|---|---|
| General | Our plant no. | Identifies your plant in the automotive context. The value is reused in downstream messages and documents. |
| General | D-U-N-S number | Important for partner identification in message exchange. |
| General | Currency VDA ISO key | Controls industry-specific currency representation in documents and EDI. |
| General | Messages if no event control | Defines whether messages without event control are logged and shown as simple user messages. |
| General | Check duplicate item cross reference | Helps detect faulty or duplicate item references early. |
| Sales | Sales order no. series | Assigns numbers for automotive sales orders. |
| Sales | Transport number series | Must be numeric and can contain no more than eight digits. This restriction is validated directly in code. |
| Sales | Keep sales order status | Important if you work without a classical goods-issue step and want the previous status restored after posting. |
| Sales | Consignment based on item | Controls whether the EDL/Consi flag is inherited from the item instead of the customer. |
| Sales | Post EDL/Consi invoice | Allows automatic invoicing in consignment scenarios, but only with matching shipment logic. |
| Sales | Check account keeper | Forces a loading-equipment account-keeper check before posting. |
| Sales | Price unit | Default value for the VDA price unit on items and price lines. |
| Sales | Check lines to be posted | Restricts posting in call-off orders to lines with quantity greater than zero. |
| Purchasing | Post shipment EDI | Automates goods receipt from inbound EDI delivery notes. Only enable this with matching warehouse logic. |
| Purchasing | Keep purchase order status | Resets the purchase order status after posting to the previous state. |
| Purchasing | Only post purchase lines with quantity | Prevents follow-up errors caused by empty movement lines. |
| Label print | Direct print or save labels as attachment | Controls whether labels are printed immediately or stored as PDF document attachments. |
5. Complete EDI Setup
In the current code, EDI Setup is not a side topic. It is a separate central setup block. Here you define, among other things:
| Area | Field or topic | Meaning |
|---|---|---|
| General | Interface is active | Enables the EDI interface from a business perspective. |
| General | Default transmission type | In the current cloud build, Web Interface and Azure File Share are the relevant standard options. |
| General | Archive messages and archive grouping | Defines whether and how messages are archived technically. |
| No. series | Partner number series plus inbound and outbound message number series | Mandatory basis for unique processing and traceability. |
| Import | Inbound message error handling and maximum processing attempts | Controls retry and abort behavior for failed files or messages. |
| Web service | Provider, URL, timeout, user, password, app key, company ID | Relevant basis for integrations such as Ecosio or similar platforms. |
| Azure File Share | Account, access key, inbound, outbound, and archive URLs | Required when message exchange runs through Azure file shares. |
Do not maintain EDI setup in isolation. It connects directly to number series, partner parameters, and later operational message processing.
6. Plan Additional Setup Pages by Scenario
Besides Automotive Setup and EDI Setup, the code shows further dedicated setup pages that should be activated consciously depending on the project scope:
| Setup page | When relevant | Purpose |
|---|---|---|
| Logistics SMART Setup | for mobile or SMART-driven warehouse processes | Activates Logistics SMART and stores the journal templates and batches for reclassification, output, and adjustments. |
| Logistics Supply Chain Setup | for LSC processes in warehouse, production, receipt, shipment, or inventory | Enables LSC and controls number series, pick logic, production posting, receipt behavior, and physical-inventory settings. |
| Pack Structure Setup | for packaging hierarchies, KLT logic, or label scenarios | Defines packaging-structure rules used by sales, warehouse, and LSC. |
| Dispatch Control Setup | for active dispatch control | Controls filters and standard behavior for dispatch releases. |
| Warehouse Receipt Control Setup | for controlled warehouse receipt | Extends warehouse-receipt checks with project-specific rules. |
| Key Setup | for maintaining or extending automotive keys | Maintains key values for shipping, processes, usage codes, price logic, and references. |
7. Complete Items, References, and Packaging Logic
Maintain the automotive-specific fields on all relevant items. This includes price unit, weights, country of origin, reference numbers, and, where required, loading-unit characteristics. For loading-unit items, also maintain packaging type, dimensions, stacking factor, identifiers, and packaging structure.
The following master data is especially important for operational use:
- VDA price unit on the item because it drives the pricing logic for automotive documents.
- Automotive reference no. so that customer-specific or vendor-specific numbers can be processed reliably.
- Packaging structure with single, master, and accessory logic so that labels, fill quantities, and reservations stay consistent.
- Loading-unit attributes such as dimensions, stacking factor, and ownership logic when loading-unit accounts or empty-return processes are used.
8. Add Customer, Vendor, and Shipper Data
Then maintain the partner-specific automotive data.
For customers, the following information is especially relevant:
- delivery call-off release method
- EDL/Consi activation
- D-U-N-S number and partner identifiers
- ship-to addresses with plant, unloading point, and if needed warehouse logic
- account-holder rules for loading units when ownership does not remain with the customer
For vendors, maintain in particular:
- automatic generation or processing of call-off data
- delivery interval definitions
- purchase-price date logic
- rules for immediate demand and special cases
For shippers, maintain in particular:
- SCAC code or comparable partner identifiers
- means of transport and transport-related VDA codes
- freight classification and related shipping indicators
- customer-specific references
9. Enable Warehouse, Logistics SMART, and Logistics Supply Chain
If you use warehouse or consignment scenarios, configure warehouse locations, transfer routes, and available-quantity filters. For EDL/Consi, you need a clear definition of which locations count as external warehouses and how transfers between the standard warehouse and consignment warehouse are controlled.
For Logistics SMART, the setup page requires in particular:
- activation of Logistics SMART
- journal template and batch for SMART reclassification
- journal template and batch for SMART output
- journal template and batch for item adjustment
- internal label definition for mobile or internal identification
For Logistics Supply Chain, the following fields are especially relevant from a business perspective:
- enable Logistics Supply Chain
- number series for packages and packaging activities
- sorting method and date range for warehouse picking
- journal template and batch for production backflush
- settings for routing posting, mandatory location, and packaging-structure check during output
- rules for receipt with EDI, receipt without file, package checks, and reuse of vendor labels
- physical-inventory rules such as quantity prefilling, confirmation requirement, and multiple recording
If mobile data entry is used, also configure transport types and function groups. Without this assignment, mobile transport processes are not fully usable.
10. Test Barcode and Printing Scenarios
In the current cloud product state, a working barcode service is required. Use productive credentials only from an approved project context and document test and production environments separately. Also verify whether the intended label layouts, direct-print options, and PDF attachments really fit your operational process.
Deepen Cross-Cutting Topics Deliberately
Not every project-critical setup topic is described completely on this page. For three cross-cutting areas, you should deliberately continue into the dedicated detail page:
- Pack structure management, when pack-structure definition, item assignment, alternatives, and registration per process need to be prepared cleanly.
- Mobile processes, BE-Mobile Fusion, and legacy MDE, when scanner processes, device profiles, endpoints, or hybrid operation with legacy MDE are part of the project.
- Electronic Sales Labels, when label platform, access points, radio coverage, and the release of electronic displays must be planned as part of the setup.
Required Master Data by Object Type
| Object type | Key required values |
|---|---|
| Item | Price unit, automotive reference no., weights, country of origin, and where needed loading-unit flags |
| Loading-unit item | Packaging type, dimensions, stacking factor, ownership logic, packaging structure |
| Customer | Call-off release, plant and unloading point in ship-to addresses, EDL/Consi flags where needed |
| Vendor | Delivery interval, price-date logic, call-off or EDI-related options |
| Shipper | SCAC code, freight classification, means of transport, further shipping indicators |
| Warehouse location | EDL/Consi flag, warehouse filter, transfer relation |
Special Cases and Variants
EDL and Consignment Warehouses
If you use external warehouses or consignment scenarios, warehouse location, customer, item, and transfer route must align. An activated EDL/Consi scenario without a clean warehouse reference quickly leads to posting errors or unintended default behavior.
Q-Status and Engineering Change Levels
Enable Q-status early only if the process is actually required from a business perspective. Q-status affects variants, release statuses, engineering levels, and potentially whether an item may only be shipped or also produced.
Price Scaling Through the Price Unit
If prices are not maintained per single unit but, for example, per 100 or 1,000 units, the correct VDA price unit on the item is mandatory. Errors at this point directly affect quotation, order, and billing logic.
SaaS Barcode Generation
In the current product state, barcode generation in cloud operation is not handled locally through fonts. Plan the service connection early and test printing, label layout, and response times before go-live.
Control Steps Before Go-Live
Check the setup at least against these points:
- The Automotive Setup Wizard has been completed successfully.
- At least one country or region contains VDA country of origin and trade preference.
- At least one unit of measure contains a VDA unit-of-measure code.
- At least one currency contains a VDA ISO key.
- The global automotive setup is fully maintained.
- The transport number series is numeric and no longer than eight digits.
- EDI setup contains the required number series for partners and inbound and outbound messages.
- All relevant items have the correct price unit and automotive reference.
- Packaging structures and ownership logic are complete for loading-unit items.
- Customers and ship-to addresses contain plant, unloading point, and where needed EDL/Consi logic.
- Shippers contain the required VDA and transport identifiers.
- Optional scenarios such as Q-status, EDL/Consi, MDE, Logistics SMART, or LSC are intentionally enabled and tested.
- Barcode printing, label layouts, and where relevant PDF attachments have been tested successfully.
Typical Failure Patterns
| Situation | Possible cause | Check |
|---|---|---|
| The setup wizard cannot be completed cleanly | Mandatory values for country, unit, or currency are missing | Check VDA fields on country or region, unit of measure, and currency |
| Call-offs behave unexpectedly | Wrong delivery call-off release method | Compare customer settings with global call-off parameters |
| Prices seem too high or too low | Wrong price unit on the item | Check item card and VDA price unit |
| Automatic goods receipt posts incorrectly | EDI auto-posting enabled without matching warehouse logic | Check warehouse requirements and purchasing parameters |
| Loading units cannot be posted consistently | Missing account-holder or packaging-structure data | Check loading-unit item, account holder, and packaging structure |
| EDI messages do not start cleanly | Number series or web-service or Azure settings are incomplete | Check EDI setup for number series, provider, and URLs |
| Barcode output fails | Barcode service or layout assignment is not working | Test service connection, label layout, and print setting |
Migration checklist from legacy help
When migrating from older BE-Automotive content to this structure, track at least the following points per project:
| Checkpoint | Target state | Evidence |
|---|---|---|
| Register depth in Automotive Setup | Every used register is not only listed, but explained field by field from a business perspective. | Short field-impact list per register |
| Subcontracting setup | Location split, transfer routes, work plans, and pricing logic are fully documented. | End-to-end test case run |
| Label and print control | Printer selection, direct print, attachment storage, and fallback paths are documented. | Screenshot sequence with print result |
| EDL/consignment base | External locations, transit rules, and partner references are unambiguous. | Cross-check in receipt and shipment |
| Go-live check | Mandatory values and number series are validated for all productive scenarios. | Signed-off go-live checklist |
This checklist complements the running setup activities and reduces the risk that legacy detail rules are lost during migration.
Result
- You have defined the central setup sequence for Automotive.
- You know which master data, setup pages, and mandatory checks must be complete before the first operational use.
- You can deliberately include or defer special cases such as EDL/Consi, Q-status, Logistics SMART, LSC, and barcode service.
Links