High- Level Specification

Functional Overview

The purpose of this enhancement is to introduce a validation and logic control during the creation of Settlement Rules in Plant Maintenance Orders.
Settlement rules are automatically created with Cost Center as the settlement receiver for all the maintenance orders. However, for Turnaround scenarios, the settlement should not go to a Cost Center but instead to a WBS Element associated with the Turnaround event.

The enhancement will intervene at the moment of Settlement Rule creation (not necessarily during Order Release), check whether the Maintenance Order is part of a Turnaround (via Revision/Maintenance Event field), and assign the correct receiver type accordingly.

Scope and Objectives

• Enhancement of Settlement Rule creation logic in PM Orders (via BAdI or Enhancement Spot).

• Automatic determination of WBS element for Turnaround-related orders.

• Validation and override of default settlement receiver.

To ensure correct and automated determination of the appropriate settlement receiver (WBS or Cost Center) based on Turnaround context, maintaining compliance with project cost accounting principles.

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

   • Settlement rule generation is handled through standard SAP functionality based on the assigned settlement profile.

   • 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

1. Notification Type Y3 Creation

   • When users create a maintenance notification of type Y3 (Project-related), the system must enforce the WBS Element as a mandatory field in the notification.

   • The user should not be able to save or release a Y3 notification without entering a valid, released WBS Element.

2. Order Creation from Notification

   • When converting a Y3 notification into a maintenance order via the Find Maintenance Notification Fiori app:

     • The WBS Element must be automatically transferred from the notification to the order’s Account Assignment section (field: ILOA-PROID).

     • The system must automatically generate a settlement rule in the maintenance order using the WBS element as the settlement receiver.

     • The generated settlement rule must use standard settlement parameters 

3. Error Handling

   • If the WBS Element in the notification is missing, invalid, or not released, the system should prevent order creation and display an error message (e.g., “WBS Element is mandatory for Notification Type Y3.”).

4. Standard Compliance

   • The enhancement should utilize standard SAP settlement functionality and standard configuration (settlement profile, order type setup).

   • No manual user action should be required for settlement rule creation.

Proposed Technology to Use

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Configuration Table

Selection Screen Enhancement

Processing Logic

• Notification Creation (Type Y3):

  • User creates notification via Fiori app.

  • System checks if notification type = Y3.

  • If yes → WBS field must be filled.

  • If WBS is blank → error message displayed.

  • Notification saved only if WBS valid and released.

• Order Creation (from Notification):

  • User converts Y3 notification to order.

  • System automatically copies WBS element to Order-Account Assignment section (ILOA-PROID).

  • Settlement rule generation is handled through standard SAP functionality based on the assigned settlement profile.

  • System creates settlement rule automatically.

  • Error message displayed if settlement rule creation fails.

• Order Processing:

  • Order processed normally.

  • Settlement executed automatically based on the generated rule.

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