The Soft Link between IM Level Storage Location and WM level Storage Type?(2)

简介: The Soft Link between IM Level Storage Location and WM level Storage Type?(2)

3, The material 800 is used for this blog.

image.png


The values of the field stock removal indicator and stock placement indicator are both Z05.


3.1, Execute the transaction code MIGO, receive the materials into storage location 0001 then put away, to observe WM level documents.

image.png


Post, SAP switched to the screen of transaction code LT06, click Enter, we got below screen,

image.png


Save it directly,

image.png

Execute the transaction code LT21 to display this TO document,

image.png

We found that the inventory was placed into storage type Z05, it is correct since the stock placement indicator is Z05.


3.2, Execute the transaction code MIGO to receive materials into storage location 0003, then put away. Observe the WM level document.

image.png


Post, then SAP switched to transaction code LT06 screen, click Enter key, then we got below screen,

image.png

Save it directly,

image.png

Execute transaction code LT21 to display this TO document,

image.png


You can see the stock was placed into the storage type ZZ2.


3.3, Post goods issue to cost center from storage location 0001, then observe the WM level document.

image.png

Post, then SAP switched to transaction code LT06 screen, click Enter key, then we got below screen,

image.png

Save it directly,

image.png



Execute transaction code LT21 to display this TO document,

image.png

The stock was removed from storage type Z05, it is correct, since the stock removal indicator is Z05.


3.4, Post goods issue to cost center from storage location 0003, then observe the WM level document.

image.png

Post, then SAP switched to transaction code LT06 screen, click Enter key, then we got below screen,

image.png

Save it directly,

image.png

Execute transaction code LT21 to display this TO document,

image.png

The source storage type is ZZ2, it is consistent with our expectation.


In this way, the actual location of inventory can be distinguished at both IM and WM levels. Because the storage location at the IM level and the storage type at the WM level cannot be directly hard bound. Through this function, the soft link between the storage location at the IM level and the storage type at the WM level can be realized.


Note: This blog is based on SAP S4/HANA 1909 system.

相关文章
SAP WM高阶IM层面冻结物料库存过账后WM层面有三个不同的移动类型?
SAP WM高阶IM层面冻结物料库存过账后WM层面有三个不同的移动类型?
SAP WM高阶IM层面冻结物料库存过账后WM层面有三个不同的移动类型?
The Soft Link between IM Level Storage Location and WM level Storage Type?(1)
The Soft Link between IM Level Storage Location and WM level Storage Type?(1)
The Soft Link between IM Level Storage Location and WM level Storage Type?(1)
SAP WM 使用Storage Location Reference实现IM层面的存储地点和WM层面的存储类型之间的软关联(2)
SAP WM 使用Storage Location Reference实现IM层面的存储地点和WM层面的存储类型之间的软关联(2)
SAP WM 使用Storage Location Reference实现IM层面的存储地点和WM层面的存储类型之间的软关联(2)
SAP WM 使用Storage Location Reference实现IM层面的存储地点和WM层面的存储类型之间的软关联(1)
SAP WM 使用Storage Location Reference实现IM层面的存储地点和WM层面的存储类型之间的软关联(1)
SAP WM 使用Storage Location Reference实现IM层面的存储地点和WM层面的存储类型之间的软关联(1)
|
存储 供应链
SAP WM初阶之IM层面货物移动后WM层面自动完成TO创建和确认
SAP WM初阶之IM层面货物移动后WM层面自动完成TO创建和确认
SAP WM初阶之IM层面货物移动后WM层面自动完成TO创建和确认
|
存储 供应链
SAP MIGO + 311将库存从IM管理库存地转入WM管理库存地,物料凭证号里不显示WM 选项卡
SAP MIGO + 311将库存从IM管理库存地转入WM管理库存地,物料凭证号里不显示WM 选项卡
SAP MIGO + 311将库存从IM管理库存地转入WM管理库存地,物料凭证号里不显示WM 选项卡
|
2月前
|
数据采集 监控 测试技术
大型IM稳定性监测实践:手Q客户端性能防劣化系统的建设之路
本文以iOS端为例,详细分享了手 Q 客户端性能防劣化系统从0到1的构建之路,相信对业界和IM开发者们都有较高的借鉴意义。
93 2
|
2天前
|
人工智能 自然语言处理 搜索推荐
AI技术在智能客服系统中的应用与挑战
【9月更文挑战第32天】本文将探讨AI技术在智能客服系统中的应用及其面临的挑战。我们将分析AI技术如何改变传统客服模式,提高服务质量和效率,并讨论在实际应用中可能遇到的问题和解决方案。
93 65
|
19天前
|
数据挖掘 API
如何选择适合的售后工单管理系统
选择合适的售后工单管理系统需评估需求和预算,考察功能、技术支持及服务商可靠性,并全面试用评估。ZohoDesk适合初创和中小企业,具备强大的工单管理、报告分析及可定制性,助力提升服务质量和客户体验。通过合适系统,企业不仅能优化客户服务流程,还能通过数据分析支持决策,推动长远发展。
44 16
|
16天前
|
人工智能 自然语言处理 前端开发
从客服场景谈:大模型如何接入业务系统
本文探讨了大模型在AI客服中的应用。大模型虽具有强大的知识生成能力,但在处理具体业务如订单咨询、物流跟踪等问题时,需结合数据库查询、API调用等手段。文章提出用Function Call连接大模型与业务系统,允许大模型调用函数获取私域知识。通过具体示例展示了如何设计系统提示词、实现多轮对话、定义Function Call函数,并利用RAG技术检索文档内容。最后,展示了该方案在订单查询和产品咨询中的实际效果。

热门文章

最新文章

下一篇
无影云桌面