I understand why it’s happening but is there a work around.
We have a Generic Part# for Maintenance to use for their one-time purchase items. They submit a request with that generic part being used say 3 times.
Purchasing gets 3 suggestions and clicks buy on all 3 and select Create Purchase Order. Because it’s a generic part, it comes over as 1 line and 3 releases. Doing so, also wipes out the description of the other 2 lines.
Is there a way for maintenance to use a generic part number that will come over as lines instead of releases?
2 Likes
Does the requisition include the same supplier on each line? Or perhaps the Buyer is assigning the same supplier to each prior to converting to a PO?
I guess that could happen either way… but agreed, I could see why it wants to combine if its same supplier/same PN. 
1 Like
We went through the same annoyance, and confusion at first, when we started using a general part number for purchased items. Since they were using req entry we just had the users amend the default part number with an underscore and the supplier part number. This way it was repeatable and we would get our multiline PO.
2 Likes
My only thought (after reviewing the PO Suggestion screens again… its been awhile) would be the buyer would have to convert them one at a time. The problem there is you’d end up with 3 different PO’s… but at least you’d have the correct descriptions.
You CAN requisition a Part-on-the-Fly though, if that’s a route you could take. The requestor can type anything they want in the part field. Doesn’t have to be in the Part Master. So, for example, if they want to requisition something from McMaster-Carr… they can just put in the MMC Part Number & description.
Is there a reason you want/need a standard generic maintenance PN?
2 Likes
Thanks for the idea. I went into Pilot to test and that seemed to work well.
I’ll put an updated training class together next week and this should be solved.
Appreciate the assistance!
1 Like
You might also want to try the “Split PO Line” check box on the Part Class for that part. Might work.
2 Likes
Good one! Those are on in all of our part classes.
“Initial Value” is false, and I’m the one who DMT’d all our Part classes into the system, but I don’t remember including that in my template.
Forgot all about that functionality.
FIELD HELP: Checking SplitPOLine will result in separate PO lines generated from PO suggestions for the same part number when the suggestions have different comments.
Wonder what they mean by the “suggestion” having different comments. Hopefully coming from different Req. Lines will count.
1 Like
I think you literally have to put something in the comments or they will not split.