| Status | Approved |
|---|---|
| Owner | |
| Stakeholders | |
| Jira Request ID | |
| Jira Development ID |
High- Level Specification
| Parameter | Value |
|---|---|
| Application System | |
| Business Process Reference |
Functional Overview
To enable external users (from the R&I Sites in Lyon & Paris) to submit maintenance requests from SAP Build Workzone (standard edition), there needs to be a Custom Fiori app developed and deployed to SAP Build Workzone.
Scope and Objectives
The scope of this interface includes enabling external users to submit maintenance requests without named S/4HANA users, leveraging a custom app integrated with SAP Build Workzone. The objective is to provide a secure, efficient, and user-friendly solution while addressing gaps in licensing and security compared to SAP Standard.
Process Flow Diagram
Application Screen:
Step | Description | Comment |
|---|---|---|
1 | User inputs email and other details in the custom app. | Email validation and default value derivation (Last Name, First Name, Telephone, Site, Plant, Receive a copy by e-mail) from Z1 table. |
2 | User selects Functional Location or Equipment in "Building/Laboratory" field. |
|
3 | (Option) User marks notification Risk and HSE Procedures. | |
4 | User clicks "Save" button. | API call to Y1-create maintenance request in SAP. |
5 | (Option) Activity items creation for Risk and HSE checkbox. | Activity code derive from Z2 table. |
6 | Email Notification sent based on Z1, Z2, Z3 table content. |
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
Language Requirements
Special Requirements
Design Rationale
Functional Requirements
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 |
|---|---|---|---|