You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
| Status | |
|---|
| Owner | |
|---|
| Stakeholders | |
|---|
| Jira Request ID |
ERP-99
-
Getting issue details...
STATUS
|
|---|
| Jira Development ID |
ERP-350
-
Getting issue details...
STATUS
|
|---|
High- Level Specification
| Parameter | Value |
|---|
| Application System | SAP S/4HANA ROW, SAP S/4HANA China, SAP S/4HANA CUI |
|---|
| Business Process Reference |
|
|---|
Functional Overview
The functional design of the enhancements describes the scenario(s) where enhancements to existing SAP programs are required.
Scope and Objectives
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.
Process Flow Diagram
Assumptions
Dependencies
Security, Integrity and Controls
Configuration Requirements
Language Requirements
Special Requirements
Design Rationale
Functional Requirements
Proposed Technology to Use
Data Source Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|
|
|
|
|
|
|
|
|
|
Data Validation Considerations
| Table | Field Name | Comments/Calculation/Field Manipulation |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
Custom Tables
Master Data
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|
|
|
|
|
|
|
|
|
Configuration Table
| Field | Description | Data Type/Length | Validation rule/ Value Help |
|---|
|
|
|
|
|
|
|
|
Selection Screen Enhancement
| Field Name | Description | Select: | Data Type/Length | Default Value/ Validation rule/ Value Help | Selection Logic |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
Processing Logic
Performance Considerations
Testing
How to Test
Test Conditions and Expected Results
| ID | Condition | Expected Result |
|---|
|
|
|
|
|
|
|
|
|
Test Considerations/Dependencies
Development Details
Package
| Package Name | Parent Package |
|---|
|
|
|
|
Enhancement Implementation
| Enhancement Type | Standard Definition Name | Custom Implementation Name | Design Rationale Reference |
|---|
|
|
|
|
|
|
|
|
Other Development Objects
| Object Type | Object Name | Purpose/High Level Logic | Design 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 | ZFI | ZMM | ZPS | ZCO | ZSD | ZBC | ZFI | ZCA |
|---|
| TABLES | ZFIT | ZMMT | ZPST | ZCOT | ZSDT | ZBCT | ZFIT | ZCAT |
|---|
See also
No files shared here yet.