- Stock Data Of Serial Number Not Suitable For Movement Sapphire
- Stock Data Of Serial Number Not Suitable For Movement Sap
- Stock Data Of Serial Number Not Suitable For Movement Sapo
- Stock Data Of Serial Number Not Suitable For Movement Sapulpa
Affinities:| © Copyright 2014 - 2019,, The Best Online SAP Object Repository SAP Datasheet web site and its affinity sites content is based on our knowledge of SAP system, and it is constantly reviewed to avoid errors; well we cannot warrant full correctness of all content. While using this site, you agree to have read and accepted our terms of use, cookie and privacy policy.
Use the information and content on this web site at your own risk. SAP and the SAP logo are registered trademarks of.
This web site is not sponsored by, affiliated with, or approved. This web site is validated by as.
Dear experts: The problem is driving me crazy. Company is transferring material from plant to plant and wishing to keep the same serial number for the amterial, which is quite make sense from business point of view. We are using STO (UB) to transfer material from plant A to B. When doing GR reference to outbound delivery, the error msg is 'IO 231 Stock data of serial number XXXX not suitable for movement'.
![Data Data](https://image.slidesharecdn.com/movement-types-in-sap-mm-130608031207-phpapp02/95/movement-typesinsapmm-24-638.jpg?cb=1370661170)
124, Serial number &1 and material number &2 are already in the object list. 125, Batch of. 231, Stock data of serial number &1 not suitable for movement. May 2, 2008 - set by the system internally and if the serial number status is having “ALVB” then. Stock data of serial number 209 not suitable for movement.
I did some research but cannot find any clue. Any advice will be greatly appreciated.
More info is here, after goods issue posting, the system status for the serial number is EDEL & ESTO (i guess might this status prevent GR for plant B with same SN??). Millions of thanks. Dennis Posts: 64 Joined: Mon May 29, 2006 10:45 pm. Dennis_yan wrote:Dear experts: The problem is driving me crazy.
Company is transferring material from plant to plant and wishing to keep the same serial number for the amterial, which is quite make sense from business point of view. We are using STO (UB) to transfer material from plant A to B. When doing GR reference to outbound delivery, the error msg is 'IO 231 Stock data of serial number XXXX not suitable for movement'. I did some research but cannot find any clue. Any advice will be greatly appreciated. More info is here, after goods issue posting, the system status for the serial number is EDEL & ESTO (i guess might this status prevent GR for plant B with same SN??).
Millions of thanks. Dennis Which version is your system on? Are you in ECC6.0? Was your material item activated with either batch management or split valuation? Dennis_yan wrote:Dear experts: The problem is driving me crazy. Company is transferring material from plant to plant and wishing to keep the same serial number for the amterial, which is quite make sense from business point of view. We are using STO (UB) to transfer material from plant A to B.
When doing GR reference to outbound delivery, the error msg is 'IO 231 Stock data of serial number XXXX not suitable for movement'. I did some research but cannot find any clue.
Any advice will be greatly appreciated. More info is here, after goods issue posting, the system status for the serial number is EDEL & ESTO (i guess might this status prevent GR for plant B with same SN??). Millions of thanks. Dennis Which version is your system on? Are you in ECC6.0? Was your material item activated with either batch management or split valuation? Cheers, HT Posts: 64 Joined: Mon May 29, 2006 10:45 pm.
I did some more research and test. I reviewed BS23 to check system status. It indicates for ESTO, GR is prohibited, which makes sense. I maintained table T156SY using SM31 V_156SY. In my system, originally for 641, business transaction/event is PMSU & PMSD. I took the risk and changed the key to PMS1 & PMS5, the same one as for 643.
When I posted Gi again, the status for SN is ECUS, not EDEL+ESTO. But, GR still failed with the same error message. It's still confusing as from BS23, for ECUS, GR is warning. The stock type for the SN is 06, in transit It's dead end for me now. Hope valuable advice from experts. Posts: 64 Joined: Mon May 29, 2006 10:45 pm.
Dennis_yan wrote:I did some more research and test. I reviewed BS23 to check system status. It indicates for ESTO, GR is prohibited, which makes sense. I maintained table T156SY using SM31 V_156SY. In my system, originally for 641, business transaction/event is PMSU & PMSD. I took the risk and changed the key to PMS1 & PMS5, the same one as for 643.
When I posted Gi again, the status for SN is ECUS, not EDEL+ESTO. But, GR still failed with the same error message. It's still confusing as from BS23, for ECUS, GR is warning.
The stock type for the SN is 06, in transit It's dead end for me now. Hope valuable advice from experts. Have a look into OSS Note 213861. If it does not help fix your problem, I would suggest you to log an OSS message to SAP. Please also keep me informed of their investigation result as I am much interested in this case. Dennis_yan wrote:I did some more research and test.
I reviewed BS23 to check system status. It indicates for ESTO, GR is prohibited, which makes sense. I maintained table T156SY using SM31 V_156SY. In my system, originally for 641, business transaction/event is PMSU & PMSD. I took the risk and changed the key to PMS1 & PMS5, the same one as for 643.
![Stock data of serial number not suitable for movement sapulpa Stock data of serial number not suitable for movement sapulpa](http://www.sgwatchmall.com/images/item5/14379855142_23729.png)
Stock Data Of Serial Number Not Suitable For Movement Sapphire
When I posted Gi again, the status for SN is ECUS, not EDEL+ESTO. But, GR still failed with the same error message. It's still confusing as from BS23, for ECUS, GR is warning. The stock type for the SN is 06, in transit It's dead end for me now. Hope valuable advice from experts. Have a look into OSS Note 213861. If it does not help fix your problem, I would suggest you to log an OSS message to SAP.
Stock Data Of Serial Number Not Suitable For Movement Sap
Please also keep me informed of their investigation result as I am much interested in this case. Cheers, HT Posts: 64 Joined: Mon May 29, 2006 10:45 pm. Dennis_yan wrote:I did some more research and test. I reviewed BS23 to check system status. It indicates for ESTO, GR is prohibited, which makes sense. I maintained table T156SY using SM31 V_156SY.
In my system, originally for 641, business transaction/event is PMSU & PMSD. I took the risk and changed the key to PMS1 & PMS5, the same one as for 643.
Stock Data Of Serial Number Not Suitable For Movement Sapo
When I posted Gi again, the status for SN is ECUS, not EDEL+ESTO. But, GR still failed with the same error message. It's still confusing as from BS23, for ECUS, GR is warning. The stock type for the SN is 06, in transit It's dead end for me now. Hope valuable advice from experts.
Stock Data Of Serial Number Not Suitable For Movement Sapulpa
Posts: 129 Joined: Wed Jul 23, 2008 8:48 pm.