Skip to main content

Change Orders

Visual Mapping​

From Autodesk Build to Sage 100C​

Agave Sync allows you to sync a SCO or OCO in Autodesk Build as a Change Order in Sage 100.

Autodesk Build and Sage 100 Change Orders Mapping

Autodesk Build and Sage 100 Change Orders Mapping

Autodesk Build and Sage 100 Change Orders Mapping

Autodesk Build and Sage 100 Change Orders Mapping

Autodesk Build and Sage 100 Change Orders Mapping

Autodesk Build and Sage 100 Change Orders Mapping

From Sage 100 to Autodesk Build​

Agave Sync allows you to sync a Change Order in Sage 100 as a Supplier Change Order (SCO) in Autodesk Build.

Autodesk Build and Sage 100 Change Orders Mapping

Autodesk Build and Sage 100 Change Orders Mapping

Autodesk Build and Sage 100 Change Orders Mapping

Once the SCO is synced, you should be able to the see the impact from SCOs on the original Subcontracts in both Sage 100C and Autodesk Build.

Autodesk Build and Sage 100 Change Orders Mapping

FAQs and Common Errors​

Mapping Change Order Types​

To enable a seamless sync of Change Orders from Autodesk to Sage 100 Contractor, you will want to enable a mapping of Change Order Types between Autodesk Build and Sage 100C.

To enable this mapping:

  1. In Autodesk Build, from Cost, go to Settings-->Change Order-->Change Order Types.
  2. In Sage 100 Contractor, go to a Change Order, and select the arrow next to Type to open the list of valid Change Order Types.
  3. Add the list of Change Orders types in Autodesk Build to Sage 100 Contractor.

Autodesk Build and Sage 100 Change Orders Mapping

Purchase Order Change Orders​

Agave Sync allows you to sync SCOs that reference purchase orders from Autodesk Build to Sage 100 Contractor as additional line items on the original 6-6-1 Purchase Order record. This is because Sage 100 Contractor does natively support modifying 6-6-1 Purchase Orders with 6-4-1 Change Orders.

Note: Your Agave account manager can change which prefix is used to differentiate the change order line items from the original schedule of values.

Autodesk Build and Sage 100 Change Orders Mapping

Does Agave Support Syncing Sub-items from Autodesk Build?​

Yes, Agave supports syncing one level of sub-items from Autodesk Build for the following record types:

  • Subcontracts
  • Purchase Orders
  • Change Orders
  • AP Invoices
  • Prime Contracts
  • Prime Contract Change Orders
  • AR Invoices

To enable syncing for sub-items, ask your Agave Account Manager to enable it for you.

How It Works

Autodesk Build records have a hierarchical structure with:

  • Root items — parent line items
  • Sub-items — child line items
  • Sub-sub items — which are explicitly filtered out (only one level of nesting is supported)

Agave Sync will include root items and their direct sub-items when syncing. Any items nested deeper than one-level are excluded.

Differentiating Revenue and Cost Amounts When Syncing Owner Change Orders from Autodesk​

When syncing Owner Change Orders from Autodesk to your ERP, you may want to separate cost and revenue amounts so that profit (i.e. revenue − cost) can be calculated correctly.

By default, a Change Order line item may generate both cost and revenue in the ERP. Agave Sync provides two ways to mark certain line items as revenue-only, meaning they generate revenue but no cost.

Available Approaches​

1. Revenue-only Cost Code​

A specific Cost Code can be configured as revenue-only.

  • Line items using this Cost Code will:
    • Generate revenue
    • Not generate cost
  • Configuration is enabled by your Agave Account Manager

Best used when:

  • Markups, fees, or similar items are tracked using dedicated Cost Codes
  • You want the rule to apply regardless of Cost Type
2. Revenue-only Cost Type​

A specific Cost Type can be configured as revenue-only.

  • Line items using this Cost Type will:
    • Generate revenue
    • Not generate cost
  • Configuration is enabled by your Agave Account Manager

Best used when:

  • Markups or fees are categorized by Cost Type (e.g., Markup, Fee)
  • You want consistent behavior across multiple Cost Codes

Important Notes​

  • These settings must be enabled by your Agave Account Manager
  • Once configured, the rules are applied automatically during syncs