Analytics Catalog/SAP S/4HANA/Materials Management/Stock transfers
Explore the catalogModulesMaterials ManagementMovement typesSpecial stocks
SAP S/4HANA · Materials Management · Report

Stock between two places

A transfer is two events pretending to be one. May’s 29 transfer documents moved 460 units through four named routes, and the page’s real subject is the in-between state: the stock that is briefly nowhere, and who owns it while it is.

RulePost transfers two-step so transit exists, and age the in-transfer quantity daily, because stock between two places belongs to nobody by default.
Neverlet one-step transfers hide the journey. Stock that teleports cannot lose anything in the corridor, on paper.
29 transfers in May 460 units moved Four routes, named quality, returns, back Aged while between transit owned daily
A transfer is two events pretending to be one. The gap between them is where units go quiet.
◆ May transfers, by routethe 311 row, opened.
RouteDocumentsUnits
Raw store into quality hold9140
Quality hold released to raw8120
Finished goods into returns7130
Returns recovered to finished570
Transfers, May29460

These are the movement partition’s 311 row, opened by route: plant-level nothing, location-level everything. The quality loop and the returns loop each tell a process story the single 460 hides. Sample values are illustrative, never client data.

◆ Stock that teleportsthe one-step shortcut.

A one-step transfer moves stock instantly between locations, so transit never exists and nothing can age there. Convenient, and blinding: the corridor, the truck, and the handover disappear from the record. Two-step posting creates the in-between state that can then be owned and counted.

◆ The leftover nobody ownsissued, never received.

Two-step transfers leave an in-transfer quantity whenever the issue posts and the receipt does not. The delivered views list it without an age, and practitioners report month-old leftovers surfacing only at count time. Aging the in-between daily gives every stranded unit a clock and an owner.

Use case
Problem
Transfers post one-step for convenience, in-transfer quantities sit unaged for weeks, and corridor losses surface as count differences nobody can place.
What we build
Two-step routes landed with both events, the in-between aged daily with owners, and route-level views of the quality and returns loops.
What you get
A transfer record with no quiet places: transit that exists, leftovers with clocks, and count differences that stop absorbing corridor losses.
How old is your oldest in-transfer quantity?
We build the aged transit view that answers daily.
Talk to us
Terms on this page
SAP
The vendor. Systems, Applications, and Products in data processing.
HANA
SAP’s in-memory database, the platform S/4 runs on.
MM
Materials Management, the purchasing and inventory module.
311
The location-to-location transfer movement type.
one-step transfer
Instant move; transit never exists in the record.
two-step transfer
Issue then receipt; the in-between is real and countable.
in-transfer quantity
Issued, not yet received; the stranded state to age.