The value assigned here to the warehouse number can then be used in field T321-MAILK to ensure that an express mail is sent to the user if automatic TO creation fails.ĭetermining the WM movement type used in configuration through debug Flag either "Document user" or add a specific user name.Add a value for mail alert, for example '01'.In this table (T333M) the following entries should be added:
![sap movement type 321 sap movement type 321](https://image.slidesharecdn.com/allmovementtypesinsap-121126134204-phpapp02/95/all-movement-types-in-sap-1-638.jpg)
TO Creation for TRs / Posting Change Notices -> Mail Messages – Assign Recipient SPRO -> Logistics Execution -> Warehouse Management -> Activities -> Transfers -> Set up Autom. The customising menu path for mail alerts is as follows: Once the mail alert customising is in place, it can be assigned directly into table T321 (see above customising). Mail alerts should be configured if automatic TO creation is used. The user can then branch directly to the TO creation and carry out foreground processing. If mail alert is correctly set up, then the document creator / specified user will get an express mail stating that the TO creation failed. If automatic TO creation is set, it is important to note that mail alerts should also be configured. If a TO is to be created in foreground, field T321-TAFKZ should be set to ‘X’ while if it should be background processing, this should be set to ‘A’. If TR’s or PCN’s should be created immediately, their corresponding field should be set to ‘X’.
![sap movement type 321 sap movement type 321](https://trydale.com/wp-content/uploads/2021/02/Trydale-01.jpg)
The table view appears as in the below diagram: Transfer posting (WM movement type reference) – field T156S-UMRBUĪlso, new table entries cannot be added directly into this table.Stock transfer (WM movement type reference) – field T156S-UMRBL.Reference movement type – field T156S-RBLVS.Only the following entries can be modified:
Sap movement type 321 update#
the IM movements, value update, quantity update settings, etc. The entries in table T156S are not changeable – i.e. SPRO -> Logistics Execution -> Warehouse Management -> Interfaces -> Inventory Management -> Define Movement Types -> Assign WM Movement Type References to IM Movement types
![sap movement type 321 sap movement type 321](https://wiki.scn.sap.com/wiki/download/attachments/403571018/IM-WM_pic2.jpg)
In WM customising, a reference movement type is created and is assigned to an IM movement. Adding a Reference WM movement type to an IM movement
Sap movement type 321 how to#
This document will outline a procedure firstly on how to configure the reference and WM movement types and secondly, how to find the WM movement type that is selected, without having to review configuration settings directly. However, despite setting up the configuration in customising, TO’s are created with the "wrong" movement type.
![sap movement type 321 sap movement type 321](https://image.slidesharecdn.com/allmovementtypesinsap-121126134204-phpapp02/95/all-movement-types-in-sap-5-638.jpg)
These are in turn linked to inventory management (IM) movements. The WM movement type is configured in customising in relation to reference WM movement types. The purpose of this document is to clarify how to configure and subsequently find the warehouse management (WM) movement type that is used for transfer order (TO) creation.