2019
Below are the notable changes to the Procore + Sage 300 CRE® integration in 2019.
Export PCCO Markups to Sage 300 CRE Estimates (8/22/2019)
Procore has released an update that was developed for companies utilizing the automatic financial markup feature for Prime Contract Change Orders on Sage 300 CRE®-integrated Prime Contracts. The update allows individual markups to be selected as affecting the Contract Amount and the Estimate Amount when syncing Prime Contract Change Orders. This mapping ensures that when a Prime Contract Change Order (PCCO) is exported from Procore to Sage 300 CRE®, the estimate in Sage 300 CRE® is updated accordingly. Prior to this release, the export from Procore only updated revenue amounts. See ERP Integrations: Export PCCO Markups to Sage 300 CRE Estimates.
Delete Sage 300 CRE® Project Cost Codes in Procore (3/23/2019)
Procore has been updated to allow for the deletion of Sage 300 CRE® Cost Codes on Procore projects synced with Sage 300 CRE®. Users with 'Admin' level permission on the project's Admin tool will now have the ability to delete project cost codes that have previously been synced with an ERP system. The only requirement is that the cost code must first be deleted in Sage 300 CRE®. See Delete Project Cost Codes from a Procore + Sage 300 CRE Project.
New Unlink Button for CCOs Synced with Sage 300 CRE® (3/4/2019)
When a Commitment Change Order (CCO) in a Procore project is synced with a integrated ERP system, a link is created between the records stored in each system. Sometimes, users will inadvertently export a commitment from Procore and then discover that the commitment's data as exported was incorrect. When this occurs, the records in both systems will need to be deleted manually and then the correct information must be re-entered in Procore and exported to the integrated ERP system. See Unlink CCOs Synced with Sage 300 CRE.
Delete Cost Code Cost Type Assignments Synced with Sage 300 CRE® (2/13/2019)
Before this update was released, your Procore Administrator was required to submit a request to reset a cost type assignment before it could be deleted in Procore. Now, users can delete the cost code type assignment in Procore. See ERP Integrations: Delete Cost Code Cost Type Assignments Synced with Sage 300 CRE.
New Unlink Button for Commitments Synced with Sage 300 CRE® (2/1/2019)
When a commitment in a Procore project is synced with a integrated ERP system, a link is created between the records stored in each system. Sometimes, users will inadvertently export a commitment from Procore and then discover that the commitment's data as exported was incorrect. When this occurs, the records in both systems will need to be deleted manually and then the correct information must be re-entered in Procore and exported to the integrated ERP system. See Unlink Commitments Synced with Sage 300 CRE.
New Transaction Date Field for CCO Exports to Sage 300 CRE® (1/30/2019)
Added a new Transaction Date field to the form that is used by accounting approvers when exporting Commitment Change Orders (CCOs) to Sage 300 CRE®. See Accept or Reject a CCO for Export to Sage 300 CRE.
Sage 300 CRE®: Now Pre-filling SubJob ID for Accounting Approvers (1/14/2019)
When sending a SubJob to the ERP Integrations tool for accounting approval, the system now pre-fills the SubJob ID for accounting approvers. See Send a Sub Job to ERP Integrations for Accounting Acceptance.
Admins Can Now Archive Standard Cost Codes on ERP-Integrated Projects (1/8/2019)
Updated the Company level Admin tool to give Procore Administrators with the ability to archive Standard Cost Codes in Procore in order to prevent project users from adding those codes to a project. The archive action does not remove Standard Cost Codes from all lists.This update only affects users that have setup the ERP Integrations tool for Procore.