Logistics Supply Chain on Product Documentation

LSC setup and master data

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

Purpose

This page describes setup and master data for Logistics Supply Chain (LSC) in Automotive. The goal is a stable process start for goods receipt, warehouse, production, goods issue, and inventory.

How this fits into standard BC

In LSC, Automotive extends standard BC with package-oriented process control. Keep this separation clear:

Standard BC controls document flow, locations, bins, production, and inventory documents.
LSC controls package status, package activities, QA targets, and package-level selection rules.

Work pages available in code

The solution provides these pages for daily operations and key users:

LSC Goods Receipt and QA

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

Purpose

This page describes the operational LSC process for goods receipt, packaging structure validation, QA control, and put-away activities. It is intended for warehouse staff and key users who perform the goods receipt process in LSC.

Goods Receipt Process Overview

The LSC goods receipt process differs from standard BC by offering a package-oriented view. The process includes:

Receive: Create or import a goods receipt document
Validate packaging: Check physical delivery against configured packaging structure
QA control: Initiate QA if required
Put-away: Book packages into warehouse locations
Track: Monitor package activities

graph LR;

%% Nodes
A["Create goods receipt"]
B["Check packaging<br/>structure"]
C{"Structure<br/>matches?"}
D["Accept structure"]
E["Adjust structure<br/>manually"]
F{"QA<br/>required?"}
G["Start QA activity"]
H["Post goods receipt"]
I["Make QA decision"]
J{"QA<br/>approved?"}
K["Return or<br/>rework"]
L["Execute put-away<br/>activities"]
M["Package available<br/>in warehouse"]

%% Flow
A -.- B
linkStyle 0 stroke:#ffffff
B ==> C
C ==>|Yes| D
C ==>|No| E
E ==> D
D ==> F
F ==>|Yes| G
F ==>|No| H
G ==> I
I ==> J
J ==>|Yes| H
J ==>|No| K
K ==> F
H ==> L
L ==> M

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

Prerequisites and Master Data

Item Master Data

Field	Description	Example
Item number	Unique identifier	1000-00001
Description	Readable item description	Steel Pipe Ø 50mm
Unit of measure	Standard measurement unit	PC (Pieces) or KG
QA required	Flag QA-relevant items	Yes / No
Packaging structure	Standard packaging for receipt	Master / Single / Pair etc.
Lot tracking required	Enable lot number tracking	Yes / No
Track expiry date	Enable shelf-life management	Yes / No

Vendor Master Data

Field	Description	Example
Vendor number	Unique vendor ID	VN-0001
Vendor name	Readable designation	Acme Raw Materials GmbH
Standard location	Standard goods receipt location	HAMBURG
Packaging specification	Vendor-specific packaging requirements	Carton 25 pieces

Warehouse Configuration

Field	Description	Example
Receipt location	Goods receipt area	HAMBURG-GR-01
QA location	QA holding area	HAMBURG-QS-01
Standard put-away location	Target location after QA	HAMBURG-01-01-01

Step-by-Step Goods Receipt Process

Step 1: Create or Import Goods Receipt Document

Navigate to Logistics Supply Chain Setup > Purchase > Purchase Orders.
Click New.
Fill in:
- Vendor number: Select from dropdown
- PO number: Reference to purchase order
- Packing slip number: Vendor’s document number
- Location code: Standard location is suggested
- Receipt date: Actual arrival date
Click Save.

Step 2: Validate Packaging Structure

After document creation, packaging structures are automatically proposed.

LSC warehouse and package management

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

Purpose

This page describes operational warehouse control in LSC with focus on package management and package-based movement activities.

Core principle

In LSC warehouse processing, not only quantities but concrete package units with status, content, and location are controlled.

Package management

Typical operational actions:

create empty package,
repack package content,
change assignment,
correct fill quantity,
assign RFLT-ID.

Business rules

Repacking only with business-compatible content.
Structure changes only with plausible target hierarchy.
If cause-code requirement is active, cause code must be captured.

Package activities

Activities control the physical process between source and destination.

LSC production and output feedback

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

Purpose

This page describes the production-related LSC process from component staging to structured output reporting.

Component staging

The staging process controls which package units are made available for production.

Key points:

filter by production order or staging location,
define required quantity from business perspective,
create staging activities,
monitor coverage status actively.

Production output feedback

Operational feedback is processed through Production Backflush.

Typical flow:

Select production order and line.
Validate alternative packaging structure.
Maintain Number of Singles and Output Quantity.
Set Lot No. where lot logic is mandatory.

graph LR;

%% Nodes
A["Create production<br/>order"]
B["Plan component<br/>staging"]
C["Load staging<br/>location"]
D["Release packages<br/>to production"]
E["Consume components<br/>physically"]
F["Run production"]
G["Prepare output<br/>feedback"]
H["Run Production<br/>Backflush"]
I{"Packaging<br/>required?"}
J["Pack output as<br/>handling unit"]
K["Complete output<br/>posting"]
L["Finished packages<br/>available"]

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

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

Finish feedback through Register/Finish actions.

Packaging-structure and quantity rules

Single/master logic must match active structure.
Partial quantities must be transferred consistently into package hierarchy.
Resulting activity depends on QA requirement and target process.

Component consumption

Depending on setup, consumption follows FEFO/FIFO or allocation sequence. Blocked packages must not distort consumption behavior.

LSC goods issue and picking

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

Purpose

This page describes LSC logic for goods issue, warehouse picking, package selection, and shipping-relevant checks.

Process flow

Create shipment document.
Create warehouse pick.
Build shipping packaging structure.
Create and register package activities.
Post final shipment.

graph LR;

%% Nodes
A["Take over<br/>customer order"]
B["Create warehouse<br/>pick"]
C["Generate FIFO/FEFO<br/>proposal"]
D{"Manual adjustment<br/>needed?"}
E["Adjust pick<br/>lines"]
F["Remove packages<br/>from warehouse"]
G["Packages<br/>picked"]
H["Build shipping<br/>packaging structure"]
I{"Customer checks<br/>required?"}
J["Check labels,<br/>RFID/barcode, weight"]
K["Post shipment"]
L["Hand over to<br/>carrier"]

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

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

FIFO/FEFO and tolerance control

Proposal logic prioritizes package units based on setup.

LSC inventory and special scenarios

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

Purpose

This page describes inventory processes and special operational scenarios within LSC.

Lot and expiration process

graph LR;

%% Nodes
S(["Lot and expiration process"])
subgraph Eingang["Goods receipt and QA"]
  direction TB
  A["Supplier sends material<br/>with lot and expiry"]
  B["Goods receipt checks<br/>lot and expiry"]
  C{"Lot<br/>readable?"}
  D["Enter lot and expiry<br/>into the system"]
  E["Document QA<br/>deviation"]
  F["Contact supplier<br/>or initiate return"]
end
subgraph Versand["Warehouse, shipping, and traceability"]
  direction TB
  G["Material available<br/>in warehouse with lot"]
  H["Select package by FEFO<br/>and expiry date"]
  I["Post shipment with<br/>lot and expiry data"]
  J["Trace lot for<br/>customer complaint"]
end

%% Flow
S ==> A
A ==> B
B ==> C
C ==>|Yes| D
C ==>|No| E
E ==> F
D ==> G
G ==> H
H ==> I
I ==> J
%% Classes
class S btProcessTitle
class A btProcessExternal
class B,C,D,E,F,G,H,I,J btProcessActive

Mobile operations

Subcontracting

In subcontracting, material dispatch and return flow must be integrated into regular LSC processing. The process chain must be modeled clearly in operational and posting logic.