SAGE 300 C & R Timberline

SUGGESTED

Newbie here.

Setting up Job Cost from older system; looking for suggestions on best way to number jobs.  Currently use xx-yyzz (x=year, y=next job in sequence, zz=additional letters for exdtras, separate costs tracking).

Job number also integral part of purchasing; job no is beginng of the PO number.

Suggestions much appreciated, thank you!

John

Parents
  • 0
    SUGGESTED

    John,

    It's hard to say what is best Job # format. It really depending on your company's operation, and annual job volume. Some company have only a few very high price job a year while some other companies have thousands of small jobs a year.

    Keeping the first segment as a reset trigger is a very good approach, then last segment as sequence number. You may need more segment in the middle if you like to be able to create reports and queries such as by team or division.....etc.

    One biggest suggestion is not to use job# as prefix for your PO#. That's what many inexperience people love to do, but that doesn't provide much info and you are just clustering up the system. You can always query PO by Job regardless if Job# is a part of your PO#. In another word, you can always create report listing POs grouped by Jobs.

Reply
  • 0
    SUGGESTED

    John,

    It's hard to say what is best Job # format. It really depending on your company's operation, and annual job volume. Some company have only a few very high price job a year while some other companies have thousands of small jobs a year.

    Keeping the first segment as a reset trigger is a very good approach, then last segment as sequence number. You may need more segment in the middle if you like to be able to create reports and queries such as by team or division.....etc.

    One biggest suggestion is not to use job# as prefix for your PO#. That's what many inexperience people love to do, but that doesn't provide much info and you are just clustering up the system. You can always query PO by Job regardless if Job# is a part of your PO#. In another word, you can always create report listing POs grouped by Jobs.

Children
No Data