With SAP S/4HANA 2025, SAP introduced Object-Based Authorization (OBA) for Project System, providing a new authorization framework that enables project-level access control beyond traditional role-based security.
For a general introduction to Object-Based Authorization, refer to SAP Community's blog on Introducing Object-Based Authorization (OBA) in SA… – SAP Community
While SAP S/4HANA 2025 FPS00 introduced the OBA framework, SAP S/4HANA 2025 FPS01 and FPS02 further expands its capabilities:
- SAP S/4HANA 2025 FPS01 introduces the Object-Based Authorization (OBA) Deletion Report, (Refer to the SAP Community blog using the link – Introducing Object-Based Authorization (OBA) delet… – SAP Community for more details.)
SAP S/4HANA 2025 FPS02 extends OBA support to project scheduling and date planning processes. This enhancement allows organizations to control who can schedule or modify dates for specific project objects, offering a much finer level of authorization than was previously possible.
Why is this Enhancement Important?
Traditionally, scheduling authorization in SAP Project System was controlled entirely through PFCG role-based authorizations.
Although PFCG determines which transactions and actions a user can execute e.g. based on high level organizational assignments, it cannot easily distinguish between individual project objects.
For example:
- A planner may be authorized to execute CJ20N.
- However, the business may want the planner to schedule Project A but prevent scheduling Project B.
Object-Based Authorization addresses this restriction by introducing project object-level authorization.
In case OBA is active for a project user must now satisfy both:
- Standard PFCG authorization
- Object-Based Authorization (OBA)
Only when the right level of privileges is granted to the user scheduling or date-related operations be performed.
Project Objects Covered by OBA
The scheduling enhancement supports authorization checks across the following Project System objects:
- Project Definition
- WBS Elements
- Networks
- Activities
- Activity Elements
- Subnetworks
This ensures authorization is consistently enforced throughout the complete project hierarchy.
Prerequisites for Using OBA in Scheduling
Before scheduling authorization becomes effective, several configuration steps are required.
Step 1 – Activate OBA in the Profile
Ensure that Object-Based Authorization is enabled in the appropriate Project Profile or Network Profile before using OBA-enabled scheduling functionality.
The activation process is covered in detail in the SAP Community blog ” Introducing Object-Based Authorization (OBA) in SA… – SAP Community “ and is not repeated here.
Step 2 – Configure Message in application area CN 475 in Transaction OBA5
Transaction OBA5 determines how the system behaves when a user attempts to schedule an object without sufficient OBA authorization.
Message CN 475 controls this behavior.
OBA5 Configuration | System Behavior |
Error (E) | Scheduling is blocked immediately and message CN475 is issued. |
Warning (W) | Scheduling continues, while message CN475 is logged. |
Not Configured | Defaults to Warning behavior |
Step 3 – Maintain User Authorizations
Assign object-level permissions through the OBA tab.
Supported authorization levels include:
- Read
- Write
- Admin
- No Authorization
Permissions can be assigned individually for each project object.
Scheduling Scenarios Supporting OBA
- Project Scheduling
Project scheduling performs scheduling across the complete project hierarchy.
OBA authorization is validated for:
- Project Definition
- WBS Elements
- Networks
- Activities
- Subnetworks
- WBS Scheduling
When scheduling starts from a WBS element, SAP automatically schedules all related child networks and activities.
- Network Scheduling
Object-Based Authorization is also enforced during network scheduling in:
- CJ20N – Project Builder
- CN22 – Change Network
- CN24 – Overall Network Scheduling
Authorization checks apply to:
- Networks
- Activities
- Activity Elements
- Subnetwork
- Project Planning Board
The Project Planning Board (CJ2B) supports several date management functions, including:
- Reconcile Dates
- Shift Dates
- Check Dates
Unlike scheduling transactions, these functions primarily synchronize or copy dates rather than execute complete scheduling calculations.
Nevertheless, Object-Based Authorization is enforced wherever applicable.
Key Points –
OBA Complements PFCG
Object-Based Authorization does not replace traditional SAP role authorizations.
Instead, it introduces an additional layer of security.
Users require both:
- Appropriate PFCG authorizations
- Required OBA permissions
Choosing Between Error and Warning
The selection of Error or Warning should align with business requirements.
Use Error (E)
Recommended when:
- Strict governance is required.
- Unauthorized date changes via scheduling must be prevented.
- Compliance is mandatory.
Use Warning (W)
Recommended when:
- Business continuity is more important.
- Organizations are gradually implementing OBA.
- Authorization assignments are still being refined.
Key Takeaways
The adoption of Object-Based Authorization for scheduling in SAP S/4HANA 2025 FPS02 represents a significant enhancement for SAP Project System.
Key benefits include:
- Fine-grained authorization at the project object level
- Secure scheduling across WBS, networks, activities, and related objects
- Seamless integration with existing PFCG authorizations
- Flexible enforcement through configurable OBA5 message handling
- Improved governance without sacrificing operational flexibility
By extending OBA into scheduling and date management, SAP enables organizations to protect critical project planning activities while maintaining the flexibility required for complex project execution.
Source link