This page explains Default Shipping Points for consultants and prototype builders defining outbound behaviour in In-House Secure’s FIT 4 SAP environment. In short, a default shipping point is SAP’s “starting assumption” for where a sales order intends to ship from. It matters because delivery creation relies on this assignment to route workload to the right warehouse. Use it when you want predictable sales order behaviour. Avoid ignoring it unless you enjoy error messages, misrouted stock, and a warehouse team politely asking why you hate them.

</aside>

A reasoning page that explains the business purpose of assigning default shipping points and why SAP insists on having one set before it will build deliveries with any confidence.

The Principle

SAP hates ambiguity. A sales order without a shipping point is like a parcel with no return address. Someone has to guess, and guessing is how disasters begin. Default Shipping Points give SAP a polite head start: a baseline warehouse to use unless more specific logic overrides it.

Jargon Busting (WHAT section)

Shipping Point

The physical or logical location where outbound activities occur. Think “dispatch desk with forklifts”.

Default Shipping Point

SAP’s predetermined assumption when it cannot determine a more specific answer during sales order creation.

Shipping Point Determination

The process SAP uses to derive the correct shipping point based on Shipping Condition, Loading Group, and Plant.

Sales Area

The commercial context: Sales Org + Distribution Channel + Division. SAP uses this as part of the fallback logic.

WHEN it becomes critical

Default shipping points matter the moment a sales order is saved. That first save triggers delivery scheduling and ATP logic. When SAP cannot determine a shipping point from the item’s own data, it consults ovl2.

When ovl2 has valid entries