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.

Insert the flowchart and fill in the steps

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

Specify the language requirements for this object. Specify the required language and type of translation, like labels, data.

Special Requirements

Specify any special requirements or considerations that may impact the enhancement based on specific locations, regulatory compliance or system limitations. Clearly outline requirements e.g. localization rules for countries like China

If the enhancement interacts with third-party systems such as Icertis, describe any additional integration, security or authentication considerations that must be taken into account.

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