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 created automatically created with Cost Center as the settlement receiver for all the maintenance orders. However, for in line withstandard SAP functionality, based on the Order Type configuration and assigned Settlement Profile. For Turnaround scenarios, the settlement should not go to a Cost Center but instead to a the WBS Element associated with the Turnaround event.

The enhancement will intervene trigger 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 receiverPreserve standard settlement functionality for all non-Turnaround orders (no impact or modification in this case).

To ensure correct and automated determination of the appropriate settlement receiver (WBS or Cost Center) based on Turnaround contextelement for Turnaround scenarios), while all other PM orders follow the standard settlement rule logic, maintaining compliance with project cost accounting principles.

Process Flow Diagram

draw.io Board Diagram
border true diagramName Settlement Rule ERP 350-1763381168591 simpleViewer false width links auto tbstyle top lbox true diagramWidth 810 height 471 revision 1

Assumptions

• Y3 notification type Notification Type is available and configured in the system.

• Maintenance Orders will be released exclusively via the Fiori applications.

• Relevant users have Fiori app access (Create Maintenance Notification, Find Maintenance Notification).

• WBS element is always valid and released.

Dependencies

• Change Maintenance Order).

• Each Turnaround Order has at least one Maintenance Event/Revision assigned.

• Notifications with the same Maintenance Event/Revision contain the correct WBS element to be used for settlement.

• Standard SAP PM settlement logic is assumed to be functioning correctly for non-turnaround orders.

• Users creating Maintenance Orders have appropriate authorization for reading Notifications and WBS Elements.

Dependencies

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

• Check Order:

  • Validate if the order is PM Order (Table-Field): AUFK-AUTYP.

  • Check if the Maintenance Event/Revision (Field: REVNR) field is filled in the order (Table: AFIH).

• Retrieve Maintenance Event:

  • If Maintenance Event/Revision (Field: REVNR) exists, go to the Notification (Table: VIQMEL) and populate Y3 Notification Type (Field: QMART) with the Maintenance Event/Revision (Field: REVNR) value from the order.

• Identify WBS Element:

  • For the maintenance notification matching this Maintenance Event/Revision (Field: REVNR), retrieve the associated WBS element (Field: PROID).

• Settlement Rule Creation:

  • For all orders with this Maintenance Event/Revision, create settlement rule to the retrieved WBS element.

  • If no Maintenance Event/Revision (Field: REVNR) is found, continue with the standard settlement rule logic.

Proposed Technology to Use

When the system starts creating a settlement rule for an order, the exit IWO10027 is called.

Data Source Considerations

Data Validation Considerations

Custom Tables

Master Data

Volumetrics

Not Applicable

Performance Considerations

Not Applicable

Error Handling

No Error Handling Needed.

Testing

How to Test

Unit testing should be performed during settlement rule creation for maintenance orders to validate the enhancement logic implemented inUser Exit IWO10027 (Generate user-defined settlement rule). The tester should create or use existing maintenance orders under different scenarios to confirm that settlement rules are correctly assigned to WBS elements or Cost Centers according to the defined logic.

Test Conditions and Expected Results

Test Considerations/Dependencies

• This enhancement depends on the implementation of User Exit IWO10027 – Generate user-defined settlement rule.

• Data validation relies on correct entries in tables AFIH (REVNR), VIQMEL (QMART, REVNR, PROID).

• Ensure master data such as Cost Centers and WBS Elements are valid and open for posting in the test environment.

• To prevent creation of multiple Y3 notifications for the same Maintenance Event, a separate enhancement under “ERP-98 – UI Extensions in Create Maintenance Notification App” will provide additional control and validation.

• Testing should be executed in both standalone order creation and integrated Turnaround scenarios to confirm system behavior consistency.

• Ensure proper authorizations exist for testers to create and edit orders, notifications, and settlement rules.

Other Information

Not Applicable.

Test Considerations/Dependencies

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