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.

• Maintain standard behavior for non-turnaround orders (default Cost Center settlement).

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.

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)

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

• Notifications with the same REVNR 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

• Fiori app configuration for notifications and orders.

• Y3 Notification must have WBS element assigned.

• BADI implementation must be activated in the system for settlement rule enhancement.

• Integration with PS module (for WBS element retrieval) must be in place.

• Other custom developments interacting with AFIH, VIQMEL, or settlement rules must not conflict with this logic.

Security, Integrity and Controls

To ensure secure processing of this enhancement, the following points apply:

Configuration Requirements

The following configuration changes are required to support the enhancement:

• Implementing BADI for settlement rule creation

• No additional customizing required for standard Cost Center settlement logic.

Language Requirements

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

Special Requirements

• Ensure performance is not impacted when processing large numbers of orders or notifications.

• In case of multiple notifications for the same Maintenance Event, implement a rule to select the correct WBS.

• If future integrations consume WBS or settlement data, ensure compliance with their data structure and format.

Design Rationale

Functional Requirements

Proposed Technology to Use

• Check Order:

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

• Retrieve Maintenance Event:

  • If REVNR exists, go to the maintenance notification (VIQMEL) and populate Y3 (QMART) with the REVNRvalue from the order.

• Identify WBS Element:

  • For the maintenance notification matching this REVNR, retrieve the associated WBS element (PSP_NR).

• Settlement Rule Creation:

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

  • If no REVNR is found, default settlement rule is created to the order’s Cost Center.

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

• 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

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

• 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

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