Stock Removal Strategy A(Partial Pallet Quantity)in SAP WM

简介: Stock Removal Strategy A(Partial Pallet Quantity)in SAP WM

Stock Removal Strategy A(Partial Pallet Quantity)in SAP WM


In SAP WM module, the stock removal strategy A(partial pallet quantity) is also commonly used. There are partial pallets and full pallets of materials placed in the warehouse. If a small amount of materials need to be removed from the shelf, SAP system can suggest that they should be removed from the partial pallet shelf automatically, which is naturally a good and convenient stock removal strategy for warehouse management.


This blog is used to demonstrate the control effect of stock removal strategy A.


1, The Storage type Z05, its stock removal strategy is A.

image.png

2, Storage type search configuration.

image.pngimage.png

3, The material 800 is used for this demo. See the WM views setting.

image.png

In material master data, the stock placement indicator and stock removal indicator are both Z05. It means that when we conduct put away for that material, the destination storage type will be Z05; when we remove stock from shelf, the source storage type will be Z05 too.

image.png

In palletization data, we set that a full IP type pallet can store 500 EA of this material.


4, The purchase order 4500000851 of material 800, is used for the demo of this blog.

image.png

5, Execute the transaction code MIGO to do goods receipt against this purchase order, and complete the put away transaction of SAP WM level, then we have the inventory of this material.


We received 1233 EA of material 800, it means that we will have 2 full pallet and 1 partial pallet.

image.png

Save it,

image.png

Click enter and goto below screen,

image.png

Save it directly,

image.png

Check the WM Level inventory,

image.png

We can see that this material have inventory in 3 storage bins.


Storage bin 17-01-01, the quantity is 500 EA, full pallet;


Storage bin 17-01-02, the quantity is 500 EA, full pallet;


Storage bin 17-01-03, the quantity 233 EA, partial pallet.


6, Now we conduct a goods issue to cost center transaction, the quantity is 10 EA. Observe how SAP remove stock from shelf.

image.png

Save it, SAP switch to the LT06 transaction, we click enter, then goto below screen,

image.png

Save it directly,

image.png

Execute transaction code LT21 to check this TO document,

image.png



These 10 EA material are removed from the storage bin 17-01-03 of storage type Z05, because the inventory stored on this storage bin is partial quantity. This is the control function of stock removal strategy A(partial pallet quantity).


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

相关文章
|
机器学习/深度学习 分布式计算 Java
Hbase入门(二)——安装与配置
本文讲述如何安装,部署,启停HBase集群,如何通过命令行对Hbase进行基本操作。 并介绍Hbase的配置文件。 在安装前需要将所有先决条件安装完成。
1216 0
Hbase入门(二)——安装与配置
|
10月前
|
计算机视觉
YOLOv11改进策略【Neck】| TPAMI 2024 FreqFusion 频域感知特征融合模块 解决密集图像预测问题
YOLOv11改进策略【Neck】| TPAMI 2024 FreqFusion 频域感知特征融合模块 解决密集图像预测问题
417 11
YOLOv11改进策略【Neck】| TPAMI 2024 FreqFusion 频域感知特征融合模块 解决密集图像预测问题
|
Prometheus Kubernetes 监控
深入探索Kubernetes中的Pod自动扩展(Horizontal Pod Autoscaler, HPA)
深入探索Kubernetes中的Pod自动扩展(Horizontal Pod Autoscaler, HPA)
|
NoSQL 关系型数据库 MySQL
微服务架构下的数据库选择:MySQL、PostgreSQL 还是 NoSQL?
在微服务架构中,数据库的选择至关重要。不同类型的数据库适用于不同的需求和场景。在本文章中,我们将深入探讨传统的关系型数据库(如 MySQL 和 PostgreSQL)与现代 NoSQL 数据库的优劣势,并分析在微服务架构下的最佳实践。
|
云安全 弹性计算 Linux
幻兽帕鲁Palworld服务器部署教程(阿里云服务器3分钟搭建幻兽帕鲁保姆级攻略)
想要部署属于自己的幻兽帕鲁服务器(Dedicated Server),您首先需要拥有一台服务器,服务器是幻兽帕鲁运行的基础。部署完成后,您和您的朋友便可以登入专属的游戏服进行体验。使用云服务器搭建幻兽帕鲁服务器,便可以让您与您的朋友在一个相对独立且私密的空间中进行游戏,确保获得更加畅快的游戏体验。 您可以选择阿里云服务器作为游戏服务器,并按照下面教程来部署幻兽帕鲁。
|
JavaScript 关系型数据库 数据库
PostgreSQL支持哪些编程语言?
【8月更文挑战第5天】PostgreSQL支持哪些编程语言?
681 8
|
Kubernetes 负载均衡 API
在K8S中,kube-proxy ipvs 原理是什么?
在K8S中,kube-proxy ipvs 原理是什么?
|
存储 关系型数据库 MySQL
"深入探索MySQL临时表:性能优化利器,数据处理的灵活之选"
【8月更文挑战第9天】MySQL临时表专为存储临时数据设计,自动创建与删除,仅在当前会话中存在,有助于性能优化。它分为本地临时表和全局临时表(通过特定逻辑模拟)。创建语法类似于普通表,但加TEMPORARY或TEMP关键字。适用于性能优化、数据预处理和复杂查询,需注意内存占用和事务支持问题。合理使用可大幅提升查询效率。
783 2
|
SQL NoSQL 数据库
深度解密 pandas 的行列转换,以及一行变多行、一列变多列
深度解密 pandas 的行列转换,以及一行变多行、一列变多列
809 0
|
SQL 关系型数据库 MySQL
OceanBase 的 SQL 兼容性与优化
【8月更文第31天】随着分布式计算的发展,越来越多的企业开始采用分布式数据库来满足其大规模数据存储和处理的需求。OceanBase 作为一款高性能的分布式关系数据库,其设计旨在为用户提供与传统单机数据库类似的 SQL 查询体验,同时保持高可用性和水平扩展能力。本文将深入探讨 OceanBase 的 SQL 引擎特性、兼容性问题,并提供一些针对特定查询进行优化的方法和代码示例。
1005 0