SAP Knowledge Base Article - Public

3067316 - Shipping Point in delivery created from post goods movement (MIGO)

Symptom

When creating a transfer posting to a 3rd party distributed storage location via the Post Goods Movement APP (MIGO).
The system generates an outbound delivery instead of a material document directly.  The outbound delivery is created in 
a shipping point that is unexpected. 

Environment

SAP S/4Hana Cloud - All Versions 

Reproducing the Issue

1) Go to the APP Post Goods Movement (MIGO) 
2) Choose transfer posting and movement type 311. 
3) Enter in the mandatory fields and a 3rd party receiving storage location.
4) Press Post 

Cause

Standard system behaviour.
The system can default the shipping point from the plant storage location combination or from the plant itself.
It will firstly try to pick up the shipping point from the plant storage location (T001L) and if nothing is found it will default the shipping point from the plant (T001W)    

Resolution

If you do not want the default shipping point of the plant to be assigned you can maintain the customising for the
plant/Sloc combination via the SSCUI 500122 - Define Shipping Data for Stock Transfers Between Storage Locations (180019) 

See Also

LE_MOVEMENT_DATA_DETERMINE_TAB, T001L, T001W, DETERMINE_ORG_DATA, MM07MLVS, VERSANDSTELLE, V_T001L_L_MM, MB_DELIV_MM, LLE_MOVU01, IF_SELECT_T001W, IF_SELECT_T001L, ls_lemovdat_source, komdlgn-vstel
likp-vstel

Keywords

KBA , MM-IM-GR-MIGO , Goods Receipt from External Procurement (MIGO) , LE-SHP-DL , Delivery Processing , Problem

Product

SAP S/4HANA Cloud all versions