High- Level Specification
| Parameter | Value |
|---|---|
| Application System | SAP S/4HANA ROW, SAP S/4HANA China, SAP S/4HANA CUI |
| Business Process Reference |
Functional Overview
This enhancement aims to support a specific scenario where maintenance notifications and orders need to be created in the context of a project. A dedicated notification type (Y3) will be used exclusively for these project-based cases. The process begins with the Create Maintenance Notification Fiori app, where users will select the Y3 notification type. To ensure proper project linkage, the enhancement will enforce the WBS element as a mandatory field when the notification type is Y3.
Subsequently, the maintenance notification will be converted into a maintenance order using the Find Maintenance Notification Fiori app. When the relevant notification is selected, the system will provide an option to create a maintenance order, during which the WBS element will be automatically transferred from the notification to the order.
Scope and Objectives
Introduce notification type Y3 for project-related maintenance.
Enforce WBS element as a mandatory field for Y3 notifications.
Transfer the WBS element from the notification to the maintenance order during conversion.
Automate settlement rule creation in the maintenance order with the WBS as settlement receiver.
Ensure standard settlement functionality is applied without requiring manual user intervention.
Step | Description | Comment |
|---|---|---|
| 1 | User creates maintenance notification via Fiori App: Create Maintenance Notification | |
| 2 | Notification Type Y3 is selected and WBS element is entered. | The WBS element entry will be mandatory |
| 3 | User converts notification into a maintenance order via Fiori App: Find Maintenance Notification. | System transfers WBS element from notification to order. |
| 4 | During order creation, system automatically generates settlement rule using WBS element. | |
| 5 | Order is processed and settled as per project requirements. |
Assumptions
Y3 notification type is available and configured in the system.
Relevant users have Fiori app access (Create Maintenance Notification, Find Maintenance Notification).
WBS element is always valid and released.
Dependencies
PS (Project System) configuration for WBS elements.
Fiori app configuration for notifications and orders.
Workflow for order release.
Security, Integrity and Controls
To ensure secure processing of this enhancement, the following points apply:
- The enhancement will be triggered during maintenance notification and order creation via Fiori apps (Create Maintenance Notification and Find Maintenance Notification).
Authorization to create or convert Y3 notifications will depend on existing SAP Plant Maintenance roles (e.g.,
PM_NOTIFICATION_CREATE,PM_ORDER_CREATE), along with project authorization via WBS.The system must verify user authorization to assign or modify a WBS element linked to a project.
No custom authorization objects are foreseen.
No custom tables are required for this enhancement. If later introduced, they must be assigned to an authorization group.
Since the authorization checks for creating and converting notifications/orders are already handled in the calling standard Fiori apps, this section applies:
“Follow calling program authorization check.”
Configuration Requirements
The following configuration changes are required to support the enhancement:
Notification Type Y3
New notification type created for project-related maintenance.
Order Type Configuration
Settlement profile assigned to the relevant order type.
Ensure order type allows account assignment to WBS.
Settlement Profile
- A Settlement Profile will be created: YEAM03
Settlement receiver type: WBS element.
Default Object Type: WBS
Validation/Enhancement Spot
Implementation of BAdI or User Exit for settlement rule automation.
Error message configuration for missing or invalid WBS entries.
Language Requirements
Special Requirements
Design Rationale
Functional Requirements
Proposed Technology to Use
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Data Validation Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|---|---|
Custom Tables
Master Data
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Configuration Table
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|---|---|---|
Selection Screen Enhancement
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|---|---|---|---|---|
Processing Logic
Volumetrics
Performance Considerations
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 |
|---|---|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|---|---|---|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design Rationale Reference |
|---|---|---|---|
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.
ABAP | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|---|---|---|---|---|---|---|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |