Sales on Product Documentation

Sales and call-off processing

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

Purpose

This page describes the actual operational sales flow in Automotive based on the real pages and actions available in the application. It shows how to prepare automotive orders, validate delivery and detailed call-offs, steer shipping and transport, and complete the document flow through invoicing and traceability.

Business value

You work with the real sales and transport pages instead of an abstract process model.
You see early which header fields on the automotive order drive later call-off, shipping, and pricing errors.
You can distinguish LAB, FAB, and PAB scenarios and use the correct action for each one.
You connect order, open call-off lines, warehouse processing, transport data, EDI, and invoicing in one traceable chain.

Prerequisites

The global automotive setup is complete.
Customers, ship-to addresses, plants, item references, and price units exist for the relevant customers.
Carriers, transport identifiers, shipping control, and where needed loading-unit logic are configured.
EDI, barcode, and label scenarios have been tested before the first live process.

Key working pages in daily operations

Page	What you use it for	Typical decision
Automotive Sales Orders	Overview of call-off-driven orders, ownership, location, and status	Which order must be checked, released, or shipped today?
Automotive Sales Order	Central maintenance of header fields, call-off control, transit handling, and EDL fields	Do order type, plant, unloading point, and pricing logic still fit?
Plausibility Check	View of warnings and blocks before release	Can the call-off be released from a business perspective?
Released Delivery and Detailed Call Offs	Review of the last released LAB and FAB documents	Was the call-off imported fully and correctly?
Open Detailed Call Off Lines	Operational view of open JIT, JIS, and detailed call-off lines	Which lines still need shipping or sequence handling?
Sales Transport Data	Entry of carrier, expected arrival, shipping evidence, EDI, and labels	Is transport data complete before posting?

Process overview

graph LR;

%% Nodes
A[Inbound LAB or FAB or PAB]
B[Prepare automotive order]
C[Plausibility check]
D[Create or reread call-off]
E[Control open lines and transit]
F[Prepare warehouse and shipping]
G[Capture and post transport data]
H[Invoice or reinvoice]
I[History, warnings, and audit trail]

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

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

How this fits into standard Business Central

In sales, Automotive does not replace the normal Business Central document flow. It extends standard sales processing with automotive call-off and transport logic. For end users, it is therefore important to separate two views clearly:

Shipping control and sales planning

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

Purpose

This page deepens the sales-planning area around shipping control. It describes the operational path used in Automotive to build shipments from open sales-order lines, prepare mixed pallets, and control quantity deviations consciously.

When shipping control is the right tool

Shipping control is the intended standard path for shipping in Automotive. Quantities can also be shipped directly from the sales order, but that route is much weaker for complex shipment patterns. Mixed pallets or consciously grouped shipment scenarios are handled much better through shipping control.

Periodic activities in sales

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

Purpose

This page describes the recurring sales activities that must be handled routinely in daily operations. It complements the sales overview with the concrete reports, checks, and exception handling from the legacy wiki documentation.

Typical work rhythm

Review imported delivery, detailed, or production-synchronous call-offs.
Approve open call-offs in a controlled batch.
Register detailed and production-synchronous call-offs.
Update material-release and production-release dates on a rolling basis.
Execute cancellations according to the real shipping model.

Approve delivery and detailed call-offs

The batch report for delivery and detailed call-offs is the central approval point for still-open call-offs. Without filters, all releasable records are processed. In practice, you should still filter deliberately, for example by customer, plant, ship-to, or order.

Reporting, labels, and history

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

Purpose

This page extends the sales process with reports, reprints, and historical control views. It describes how to reprint goods labels, which archive objects matter in daily work, and how the navigator shows gaps between shipment, transport, and EDI output.

Reports and reprints

In sales, you have not only standard BC reports, but also automotive-specific reprints and evaluation views. The important point is not only the print itself, but the right business reason for using it.

BMW JIS5000 sequence process

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

Purpose

This page describes the BMW JIS5000 sequence process in Automotive. It focuses on the steps that differ from a normal sales process: base setup, PAB order creation, EDI configuration, release of JIS messages, sequence control, and sequence-based loading-unit assignment.

1. Prepare the base setup

BMW uses a GLT number on the master label. The highest already used number must be maintained in Automotive Setup. If the field is not visible, it must be added through personalization.