0% found this document useful (0 votes)
2K views16 pages

Functional Specification Document (FSD) : A. Requirements

The document describes requirements for two custom SAP Fiori apps - IW38 for viewing a list of PM work orders and IW32 for changing work orders. It provides details on necessary fields, screens, and test scenarios for the apps to allow technicians to manage work orders from a mobile device.

Uploaded by

daniel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2K views16 pages

Functional Specification Document (FSD) : A. Requirements

The document describes requirements for two custom SAP Fiori apps - IW38 for viewing a list of PM work orders and IW32 for changing work orders. It provides details on necessary fields, screens, and test scenarios for the apps to allow technicians to manage work orders from a mobile device.

Uploaded by

daniel
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Functional Specification Document (FSD)

CR 12643
Project SAP
Title Global safety notice on PM Operation control ticket
CO FI MM PP SD

Impacted SAP Config X ABAP Security PS Workflow


Area
Interface Basis X PM X FIORI

Author Functional – Somanath


Requesting PTP
Area/Team
Business Owner Todd Manning

Version Date Description Modified By


V0 7.30.2020 Initial Draft Somanath
V1 8.14.2020 1. Operation external details sub tab added Somanath
2. Test Scenarios added

A. Requirements
1. Business Case
The Plant Maintenance Team is looking for areas to improve the newly installed PM Module
with our upgrade to SAP HEC we have found the opportunity to utilize the SAP FIORI PM
Mobility App. to improve our plant technician’s productivity while conducting PM
Maintenance activities.
2. Current Functionality in brief
Currently there is no mobile applications active for Plant Maintenance. All work is done on
desktop.

3. Requested Functionality in brief

The current requirement is of two FIORI Apps

Page 1 of 16
1. IW38 – Change PM Orders – List
2. IW32 – Change Work Order

4. Assumptions
As the requirement is for the T Codes IW32 & IW38, the remaining steps of the business
process are to be executed from desktop i.e. Creation of Notification (IW21), change /
approval of notification (IW22), time confirmations (IW41), cost settlement (KO88) and any
other transation except IW32 / IW38 are to be executed from desktops.

B. Solution Summary
1. Summary

Requirement : The current requirement is of two cutom FIORI Apps


1. IW38 – Change PM Orders – List

Technicians will need the ability to pull up a list of Outstanding and or In Process work orders with
the following criteria:

Order Selection screen should include the below listed fields:

Order number , Order Type, Functional location, Equipment, Main. Work center,

General Data/Administrative Data:

Priority, created by

Location Data/Acc. Assignment:

Maintenance Plant

Output:

Main. Plant, Priority, Notification, Order No., Description, Order Type, basic start date, Functional
location, Equipment, Equip. Desc. Main, work center, cost center, Plant selection, System Status,
entered/created by.

2. IW32 – Change Work Order

Page 2 of 16
PM Tech. will need the ability to manage the following in a work order.
1. Change/update the following
Technicians will need ability to release a work order
Technician needs to be able to technically complete works orders
Header Data Tab
• Order Desc.
• Maint. Work center
• PMActType
• SystCond.
• Basic Start and Fin. date
• Priority
• Functional location
• Equipment
Operations Tab
• Operation Description
• long text
• Work (hours to perform operation)
• Number of Persons working on operation
• Duration (total number of hours to complete operation)
• Should also be able to add an operation as needed

Components Tab
• Add or update components (spare parts) and Reqmt Qty as needed

OUTPUT:
Should look similar to, IW32 screen desk top view. With above items available to add, edit…
Should also include a ref. to the notification if work order was created from an approved
notification.

Proposed Solution :

Page 3 of 16
1. IW38 – Change PM Orders – List

It is proposed to use the existing standard FIORI app F2175 - Find Maintenance Order. On
clicking on the work order number it should redirect to IW32 (Change Work order) app.

3. IW32 – Change Work Order

It is proposed to develop a new custom FIORI app to meet the requirement and the details
are as below.

Input Screen with search help

On pressing the search help, the user should be able to filter with below fields
(similar to the app ID F2175)
Order No
Order type
Priority
Funtional Location
Equipment
Start date
End Date
Work Center
Maintenance Plan
Maintenance Item
Order Status

Page 4 of 16
Upon entering the required filter criteria, below output to be displayed

On selecting a perticular work order, below change work order screen to be displayed which will be silar
to IW38 screen below

Page 5 of 16
PM Tech. will need the ability to manage the following in a work order.
Change/update the following
Technicians will need ability to modify the header status, and Description
Header Data Tab
• Maint. Work center
• PMActType
• SystCond.
• Basic Start and Fin. date
• Priority
• Functional location
• Equipment

Page 6 of 16
Operations Tab
• Operation Description
• long text
• Work (hours to perform operation)
• Number of Persons working on operation
• Duration (total number of hours to complete operation)
• Should also be able to add an operation as needed
 External sub tab
o Operation Qty
o Price
o Currency
o Material Group
o Cost Element
o Agreement
o Vendor
o Requisitioner
 Actual data sub tab
o Requision number & Item Number
o GR Qty
o PO Exist (Check box)

Page 7 of 16
External sub tab

Actual data sub tab

Page 8 of 16
Components Tab
• Add or update components (spare parts) and Reqmt Qty as needed
 Item
 Component
 Description
 Item Category
 Requirement Qty
 UOM
 Storage location
 Plant
 Operation number
 Batch
 Purchasing data – sub tab
o Requirement Qty
o Price
o Currency
o Material Group
o G/L Account
o Agreement
o Vendor
o Requisitioner

Page 9 of 16
Purchasing data - Sub tab

2. Solution Integration & Process Details


NA

3. Alternate Solutions – Evaluations


N# Alternative Evaluation Reason for Rejection
N/A

Page 10 of 16
C. Key-user / Business Analyst Information
1. Country Specific Considerations
NA

2. Dependencies
NA

3. Test Scenarios
test scnarios
ID Test Scenario Expected Results Comments Regr

(Y/N)

1 IW38 – Test Work order list Work order list should


be displayed as per the
search criteria
2 IW32 – Test Work order change Change work order
3 IW32 – Add internal operations Should be able to add
operations with Work
details i.e total work,
no of labours, duration
4 IW32 – Add external operations Should be able to add
external details and PR
should get created
5 IW32 – Add stock components Should be able to add
Components, and
reservation nuber
should get generated
6 IW32 – Add non stock Should be able to add
components Components, and PR
nuber should get
generated
7 IW32 – Delete operations Should be able to
delete the operations
fron the order
8 IW32 – Delete components Should be able to
delete the components
fron the order

4. User Interaction
N/A

Page 11 of 16
5. Execution Frequency (select all that apply)

X On Demand / Ad Hoc Batch / Scheduled


X Real-time X Daily
Process Dependent Weekly
Workflow Triggers Monthly
Other Yearly

Page 12 of 16
6. High Level Cut-Over Plan
NA

7. Change Management Items


NA

7.1 Overview
N/A

7.2 Organizational Changes


N/A

7.3 Business Process Changes


N/A

8. High Level Contingency Plan


N/A

9. Open Issues
N# Issue Date Issue Title / Description Priority Assigned To Resolved
Date
N/A

D. Solution Details per RICEFW

REPORTS Yes No

Page 13 of 16
INTERFACES / CONVERSIONS Yes No

ENHANCEMENTS Yes No

FORMS
Yes ● No

Yes No

Page 14 of 16
Section II - Additional Details
Yes No
A. Configuration

9. Requested Functionality in brief

1. Custom Tables
NA

2.1.Table Maintenance Requirements (custom tables only)

2.2.Table Type
Customizing Table Application Table
Maintenance Screen Volume (expected records)

Field Key Data Type / Description Additional


Element Requirements

2.3.Security Requirements for table maintenance

Page 15 of 16
2. Detailed Processing Logics / Processing Steps

B. Security/Authorization Requirements
Role Role Description Tcode Impact

C. Basis Activities

1. Servers / Folders
NA

2. Batch jobs
NA

Page 16 of 16

You might also like