Skip to main content

Budget Transfers

Agave Sync allows you to export Autodesk Build Budget Transfers to Spectrum Change Requests with Cost Lines.

The status field mapping is flexible based on your preferences; work with your Agave rep to configure this.

Visual Mapping​

Autodesk Build and Spectrum Visual Mapping

Autodesk Build and Spectrum Visual Mapping

Common Errors and FAQs​

Are there any pre-requisites to syncing Budget Changes?​

Yes:

  1. You need to enable the Info-Link tables (see below),
  2. You will need to sync the following records referenced by the Budget Change:
    • The Customer
    • The Project
    • The Prime Contract
    • If included, the Unit of Measure,
    • The Cost Code (Phase Code), and
    • The Cost Type

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​

When syncing Autodesk Build Budget Changes to Spectrum Change Requests, the Change Request status will match the Subcontract Change Order setting.

Note the status must have an Action set to 3. Recognize Cost Revisions, No Billing. Otherwise when attempting to sync a Budget Transfer you will receive the following error: "[Spectrum Error] Non-cost reimbursable change request cannot have this status."

Autodesk Build and Spectrum Visual Mapping

Duplicate Cost Codes​

You cannot use the same Cost Code twice in a Budget Change in Autodesk BUild. This will result in an incorrect Spectrum Change Request.