Skip to main content

Change Orders

Subcontract Change Orders​

Visual Mapping​

Procore and Spectrum AR Invoice Visual Mapping

Procore and Spectrum AR Invoice Visual Mapping

Procore and Spectrum AR Invoice Visual Mapping

Procore and Spectrum AR Invoice Visual Mapping

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.

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").

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 Change Orders​

Visual Mapping​

Procore and Spectrum AR Invoice Visual Mapping

Procore and Spectrum AR Invoice Visual Mapping

Procore and Spectrum AR Invoice Visual Mapping

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.

Status​

Procore Prime Contract Change Orders exported to Viewpoint Spectrum will create a Change Request with a "Billing" Line Item. Since the "Status" in Spectrum Change Requests value will determine whether the "Billing" tab in Spectrum Change Requests is enabled (and if there is a revenue impact), please let your Agave Account Manager know which "Status" value you would like to sync for all Prime Contract Change Orders (e.g. "Approved", "Executed").

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.