Plan around your account

Feature availability depends on your account, enabled modules and upgrade timing. Match each capability to the workflow you want to improve.

Spreadsheet exports: follow the file downstream

Oracle documents a change from .xls to .xlsx for exports of lists, saved searches and reports. The useful question is what happens after a colleague clicks Export. A workbook may be opened manually, read by a recurring process or dropped into a shared reporting workflow.

Our recommended check is to take a representative export through its full journey. Confirm the file is accepted, key fields retain their intended meaning, and any naming or extension-based automation still behaves as expected. Give the person consuming the file a chance to validate the result.

Report order: make an assumption explicit

For generic-transaction SuiteQL queries and analytics datasets without a specified order, Oracle now uses transaction date rather than transaction display name as the default sorting field. An explicit sort is unaffected.

A result can contain the right records and still be used incorrectly if another step assumes a particular order. Review recurring extracts, first-row selections and manually compared reports. Where order matters, document the required behavior and test it intentionally.

September changes to evaluate with the right owner

Change to reviewPractical check
Manufacturing visibility

The September notes introduce a Production Control Board for reviewing work-order information. Ask production leaders which exceptions they need to see first, who will act on them and whether the available view supports that routine.

Inventory planning context

Oracle describes separate supply-history settings and expanded inventory analysis. Before changing planning assumptions, compare a selected group of items against a known period and have the planning owner explain any meaningful difference.

Saved-search access through REST

The September release adds REST support for retrieving and executing saved searches. Integration owners can evaluate whether this fits a defined use case, with attention to permissions, result shape and error handling.