“To generate this document, first define the numbering series” in SAP Business One®: what to check

You open a document or choose Add, and SAP Business One refuses with a numbering series error:

To generate this document, first define the numbering series in the Administration module

We found no confirmed report of this message from the Service Layer or the Web Client.

In plain terms, SAP Business One can’t find a series this user may use for this document and date. That’s our reading. Start with the row that matches what you see. The order is our suggestion too.

SAP’s page: message 10000867.

SAP’s help says only superusers can create and maintain document series, so you may need yours for the changes below. These paths assume Permit More than One Document Type per Series is off (Company Details, Basic Initialization tab). If it’s on, SAP uses different windows for series, and SAP’s journal entry rule in section 4 is stated only for that setting being off.

1. No series for the new period indicator

This only applies if your posting periods use a period indicator per year. If everything is on Default and numbers simply continue, go to section 2.

SAP’s support post explains the pattern. Most documents must use a series with the same period indicator as the posting period of the posting date. A series under another indicator can’t be used, even if it’s the default. A new marketing document opens with today as its posting date, so once today falls in the new period, a document type with no series under the new indicator shows this message as soon as you open it. SAP’s example is a Goods Receipt PO.

1. Open Administration > System Initialization > Posting Periods and read the new period’s Period Indicator.
2. Open Administration > System Initialization > Document Numbering and double-click the row number of the document. This opens the series window for that document.
3. Look for a series with that indicator in the Period Ind. column.
4. If there isn’t one, add it, with its own number range, the same Group as last year’s series and the new indicator. Then choose Update in both windows. If SAP refuses the range because it overlaps, see “Adding or changing a series” below. Our year-end checklist has the full set-up.

Check each document type you use, because each has its own series. SAP’s pages differ on which date decides what the series dropdown offers: its training page says the system date, and its support post says the posting date. So a backdated document may not offer the series you expect. Try the dates on a test company. In your live company, a test document uses up a number and can post stock and journal entries.

SAP’s post: Document Numbering Series under different Period Indicators.

2. The user has no authorization or no default series

• No authorization. SAP’s training page says a new user has no access to any series, even the default, and can’t open the document’s first window until authorized for the series group. Set it in Administration > System Initialization > Authorizations > General Authorizations, under Numbering Series, which has one entry per group. The group number is in the series window’s Group column. SAP has a knowledge base article titled “Users are unable to access numbering series”, whose symptom is this message. A 2009 user says to log the person out and back in after you change the authorization.
• No default series. SAP’s help says each user’s default series must be defined, or the user can’t open that document’s first window. In the series window, specify the group, select the series and choose Set as Default. Pick the option for the users you need, then choose Update in both windows. Users must be authorized for the group of their default series.

Don’t stop here if the rights look fine. One user in a multi-branch company in 2023 reports the message despite full authorization, with no accepted fix, and a 2009 report came from the manager superuser. If only one user is affected, check that user’s own default series. It can differ from everyone else’s and not show as the default in the setup window, and it may be locked or used up. A forum answer on that 2023 thread suggested this, although with multiple branches SAP limits Set as Default (section 5).

3. The series is locked or used up

• Locked. SAP’s help says that once Lock is selected, no more documents can be created in that series, and to make sure another series is the default. It doesn’t tie this to the message. SAP’s forum team told a user with this error to check for it (2009), though that series turned out not to be locked, and users and partners name it too. If the period still needs that series, clear Lock. If not, set another series as default.
• Used up. SAP ties the message to numbers running out only in its Period-End Closing post, about the journal entry series (section 4). Users report the same on ordinary documents (2009, 2020). In the series window, compare Next No. with Last No. To extend it, raise Last No. if that doesn’t overlap another series, or set another series with enough numbers as default.
• Another document’s series. A 2020 user on the DI API got this on a receipt from production when the Goods Issue series had run out, though the receipt’s own series was fine. So look at the documents the transaction creates, too. That user says the same receipt still posted from the desktop client, so this may be limited to the DI API.
• An approved draft. SAP’s forum team said in 2009 that a draft uses its old series when it’s added, and suggested raising Last No. on that series if it doesn’t overlap, or adding a new document for approval. So if only drafts fail, check the draft’s original series. That’s one old thread.

4. The journal entry series, and Period-End Closing

Unless you use multiple branches, SAP says a document’s journal entry always takes the default journal entry series, and the system doesn’t check that series’ period indicator. So, as we read it, it doesn’t need a series per year, but it must be unlocked and have numbers left.

SAP’s support post on Period-End Closing covers [Message 131-3] and gives two causes: a multiple-branch issue fixed in 9.3 PL07 (SAP Note 2701315), and, on later versions or without branches, the default journal entry series running out. The closing creates 2 journal entries per row, so 1,500 rows need 3,000 numbers, and a series that looks fine can still run short. SAP’s fix is to raise Last No. or set another series with enough numbers as default.

Users with the “entered Posting Date” text point the same way. One on the HANA version fixed it with “Unlock the JE series” (2021), and another says the default journal entry series came locked on a new system (2022). A user quoting SAP Note 2940618 lists that text as a bug or system limitation, and says to check multiple branches and differing period indicators. We couldn’t open the note. SAP’s knowledge base article 3328560 covers that text on 10.0, but its cause is behind a login.

SAP’s post: Document Numbering error when running Period-End Closing.

5. With multiple branches

The journal entry rule changes. SAP says the system takes the first unlocked journal entry series defined for the current period and assigned to the branch. SAP’s help says you can add transactions only if a series is assigned to that branch or available to all branches. So each branch needs an unlocked series for the new period, assigned to it or open to all branches. SAP also says that once one series is assigned to a branch, all the others must be too.

Set as Default isn’t available here for marketing documents or journal entries. SAP Support staff explain that the system picks the first series per branch, and the user can switch it on the document. One user replied that after a new year with period indicators, people couldn’t add transactions until they locked the old series (2023). That’s one report, and we couldn’t test it. Locking stops further documents in that series, so anyone posting late to the old year can’t use it. Our year-end checklist says not to lock last year’s series until the last posting is done, so check with finance first.

6. From an import, the DI API or an integration

• Send the series key, not a name. Series is a number that points to the series. One DI API user (2017, adding a business partner) had Series = 1 when it had to be 70. In 2009, another user with a loosely quoted -5002 error was told to remove the Series line and reported it solved. One integration vendor says to map a supported series or leave the field empty so the default applies. With no series sent, the document goes to the default series, so check which one that is.
• DTW takes the same numeric key in its Series column, according to a 2019 user. We found no SAP template page for it.
• Find the key by reading it. Users check it with a read-only query, for example SELECT Series, SeriesName, Indicator, Locked, NextNumber, LastNum FROM NNM1 WHERE ObjectCode = '13' AND DocSubType = '--' (SQL Server form; a 2019 answer uses those two filters for A/R invoices, so change them for other documents). In the DI API, SeriesService has GetDocumentSeries and GetDefaultSeries. For the Service Layer, SAP Support staff pointed to SeriesService_GetDocumentSeries in 2021, and a 2024 answer from an SAP expert says to query the Series entity instead, so try both.
• Never change these tables with SQL. SAP’s guidelines don’t allow direct updates to system tables. One user ran a delete on NNM1 in 2023, got overlap errors and could only recover from a backup.

Adding or changing a series: two more errors

You can meet these in the same window, while fixing the first error.

“Series Primary overlaps object AR Invoices”. The new range runs into another series. SAP’s help says you can’t define overlapping series for one document type, and that you must first set Last No. on the previous series to close its range. Primary has no last number by default.

SAP’s year-end guide also says you can restart with the same document numbers under a new indicator per fiscal year, and warns that with the same numbers in two periods, you can’t select different period indicators in report selection. That and SAP’s help don’t square, and a 2008 forum answer reads the rule as “within the same period indicator”. We couldn’t test which is right, so for a new set-up the safe choice is a range that overlaps nothing, for example 1001-1999 and 2001-2999. If your company already restarts at the same numbers each year, follow what worked last year, and ask your accountant before you change that. A prefix doesn’t clearly solve it: SAP’s notes on this differ, and one 2023 user on 10.0 got no fix that way.

“Invalid series next number [Message 3535-3]” or “invalid series initial number”. SAP’s 2011 post lists the checks: First No. or Next No. missing, an overlap, Next No. more than one above Last No., or First No. above either of them. It says this doesn’t necessarily mean corruption. Users add that someone posting during your update can move the real next number, so do it when nobody is working. If the checks are clean, or you can’t correct the values in that window, open a support case. A user quoting SAP Note 1534463 says to log a ticket if that note’s queries return rows. We couldn’t open the note.

Users also report Help > Support Desk > Restore > Restore Numbering File clearing it (2011), with a backup first. SAP’s authorization guide lists the option, but we found no SAP page on what it does. The user who suggested it says it corrects numbers for all modules, so it isn’t a narrow fix and it could affect your numbering. Another user, on 10.0 with a different error (“This entry already exists in the following tables”), was still running it several times a week with no root cause. Treat it as a stopgap, and ask SAP support or your partner first.

What SAP’s help says you can change:

SAP doesn’t name a country for that legal rule, and we didn’t find a US source, so ask your accountant before you create a gap or restart numbers. Administration > Utilities > Check Document Numbering finds duplicated and missing numbers. SAP’s year-end guide says it checks within the number ranges, so a gap between ranges isn’t reported.

SAP’s page: Document Numbering – Setup.

Messages that look similar

Quick answers

← All guides