SAP Project User Licence: Definition, Rights, Costs, and Optimisation

What Is the SAP Project User Licence?

The SAP Project User licence is a named-user licence type available in the SAP S/4HANA on-premise licence model. It is specifically designed for individuals whose primary work activities in SAP are centred on project management functions — planning projects, managing project resources, tracking project budgets, processing project-specific procurement, and reporting on project status and performance.

SAP defines the Project User as a licence for users whose interactions with SAP are confined to the project management domain. This means access to SAP Project System (PS) or SAP Portfolio and Project Management (PPM), along with the associated project-centric functionalities in purchasing, financial accounting for project expenses, and project reporting. The Project User licence does not grant broad SAP system access — it is a restricted category with defined functional boundaries.

The commercial attraction of the Project User licence is straightforward: it is priced significantly below the SAP Professional User licence, which provides unrestricted access to all SAP transactions. The price differential between a Project User and a Professional User — on an annual basis including the approximately 22% annual maintenance fee — is typically in the range of 40 to 60 percent, depending on the specific negotiated rates in the customer's agreement. For organisations with large project management communities, correct use of the Project User licence can deliver material and recurring licence cost savings.

The S/4HANA User Licence Landscape

To position the Project User correctly, it is helpful to understand where it sits within the full S/4HANA named-user licence hierarchy. SAP's S/4HANA on-premise licence model defines several user categories, each with different permitted access and corresponding price points.

Professional User

The Professional User is the highest-tier named user in S/4HANA on-premise. It provides full access to all S/4HANA functionalities, including all modules, transactions, and reporting capabilities. Professionals Users are intended for individuals whose roles require broad system access across multiple functional domains. Finance managers, supply chain planners with cross-functional responsibility, senior business analysts, and system administrators are typical Professional User roles. The Professional User carries the highest per-user price.

Functional User (Limited Professional)

The Functional User (sometimes called Limited Professional User) is designed for individuals whose access is confined to a single functional area or module. A procurement specialist working exclusively in Materials Management, a maintenance technician working exclusively in Plant Maintenance, or a logistics coordinator working exclusively in Warehouse Management are typical Functional User roles. The Functional User can create and edit transactional data within their assigned domain but cannot cross into other functional areas. The price is meaningfully below the Professional User.

Project User

The Project User is a further specialised category, specifically aligned to project management activities. Unlike the Functional User — which can be applied to any single functional domain — the Project User is defined by its project-centric scope. Access to SAP PS transactions for project planning and execution, PPM portfolio management, project purchasing, project reporting, and project cost accounting falls within the Project User scope. Access to general financial accounting outside project contexts, general procurement outside project purchasing, and other non-project functional areas falls outside the Project User scope and requires a higher-tier licence.

Self-Service User

The Self-Service User is the lowest-tier named user, designed for employee self-service scenarios — expense reporting, leave requests, time recording, and similar employee-initiated transactions. It is not relevant to project management roles and is included here for completeness of the licence hierarchy overview.

Permitted Activities Under the Project User Licence

Understanding precisely what the Project User licence permits is critical for correct classification and audit defence. The permitted activity scope is defined by SAP's licence documentation and the specific contract terms, but the following framework represents the generally applicable scope.

Permitted Activities

Project User access typically covers: creating, modifying, and monitoring project definitions and project structures in SAP PS; creating and managing work breakdown structures (WBS), networks, and activities; planning and tracking project budgets and actual costs; processing project-specific purchase requisitions and purchase orders within the project procurement context; confirming project activities, recording time against project activities, and reviewing project progress; generating project status reports, project cost reports, and earned value analyses; and managing project milestones, capacity requirements, and resource allocations within the project domain.

Activities Typically Requiring Higher-Tier Licences

Access that generally falls outside the Project User scope includes: processing general procurement transactions outside project contexts (non-project purchase orders, standard purchase requisitions without project assignment); performing general financial accounting entries outside project cost accounting (posting to non-project cost centres, journal entries in general ledger without project reference); accessing cross-functional reporting dashboards that draw data from multiple modules beyond the project domain; managing master data outside the project context, such as material master records, vendor master records, or customer master records; and performing system administration tasks, transport management, or technical configuration activities.

The boundary between project-context activities and general activities is not always clear in practice, which is one source of audit risk for organisations using Project User licences extensively. Where a user's actual system activity includes both project-context and non-project-context transactions, the Project User classification may not be appropriate, and the user may require a Functional User or Professional User licence instead.

Project User Licences and S/4HANA Migration

The S/4HANA migration changes the licence baseline in ways that directly affect Project User strategy. This is one of the most important considerations for organisations currently evaluating their user classification ahead of an ECC-to-S/4HANA transition.

Under the legacy ECC licence model, Project System access was typically covered by specific Limited Professional User licences or by full Professional User licences depending on the configuration of each organisation's agreement. The S/4HANA migration provides an opportunity to formally introduce Project User licences as a separate and lower-cost category for roles that are genuinely project-centric — but only if this classification is explicitly negotiated in the migration agreement.

SAP's standard migration mapping from ECC to S/4HANA does not automatically introduce Project User licences for users previously classified as Limited Professional or Professional in ECC. SAP's commercial team typically proposes a conversion that preserves or upgrades the existing licence categories. Buyers who want to introduce Project User licences for eligible roles must explicitly request this as part of the migration negotiation and provide a role-by-role justification.

The opportunity value of this negotiation is significant. In organisations with substantial project management activity — engineering and construction companies, capital-intensive manufacturers, IT services organisations, and infrastructure developers — the population of project-centric users may represent 15 to 30 percent of the total user count. Converting these users from Professional or Functional User licences to Project User licences in the S/4HANA migration delivers recurring annual savings that compound over the post-migration contract term.

Audit Risks Associated with Project User Licences

Project User licences carry specific audit risks that arise from the boundary between permitted and non-permitted activities. SAP's licence audit tools — particularly the USMM (User and System Measurement) tool and its associated licence type classification logic — will measure all system activity for each named user and compare it against the assigned licence type. Where the measured activity includes transactions outside the Project User scope, SAP's audit team will reclassify the user to a higher-tier licence and assess the corresponding back-dated licence fees.

The Cross-Functional Access Risk

The most common audit finding for Project User licences is cross-functional access — a Project User who has been granted access to transactions outside the project domain. This can occur through: roles that are too broadly defined in the SAP role design, where the security administrator assigned generic roles that include non-project transactions for convenience; manual workarounds where users with project roles occasionally process non-project transactions to complete a task more efficiently; and system upgrades or configuration changes that activate additional transaction access for existing roles without a licence review.

The mitigation is role-level access control aligned to the Project User definition. Each Project User should have an SAP security role set that is explicitly restricted to project-domain transactions, with appropriate segregation of duties controls. Regular access reviews that compare actual transaction activity (via USMM measurement) against the assigned role set identify drift before it creates audit exposure.

The ECC Migration Risk

A second audit risk arises during ECC-to-S/4HANA migrations that use temporary project licences for consultants and implementation team members. SAP allows the use of temporary access for specific migration activities, but this temporary access must be correctly documented, time-limited, and licenced appropriately. Organisations that maintain temporary full-access licences for implementation consultants beyond the migration period, or that do not have clear documentation of the temporary nature of such access, face audit exposure if the access is not formally aligned to the contracted licence type.

Optimising Project User Licences: Five Practical Steps

Step 1: Identify your project-centric user population. Conduct a role-by-role analysis of every SAP user whose primary work activities involve SAP Project System or Portfolio and Project Management. Identify which users' system activities are genuinely confined to project domain transactions. This analysis becomes the basis for reclassification discussions internally and with SAP.

Step 2: Validate the scope of project-domain transactions for each candidate role. For each candidate Project User, pull the actual transaction activity data from USMM or the SAP licence audit reporting tools. Confirm that the transaction profile is consistent with the Project User scope definition in your SAP contract. Where activity crosses into non-project domains, either restrict the access (by tightening the SAP security role) or retain the higher-tier licence for that user.

Step 3: Negotiate Project User licence introduction in the next SAP renewal or S/4HANA migration. Use the evidence from your role analysis and transaction data to propose Project User licences for qualified users as part of the next SAP commercial event. Present the analysis to SAP's licence team as a formal reclassification request with supporting documentation. SAP will typically accept reclassifications that are supported by data, though the resulting savings will be reflected in the renewal rather than applied retroactively.

Step 4: Align SAP security roles to the Project User boundary. For every user reclassified to Project User, ensure the SAP security role set is explicitly restricted to project-domain transactions. Engage the SAP basis and security team to implement role-level controls that prevent access drift. Document the role design rationale and maintain it for audit response purposes.

Step 5: Run quarterly access reviews for Project User populations. Quarterly USMM-based reviews of Project User activity confirm that the classification remains accurate as roles evolve. Where quarterly reviews identify cross-functional access, address it immediately — either by restricting the access or by reclassifying the user before an audit event forces the issue at list price.

Project User Licences in RISE with SAP and S/4HANA Cloud

For organisations on RISE with SAP or S/4HANA Cloud Public Edition, the Project User licence concept translates into the subscription model differently. Cloud licences are typically structured as user types within the FUE (Full Use Equivalent) model, and the specific user type definitions may differ between on-premise and cloud deployments.

In cloud deployments, project management access may be covered by a dedicated subscription package aligned to SAP Project System and PPM capability, rather than a named-user tier equivalent to the on-premise Project User. The commercial principle remains the same — targeting the minimum subscription scope that meets each user's actual functional requirements — but the specific packaging must be verified against the applicable cloud contract.

Organisations moving from on-premise to RISE should ensure that the user reclassification opportunity for project-centric roles is captured in the migration negotiation, as the post-migration subscription structure may not automatically reflect the optimised on-premise classification. The migration negotiation is the right moment to formalise the project user tier at the lowest appropriate cost, rather than defaulting to a higher-cost equivalent.