Be.Smart ERP Connector
(EN) ERP Connector
(EN) ERP Connector
  • ℹī¸What is ERP Connector?
  • ⚙ī¸System Requirements
  • 🔑Installation & Activation Guide
  • 🆕What's New
    • Versions 30.1.0.6, 29.3.0.5, 28.8.0.5 & 27.14.0.5
    • Versions 30.0.0.3, 29.2.1.2, 28.7.3.3 & 27.13.0.5
    • Versions 28.7.1.1, 27.13.0.1
    • Versions 29.2.1.0, 28.7.1.0, 27.13.0.0
    • Versions 29.1.0.0, 28.6.0.0, 27.12.0.0
    • Versions 29.0.0.1 & 28.5.1.1
  • Data Interface - Reference Manual
    • Abbreviations
    • Data interface
      • Data tables, relations
        • Table EcENTITY
        • Table EcASSOC
        • Table EcLINK
        • Table EcLOG
        • Stored procedure EcWriteEntity
    • Exporting data from a Vault
      • Properties / Attributes
      • Associations
      • Links
      • Reading data from data interface
        • Workflow sample
        • Another samples
    • Importing data into a Vault
      • Mandatory EcENTITY table fields
      • Default values
      • LifeCycle States
      • Writing data into data interface
        • Using SQL Stored Procedure
          • Example #1 – insert single EcENTITY record
          • Example #2 – insert two associated EcENTITY records
        • Using SQL syntax
        • Using SQL Management Studio
    • SQL views
      • ERP data displayed dynamically in VE Tab
        • SQL view definition sample:
      • ERP synchronized enums
    • Logging
    • Using thumbnail image data
Powered by GitBook
On this page

Was this helpful?

What is ERP Connector?

NextSystem Requirements

Last updated 24 days ago

Was this helpful?

Be.Smart ERP Connector is an add-on to Autodesk Vault Professional, allowing automatic bi-directional communication between Autodesk Vault and ERP systems.

ERP Connector connects the design department with the rest of the company, allowing dynamic ERP values like stock inventory, purchased items, invoices, etc., to be accessed from Autodesk Vault, whereas the design documentation can be accessed from the ERP system.

Communication is based on SQL interfaces, and the automation is ensured by a Job Processor.

ℹī¸