This page details the notable changes to the Company level ERP Integrations tool for the year 2016.
Updated the ERP Integrations tool so that now, when importing a Commitment Variation (CV) from Sage 300 CRE into Procore, the system adds the ERP Number as the Variation Number in Procore.
Updated the ERP Integrations tool to implement error messaging for Job and Sub Job list updates when the the system returns bad data. The message informs the user that the sync failed and also more clearly explains the issue.
Updated the ERP Integrations tool to implement error messaging for Sage vendor list updates when there is a duplicate origin ID or a duplicate Sage code. The message informs the user that the sync failed and to contact support for assistance.
Updated the ERP Integrations tool for Sage to that users now have the ability to export budgets in Sage-integrated companies when they have budget line items tied to Sub Jobs. These are exported into Sage as an original estimate for the Sage "Extra".
Updated the ERP Integrations tool to change the system's behaviour for exports. Now, if an export event from the ERP Integrations tool does not successfully complete after 10 tries, the system fails the export.
User-facing change: Updated the ERP Integrations tool for Sage 300 CRE integrations. Now, when the system fails to sync standard categories, a new error message will inform the user that an error has occurred and direct the user to contact Procore support.
Updated the ERP Integrations tool to improve the user experience when a standard cost code sync fails. Now, Procore displays an error message (instead a stuck progress spinner).
Updated the Commitments tool to change the tooltip that appears on a commitment that has been sent to the ERP Integrations tool for acceptance by an accounting approver. The text on the tooltip has been changed from "Subcontract [or PO] has been sent to Sage 300" to "Subcontract (or PO) has been send to ERP".
When adding a new Procore project to both ERP-integrated and non-integrated companies, Procore now displays a notification message in the banner of the Create New Project page of the Portfolio tool and also on the ERP Integrations tool's Jobs subtab. This banner only displays if your company has reached its maximum number of projects (Project limits are set by your Procore point of contact during the implementation process).
Created a feature that updates a synced Procore vendor with any changes made to that vendor in the user's accounting system. Changes detected include: name, address, phone number and email address.
Updated the ERP Integrations tool to freeze the column header row on the table in the Job Cost subtab, so users can have a better experience when scrolling through data.
Updated Procore's handling of vendors marked "Inactive" in Sage. Inactive vendors now appear in the "Archived" filter on the Vendors subtab in the ERP Integrations tab after the initial import or when a user updates the vendor's name, address or contact information (along with active/inactive status) and syncs the information using the hh2 service.
Added validation in Change Events tool to prevent the creation of a Commitment Variation (CV) with a number that exceeds five (5) characters. This limit only affects ERP-integrated projects. A banner will appear to alert users when user exceeds the character limit. For non-ERP projects, numbers can exceed 5 characters.
Updated the ERP Integrations tool to change the backend validations for the accepted cost code delimiters for Sage-integrated companies. The system now allows a forward slash (/) along with a dash (-) and period (.).
Updated the ERP Integrations tool to change the sort order on the Sub Jobs and Job Costs subtabs. Prior to this fix, sub jobs were sorted by the create date/time. They now sort by sub job number.
Updated the ERP Integrations tool to fix a responsiveness issue in Configure ERP Integrations Settings > Vendor Type Import Settings page where the Vendor Type was not responding as expected. This has been fixed.
Added the inline editing capabilities for Sage-integrated company. This allows users to edit the name of sub jobs in Procore. This does not affect the naming convention within their Sage system.
Updated an Admin tool error message for ERP-integrated companies. This updated affects the 'Standard Cost Codes' and 'Cost Code Category Assignment' pages. Now when a user changes a category assignment, the system checks the company's credentials and alerts the user if the credentials are invalid. Credentials are entered in the 'Configure ERP Integrations Settings' page of the ERP Integrations tool.
Updated the project's Admin tool to revise the informational banner so it more accurately reflects why users on Sage-integrated projects should re-send their project to the ERP Integrations tool to be updated.
Updated the ERP Integrations tool so that the 'Customers' drop-down list in the Jobs subtab under the 'Ready to Import' page now uses alphanumeric sorting.
Updated the ERP Integrations tool for Sage-integrated projects so that when users push a variation from ERP to hh2, the Commitment Creation Date in Procore is also pushed so that date can be passed into Sage as the date for a commitment.
Project Number (if present) will now be displayed alongside Project Name in the header of the Company level ERP Job Costs report for Sage-Integrated projects. See View Job Costs Report.
Procore users in Australia needed a way to assign a Goods and Services Tax (GST) Group on Commitments and Commitment Variations (CVs) being sent from Procore to their third-party accounting system. This feature must be enabled on the backend by Procore. To request to enable the feature, contact your Procore point of contact.
If you've integrated your company's Sage 300 CRE with Procore's ERP Integrations tool, you now have the ability to export a Procore budget to Sage. See Export a Budget from ERP to Sage.
Updated the Procore ERP Integrations tool (for Sage 300 CRE) so it now exports the Procore 'Commitment Creation Date' to the hh2 service. This allows the hh2 service to pass the Procore date into what the Sage 300 CRE database calls the 'Commitment Date'.
Updated the Admin tool (see Admin (Project Level)) to add minor user interface improvements to better inform users when projects have been integrated with an ERP system. Added a green ERP symbol that appears next to the "Project Home" and the "Project Admin" headers when ERP is enabled. Also added a non-editable Sage ID field in the Project level Admin tool for projects where Sage 300 CRE (STO) is enabled.
Updated the ERP Integrations tool to add an error message when a project import from an ERP system into Procore fails due to the presence of double quotes (") in the project name.
Updated the Project level Tendering tool to no longer show the Convert to Contract button on a Tender Sheet if the project is integrated with an ERP system that does not use Categories/Line Item Types.
On vendor edit pages in Procore's Directory tool, there is now an orange action button for activating/deactivating the vendor rather than a checkbox on the vendor profile. Additionally, if a vendor is linked to an ERP vendor at the time that the Procore vendor is deactivated, Procore will now automatically dissociate the Procore vendor from the ERP vendor and will archive the ERP vendor in the ERP Vendors subtab.
Updated the ERP Integrations tool to display a proper error message when a project import from an ERP system fails due to the presence of double quotes (") in the project name. Procore does not support imports with double quotes in project names and the notification message now displays to remind users of this requirement.
On vendor edit pages in the Procore Directory, there is now an orange action button for activating/deactivating a vendor (e.g., rather than a checkbox on the vendor's profile). Additionally, if a vendor is linked to an ERP vendor at the time that the Procore vendor is deactivated, Procore will now automatically dissociate the Procore vendor from the ERP Integration tool's Vendor list and will archive the vendor in the Vendors subtab.
Expanded the scope of the Search capabilities in the ERP Integrations tool to include project budgets. Users can now search for the filters defined in the Budget subtab
Previously, when a user selected an existing commitment line item from the line item picker while editing a Commitment Variation's (CVs) Bill of Quantities (BOQ) on an ERP Integrated project (i.e., Sage 300 CRE), Procore would auto-populate the commitment line item's description into the Description field as a read-only value. This has been changed. Procore now auto-populates the Description, as before, but it is now editable during line item creation. See Send a Variation to ERP.
Users are now permitted to add parent-level cost codes (i.e., Divisions) to the Budget on ERP integrated projects if the ERP system integrated with Procore allows the application of costs to parent-level codes (e.g., Sage 300 CRE).
Users are now permitted to delete "synced" cost codes from ERP projects if the ERP system that the company has integrated with has no explicit relationship between projects and cost codes (e.g., QuickBooks). Note: There is one caveat to this change--Users will not be permitted to delete cost codes if they are used anywhere in the Procore project.
Expanded the scope of the Search capabilities in the Company level ERP Integrations tool to include project budgets. Users can now search for the filters defined in the ERP Budget sub tab.
Changed labels from 'Extras' to 'Sub Jobs' on the ERP Sub Jobs subtab in the ERP Integrations tool.
Commitment line item descriptions are now truncated during the export from Procore to the accounting system, so users can now edit commitment line item descriptions inline on ERP-integrated projects. Prior to this improvement, there was a 30 character maximum limit.
Updated Procore to allow inline editing of Commitment Variation (CV) line item descriptions on ERP integrated projects.
Note: If the CV line item being edited is tied to a $0 commitment line item created as a result of the CV line item's creation, the description on the Commitment line item will NOT change to match the inline-edited CV line item description.
Updated the logic surrounding the "last synced with Sage [X] ago" timer for the Budget of ERP-integrated projects. This timer will now reset each time the job cost sync runs, as well as when the budget is manually re-imported from the ERP tab.