EBENSTEAD
Menu
Ebenstead / NetSuite Intelligence

Are your AI scripts relying on OCI settings NetSuite now ignores?

Oracle says ociConfig supplied to the affected SuiteScript AI APIs is ignored without producing an error. Review scripts that depend on those settings or on older free-usage assumptions, rather than treating a successful call as proof the old configuration is honored.

← All NetSuite Intelligence

SuiteScript AICompatibility change
By Ebenstead · Published · Guidance updated · Sources checked
Why it matters

Calls can keep succeeding while an old OCI configuration is ignored, and a deprecated free-usage counter now represents AI Units rather than the old usage pool.

First step

Find ociConfig and legacy usage-counter calls, then verify their actual behavior before changing working scripts.

Suggested owner

SuiteScript developer and AI usage owner

Who should check?

Owners of affected AI API calls in N/llm, N/documentCapture or N/task that pass ociConfig or interpret deprecated free-usage counters. The change concerns the affected API calls, not all N/task operations or AI scripts. The SDF tool-to-toolset migration is a separate change.

Published milestones

  1. 2026.1 — API reference “Since” labelThe llm.getRemainingUsage reference identifies this version; it is not a separate publication date.
  2. August 2026 minor release (NetSuite 2026.2)Oracle documents ignored ociConfig values and compatibility wrappers for deprecated free-usage methods.
  3. No fixed removal date statedThe deprecated method may be removed in a future release; this is not an announced calendar cutoff.

Check your Oracle account notice before scheduling an update.

What to do next

  • Locate the affected method calls and distinguish unused configuration from a dependency that changes expected behavior.
  • Review use of llm.getRemainingUsage and the documented corresponding methods, then test usage monitoring and error handling without exposing credential material.
  • Test a representative AI workflow, agree any code or control changes, and prepare a rollback plan before deployment.

What we’ll review

The selected method calls, with credential values removed; expected usage, enabled features, provisioned AI Units, execution roles, monitoring thresholds and approved sample tests.

See the approach

See a related project

See our script-readiness approach →
Sources and updates

Oracle documentation

NetSuite 2026.2 August minor release ↗Oracle publication/update date not stated on this page. · Source checked:
llm.getRemainingUsage API reference ↗Oracle publication/update date not stated on this page. · Source checked:
llm.getRemainingFreeUsage deprecation notice ↗Oracle publication/update date not stated on this page. · Source checked:
NetSuite AI Units and NetSuite features ↗Oracle publication/update date not stated on this page. · Source checked:

Update history

  • 2026-10-18 — Published this guide using existing Oracle documentation.

Follow this topic via RSS

Let’s discuss your NetSuite needs

Tell us what you need help with.

This form sends us a message. It does not connect to NetSuite or sign you up for marketing emails.

Topic: SuiteScript AI Usage Compatibility Check

Please leave out passwords and sensitive records. We’ll use your details to reply, not subscribe you to marketing. Privacy information.