The client is implementing Epicor and has multiple companies. Is there any way to add a prefix to purchase orders, sales orders, based on the company?
Company is already a field on every record. Where would they like to see it? Where do they see confusion?
1 Like
@csajda PO and SO is a numeric field. You can add a UD field in Company to store prefix and modify the forms to display prefix with PO Num, SO Num, Invoice, etc.
Another option may be to set the starting number sequence for SO, PO, Jobs, Invoices, etc. to different ranges of numbers to more easily tell them apart.
ie SO starts at 10000, PO at 30000, Job at 50000
1 Like
Hi,
To be honest this should be standard functionality in epicor. It is in alot of systems. Please raise an enhancement request.There is nothing out of the box. However, in practical terms this can be a nice to have, depending on your environment. If from a purely document point of view you can modify the document to put a suffix/prefix but this wont do anything in terms of typing stuff into epicor.
Are we asking to be able to do mutli-company entry from within any company to another company?
Now that would be nice!!!
But as I say, once people get use to things it becomes a non issue
I think it’s a big ask. Next thing people will want to be able to do the same with sites!
1 Like
Company context input… on a serious note how many epicor customers would like this. E.g. you have one credit control department physically, but multi company credit control. E.g. enter a context, e.g. a customer I’d and it will drop into the company required etc.
Transfer Orders have this. And it is somewhat annoying. You have to specify the number of digits to use in the TO OrderNum. And then that number is padded with leading zeros between the site prefix and the order number.
The 5th TO Order for site AB will show as AB000005 in our system.
I tried to suggest adding a formula to put in a prefix based on the company on our documents. It was chosen to do the numbering scheme. It really isn’t that bad once you get going. Once they centralize AR it will keep all the headaches away 
Field Service job number also same.It will be F0100000001.
Its preferable to have prefix if business has centralised AR or AP or shared premises which will help users to straight away identify the documents.
I think the major question to ask is if its need is primarily for automation, or for human use (and particularly for outward facing documents - like invoices or packers sent to customers).
If its the later, you can simply modify the form’s RDL to include the company code. But then you run into the issue of you users needing to know that the prefix should be left off, when looking up a packer, order, or invoice, when the customer provides it.
Or maybe better yet, have a BPM that check the prefix against the current company and provides a warning if they don’t match. This would eliminate the issus when a customer calls in with a question about invoice MC0012345, and the user enters 0012345 - but while in company XY. It would pull up company XY's invoice 12345, not 12345 for company MC.