SAP WM & HU (nested) Stock Upload

SAP WM & HU (nested) Stock Upload

转载自:http://scn.sap.com/docs/DOC-47864

 

I've recently faced the problem to upload the stock in WM
where HU management is active on the storage location.

 

As probably you already know in SAP there is also a
standard program to do this: RHUWM_INITIAL_LOAD  but in my opinion it requires a very well
structured input file, and it is not always so easy to get such a file from a
legacy system.

 

Moreover I had another complication, because our HUs were
nested, and using inbound delivery didn't seem to me so “easy-to-use”, so I
decided to upload the stock in another way that I'm going to explain, hoping
that it could be useful for others.

 

The process consists in "splitting the upload
process in 5 different easy steps:

 

1. Upload the stock in a storage location (e.g. XXXX,
managed only in MM without WM nor HU).

2. Create the lower level HUs.

3. Create the upper level HUs and assign at the same time
the lower level HUs to them.

4. Transfer the nested HU to the WM/HU managed storage
location (e.g YYYY).

5. Transfer the SU/HU in the final destination bin.

 

Here is a short explanation of the above mentioned steps:

1. I wouldn't go in depth into this point since it is not
the scope of this post

2. I've created an LSMW using

?Business Object (BUS3070)

?Method (CREATE)

?Message Type (HU_CREATE)

?Basic Type (HU_CREATE01)

 

In this LSMW you will have to indicate the data of the
lower level HU:

 

Header data: basically packaging material, External ID

Item data: basically material, quantity, unit of measure
plant, storage location, etc

 

3. I've created an LSMW using

?Business Object (BUS3070)

?Method (CREATE)

?Message Type (HU_CREATE)

?Basic Type (HU_CREATE01)

 

 

In this LSMW you will have to indicate the data of the
upper level HU:

Header data: basically packaging material, External ID

Item data: lower level HUs

 

Note: for this LSMW I’ve used a hierarchical source like:

 

UPPER_LEVEL

 

            LOWER_LEVEL

 

Since more lower level HUs can be assigned to the same
upper level HU.

 

4. You use a standard functionality inside HUMO to move
the HUs towards another storage location or in alternative it is possible to
use a LSMW by recording a VLMOVE (mov. 311)

 

5. Simple LSMW with recording on LT09….to transfer the SU
(upper level Hus become SU in WM)

 

That's it.

Have a nice stock upload!

 

Claudio

 

PS Please note that if you are working with single-level
HUs, you should ignore the step #3

 

 

 

时间: 2024-07-29 19:15:28

SAP WM & HU (nested) Stock Upload的相关文章

SAP WM Cross Line Stock Putaway

SAP WM Cross Line Stock Putaway   上图的意思是先放满各个货架的第一层,然后去搜第二层,第三层...... 要想实现上图的cross line的方式的put away,就需要在 Storage bin 主数据里定义sort field stock placement字段值,如下图:       后台这里配置这个 sort field,       之前我们的120仓库下的015 storage type下的 storage bin里没有定义Sort Sequenc

SAP WM 先进先出原则在’Stock Removal Background’的时候的体现

SAP WM 先进先出原则在'Stock Removal Background'的时候的体现 Warehouse number 360 Material number 30541504-WH Storage type Z05 Put away strategy is F (fixed bin); Stock removal strategy is F(FIFO); Storage bin Z05 1)The stock information:   2)LT01 try to remove st

SAP WM Stock Removal Strategy - StringentFIFO 在仓库号级别下的先进先出

SAP WM Stock Removal Strategy - Stringent FIFO ,在仓库号级别下的先进先出   需要去后台这里做配置,   如果是改成了***,即从所有的storage type里出货,这些storage type有是包含有interim storage type的,需要将这些interim storage type排除掉,通过如下的方式,     微信号:JINYULIN_SH_ QQ: 2806032155  

SAP WM LQ02 为供应商寄售库存去K的时候,如果有Open TO单,则不能成功为物料去K?

SAP WM LQ02 为供应商寄售库存去K的时候,如果有Open TO单,则不能成功为物料去K?   物料10504117 在100下有10个K库存,同时有20个数量的库存是stock for put away (open TO).   LQ02,试图去将这个物料的K库存去K, 这个物料的项目不能被选中,即无法成功的去K.   为什么?   查过资料得知,这是SAP标准逻辑,解决方案就是将相关的Open TO单据confirm掉.然后LQ02就可以对其做去K之操作了.   2016-11-22

SAP WM LP10 创建TO单据的时候,系统根据目的地100下的库存自动扣减TO里的数量?

SAP WM LP10 创建TO单据的时候,系统根据目的地Storage Type 100下的库存自动扣减TO里的数量   LP10将TR转成TO单据的时候,我们常常发现,生成的TO单据里的数量并不是等于TR里的数量,而是系统自动根据目的地storage type 100下的库存数量自动扣减之后的数量作为生成的TO的数量.原因何在?     下一步,   下一步,     勾选100 Storage Type 下的Deactivate qty reduction 选项即可避免此种情况的出现.  

SAP WM RF Queue Management Setting

SAP WM RF Queue Management Setting   In this section you configure the settings for the RF Queue Management.  Activities  Define queues  The fields "warehouse number" and "queue" are mandatory and serve to uniquely identify aqueue.  Th

SAP WM 明明有vendor consignment库存,将TR Convert TO却不成功?

SAP WM 明明有vendor consignment库存,将TR Convert TO, Error Msg – Storage type CON does not allow negative stock figures – 之对策               回车, Error msg – Storage type CON does not allow negative stock figures   实际上CON 这个storage type下是有库存的,K库存.为什么会报错!!! 经

SAP WM Production Schedule Profile设置问题导致生产补货的TO单自动创建问题

SAP WM Production Schedule Profile设置问题导致生产补货的TO单自动创建问题   笔者所在的D项目上,业务人员希望工单一旦release,自动触发为生产补货的TR单.然后业务人员手工将TR 转成TO单把物料从仓库到产线边上(storage type 100).   按照客户的需求,我做好了配置,准备好了相关主数据.在我测试的时候,发现了一个问题,困扰了我半天.   我CO01创建了工单并下达之后,却发现TR产生了,同时自动创建了TO单!     保存,   看这个

SAP WM 如何理解使用LT0G撤销TO时系统出现的锁的标志

SAP WM 如何理解使用LT0G撤销TO时系统出现的锁的标志   http://mp.weixin.qq.com/s/qsDd_ffojh6C1M9YiShmJQ     我们在使用LT0G对TO做撤销的时候,系统有的时候会在这一行的行头显示一个锁的标志,有的时候就没有.你可能会很矛盾,为什么系统有的时候会出现锁的标志呢?   今天,向大家推荐一篇SAP WIKI的文章,希望能够帮助您理解系统在什么情况下会出现锁的标志.   我们知道,LT0G是用来返还库存到最初的存储类型和存储仓,或者将库存