ERP indirect access: does extracting data for AI trigger license fees?

What is ERP indirect access?#

ERP indirect access is the use of an ERP system's data or functions by people, devices or software that reach it through another application instead of logging in with their own license. A web store that creates sales orders, a MES that posts production confirmations or a customer portal that shows order status can all count as indirect access, depending on the contract.

Vendors have pursued license fees for this kind of use, and some have moved to models that count documents or transactions created by connected systems rather than named users; the phrase digital access is often used for these. The details are vendor-specific and contract-specific, which is why the answer always starts with your own agreement.

Manufacturers feel this most because their ERP sits in the middle of quoting, production planning, quality and shipping, with MES, QMS and EDI connections all around it.

Does extracting data for AI count as indirect access?#

Extracting data for AI licensing is usually lower risk than an operational integration, but whether it counts as indirect access depends on how the data leaves the ERP and what your license says. A licensed administrator running standard exports of historical records is a different fact pattern from a third-party tool reading the database continuously.

The buyer of a licensed dataset never touches the ERP; it receives prepared files. Most indirect access disputes concern ongoing use of the system for the benefit of unlicensed users, not one-time copies of historical records. Still, some agreements restrict extraction methods, database-level access or use of the software for third parties' benefit, so read those clauses before choosing a method.

Export patterns that lower licensing risk#

The safest export patterns use tools the vendor documents for the purpose. Oracle's NetSuite help, for example, lists several ways to extract data, including exporting saved search results to CSV, exporting reports, writing a SOAP web services program and using SuiteAnalytics Connect, and notes that ODBC access is an additional service with a fee. The extraction route itself can carry a cost.

On-premises systems raise a different question. An older SAP blog post describes copying an active SAP Business One database on the SQL Server edition by restoring a backup under a new database name; the HANA edition uses different tooling. Whether reading that copy with third-party tools is allowed is a license question to confirm before relying on it.

• 1Use the vendor's standard export, report or archive functions, run by a licensed user.
• 2Prefer a one-time historical extract to a recurring connection, and remove any temporary connection when done.
• 3For on-premises systems, check whether the license allows copying the database to a separate non-production environment.
• 4Do not create new integration or API users without checking how the license counts them.
• 5Never write data back into the ERP as part of a licensing project.
• 6Log the date, user, tool and tables or reports for every extraction.

Which ERP records manufacturers usually extract#

Manufacturers usually extract records that show decisions and outcomes rather than master data alone. Quote-to-order history, production orders with schedule changes, nonconformance reports, CAPAs, supplier exceptions and maintenance work orders are the families AI developers ask about.

Exclude customer-owned designs and drawings and any export-controlled technical data at the extraction step, not just from the final dataset. Keeping them out of the export means they never land in a staging folder someone later forgets.

Data ownership and access rights are different questions#

Owning your ERP data does not settle how you may reach it. Cloud ERP terms typically treat the records you put in as your customer data; Oracle's NetSuite terms, for example, define Customer Data as content the customer provides that is stored in or run through the service. That supports your ownership of the records.

Access is governed separately, by the license metric, the use definitions and any limits on tools and interfaces. A company can own every record in its ERP and still owe fees if it reaches them in a way the license counts as a separate use. Keep both questions on the checklist, and answer the access question before the first export runs.

What to have ready if an ERP license audit asks about exports#

An ERP license audit that asks about exports is easier to answer with a short file prepared at the time than with recollections a year later. Auditors typically want to know which users and interfaces touched the system, how often and for what purpose.

Keep the extraction log, the names of the licensed users who ran each export, confirmation that any temporary connection was removed and the license clauses you relied on. If a reseller or vendor answered a written question about the method, keep that exchange with the file. The same record later supports the provenance documentation a data buyer asks for, so the work is done once.

Illustrative: a contract manufacturer plans a one-time extract#

Illustrative: a fictional contract manufacturer of machined components runs an on-premises ERP, a separate QMS and a MES integration that once prompted a licensing discussion with its ERP reseller. It wants to license nonconformance, CAPA and quote-to-order history.

The CTO's team reads the license agreement's definitions of use and access and confirms its rights to non-production copies. A licensed administrator runs standard report exports from the sales and quality modules and a one-time, read-only extract from a database copy in an isolated environment. No new integration accounts are created, nothing writes back to the ERP, and every extraction is logged. QMS records are exported through the QMS vendor's own tools under its terms, and customer drawings are excluded at the source.

The data stays in the manufacturer's own storage during preparation, and the extraction log becomes part of the dataset's documentation.

How SourceX approaches ERP extraction#

SourceX does not connect to supplier ERPs. Under the SourceX five-step transaction, the supplier's own team runs exports during Preparation using methods its license supports, and large datasets stay in the supplier's storage or ship on encrypted drives.

The extraction method, systems and exclusions are recorded in the SourceX Evidence Packet as part of provenance, so the supplier approves a dataset whose origin and handling are documented.