You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Status

  Approved

OwnerYILMAZTURK-ext, Gokhan 
StakeholdersLEIGHTON-ext, Dean 
Jira Request ID

ERP-98 - Getting issue details... STATUS

Jira Development ID

ERP-349 - Getting issue details... STATUS

High- Level Specification

ParameterValue
Application SystemSAP S/4HANA ROW, SAP S/4HANA China, SAP S/4HANA CUI
Business Process Reference07.05.01.01. Manage Asset, Faults and Incidents

Functional Overview

For requesting maintenance on regular activities, the app “Create Maintenance Request”  (App ID : F1511A) will be used. However, when requesting Project Work, we will need to use a different WDA application called “Create Maintenance Notification” (App ID : W0006). In this application, we will need to make WBS Element field mandatory. Also after the WBS Element is entered, we will need to validate if this WBSE is a valid one. (e.g. Accounting Indicator must be set etc.)


Scope and Objectives

This development has 3 main objectives as follows;

  1. Launchpad Design & App Tile Configuration: In A2D, the app “Create Maintenance Request”  (App ID : F1511A) will be used for raising maintenance requests on regular activities. However, we will need a separate Fiori application to raise "Project Work". For this purpose, the WDA application called “Create Maintenance Notification” (App ID : W0006) will be used with certain launchpad configuration which is mentioned in detail at the Configuration Details section. This app will be targeted only for certain user groups (e.g. Project Managers), which is also explained in the Security, Integrity and Controls section.
  2. Enabling certain standard fields and making them mandatory: In standard app “Create Maintenance Request”  (App ID : F1511A), WBS Element field (which is also a standard field) is not present. It is also not supplied with OData Services/CDS Views the app is using as well. On the other hand, the field is available in the “Create Maintenance Notification” (App ID : W0006) which is intended to be used for this process but hidden. Therefore, this field needs to be configured to become visible and also have to be a mandatory field via configuration that is explained in the Configuration Details section. 
  3. Performing checks and validations during saving the notification: Once the WBS element field is entered, a validation has to be done to check if the WBS Element is a valid one. A valid WBS Element has Accounting indicator as true.


Process Flow Diagram


Step

Description

Comment

1User launches app “Create Maintenance Notification” (App ID : W0006) using a following parameter: "QMART=Y3", initial screen where the notification type needs to be selected, will be skipped.
2User enters Notification Detailse.g. Notification Description, Technical Object, Maintenance Plant, Company Code, etc.
3User enters WBS Element in Locations Tab
4Enhancement triggers checks for WBS Element to see if it's validif not it will populate an error
5User saves the notification


Assumptions

The “Create Maintenance Notification” (App ID : W0006) will only be used for creating Y3 Notifications via a targeted group of users. For regular maintenance activities, “Create Maintenance Request”  (App ID : F1511A) app will be used instead.

Dependencies

Security, Integrity and Controls


Configuration Requirements

Language Requirements

Special Requirements


Design Rationale

Functional Requirements

Proposed Technology to Use

Data Source Considerations

TableField NameComments/Calculation/Field Manipulation











Data Validation Considerations

TableField NameComments/Calculation/Field Manipulation













Custom Tables

Master Data

FieldDescriptionData Type/LengthValidation rule/ Value Help









Configuration Table

FieldDescriptionData Type/LengthValidation rule/ Value Help








Selection Screen Enhancement

Field NameDescription

Select:

Data Type/LengthDefault Value/ Validation rule/ Value HelpSelection Logic













Processing Logic



Volumetrics


Performance Considerations



Error Handling


Testing

How to Test

Test Conditions and Expected Results

IDConditionExpected Result










Test Considerations/Dependencies


Other Information


Development Details

Package

Package NameParent Package




Enhancement Implementation

Enhancement TypeStandard Definition NameCustom Implementation NameDesign Rationale Reference









Other Development Objects

Object TypeObject NamePurpose/High Level LogicDesign Rationale Reference








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.

ABAP

ZFIZMMZPSZCOZSDZBCZFIZCA
TABLESZFITZMMTZPSTZCOTZSDTZBCTZFITZCAT

See also


No files shared here yet.

Change log

Version Published Changed By Comment
CURRENT (v. 5) Dec 02, 2025 17:30 YILMAZTURK-ext, Gokhan
v. 23 Dec 02, 2025 17:22 YILMAZTURK-ext, Gokhan
v. 22 Dec 02, 2025 17:17 YILMAZTURK-ext, Gokhan
v. 21 Nov 20, 2025 09:49 YILMAZTURK-ext, Gokhan
v. 20 Nov 13, 2025 14:22 YILMAZTURK-ext, Gokhan
v. 19 Nov 13, 2025 13:44 YILMAZTURK-ext, Gokhan
v. 18 Nov 12, 2025 14:10 YILMAZTURK-ext, Gokhan
v. 17 Nov 11, 2025 17:27 YILMAZTURK-ext, Gokhan
v. 16 Nov 11, 2025 17:24 YILMAZTURK-ext, Gokhan
v. 15 Nov 11, 2025 17:16 YILMAZTURK-ext, Gokhan

Go to Page History

  • No labels