Acumatica OData
DLH.io documentation for Acumatica OData
Acumatica is a cloud ERP platform covering financials, distribution, projects and CRM. This connector reads the tables and Generic Inquiries that your Acumatica instance exposes through OData, so finance and operations teams can analyze general ledger, receivables, payables, orders, inventory and project data in their warehouse.
Setup Instructions
Follow the setup steps guide for configuring your Acumatica OData connection to enable data to flow into your destination via DLH.
Supported Features
Here are key features supported for this connector.
| Sync Feature | Supported | Details |
|---|---|---|
| Custom Data and Development | ✓ | Ability to enhance connector upon request |
| Historical Re-Load/Load | ✓ | |
| Incremental/Delta Load | ✓ | Tables and Generic Inquiries with a modified-date column are read incrementally; others are read in full |
| Column Selection | ✓ | |
| Column Hashing | ✓ | |
| Re-Sync Table/Entity | ✓ | Select at the table level to reload data history (on next Sync Bridge run) |
| Custom Queries | Utilizing SQL Data Query Connector | |
| Custom Data | ||
| Captures Deleted Rows | ||
| API Sync Bridge Initiation | ✓ | |
| Priority Scheduling | ✓ | |
| Private VPC/Link | ☂ | |
| DLH Data Model Available | - |
If you have any questions about these supported features please reach out to our Customer Support team.
Details on Sync Processing
- Your Acumatica instance must be version 2024 R2 or later, which is required for table-level OData access.
- The connector reads Acumatica's OData endpoints: OData v4 (
/odatav4/) for tables and OData v3 (/odata/) for Generic Inquiries. - Tables with a modified-date column are read incrementally, starting from the previous run with a lookback of at least 60 minutes (Generic Inquiries get an extra 24 hours). Tables without one are read in full on every run.
- The first synchronization and any historical re-sync start at the Historical Start Date, or two years back if none is set. Rows whose modified-date column was never stamped are read separately.
- Requests are limited to 4 concurrent requests and 200 requests per minute, and rate limit responses from Acumatica are retried after waiting.
- This connection is read only and never writes data back to Acumatica.
How Tables Are Determined
This connector has no fixed table list. When you save the connection, DLH.io reads the OData $metadata of your Acumatica instance and builds the schema from it:
- Every table exposed by OData v4 becomes a table in your target, named from the Acumatica table (for example
GL_ACCOUNT,AR_CUSTOMER,IN_INVENTORYITEM). If two tables would share a name, the namespace is added to keep names unique. - Every Generic Inquiry exposed through OData v3 becomes a table whose name starts with
GI_, followed by the inquiry name in upper case. A Generic Inquiry appears only if Expose via OData is ticked on the Generic Inquiry screen (SM208000). - Columns, and which columns are keys, come from the same metadata.
Every exposed table and Generic Inquiry is selected by default. Open the Schema tab to uncheck the ones you do not need. Because the list depends on your instance, view it after creating the connection.
Issue Handling
If any issues occur with the connection simply return to the sources page in DLH.io, edit the source details and click the Save & Test button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.
Replicated Entities
The following entities are replicated by default to your Target Connection. These are the table names you will see in your Target Connection. If you believe any entities/tables are missing please open a ticket with Customer Support:
- View list of entities after creating a connection for the most up-to-date list (tables, plus
GI_tables for Generic Inquiries)