Some time ago, I posted the article "Summary of STO Inventory Dump" written by Xiaospider, but I haven't posted a test example. The article was written 4 years ago, and I just dug it out of the draft box today.
Article directory navigation
一、Plant to plant 1 step
Under the same company, the material TEST00981 is transferred between factories, from factory 8700 to factory 8702 in one step
MvT:301
T_CODE:MIGO
Material voucher generated by posting: 4907362859, MB51 Check the material voucher, you can see that the material has been transferred from 8700 factory to 8702 factory for 5 sets, but the inventory amount of 8700 factory has decreased by 50 yuan, while the inventory amount of 8702 factory has increased by 60 yuan, and there are 10 meta difference.
Double-click the accounting document to view:
Generate inventory variance analysis:
MM03 View the material master data of this material, accounting view 1, select 8700 and 8702 respectively for the organization: you
can see that the standard price of the material in factory 8700 and factory 8702 is 10 yuan and 12 yuan respectively, and the difference is 2 yuan. Transfer 5 pieces of this material from factory 8700 to factory 8702, there is a difference of 2*5=10 yuan. This difference will be recorded in the difference subject, which is determined by the enterprise itself.
二、Plant to plant 2 steps
Under the same company, the material TEST00981 is transferred between factories, from factory 8700 to factory 8702 in one step
MvT: 303 sent, 305 received
T_CODE:MIGO
MvT: 303 Issue material, generate material certificate: 4907362861
Check the corresponding accounting documents:
There seems to be no difference between the accounting documents and 301 one-step transfer. However, MMBE checks the inventory: there is a dumped quantity of 3
T_CODE:MB5T in the inventory transfer, and there is no in-transit inventory. The material does not belong to the category of in-transit inventory that can be viewed by MB5T (the transaction code MB5T can view the in-transit inventory formed through the stock transfer order (STO)). We operate 303 to issue 305 to receive, and there is no inventory transfer order:
why is it like this? It is necessary to clarify the concept of transit inventory and in-transit inventory. The following content is to move bricks on the Internet, and briefly express it:
Stock In Transfer
The "in-transit" formed by the transaction code MB1B/MIGO instead of STO is called Stock In Transfer, and the transaction code MB5T can view the in-transit inventory formed by the stock transfer order (STO).
The transfer inventory caused by movement type 303 is recorded in table MARC, and the transfer inventory is at the factory level. The transfer inventory
caused by movement type 313 is recorded in table MARD, and the transfer inventory is at the storage location level
[Review what was written in the previous article:
303 Transfer posting plant to plant in two steps - removal from storage
305 Transfer posting plant to plant in two steps - placement in storage
313 Stock transfer storage location to storage location in two steps - removal from storage
315 Transfer posting storage location to storage location in two steps - placement in storage
It can be clearly distinguished from the above concepts:
The movement type (303+305) is for the transfer between different factories
The movement type (313+315) can only be used for transfers between different storage locations under the same factory]
Stock in Transit
The "in-transit" formed through STO is called Stock in Transit (STO refers to transfer order)
The in-transit information caused by the inventory transfer order is not recorded in the inventory table, but is recorded in the table EKET, which records the planned quantity, delivery order quantity, delivery posting quantity, receipt Quantity
Continue to the previous step to test the content:
T_CODE: MIGO
MvT: 305 Receive material, generate material voucher: 4907362872
MB51 View material voucher:
305 Receive goods without follow-up accounting voucher:
MMBE Check inventory again:
3. STO without SD
Under the same company, the material TEST00981 is transferred between factories, from factory 8700 to factory 8702, and a UB inventory transfer order is created
MvT: 351 sent, 101 received
T_CODE:ME21N Create UB inventory transfer order: 4500000057, supply factory: 8700, purchase factory: 8702
T_CODE:MMBE Check the inventory overview of this material under 8702 factory, there are 8 sets of outstanding purchase orders:
T_CODE:MIGO, according to UB inventory transfer order, MvT351 delivery, generate material certificate: 4907362874
MB51 View material certificate and accounting certificate:
T_CODE: MB5T View in-transit inventory:
T_CODE: MIGO MvT: 101 Receipt according to UB purchase order Material certificate: 5002827171
T_CODE :MB51 View material vouchers, no follow-up accounting vouchers
T_CODE: MB5T in transit inventory disappears.
The UB order can only be divided into two steps, delivery and receipt.
UB bill background configuration: use the standard UB bill type of the system, as long as both sides of the material exist at the factory level.
4. STO with SD
Under the same company, the material TEST00981 is transferred between factories, from factory 8700 to factory 8702. To create a UB inventory transfer transfer document, a delivery document needs to be created. The delivery document type: NL (intra-company), and the delivery posting can be done in one step or two step.
One-step posting:
MvT:647 Goods issue for a stock transport order in onestep(shipping)
Two-step posting:
MvT:641 Goods issue for a stock tansport order(shipping)
MVT:101
One-step posting or two-step posting requires background configuration:
T_CODE: ME21N Create UB inventory transfer order: 4500000057, supply factory: 8700, purchase factory: 8702