An asset number range defines which identifiers may be used for fixed-asset master records in SAP Asset Accounting. An internal range lets SAP assign the next number; an external range requires a user or connected system to provide a permitted identifier. The relevant asset class and company-code settings control how numbers are assigned.
Why the identifier matters
When a business buys ten similar forklifts, each physical asset needs a distinct master record even if all ten use the same asset class. The class groups accounting treatment; the number identifies the particular record for acquisition, depreciation, transfer, retirement and audit tracing. Numbering is therefore a data-governance decision, not a substitute for correct classification.
In SAP FI-AA an asset can also have subnumbers, allowing components or portions to be tracked under a main asset. A subnumber is not the same as a separate asset class, and its assignment rules must be evaluated separately.
Internal versus external assignment
Internal assignment usually suits routine asset creation: the application selects a number from the configured interval, reducing manual keying and accidental collisions. External assignment may suit controlled migration or alignment with an approved legacy identifier, but it introduces the need to validate incoming values and reject duplicate or out-of-range IDs.
Number intervals are configured in the company-code context, while relevant range assignments and internal/external behavior are governed through asset-class configuration. SAP also documents a cross-company-code assignment option, so identical-looking numbers across legal entities must be interpreted with their organizational context.
Example: onboarding a packaging machine
A manufacturer capitalizes a new packaging machine. The asset accountant selects the machinery asset class and correct company code, then checks whether the record should receive an automatically generated number. If the machine came from a legacy system, the team may instead need an approved externally assigned identifier and documented migration mapping.
The decision is not whether “machine 0098” is easier to remember. The decisions are whether the identity stays unique, supports traceability, fits the approved interval and continues to align with accounting controls.
Controls and consultant checks
Test a valid new ID, a duplicate external ID, an out-of-range value and the behavior near interval exhaustion. Check whether interfaces and migration files preserve company-code identity, whether users have permission to create records, and whether subnumber conventions are documented. Reserve sufficient range capacity before a rollout or acquisition.
Do not assume every deployment uses the same interval lengths, screen behavior or asset-numbering policy. Confirm settings in the target SAP release and organization rather than treating a sample range as universal.
Related Knowledge
See asset classes, Asset Accounting organizational structure and G/L account master data for neighboring controls. Return to SAP FI / FICO.