We use requisitions for misc shop & office supplies. When the same part number is inadvertently used for multiple (otherwise unique) lines on a req., Epicor generates a single line with multiple releases on the PO. Descriptions for all but one of the lines is lost. Buyers then need to manually add the lost lines back to the PO, which is extra work and breaks the link between the req. and the PO lines.
These purchases are often one-offs where we don’t have our own part number. In these cases, users generally enter the mfg. p/n in the Part/Rev field on the Lines > Detail tab in Requisition Entry. If there is no mfg p/n, the user will just make something up to put in this field. Despite my efforts to educate users over the years, we continue to receive requisitions with the same part number used on multiple (otherwise unique) lines. In the example, part 1530 has a configurable length. When a PO was created, a single line was created which has the description from Line 1 on the req. and 4 separate releases - not what the requestor intended and not suitable to send to the supplier.
Has anyone dealt with this? I suspect a solution would need to be implemented in Requisition Entry in order to prevent any impact on inventory (qty bearing) parts.
We have a similar issue but with real parts. We use the PO for intercompany so we need to use global parts in the req. If we put the same part number in 2 or more different lines in the req, when the PO is generated, it creates just one line with multiple releases. The issue is we have different unit prices so only one of them makes it to the PO (the first line). We rarely do this so we ended up adding 5 global parts so you can do part1, part2, etc. More of a lazy workaround.
A better solution would be a BPM which checks for duplicate part numbers in the req.
I have seen the opposite in Purchase Direct on a job… if you put purchasing comments in the job, and they are different, then the system forces them to be on separate lines.
SO… One could call this a BUG, because if the description is different for a Part On The Fly (POTF) then the po should generate separate line items, and not combine them.
Have you submitted a ticket on this to Tech Support to report it as a bug? If you do, we might see a fix to this.
Check you Part Class setup. There’s a checkbox called “Split PO Lines” That’s supposed to break out different lines when the comments are different. I don’t see that checkbox available in Part Maintenance, so it looks like it’s only maintainable at the Part Class level.
Thanks! Unfortunately there currently is no Part Class associated with these misc parts created on the fly, but maybe we can assign a default class in Requisition Entry. Good to know the Split PO Line functionality exists though - may help us with ordering inventory parts.
I would still try making unique comments and see if they got split. You never know what the default behaviour will be. We use it, but we do not do POTF.
Just from playing around with it just now in our Pilot database (We don’t currently utilize requisitions inside of Epicor), you’ll need to Check the “Requisition” checkbox on at least one Part Class in order for it to be selectable in Requisition Entry.
