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

Detail the functional requirements that are desired to be achieved by the Enhancement compared to current functionality

Proposed Technology to Use

Typically, an enhancement will be based on an existing SAP BADI / user exit. If this is the case, please provide the proposed details of the BADI / user exit.

Data Source Considerations

Include an overview of the source

Data Validation Considerations

Include an overview of the data validation requirement

Custom Tables

If any custom configuration tables are required, which will be read by the enhancement logic, then specify them here.

Master Data

<Title Custom Table 1>

<Include an overview of the table and what it’s used for>

Configuration Table

Title Configuration Table 1

Include an overview of the table and what it’s used for

Selection Screen Enhancement

This section will give the details on the selection screen parameters, parameter type and whether it’s obligatory or not. This section can be used to define the Import Export parameters for Function Module or User Exit or Screens.

Processing Logic

This section defines the detailed step-by-step logic implemented within the BAdI/User Exit to process the data received from the standard SAP program and database retrieval. It explains the operations performed on the data, the expected outcomes in different scenarios and how the system should behave in response to specific conditions.

Volumetrics

Provide volumetrics details: Initial load volumes, Number of Records, Expected Frequency, Expected Long term Growth)

Performance Considerations

Specify if there are any specific performance factors that need to be taken into consideration during development i.e. enhancement must be able to be executed by 10 users at the same time, etc.

Error Handling

Detail how errors will be handled: Notification, Restart/ Recovery and Re-Processing Procedures

Testing

How to Test

Please provide some guidance and/or test data to help the developer unit test the enhancement. Please include both positive and negative testing (to validate error situations handling). The developer will need to test repeatedly, so where appropriate provide instructions to reverse the actions performed so the test may be run again or explain how to create new input data to the test. The developer will need logons for test users representing the various roles within the approval process.

Test Conditions and Expected Results

Test Considerations/Dependencies

List any considerations essential for application test planning (e.g., test this before ABC along with DEF separate from GHI). If the development encompasses a user interface, explain how to test it. List any insights as to how this component could be tested the most efficiently.

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

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log