Setup wizard and parameter tabs

Detailed field and tab guide for the Automotive Setup Wizard, Automotive Setup, and SaaS barcode parameters in Automotive.

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.

The key minimum checks before finishing the wizard are:

at least one country with country-of-origin and preference logic
at least one unit of measure with a VDA unit-of-measure code
at least one currency with a VDA ISO code

If one of these points is missing, later message and document logic may look complete but still fail during call-off import, delivery-note EDI, or invoice output.

Parameter tabs in Automotive Setup

General tab

Field or topic	What it is used for	What to validate
Our plant no.	Identifies your plant in documents and messages	Is the number aligned with customers, vendors, and EDI?
D-U-N-S number	Supports partner identification	Is the value maintained consistently across the project?
Currency VDA ISO key	Transfers industry-specific currency codes	Are all productive currencies completed?
Messages if no event control	Controls whether business hints are shown without workflow control	Do you want only hard workflow cases or also simple user messages?
Check duplicate item cross reference	Helps detect duplicate or unclear references	Are there duplicate legacy references in master data?

Sales tab

Field or topic	Business effect	Typical error pattern
Automotive sales order number series	Numbers the call-off-driven sales documents	Call-offs cannot be traced cleanly
Transport number series	Controls transport documents; must be numeric and no longer than eight digits	Shipping starts, but transport numbering fails
Keep sales order status	Restores the previous status after posting	Status handling becomes inconsistent after shipment or invoicing
Consignment based on item	Inherits consignment logic from the item instead of the customer	Wrong consignment behavior in daily work
Post EDL/Consi invoice	Supports automatic invoicing in consignment scenarios	Invoicing does not fit the physical process
Check account keeper	Forces a loading-equipment responsibility check	Loading-unit movements cannot be reconciled correctly
Price unit	Default value for VDA pricing logic	Price calculation does not match the customer agreement
Only post lines with quantity	Prevents follow-up errors caused by zero-quantity lines	Documents are processed with empty or irrelevant lines

Purchasing tab

Field or topic	Business effect	Typical error pattern
Post shipment EDI	Automates inbound posting from supplier delivery-note data	Posting starts although warehouse or quality logic is not ready
Keep purchase order status	Keeps the business status stable after posting	The framework order loses the expected operational status
Only post purchase lines with quantity	Avoids empty movement or receipt lines	Goods receipt or invoice runs on technically present, but business-empty lines

Documents, labels, and output

Field or topic	Decision	Meaning for users
Direct label print	Print immediately to a device	Suitable only when printer routing and service setup are fully tested
Save labels as attachment	Store the PDF as a document attachment	More robust for evidence, repeat printing, and cloud scenarios

For many projects, PDF storage is the safer go-live option because it makes print problems visible without losing document content.

SaaS and barcode specifics

The legacy wiki still separates classic file-path setups from current cloud scenarios. For current projects, the main points are:

barcode and label processes do not rely on local print logic alone, but on the intended service architecture
file-based EDI paths are still possible for special on-premises cases, but no longer the standard approach
PDF storage, web interfaces, or Azure File Share are more robust in SaaS projects than local custom workarounds

Before go-live, always answer these questions:

Is the barcode service app installed and technically reachable?
Is it clear for each document type whether it should print immediately or be stored as PDF first?
Has at least one complete end-to-end test from order or call-off to label, delivery note, and archive been executed?

Project checklist before go-live

Check area	Expected result
Countries, currencies, and units	VDA-related fields are complete
Number series	assigned for orders, transports, and EDI
Sales and purchasing options	enabled only where the business process actually needs them
EDI transmission type	consistent globally and per partner
Barcode and labels	confirmed by a real print or PDF test
Master-data linkage	items, partners, locations, and references fully connected