Skip to main content

Change Orders (Subcontractor Change Orders)

Agave syncs Procore Commitment (Subcontract) Change Orders to Viewpoint Spectrum Change Requests with Cost Line Items.

Visual Mapping​

Procore and Spectrum SCO Visual Mapping

Procore and Spectrum SCO Visual Mapping

Procore and Spectrum SCO Visual Mapping

Video Tutorial​

Common Errors and FAQs​

Status​

Procore Commitment Change Orders exported to Viewpoint Spectrum will create a Change Request with a "Cost" Line Item. Since the "Status" in Spectrum Change Requests value will determine whether the "Costs" tab in Spectrum Change Requests is enabled, please let your Agave Account Manager know which "Status" value you would like to sync for all Subcontractor Change Orders (e.g. "Cost Rev", "Approved").

Custom Numbering​

By default, Commitment Change Orders in Procore against different commitments can reuse the same number. To help avoid errors while following Spectrum’s character limit, Agave has a custom setting that will automatically bring Commitment Change Requests into Spectrum in the following format:

  • <P or S><last 3 numbers from commitment>-<last 3 numbers from Change Order>
  • For example, a Procore Subcontract with number SC-AG2501-001 and Change Order 002 will create a Spectrum Change Request with number S001-002

Work with your Agave representative to enable this setting.

Cost Code/Cost Type Pairs​

Spectrum's web service does not accept multiple line items with the same Cost Code/Cost Type combination.

As a result, each combination of Cost Code/Cost Type can only be used once per Change Order. Agave will show this error when a combination is repeated: [Spectrum Error] All Change Order line items must have unique cost_code_id, cost_type_id, and type pairs.

To fix the error, combine these changes to a single line and re-sync the Change Order.

Prime Contract is not Synced​

Spectrum requires a contract when creating a Change Request:

Procore and Spectrum Contract

The Procore CO itself does not specify a contract, so Agave has a few options for which Prime Contract is used. Link the relevant Prime Contract in Agave to resolve the error.

Here is how Agave chooses the Prime Contract (in order of priority):

  1. Use the Prime Contract for Markup Estimates field from the CO's Change Event

    Procore and Spectrum Contract

    When this is enabled, Agave uses the specified Prime Contract on the CO's change event.

    If this field is empty, Agave will progress to option 2.

  2. Use the only Prime Contract

    If the field from Option 1 is empty and there is only one Prime Contract, Agave will use that Prime Contract.

  3. (Requires Configuration) Use the first Prime Contract in the Procore Project

    If there are multiple Prime Contracts and the field from Option 1 is empty, Agave will throw an error to avoid associating the CO with an incorrect contract.

    However, upon request Agave can use the first approved Prime Contract on the Procore project, even if there are multiple. This is best for users that may create subsequent Prime Contracts and did not utilize the Prime Contract for Markup Estimates field on the Change Event during the initial phase of the project

    Contact your Agave rep if you would like this option enabled.

The following Info-Link tables are required when syncing Change Orders from or to Spectrum:

  1. CR_CHNG_REQ_CON_DET_MC
  2. CR_CHNG_REQ_HDR_MC
  3. CR_CHNG_REQ_REV_MC
  4. CR_CHNG_REQ_STATUS_MC

For details on enabling Info-Link tables for your user, see Steps 2.7 in our Spectrum authentication guide.