SAP SD ERROR SOLUTION  |  Customer Number Assignment (XD01)

SAP SD Error: "Acct Group Sold-to Party 0001 Uses Ext. No. Assignment. Specify an Account Number" – Step-by-Step Fix

A user creates a customer with the account group Sold-to party and SAP stops because the account group uses external number assignment and no number was given. This guide explains the message, internal and external number assignment, the exact FBN1, XD01 and FS00 steps with the original screenshots, the reconciliation account, how to verify the result and how to avoid the error in future. If you run into any errors while following along, feel free to send a screenshot to pramod@learntosap.com for help.

❌ The Error Message at a Glance

SAP error account group Sold-to party 0001 uses external number assignment specify an account number
ItemValue in This Example
Message textAcct group Sold-to party-0001 uses ext. no. assignment. Specify an account number
Account group0001 (Sold-to party)
Number assignmentExternal
ModuleSAP SD (customer master) with FI
Where to fix itFBN1 as in the original, then XD01 and FS00
ResultCustomer can be created with a valid account number

The account group and the numbers in your own message may differ from this example. The same method applies with your own values.

📑 What You Will Learn in This Guide

  1. What the message means
  2. Internal and external number assignment
  3. Why the error appears
  4. Where you meet the error
  5. Diagnose the problem
  6. Solution: remove the external mark and create the customer
  7. Two ways to solve the error
  8. The reconciliation account
  9. Values used in this guide
  10. Notes before you save
  11. Verify the fix
  12. Real-world scenario
  13. Common mistakes
  14. Troubleshooting
  15. Prevent the error
  16. Frequently asked questions

✅ SAP Error Fix: Sold-to Party 0001 – Specify Account Number

This message appears when you try to create a customer with the account group Sold-to party (0001), but the system has no customer number to use. The account group is set up for external number assignment, which means SAP does not generate the number by itself. You must specify an account number, and the number has to fall inside the interval that was defined for that account group.

In simple words, the account group says "the user will choose the number", and the user left the number field empty. The message is therefore not a system fault. It is a reminder, and it is solved either by entering a valid number or by changing how the number range works. This guide follows the steps of the original tutorial and then explains the background, so you understand which option fits your company.

📝 Internal and External Number Assignment Explained

Every customer account group has a number range that controls how the customer number is created. The table compares the two types.

TypeHow the Number Is CreatedTypical Use
InternalSAP picks the next free number automatically.Most day-to-day customer creation.
ExternalThe user types the number within an allowed interval.Companies that load numbers from another system or follow their own numbering scheme.

The type is stored with the number range of the account group. When the range is external and the field is left empty, SAP shows the message in this guide. The exact transactions for maintaining customer number ranges and for assigning ranges to account groups differ by release, so confirm them in your own system.

💡 Why Does This Error Appear? Common Causes

CauseWhat Is Wrong
Empty customer numberThe account group uses external numbers, but no number was entered.
Number outside the intervalA number was entered, but it is not inside the allowed external range.
Range set to external by mistakeThe number range was marked external, although the company wants internal numbers.
Wrong account groupThe user chose Sold-to party (0001) where another group with internal numbers was intended.
Migration settings left onExternal numbers were switched on for a data load and never switched back.

In daily work the first and fourth causes are the most common. A user opens the customer creation screen, picks the default account group and presses enter without noticing that the number field is mandatory.

📋 Where You Meet This Error in Daily Work

The message can appear wherever a customer is created:

Because the message appears at the start of the process, it is easy to fix once the cause is clear.

🔧 Step-by-Step: Diagnose the Problem

1

Read the message. Note the account group, here Sold-to party 0001.

2

Check the number range of the account group. See whether it is external or internal and which interval is allowed.

3

Ask the master data team. Confirm whether the company wants to enter numbers by hand or let SAP create them.

4

Check the reconciliation account. Make sure a suitable account exists in FS00 for the company code.

5

Plan the change. Decide whether to enter a valid number or to change the range, and note who approves it.

✅ Solution: Remove the External Mark and Create the Customer

SOLUTION – TCODE – FBN1 REMOVE EXT MARK

Follow Steps

1

Go to Tcode FBN1. Remove the external mark.

SAP FBN1 remove external mark number range
2

Select – then creating customer XD01.

SAP XD01 create customer sold-to party account group 0001SAP XD01 customer creation screen with account number
3

Select – the required reconciliation account FS00.

SAP FS00 reconciliation account for customerSAP FS00 customer reconciliation account settings before saving
4

Save. SAP shows a message that the customer was created.

Check before you change number ranges: In many systems, FBN1 maintains the number ranges of accounting documents, while customer number ranges are maintained with a different transaction, often XDN1. Follow the original steps on the screens shown in the screenshots, and compare them with your own system before you change anything in production.

🔄 Two Ways to Solve the Error

OptionWhat You DoWhen to Choose It
Enter a valid numberType a customer number inside the allowed external interval.The company wants control over customer numbers.
Switch to internal numbersRemove the external indicator so SAP creates numbers automatically.The company prefers automatic numbering and has no external system supplying numbers.

The original tutorial removes the external mark, which is the second option. Both are valid, but changing a number range is a configuration change that affects every new customer of that account group, so agree it with the master data team first and move it through the transport process.

💰 The Reconciliation Account for Customers

When a customer is created for a company code, SAP asks for a reconciliation account. This is a G/L account that collects the postings of all customers of that company code, so the total of the customer accounts always matches the general ledger. The account is created or checked with FS00 and must be marked as a reconciliation account for customers.

If the account is missing or has the wrong type, the customer cannot be saved, or the system shows a new message. That is why the original tutorial ends with selecting the required reconciliation account. Agree the account number with the finance team, and use the same account for all customers of the same type, unless the business needs separate accounts for different customer groups.

📋 Values Used in This Guide at a Glance

The table below summarizes every step from the guide, so you can compare it with your own screen before saving.

ItemValue UsedNote
Account groupSold-to party (0001)Uses external number assignment
First stepFBN1, remove external markAs in the original tutorial
Customer creationXD01Create the customer
Reconciliation accountFS00Required for the company code
Final actionSaveAssign a customizing request if prompted

📝 Notes Before You Save

✅ Verify the Fix

After saving, create the customer again with XD01. If the range is internal, SAP should propose a number automatically. If it is external, enter a number inside the allowed interval. Fill the company code data with the reconciliation account, and save. Then display the customer with XD03 and confirm that the account group, the number and the reconciliation account are correct. If another message appears, for example about a missing sales area, the first problem is solved and the next setting needs attention.

💼 Real-World Scenario: Creating a Sold-to Party at Learn Pharma, Pune

At Learn Pharma in Pune, master data clerk Pooja Patil tried to create a new customer with the account group Sold-to party. SAP stopped her with the message that account group 0001 uses external number assignment and an account number must be specified. She asked functional consultant Neha Deshmukh for help.

Neha checked the number range and found that the range had been left external after a data migration. With master data lead Sameer Joshi she agreed that the company wanted automatic numbers, followed the original steps to remove the external mark, and saved the change on a customizing request. She also checked the reconciliation account with FS00.

After testing in the quality system, the transport moved to production. Pooja created the customer with XD01, SAP proposed the number and the customer was saved. Neha recorded the change in the configuration workbook so that the next migration would end with a checklist item to switch the setting back.

📝 Designing a Customer Numbering Scheme

If your company keeps external numbers, a clear scheme makes life easier. A common approach is to reserve intervals for different customer types, for example one interval for domestic customers, one for exports and one for internal companies. The interval then tells anyone reading a number what kind of customer it is, and a quick check can find numbers used in the wrong range.

IntervalCustomer TypeRule
Low intervalDomestic customersCreated by the master data team.
Middle intervalExport customersCreated after a credit check.
High intervalInternal or one-time customersCreated only on approval.

The intervals above are only an example. Agree your own with the master data and finance teams, write the rule into the work instruction, and review it once a year.

📦 Number Ranges During Data Migration

Data migration is the most common reason why an account group ends up with external numbers. When customers are loaded from an old system, the project often wants to keep the old numbers, so the range is switched to external for the load. If nobody switches it back, every later user meets the message in this guide.

Plan the switch as part of the migration checklist. Name a responsible person, set a date, and test customer creation with a normal user after the load. Also check that the numbers loaded do not collide with the internal interval, because a collision would block the next automatic number. A short checklist at the end of every migration prevents this error and saves the support team a lot of time.

❗ Common Mistakes When Fixing This Error

🔧 Troubleshooting: When the Message Still Appears

SymptomLikely CauseWhat to Check
Same message after the change.The transport has not reached this client.Check the request status and import it.
Number is rejected.It is outside the allowed interval.Check the interval of the number range.
Customer cannot be saved.Reconciliation account is missing or wrong.Check the account in FS00.
Message appears for another account group.Other groups also use external numbers.Check all account groups in use.
Cannot change the range.Missing authorization or locked request.Ask for the right role or an open request.
Remember: Most repeat messages come from a transport that has not arrived, or from another account group with the same setting.

✅ Best Practices for Customer Number Ranges

🛡 How to Prevent This Error in Future

📱 This Message in SAP S/4HANA

In SAP S/4HANA, customers and vendors are normally created through the business partner, and number ranges are maintained for business partner groupings. Screens and transactions therefore differ from the classic examples used here. Confirm the exact steps in your own release before you plan the work. The principle does not change: the number range decides whether the number is entered by the user or created by SAP.

🔄 What to Do After the Fix

Once the customer is created, finish the job. Extend the customer to the sales area, check the partner functions and the payment terms, and test a sales order. Update your configuration documentation with the final number range setting and the transport number.

If your company later migrates more customers, plan the number range first. Decide whether the migration needs external numbers, use them only for the load, and switch the range back afterwards, with a named person responsible for the switch.

🎓 Interview-Style Questions and Answers

Q: What does external number assignment mean?
The user enters the number by hand, inside an allowed interval.

Q: Why did SAP ask for an account number?
Because the account group Sold-to party uses external number assignment.

Q: How can the error be solved?
By entering a valid number or by changing the range to internal.

Q: Which account is needed when a customer is created?
A reconciliation account in the company code data.

Q: Is a transport needed?
Number range changes are customizing and normally move through the landscape.

📚 Quick Glossary of Terms Used in This Guide

🎯 Conclusion

The error "Acct group Sold-to party 0001 uses ext. no. assignment. Specify an account number" has a simple cause: the account group expects a number that the user did not give. Follow the steps in this guide: remove the external mark as shown in the original tutorial, create the customer with XD01, select the required reconciliation account with FS00 and save. Then test the customer and record the setting. If you run into any errors while following along, feel free to send a screenshot to pramod@learntosap.com for help.

❓ Frequently Asked Questions

The account group Sold-to party (0001) is set to external number assignment. That means SAP will not generate the customer number automatically, and you must type a number yourself when you create the customer.
Transaction XD01, create customer. After the number range setting is handled, the customer is created and the reconciliation account is selected.
It is a number range setting where the user enters the customer number manually, within an allowed interval. The opposite is internal number assignment, where SAP picks the next free number.
A G/L account, normally maintained with FS00, that collects the postings of all customers in the company code. It is required in the company code data of the customer master.
The original steps use FBN1 to remove the external mark. FBN1 is commonly associated with number ranges of accounting documents, so confirm in your own system which transaction maintains the customer number range, which is often XDN1.
A change to number ranges or account groups is customizing and normally goes through the transport process. Creating the customer itself is master data and does not need a transport.