High- Level Specification

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.

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:

1. Notification Type Y3

   • New notification type created for project-related maintenance.

2. Order Type Configuration

   • Settlement profile assigned to the relevant order type.

   • Ensure order type allows account assignment to WBS.

3. Settlement Profile

   • A Settlement Profile will be created: YEAM03

   • Settlement receiver type: WBS element.

   • Default Object Type: WBS

4. 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

• The enhancement must ensure that the WBS element used in notifications and orders is valid, released, and belongs to an active project.

• The Planning WBS is not automatically derived in the maintenance order.
• The WBS element in the Account Assignment is automatically assigned; however, if automatic population of the Planning WBS is required, an additional enhancement will be needed.
• No localization, legal, or country-specific compliance requirements apply.

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

• Missing WBS (Y3 Notification): Error message “WBS Element is mandatory for notification type Y3.”
• Invalid or Unreleased WBS: Error message “WBS Element is invalid or not released.”

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