Our Vista Job Numbering is set to use the following format;
######.###
We need our Purchase Orders to use Job Based PO Numbering, but if we enable it there is no delimiter between the last 3 characters of the Job number and the first character of the PO Number.
Adding a 'PO Numbering Delimiter' option to the Portal, near the 'Use Job Based PO Numbering' setting would resolve this issue.
Nolan Peters
| Company | Bird Construction |
| Job Title / Role | Manager - IT Application Services |
| I need it... | Yesterday...Come on already |
Dear Viewpoint Suggestion Box contributor;
We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs.
Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.
© 2024 Trimble Inc. All Rights Reserved. Viewpoint®, Vista™, Spectrum®, ProContractor™, Jobpac Connect™, Viewpoint Team™, Viewpoint Analytics™, Viewpoint Field View™, Viewpoint Estimating™, Viewpoint For Projects™, Viewpoint HR Management™, Viewpoint Field Management™, Viewpoint Financial Controls™, Vista Field Service™, Spectrum Service Tech™, ViewpointOne™, ProjectSight® and Trimble Construction One™ are trademarks or registered trademarks of Trimble Inc. or its affiliates in the United States and other countries. Other names and brands may be claimed as the property of others.
Hi Nolan! I reviewed this with the web team and it was decided this would be taken care of on the Vista side within the ERP.
This was their response:
Currently in Vista we have a setting at the company level that allows to create PO numbers using job number and sequence.
the setting displayed above results into PO numbering below when I create a new record for a job that has no POs in history
So what I am doing here is leveraging a job field section separator , my job mask is setup as 5R-3RN, to create a consistent separator for my PO numbers , this solution is a work around that tends to work in majority of cases. However, if you have a customer that is using sub jobs and would like to preserve that separator to include a full job number in PO, this work around will not support that scenario.Do you think this using the work around above would satisfy your request? Or are you asking to add another option to PM company parameters to specify a unique separator each customer can select for each company to separate job number from sequence number in a PO number value to assure that those separators are consistent on all project based POs?