High- Level Specification

Functional Overview

In the standard SAP S/4HANA system, named users are typically assigned to the "Person Responsible No." and "Applicant No." fields within both the Project Definition and Work Breakdown Structure (WBS) elements of a project. These assignments are used to track accountability and facilitate project-related notifications & workflows.

However, under the I2M proposed solution, this approach is being redefined. Instead of linking these fields to individual named users, the system will utilize Role based HR position. This means-

• HR positions assigned to specific roles, rather than specific named user, will be designated as the responsible entities at the Project Definition and WBS levels.
• This enables a role-based project system, allowing for greater flexibility and scalability in project governance.
• It supports organizational continuity, as responsibilities are tied to HR Position rather than individuals—reducing the need for manual updates when personnel changes occur.
• Enhanced search help will be enabled for "Person Responsible No." and "Applicant No." fields.

Scope and Objectives

Scope- This enhancement defines a scheduled SAP batch job that extracts HR positions based on their role relationships and updates-

1. Person Responsible No. Table: Populated with positions linked to Security Roles ‘Person Responsible - Project’, ‘Person Responsible - WBS’
2. Applicant No. Table: Populated with positions linked to Security Role ‘Project Financial Controller’.
3. Enhance Search Help: Enhance the search help tab to find Position based on Position Name, Personnel ID, Personnel name etc.  

Objective- The key objective are to improve data accuracy and timeliness in project and financial role assignments and reduce manual intervention in HR-Role mapping updates.

N/A

Process steps are-

DELETE-

Internal testing, TCode PO13, Position 50000038, Infotype Communication B 007

Assumptions

• Role-to-position relationships are maintained in standard HR Infotype. 
• The system will have predefined and stable Security Role. Security Roles like ‘Person Responsible – Project’, ‘Person Responsible – WBS’, and ‘Project Financial Controller’ are expected to be consistently available.

Dependencies

• HR master data must be up to date i.e. applicable Security Roles must be assigned to project management specific Position.
• Table structures for Person Responsible No. and Applicant No. must allow maintenance via Batch Job without creating Transport Request.

Security, Integrity and Controls

• Authorization Checks: Batch job runs under a technical user with restricted write access to Person Responsible No. and Applicant No. tables.
• Data Validation: Security Role codes and position IDs are validated before update.

Configuration Requirements

N/A

Language Requirements

N/A

Special Requirements

N/A

Design Rationale

Functional Requirements

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

Volumetrics

Performance Considerations

Error Handling

Testing

How to Test

Test Conditions and Expected Results

Test Considerations/Dependencies

Other Information

Development Details

Package

Enhancement Implementation

Other Development Objects

Appendix

Custom Authorization Group Naming Convention

This table is based on the Syensqo development standards document. It provides the naming conventions for authorization groups to associated with custom reports and tables to comply with security requirements.

See also

Change log