LSC inventory and special scenarios

LSC inventory processes and special scenarios such as lot and expiration handling, mobile operations, subcontracting, and reversal flows.

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.

Reversal and rollback

LSC reversals affect quantities, status, activities, and potentially lot assignment.

Before reversal, verify:

downstream documents already processed,
dependent activities completed,
rollback is still possible at the same process stage.

Checkpoints

start inventory only with cleaned activity state,
no open mandatory checks in special scenarios,
run reversals only after full impact validation.