High- Level Specification
| Parameter | Value |
|---|---|
| Application System | |
| Business Process Reference |
Functional Overview
The PM Notification application is a custom SAP Fiori application intended to allow end users to create and consult maintenance notifications in a simplified and user-friendly way.
The application will be developed on SAP BTP and integrated with SAP S/4HANA for notification creation and retrieval. The application is expected to be exposed to end users through two portals (one for internal and the other for the external)
The application provides two main capabilities:
- Create Notification
- Notifications List
The user experience is intentionally simplified in order to support non-SAP users (lab researchers), especially laboratory and site users. Technical SAP fields are hidden from the UI and automatically derived in the backend wherever possible.
Notifications are created in SAP S/4HANA through backend integration using a technical user. The actual requester identity is nevertheless captured and transferred as part of the notification data.
Scope and Objectives
- Allowing users to create maintenance notifications through a simplified Fiori UI
- Allowing users to consult existing notifications in a dedicated list screen
- Enabling secure access for internal users through SAP Cloud Identity Services
- Restricting user access based on plant/site authorization
- Integrating the application with SAP S/4HANA for both create and get operations
Process Flow Diagram
Application Screen:
Step | Description | Comment |
|---|---|---|
1 | User authenticates through the target portal / entry point | Internal users via SAP Cloud Identity Services (SSO) External needs to be defined by tech team |
2 | User opens the PM Notification application | Fiori app developed on SAP BTP
|
3 | User selects either “Create Notification” or “Notifications List" | Main navigation tabs |
3 | User enters or reviews notification information | |
3 | User submits the notification (Optional) User HSE Procedures. | Final confirmation required |
4 | Notification is created in SAP S/4HANA | API call to Y1-create maintenance request in SAP, via technical user |
5 | Confirmation is returned to the user | Notification number displayed |
6 | Email Notification sent based on custom tables content. |
Assumptions
- End users are not SAP experts and require a simplified interface
- The app is developed on SAP BTP
- SAP S/4HANA exposes the required backend services for notification creation and retrieval
- Internal users can be associated with an authorization attribute identifying their plant/site
Dependencies
The application depends on the following components:
- SAP BTP
- SAP S/4HANA PM
- SAP Cloud Identity Services
- Portal / launch mechanism for end users
- Backend integration services or APIs for create and get operations
- Custom configuration tables for approval and email routing, where applicable
Security, Integrity and Controls
Authentication for internal users shall be based on SAP Cloud Identity Services.
Authorization shall be controlled through user attributes, in particular the authorized plant/site. The application shall restrict both data visibility and data creation rights accordingly.
Users shall only be able to:
- create notifications for their authorized plant/site
- view only notifications belonging to their authorized plant/site
- access only the functional locations and equipment belonging to their authorized scope
Although the notification is technically created in S/4HANA by a technical user, the actual requester identity must be captured and transferred in the notification payload.
A backend validation shall ensure that no notification can be created outside the user’s authorized scope, even if UI filtering is bypassed.
The external access model is still under discussion and will be finalized separately by the project technical team.
Configuration Requirements
The following configuration elements are required:
- User authorization attribute identifying the plant/site
- Filtering logic for functional locations and equipment by plant/site
- Email recipient mapping by cost center if approval remains in scope
Language Requirements
The application language shall be English/French
Additional language support may be considered later depending on project needs.
Special Requirements
- Intuitive and simplified UI
- Plant/site-based filtering for both creation and consultation
- Separate list tab for consultation of existing notifications
- Priority field available in the creation form
- A section for HSE evaluation needs to be added at the bottom
Design Rationale
The following design choices have been made:
- technical fields such as planner group, work center, and cost center are exposed to end users.
- a simplified HSE / Safety section may be retained for high-level information only
- a notification list screen is introduced to provide users with visibility on previously created requests
- priority is explicitly captured in the UI to help classify the request from the start
This approach is aligned with SAP best practices, where the notification captures the maintenance need, while technical, planning, and safety assessments are handled later during order preparation and execution.
Functional Requirements
The application shall provide the following functionalities.
- Create Notification
The user shall be able to create a maintenance notification through a simplified form.
The form shall allow the user to maintain:
- Functional location
- equipment (optional)
- title (short description)
- description (long text)
- priority
- requested start date
- requested end date
- simplified safety / HSE information if retained
The system shall:
- validate mandatory fields
- restrict selectable technical objects based on plant/site authorization
- create the notification in SAP S/4HANA
- display a confirmation message with the notification number
- Notifications List (similar to IW29)
The user shall be able to consult previously created maintenance notifications through a dedicated list tab.
The user shall be able to:
- retrieve a list of notifications
- filter the list by predefined criteria
- view notification details in read-only mode
The system shall ensure that the user only sees notifications related to the authorized plant/site.
- Automatic Derivation
The system shall automatically derive from technical object:
- planner group
- work center
- cost center
The user will be able to suggest the cost center with an activity code
Recommended UI Technology
SAP Fiori (SAPUI5) on SAP build work zone
Application Screen
Wireframe or Mock-Up
Screen Behavior
Screen Navigation
First Screen - Authentication screen
fields required: First name / Last name / E-mail address / Plant (dropdown value list)
> Next Screen - Create Maintenance request
First section > User information
Second section > Standard fields required in order to create the notification
Third section: Risk Evaluation + Medical risk + HSE Checklist
button to submit the notification, with final confirmation required
Data Integration
| Field | Table-Field Name | Comments / Calculation / Field Manipulation / Input / Output / Validation rule / Value help |
|---|---|---|
Custom Tables
Master data
| Field | Description | Data Type/Length | Validation rule / Value help |
|---|---|---|---|
Configuration table
| Field | Description | Data Type/Length | Validation rule / Value help |
|---|---|---|---|
Processing Logic
Tooltips
Front-End
Mobile Services
Authentication & Authorization
Accessibility
Volumetrics
Performance Consideration
Error Handling
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|---|---|
Test Considerations/Dependencies
Other Information
Development Details
Package
| Package Name | Parent Package |
|---|---|
UI Implementation
UI Type | UI Name | Fiori Catalogue | Design Rationale Reference |
|---|---|---|---|
API Implementation
| API Type | API Name | Purpose / High Level Logic | API Product | Design Rationale Reference |
|---|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|