What Is the SAP Customer Number in License Contracts?
If you work with SAP systems, you’ve likely come across the term “SAP Customer Number.”
But what exactly does it mean, and why is it so critical in managing license contracts and system landscapes?
This article explains the meaning, purpose, and role of the SAP Customer Number—from contractual and technical perspectives—and explores how it functions across corporate groups and in license consolidation projects.
Definition of the SAP Customer Number
The SAP Customer Number is a unique identifier assigned by SAP to each legal entity.
It serves as the primary key SAP uses to identify a customer for license management, support, and installation tracking.
Purpose of the Customer Number
The main purpose of the Customer Number is to link SAP software licenses, installations, and support services to a specific legal entity.
This structure enables:
- Accurate management of license and contract information
- System registration and license key issuance
- Assignment of S-Users for support portal access
Contractual and Technical Implications of the Customer Number
Contract Perspective
- Each Customer Number holds its own set of installations, contracts, pending orders, and invoices—deletion or consolidation is therefore restricted.
- Only the contractual entity is allowed to use the licenses. However, under an Affiliate Clause, subsidiaries or affiliates may also use them if defined in the agreement.
- During periodic SAP License Audits, SAP reconciles Customer Numbers, Installation Numbers, and user counts.
- Contract terms such as product scope, license quantity, and maintenance coverage are defined per Customer Number.
Technical Perspective
License keys are generated using a combination of Customer Number + Installation Number. Key registration activates the system for use.
Typical fields include:
- Customer Number: Contracting entity identification
- Installation Number: System installation unit (multiple per entity possible)
- System ID (SID): Three-character system identifier
- Hardware Key: System-specific 11-character alphanumeric key
S-Users, who access the SAP Support Portal or OSS, are tied to the Customer Number. Once removed, those users become invalid.
How Corporate Groups Manage Customer Numbers
There are generally three patterns for how groups handle Customer Numbers:
- Each company holds its own Customer Number
- The holding company owns one consolidated Customer Number
- Both the holding and subsidiary companies each hold separate Customer Numbers
The optimal pattern depends on goals such as cost efficiency, governance control, or ease of global system rollout.
What Is Customer Number Consolidation?
Customer Number Consolidation means merging multiple Customer Numbers into one.
Effectively, it’s a re-design of contracts to unify licensing, maintenance, and support within a corporate group.
Such consolidation can lead to measurable benefits:
- Reduced total maintenance and license costs
- Simplified contract management
- Greater efficiency for global SAP operations
Industries undergoing frequent M&A activity—particularly automotive and semiconductors—often face this issue during post-merger contract integration.
Key Challenges in Customer Number Consolidation
While consolidation offers benefits, it comes with several practical and legal difficulties:
- Differences in contract conditions: Pricing, license types, and affiliate coverage vary by company. SAP may need to reprice licenses.
- Different license models: Earlier ECC Named User models versus S/4HANA FUE models must be aligned.
- Inconsistent maintenance agreements: Different renewal cycles or service scopes require redesigning maintenance structures.
- Legal entity structure: Affiliates must meet control relationship requirements; joint ventures or equity-method companies may not qualify.
- Assignment restrictions: SAP contracts typically prohibit transfer without SAP’s consent.
- Mixed licensing types: On-premise, private cloud, and public cloud contracts coexist, requiring rationalized license models.
- System architecture differences: ECC, S/4HANA, and hybrid deployments require careful license conversion planning.
- License audit risks: Consolidation may trigger SAP measurement activities, potentially exposing excess or indirect usage.
- Internal cost allocation: Unified contracts demand transparent cost-sharing rules within the group.
Summary
The SAP Customer Number is the central identifier tying together contracts, licenses, installations, and support relationships with SAP.
How your organization manages this number directly impacts license compliance, cost transparency, and governance efficiency.
For corporate groups, deciding whether to manage Customer Numbers separately or consolidate them is a strategic question—not merely an operational one.
In times of ongoing M&A and digital transformation, taking a structured, strategic approach to Customer Number design is key to maintaining effective SAP governance.
References:
Overview of SAP Clients in System Architecture Configuration
An overview of SAP clients when structuring an SAP system landscape—explaining their roles, architecture, and how they support system separation and governance.
Understanding the SAP Client Concept for Secure Operations
Overview of client copy and transport in building a global template
An outline of client copy and transport mechanisms when establishing an SAP global template.
Essential SAP Global Template Rollout Guide for Success
Reference Links
- SAP Community Blog
S-User IDとSCN User IDについて – SAP Community - SAP B1BLOG
Customer reference number (SAP Business One - JNC
Simplifying SAP Licensing – Everything you need to know – JNC - STechies Blog
Installation SAP Numbers, SAP Keys, SAP License number
Disclaimer
Parts of this article were developed with reference to generative AI suggestions and were reviewed, refined, and supplemented based on the author’s professional expertise and judgment.
Leave a Reply