Integration by Ryvit: Export a Commitment Change Order (CCO) to Viewpoint® Vista™
Objective
To export a Commitment Change Order (CCO) to Vista using the Integration by Procore.
Background
This process consists of the tasks, which are typically performed by two different users:
- A project manager completes these tasks:
- Create a Commitment Change Order (CCO)
- Send the CCO to an accounting approver for export to Vista with the Integration by Procore.
- An accounting approver (see What is the accounting approver role?) reviews the CCO that was sent to the ERP Integrations tool for acceptance. Then, the accounting approver either accepts or rejects it. The system then does the following:
- Accepted CCOs are exported to Vista.
- Rejected CCOs are NOT exported to Vista. Instead, they are returned to an editable state in the project's Commitments tool so they can be corrected and re-sent to the ERP Integrations tool acceptance by the accounting approver.
Things to Consider
- Required User Permissions:
- Prerequisites:
- The ERP Integrations tool must be enabled on the company account. The tool must also be configured to work with the Integration by Procore. See Integration by Procore: Setup Guide.
- Limitations:
- To add a Schedule of Values (SOV) line item to a CCO, it must be tied to an existing cost code and category.
- Vista has a limitation where a contract line item cannot be modified more than once on any CCO. Therefore, if you have a CCO that contains more than one modification for the same commitment line item, Procore will automatically sum the amount of the items and send it to Vista as a single (aggregated) value.
Steps
- Create a Commitment Change Order (CCO)
- Integration by Procore: Send a CCO to an ERP Integrations for Accounting Acceptance
Note: If you need to make changes to a CCO before the data has been accepted by an accounting approver for export to Integration by Procore, see: - Integration by Procore: Accept or Reject a CCO for Export to Vista