The auto increment PO number goes 1-9, characters (: ; ? @ &), then letters as a prefix to the SO number in our system. I understand that the auto increment values could also be a suffix, but the problem would still exist. Using characters for a PO can be extremely confusing for vendors since a character can be considered a mistake and dropped. Also, for AR it is difficult to differentiate between a colon and semi colon.

It seems to make more sense to use numbers then letters or increase the PO field by a digit to allow for two digit prefix.

Comments

  • I have seen that problem also that the : ; ? @ & characters at the front of the PO are the issue and if it went 1-9 and then A-Z etc there would not be an issue but a PO# that comes into a vendor that starts ?145269 or :12345678 the : will either get ignored/dropped by the vendor or it is confusing to the receiving person when the packing list comes in with that PO# on it.

  • In speaking with my customer about their challenges with this performance, I agree that the characters can be overlooked, perhaps misinterpreted, when characters are included in the assigned PO's.

  • Numbers first; then Alphabet A-Z; THEN the Non Alphanumeric characters please.

  • Agreed, numbers first, then A-Z, only non-alphanumeric characters if all else is used.

  • I agree as well, Numbers first; then Alphabet A-Z; THEN the Non Alphanumeric characters please. In my experience the vendors generally do not even pick up the colon or the semi-colon preceding the p/o number ... it reads as "schmutz"