> For the complete documentation index, see [llms.txt](https://help.besmart.software/erpc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/erpc/quick-start-guide/basic-erp-connector-connection-principles.md).

# Basic ERP Connector Connection Principles

To enable data exchange between Autodesk Vault Professional and the ERP system via the ERP Connector, a shared "connection point" is required. This connection point is established through a so-called *Data Interface* (*DI*) created in a dedicated Microsoft SQL database. Both Vault Professional/ERP Connector and the ERP system connect to this database, allowing them to send (export) and read (import) data as needed.

<figure><img src="/files/opadEYo2jG0U0eIiYHQE" alt=""><figcaption><p>A schematic of the Vault/ERP system connection, with the Data Interface serving as middleware</p></figcaption></figure>

Before installing/implementing the ERP Connector, the Microsoft SQL database must be available for the ERP connector to connect to. After that, the ERP Connector can automatically create the necessary tables (DI) in the database, making it ready for the ERP system to be connected. If not agreed upon otherwise, it's up to the ERP system vendor to connect to the database (DI). &#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.besmart.software/erpc/quick-start-guide/basic-erp-connector-connection-principles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.