Material ### 4400 cannot be used in inbound delivery because QM is active

SAP
MM VL31N Error Msg - Material 47-54-039-004 4400 cannot be used in inbound
delivery because QM is active -

【Error Msg】

SA
document number: 5500019471

 

 

Material 47-54-039-004 4400 cannot be used in
inbound delivery because QM is active

Message no. L9528

 

Diagnosis

QM is active for material 47-54-039-004 in plant
4400. As a result, the material cannot be used in an inbound delivery item
because the item is relevant for picking and because WM is active for the item.

 

This process is not supported in the current
release.

 

Procedure

Execute the putaway using a goods receipt posting
with subsequent

putaway in the Warehouse Management system.

 

 

【参考意见1】

We have the same situation – even SAP themselves
did not find any solution to the fact that the QM and WM cannot work together,
if IBDLV is used. The reason is the fact that using IBDLV enables the creation
and confirmation of putaway TO before GR – which triggers creation of the
inspection lot. And the new quant might be merged with older quant, making it
impossible for the system to know where the insp.lot. belongs to.

We have used an
alternative flow, a workaround with a separate storage location (not assigned
to WM) used for GR and QM processes and then after GR an automated Transfer
Posting from ‘GR-stor.loc.’ to ‘WM-stor.loc’ .

This TP is triggered by an Output on the GR material doc., this output (special
function) triggers a little program collection the necessary data from standard
tables + a special control table, enters the data into a MBGMCR idoc using GM
code 04, and processes this idoc with target ‘own system’. Using normal
condition technique, this output can be controlled via event type (WE,WQ) so
the transfer will be triggered immediately if materials are not QM-active, but
will await QM usage decision if QM is active.

The TP will result in a putaway TO in WM – we have incorporated in the special
function that the GR mat.doc.no.
is copyed into the TP mat.doc. as a header text. Since the putaway TO will
refer to the TP mat.doc., it is possible to trace back to the GR PO, if
necessary.

BR,

Sigurds

 

 

【参考意见2】

 

We
are not using HUM however using WM. Nonetheless, the problem persist while
creating inbounds. 

 

We
are trying to use the following approach to address this problem. 

 

uncheck 'relev. for putaway' indicator
from 'ELN' item category thus enabling VL31N to by-pass the hard stop incurred
due to QM activation.

 

SAP's reason for this hardstop is to
avoid inconsistencies that may arise when TO's are created for inbound
deliveries before GR is posted. This scenario does not pertain to us since TO
for inbounds before GR is not applicable. Therefore, we are enabling the above
configuration. By doing this, we are breaking the link between inbound delvy's
and WM, and thus disabling the functionality of creating TO's referencing
inbound delvy's (transactions like LT03, LT0F become irrelevant).

 

But,
this process will not work if we implement HUM since standard SAP will not
allow to create a putaway TO referencing a TR or a material document. It
becomes imperative to create a TO referencing a delvy, but this configuraton
will break that link hence it will not work.

 

Best
Regards.

时间: 2024-10-23 22:53:31

Material ### 4400 cannot be used in inbound delivery because QM is active的相关文章

SAP MM Inbound Delivery 181640255为什么不能删除?

SAP MM Inbound Delivery 181640255为什么不能删除? Document flow, 没有任何后续凭证产生. VL32N 去试图删除该内向交货单, 系统报错: 为什么? 1)对应采购订单号:5500025953   2)该inbound delivery的外部ID:2016111501 3)MB51 查询该物料的107预收货记录: 该inbound delivery已经完成了107的预收货,所以它不能再被删除了.   4)之所以该inbound delivery的10

SAP MM VL31N 创建的Inbound Delivery和SWP创建的Inbound Delivery的区别

  SAP MM VL31N 创建的Inbound Delivery和SWP创建的Inbound Delivery的区别 1)The inbound delivery document created by VL31N in SAP, 2) The Inbound Delivery created by SWP (ASN),

SAP Documentary Batch in Inbound Delivery

SAP Documentary Batch in Inbound Delivery    

SAP MM VL31N 不同操作方式创建Inbound Delivery有不同的结果!

SAP MM VL31N 不同操作方式创建Inbound Delivery有不同的结果! 采购订单: 5500025131 VL31N,输入PO号码, 回车, 保存,成功的创建了inbound delivery,   VL31N,输入Vendor Code, 找PO号码,然后Adopt ,       报错!不让创建Inbound Delivery. 换一个SA使用同样的操作方式,就可以成功: SA 号码:5500025000       这是为什么?   经查,SA# 5500025131 里

SAP MM 采购单据中的’Origin Accept’选项会影响Inbound Delivery创建操作方式

SAP MM 采购单据中的'Origin Accept'选项会影响Inbound Delivery创建操作方式 采购订单: 5500025131      1),VL31N,输入PO号码, 回车, 保存,成功的创建了inbound delivery,    2), VL31N,输入Vendor Code, 找PO号码,然后Adopt ,       报错!不让创建Inbound Delivery. 3)如果我取消采购订单 5500025131 里的Origin Accept选项, 再去尝试输入v

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

SAP EWM Transaction Codes

   Below you will find listed the EWM transactions and its description.   Delivery Processing Inbound Delivery Maintain Inbound Delivery Notification /SCWM/IDN Maintain Inbound Delivery /SCWM/PRDI GR Preparation - External Procurement /SCWM/GRPE GR P

SAP MM PO 使用了107收货之后还能用101收货?

SAP MM PO 使用了107收货之后还能用101收货? [2016原创字-2016001] SA Document Number:5500019529 Inbound Delivery :181125425 已经针对这个Inbound delivery完成107 收货:       MIGO,试图使用101针对该Inbound Delivery 做收货,   结论是:做了107收货之后,不能再做101收货.

SAP MM 107收货之后去做MIRO,不能带出收货数量和金额等信息之对策

SAP MM 107收货之后去做MIRO,不能带出收货数量和金额等信息之对策   Inbound delivery 180003220   MIGO+107 移动类型执行预收货,   Post,   MIRO执行发票校验,     107收货的数量和金额等信息栏目为空,如上图.   什么原因?如何避免?   经过项目组FICO大拿的反复测试与研究,原因如下,采购订单的Origin Accept选项没有勾选,     ME32L. 修改这个SA,勾选这个选项:     重新建立一个inbound