An item demand plan has an identity or date mismatch
Distinguish the plan’s identity from its item reference and check the complete planning period.
Choose the message that matches your import.
The plan and item identifiers need checking
Message may mention: internal ID.
What it means
The import is not identifying the intended record.
Import context: Item demand plans.
Check this first
Distinguish the plan's identity from its item reference before changing the mapping.
Show the steps
Check the record reference
- Find the field named in the error on the import's Field Mapping page.
- Open its edit control and check the selected reference type.
- Compare that setting with the actual CSV value. A number could be a name, an external ID, or an internal ID. Its appearance alone does not establish the type.
- Locate the intended record in the same account. Confirm its identity and whether it is available for this transaction.
- Correct the file or mapping so they agree. Use a default only when it applies to every affected row.
If you need to see internal IDs, enable them in your personal preferences or include them in a saved-search export. Supported reference types vary by field. Name matching is generally case-insensitive, so changing capitalization alone should not be the standard recommendation.
For a duplicate-record message, determine whether you intend to update the existing record or create a different one. Do not generate new external IDs simply to get past the error. For inactive records or subsidiary restrictions, verify the intended business setup before changing it. Those are account decisions, not text-cleanup operations.
If that looks right
The plan’s body Internal ID identifies the plan for an update. The Item field identifies the item. Check both separately. Read the supported field definitions.
If that looks right
Documentation checked September 16, 2026.
The planning dates are inconsistent
Message may mention: start date.
What it means
The plan dates may conflict with its year or end date.
Import context: Item demand plans.
Check this first
Supply a consistent period instead of changing the start date alone.
Show the steps
Check dates, periods, and address values
Dates
- Check the importing user's date format in personal preferences.
- Compare the actual CSV text with that format, including the year.
- If the date is ambiguous, establish the intended date from the source. Do not guess whether
04/05is April 5 or May 4. - For a period or time range, verify both ends and any accompanying year or view.
- Recheck the saved file after editing it in a spreadsheet.
Use the first check above for this record type. Their requirements are not interchangeable.
Documentation checked September 16, 2026.
Related errors
- NetSuite cannot identify the record to import
- NetSuite says the record already exists
- NetSuite cannot match an item in a CSV import
- The item unit or record type does not match
Still stuck?
We can help you work through the file, the mapping, and the NetSuite setup behind the error.
Talk to MySuite