Skip to main content

Purchase Orders

Visual Mapping​

Autodesk Build and Acumatica Purchase Orders Visual Mapping

Autodesk Build and Acumatica Purchase Orders Visual Mapping

Autodesk Build and Acumatica Purchase Orders Visual Mapping

Configuration Notes​

Status​

By default, Agave maps the "Approved" status in Acumatica to the "Executed" status in Autodesk Build. If you need a different status mapping, contact your Agave account rep.

Inventory ID​

When syncing Purchase Orders from Autodesk to Acumatica, Agave sends an InventoryID to each Acumatica line item based on the Account Group. This ensures that proper GL Account, tax, and other defaults are set.

See Setting Up Non-Stock Items for how to configure these.

Terms​

When syncing Purchase Orders from Autodesk to Acumatica, default terms must be set up on the corresponding Vendor in Acumatica:

Autodesk Build and Acumatica Subcontracts Visual Mapping

Branch​

The Branch set on the Purchase Order and its Line Items comes from the Branch selected in the project's Billing and Allocation Settings:

Autodesk Build and Acumatica Subcontracts Visual Mapping

Common Errors and FAQs​

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.