NetSuite Custom Use Restriction Search Requirements

Configure a custom use restriction search with required summary results, unchanged formulas, and stable grouping to avoid duplicate releases.

·3 min read·26 views·NetSuite 2026.2·View Oracle Docs

A customized saved search for automatic release from use restriction must preserve the supplied calculation formulas and required summary structure. Copy the locked default search to change criteria, and finalize supported grouping fields before processing starts. Later grouping changes—including when switching searches—can create duplicate releases.

When Should You Copy the Default Search?

The SuiteApp uses a locked default saved search to identify candidates for automatic processing. That search is selected during installation or upgrade. If you need different criteria, create a copy and customize it rather than attempting to edit the locked original.

For related coverage, see the automatic use restriction release workflow. Treat the copied search as processing configuration, not simply as a report: its grouping fields define the intended release combinations.

What Must the Customized Search Contain?

Before selecting the copy, verify every requirement below.

RequirementRequired configuration
Search typeTransaction saved search
ResultsSummary results
GroupingFields defining each intended release combination
Currency formula columnExactly one Formula (Currency) column
Formula summary typeSum
Formula custom labelRevenue to be Released
Formula outputA numeric amount
Posting criteriaYes

Preserve the supplied calculation formulas. The requirement for numeric output is not permission to replace the formula logic. You can change search criteria and supported grouping fields before enabling or scheduling automatic processing, but grouping must remain unchanged afterwards.

Set the posting criteria to Yes both when working with the saved search and when creating a customized copy. Include this check before selecting the search for processing.

Which Grouping Changes Can Create Duplicate Releases?

Group only by custom segments, Department, Class, or Location. Do not group by Subsidiary or Restriction. The script uses consolidated parent results and assigns restriction values when creating each transaction.

Finalize grouping before the first script run. After automatic releases begin, historical released amounts are calculated using the original grouping. Changing that structure—including when switching searches—can create duplicate releases.

Classification check: When Classification is selected as a grouping field, the selected classification value must be available on the parent subsidiary. The Release from Restriction transaction is created at that parent-subsidiary level.

For an existing process, compare a proposed replacement search’s grouping against the original before switching. Selecting another search does not remove the requirement to preserve the original grouping.

How Do You Select the Search and Open Its Report?

After confirming that the customized search meets the requirements:

  1. Go to Setup > Company > General Preferences.
  2. Open the Custom Preferences subtab.
  3. Select the customized search in Release from Use Restriction Saved Search.

The selected saved search’s label appears as a center label at NFP Financial Center > Financial. Select its name to view the release from restriction report.

Who This Affects

  • Administrators configuring preferences: Check the search requirements before selecting the copy.
  • Accountants reviewing release combinations: Check supported grouping and parent-subsidiary classification availability.
  • Teams coordinating processing: Settle grouping before the first run and preserve it when switching searches.

For separate accounting workflow coverage, see accounting task criteria and prerequisite ordering.

Key Takeaways

  • Copy the locked default search when different criteria are needed.
  • Preserve calculation formulas, summary requirements, and Posting = Yes.
  • Never group by Subsidiary or Restriction.
  • Keep grouping unchanged after processing starts, including when switching searches.
  • Select the search in Custom Preferences; access its report through NFP Financial Center.

Frequently Asked Questions (4)

Can I edit the locked default saved search to change automatic release criteria?
No. The SuiteApp’s default saved search is locked, so copy it and customize the copy for different criteria. Preserve its supplied calculation formulas and required summary structure.
What configuration must a custom use restriction release search have before I select it?
Use a transaction saved search with summary results and Posting set to Yes. Include exactly one Formula (Currency) column with Sum as its summary type, the custom label “Revenue to be Released,” and a numeric output; preserve the supplied formula logic.
Which grouping fields are supported, and can I change them after automatic releases begin?
Group only by custom segments, Department, Class, or Location; do not group by Subsidiary or Restriction. Finalize grouping before the first script run and keep it unchanged afterwards, including when switching searches, because changes can create duplicate releases.
What should I check when grouping by Classification or switching to a replacement search?
If Classification is a grouping field, its selected value must be available on the parent subsidiary, where the Release from Restriction transaction is created. Before switching searches, compare the replacement’s grouping with the original and preserve the original grouping structure.

Weekly Update History (1)

Accountingadded

Added the topic Automatic Release from Use Restriction in Non-Profit Financial Management.

View Oracle Docs
Source: Selecting a Customized Saved Search for Automatic Processing — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Searches

View all Searches articles →

Also from NetSuite 2026.2

View all NetSuite 2026.2 changes →