on 2021 May 04 11:27 AM
Hi All,
We are using the Repetitive Manufacturing process. We have created a planned HU for a semi-finished product and have created a planned order for the semi-finished product. The semi-finished product has a BOM maintained for two components and both the components have consignment info records maintained using a standard purchasing organization and have the validity periods maintained up to the maximum.
Both the components have sufficient vendor consignment inventory. In the customization, a standard purchasing organization has been assigned to the plant which is used for the components in the info-records.
Both the components have the source list (ME01) maintained as well.
While back flushing the HU using the planned order in the MFHU transaction, the system is popping up an error message "Purchasing info record not found in the Purchasing Organization".
Please advice so that the issue can be cleared.
Thanks.
Hello lkr,
Have you created info records already? From your description, I think so.
In my opinion, the error tells us about nothing else that the misssing of info records in particular Purchasing Organization.
Please check , if you have really created inforecords already, in which Purchasing Organization those info records are created. Maybe during creation of info records in ME11 someone put a wrong mark for Purch Org and this is the only reason of the error?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Piotr,
The consignment info records exist for both the components and the used purchase organization in both the info records is the standard purchasing organization. We cross verified the updated purchasing organization for both the info records at the EINE table level and the purchasing organization is the same one.
Thanks.
Hello,
Till that moment it is the best option that I have found to help you.
https://launchpad.support.sap.com/#/notes/0001633823
In the situation that you have described you need to test of course that situation with MFHU. I'm not very familiar with MFHU, but I think that this note, describing very similar situation to your error but when using MIGO, could be very helpful. If you won't be able to open the SAP Note, please let me know, so I could describe to you what is included in the Note
Regards
Piotr
User | Count |
---|---|
93 | |
9 | |
8 | |
7 | |
5 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.