BAES - FS - M-026 - App To Create Maintenance or Service Helpdesk Request

NOT PROTECTIVELY MARKED
BAE SYSTEMS PROPRIETARY
M-026
App to create maintenance or service helpdesk

request
20/10/2017
V0.01
This is an unpublished work the copyright in which vests in BAE Systems. All rights reserved.
The information contained in this document is proprietary to BAE Systems unless stated otherwise and is supplied without liability for
errors or omissions and is only for the intended recipient on the express understanding that it is to be treated as confidential and that it
may not be copied, used or disclosed to others in whole or in part in any form for any purpose except as authorised in writing by BAE
Systems. The copyright and the foregoing restriction on reproduction, disclosure and use extend to all media in which the information
may be embodied.
Public Access: Freedom of Information Act 2000, etc.
This document contains commercially-sensitive commercial information as of the date provided to the original recipient by BAE Systems
and is provided in confidence. Following a request for this information public authorities should consult with BAE Systems regarding the
current releasability of the information prior to the decision to release all or part of this document, and in any event are to notify BAE
Systems prior to any release. Release of this information by a public authority may constitute an actionable breach of confidence.
BAE Systems Surface Ships Limited, Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, Farnborough, Hants,
GU14 6YU, UK, Registered in England & Wales No: 6160534
BAE Systems Maritime Services,

Broad Oak, The Airport, Portsmouth, Hampshire PO3 5PQ

M-026 20/10/2017
App to create maintenance or service helpdesk request V0.01
Security Warning
THIS DOCUMENT IS THE PROPERTY OF

BAE Systems Surface Ships Limited
ANY PERSON FINDING THIS DOCUMENT SHOULD HAND IT TO A POLICE STATION FOR ITS SAFE
RETURN TO:
BAE Systems Surface Ships Limited

Warwick House, Farnborough Aerospace Centre,
Farnborough, Hampshire, GU14 6YU England
WITH PARTICULARS OF HOW AND WHERE FOUND.
THE UNAUTHORIZED RETENTION OR DESTRUCTION OF THE DOCUMENT MAY BE AN OFFENCE UNDER

THE OFFICIAL SECRETS ACTS OF 1911 TO 1989
Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

ii Any use, duplication or disclosure of information contained on this page is subject to the restrictions on the back cover of this document.
20/10/2017 M-026
V0.01 App to create maintenance or service helpdesk request
Approvals
Signature
Sasha Bailey
Author / Authors 20/10/2017
Service Management Functional Consultant
Signature
Del Miller
Reviewer 01/11/2017
Business Solution Lead – PNB
Signature
Andrea Miller
Authoriser 08/11/2017
Lead Solution Architect
Acceptance
Date
Signature Frank McAleer
Title Business Process Owner, BAE Systems.
Distribution
Name # Copies
Project File 1 Copy
< Others > 1 Copy

Any use, duplication or disclosure of information contained on this page is subject to the restrictions on the back cover of this document. iii
M-026 20/10/2017
Document History
Version History
Version Date Superseded documents/Change Reference
0.01 20/10/17 Initial draft
01/11/17 Reviewed - Del Miller
08/11/17 Approved - Andrea Miller
Amendments
New Version Reference:
Author of Amendment:
Date of Amendment:
Summary of Changes
Section, Paragraph etc Synopsis of Change Change Reference

iv Any use, duplication or disclosure of information contained on this page is subject to the restrictions on the back cover of this document.
20/10/2017 M-026
Contents
1 EXECUTIVE SUMMARY 8
1.1 Object Information and Attributes 8
1.2 Business Driver 8
1.3 Desired Functionality Overview 9
1.4 Assumptions 9
1.5 Project / Development Constraints 9
1.6 Performance Criteria 10
1.7 Other Objects Affected 10
1.8 Application / Tile Name 10
1.8.1 Tile Details 10
1.8.2 Field Mapping 11
1.8.3 Flow Diagram of Design (if applicable) 11
2 DETAILED REQUIREMENTS 13
2.1 Processing Logic 13
2.1.1 Dropdown Lists/Search Helps 13
2.1.2 Screen Requirements 15
2.2 Design – Screen Layout 15
2.2.1 New Notification Screen 15
2.2.2 Search Existing Notification Screen 41
2.2.3 Worklist Screen 42
2.2.4 Worklist: Filter Screen 43
2.2.5 Detail Screen – Notification Tab 44
2.2.6 Detail Screen – Attachments Tab 54
2.2.7 Detail Screen – Work Order Tab 54
2.2.8 Create Case 56
2.2.9 Create Order 56
2.3 PERFORMANCE CONSIDERATIONS 57
2.4 AUTHORISATION PARAMETERS 57
2.5 SECURITY REQUIRMENTS 57
2.6 EXISTING SAMPLE PROGRAM 57
3 Extension Details 58
3.1 EXTENSION ATTRIBUTES 58
3.2 Exit Name 58
3.3 BAdI 58
3.4 Function Group Enhancement 58
3.5 Class / Interface Enhancement 58
3.6 Source Code Plug Ins 58
3.7 Web Dynpro Enhancement 58
3.8 Associated Portal Development 58
3.9 New Custom Table Requirement 59
3.9.1 Allowed Values Tables 59
3.9.2 Custom Case Table 60

Any use, duplication or disclosure of information contained on this page is subject to the restrictions on the back cover of this document. v
M-026 20/10/2017
4 ADDITIONAL INFORMATION 61
4.1 Unit Test Plan 61
4.2 Information Security 61
4.2.1 Information Classification 61
Architecture 62
4.2.2 Security Roles (Profiles and Authorizations) 65
4.3 Audit 65
4.4 Error Handling 66
5 Exception Handling Rules 67
List of Figures
No table of figures entries found.
List of Tables
No table of figures entries found.

vi Any use, duplication or disclosure of information contained on this page is subject to the restrictions on the back cover of this document.
20/10/2017 M-026
Glossary
Definitions
Abbreviations
Acronym Description
References
No Reference Title Version / Date

Any use, duplication or disclosure of information contained on this page is subject to the restrictions on the back cover of this document. vii
M-026 20/10/2017
1 EXECUTIVE SUMMARY
1.1 Object Information and Attributes
The following is current information about this object and document:
Object ID SVM_M_026
Title M-026 Service Centre App
Team Which Owns the Service Management

Object
System Version S/4 HANA 1610 FPS02
Development Type UI5 Frontend
Disposition Draft
Estimated Complexity Very Complex
Release Phase 2 Work Package 2
Related Business 6.1.1 Work Request

Process Flow
Approver(s) & Date & Del Miller

Version
1.2 Business Driver

The EBS Programme is the implementation of SAP S/4 HANA into BAE Maritime Services.
Phase 1 focused on the system conversion from SAP ECC6 to S/4 HANA for Products and
Training Services (P&TS). Phase 2 is focused on the replacement of legacy ERP system IFS
with S/4 HANA for Naval Base Services (NBS) and Fleet Services (FS).
Across the Naval Base work is requested via the Service Desk. This can be to report a fault,
request new work or request a service. The standard SAP Notification screens are not
structure in a way that drive a Service Center call, and the business require a solution to
standardise the process and improve the customer experience. There is an expectation that
the UI5 application described in this document will aid in guiding the Service Center
operatives to request the necessary information and steer the customer through a standard
set of questions in a user friendly and intuitive manner.

8 Any use, duplication or disclosure of information contained on this page is subject to the restrictions on the back cover of this document.
20/10/2017 M-026
1.3 Desired Functionality Overview

With the introduction of S/4 HANA, UI5 applications can be developed to provide a better
user experience. This particular application will allow the Service Center operatives to
create a new request and update an existing request. When a new request is raised, a
Notification is created, and based on the rules provided in the processing logic; a Work
Order or Case could be created automatically at the same time. During the Notification
update, the ability to progress a Notification to a Work Order will be available.
UI5 Requirements
Number Description of Requirement

1. Create a Notification
The Service Center operatives will be able to enter details relating to the customer request e.g.
the work required to be carried out, which Functional Location or Equipment it relates to, the type
of object affected and any related damage codes. Additional information will be added to record
specific details relating to the type of work that is required.
2. Edit a Notification
The Service Center operatives will be able to amend a previously raised Notification.
3. Create a Work Order

A Work Order will be created automatically when raising the Notification when one is required
during the raising of a request.
4. Create a Work Order

If a Work Order is required at the point of raising a Notifications, this will be created
automatically.
5. Create a Case
If the request is to be routed through the FML/FMP process, a Case will be automatically created
when raising a Notification.
1.4 Assumptions
The development of WRICEF objects #E-207, #E-217, #E-219 and #E-245 have been
completed.
The UI5 app will only be available on a desktop and will not be used on a mobile device.
Only authorised users will be granted access to the application.
The Categories used to determine the scripts will be defined as individual Catalog Profiles
that will be used to determine mandatory / optional fields. If the categories cannot be
defined by Catalog Profiles, all fields within the script area will optional
1.5 Project / Development Constraints

WRICEF development objects #E-207, #E-217, #E219 and #E-245 must have been
completed.

Any use, duplication or disclosure of information contained on this page is subject to the restrictions on the back cover of this document. 9
M-026 20/10/2017
1.6 Performance Criteria

No performance considerations have been identified.
Performance Requirements for Conversions

<Number> <Type>
Average Transactions / Records and Type per Conversion Run:
<Number> <Type>
Peak Transactions / Records and Type per Conversion Run:
<’X’ Transactions Per Second,
Required Throughput For Conversion: Minute, Hour>
1.7 Other Objects Affected

The following item(s) are key dependencies:
Configuration – Notification Types, BUS00001 User Status profile for Notifications, Catalog
profiles, Catalog code groups, Catalog codes,
#E-217 – Additional fields on Functional Location and Equipment
#E-207 – Alert for Environmental Assets
#E-245 – Defect Code Search Enhancement
1.8 Application / Tile Name
1.8.1 Tile Details
Requirement Details (if applicable)
SAP Fiori Launch pad Tile Service Center
App Name Service Centre App
Group Service Center Operative
Catalog Z_SERVICE_CENTER_CAT
Tile Type Static App Launcher
Create/Edit/View Create / Edit / View
Wireframe link http://56ag6c.axshare.com

20/10/2017 M-026
Languages
English
1.8.2 Field Mapping
Field mappings are defined within each appropriate section below and therefore are not in the attached
document:
1.8.3 Flow Diagram of Design (if applicable)

M-026 20/10/2017
Create Notification
Enter
Notification
Details
Select Category
Enter
Additional
Details
Save Notification
Has an Alert Is this New

Is it an enquiry? No No No
been identified? Work?
Yes Yes Yes
Notification and Notification and

Notification Created Notification Created
Case Created Work Order Created

20/10/2017 M-026
2 DETAILED REQUIREMENTS
2.1 Processing Logic
2.1.1 Dropdown Lists/Search Helps
The following search helps/dropdowns are required for this application:
2.1.1.1 Dropdown Lists

Dropdown List: Type
Field Name Technical Name Details
Notification Type TQ80-QMART Notification Types. This list should be
filtered to only contain those values
found in table Allowed Values:
Notification Type (see section ).
Description TQ80_T-QMARTX The description of each Notification
Type, retrieved from table TQ80_T.
Select from TQ80_T where SPRAS =
'EN'.
Dropdown List: Category

Category This list should be filtered to only
contain those values defined in the
domain restricted to Notification Type
as described in enhancement E-229
Category Description Description of Category
Dropdown List: Type of Object

Object Part QPGR- KURZTEXT Object Part Group Code.
Select from QPGR where QPGR-
CODEGRUPPE = T352C- QCODEGRP,
found where T352C-RBNR = Category
Catalog Profile and T352C-QKATART =
“B”

M-026 20/10/2017
Object Part Code QPCD-KURZTEXT Object Part Codes linked to the Object
Part Code Group.
Select from QPCD where QPCD-
“B”
Dropdown List: Type of Damage

Damage Group CPGR- KURZTEXT Object Part Group Code.
Select from QPGR where QPGR-
“C”
This list should be filtered to only
contain those values found in table
ZPM_DEFECT where the Object Part
Group Code and Object Part Group
match. If no match found, show all
records returned
Damage Code QPCD-KURZTEXT Object Part Codes linked to the Object
Part Code Group.
“C”
This list should be filtered to only
contain those values found in table
ZPM_DEFECT where the Object Part
Group Code and Object Part Group
match. If no match found, show all
records returned
Dropdown List: Department

Department Code QPCD- KURZTEXT Department Code.
CODEGRUPPE = “ZBSDP001”

20/10/2017 M-026
Dropdown List: Priority

Priority T356-PRIOK Priority Code.
Select from T356 where ARTPR = “BA”
Description T356_T-PRIOKX The description of each Priority,
retrieved from table T356_T.
Dropdown List: Task List

Type of Task List TCA01-PLNTY Task List Type
Dropdown List: Sub Category

Sub Category Allowed value custom field Allowed Values: Sub Category (see
(section 3.9.1) section 3.9.1).
2.1.2 Screen Requirements

The App uses adaptive technology and will run on a device with a rectangular screen, with a resolution
of 1366x768 or higher.
2.2 Design – Screen Layout

(Create one of these per screen)
2.2.1 New Notification Screen
2.2.1.1 Screenshot (From Wireframe Output)

M-026 20/10/2017
This screen will allow the user to create a new Notification, or select an existing Notification using the
selection criteria on the “Existing Notification” tab. When the user first launches the app, it should show
the “New Notification” view. The “Existing Notification” screen is detailed in section 2.2.2.
2.2.1.2 Screen Fields

Field M/O/D* SAP Field Type Length Comments D/S^
Contact N/A IHPA-PARNR CHAR 12 Partner (IHPA- PARVW) = Z1 S
Person and Object Number = QMEL-
OBJNR.
Standard Search Help for
Contact Person Business
Partners
Reported M QMEL- CHAR 80 Name displayed (DIADR- D&S
by ZZ_POCNAME NAME_LIST) from Z1 Business
Partner
If no match, allow direct entry
Phone No M QMEL- CHAR 30 ADR2-TEL_NUM from Z1 D&S
ZZ_POCPHONE business partner selected
above
If no value, allow direct entry
Email O QMEL- CHAR 241 ADR6-SMTP_ADDR from Z1 D&S
address ZZ_POCEMAIL business partner selected
above
If no value, allow direct entry
Type M QMEL-QMART CHAR 2 Standard Search Help for D&S
Notification Types

20/10/2017 M-026

Category M ZZ_CATEGORY CHAR 30 Dropdown : Category D
Category will be used to drive

the scripts. See events /
actions to determine which
scripts are displayed based on
the category choice
Catalog N/A Stored in Notification table, S
Profile QMEL-RBNR CHAR 9 not displayed on screen.
Functional M VIQMEL- Standard Search Help for D&S
Location TPLNR CHAR 30 Functional Locations
Equipment O VIQMEL - CHAR 18 Standard Search Help for D&S
EQUNR Equipments
Object M QMFE-OTGRP CHAR 8 Dropdown : Type of Object D&S
Part Code
Group
Object M QMFE-OTEIL CHAR 4 Dropdown : Type of Object D&S
Part Code
(text displayed)
Damage M QMFE-FEGRP CHAR 8 Dropdown : Type of Damage D&S
Code
Group
Damage M QMFE-FECOD CHAR 4 Dropdown : Type of Damage D&S
Code
(text displayed - QPCD-
KURZTEXT)
Coding O QMEL-QMGRP CHAR 8 Predefined from enhancement D&S
Code E-245
Group Dropdown : Department
Coding O QMEL-QMCOD CHAR 4 Predefined from enhancement D&S
Code E-245
Dropdown : Department
(text displayed - QPCD-

KURZTEXT)
Priority N/A QMEL-PRIOK CHAR 1 Predefined from enhancement D&S
Code E-245
Standard Drop Down
(text displayed - T356_T-

PRIOKX)

M-026 20/10/2017

Team N/A IHPA-PARNR CHAR 12 Predefined from enhancement D&S
Leader BP E-245
Partner (IHPA- PARVW) = VW
and Object Number = QMEL-
OBJNR.
Person Responsible Business
Partner
If no match, allow direct entry
Name displayed (DIADR-

NAME_LIST)
Task List N/A PLKO-PLNTY CHAR 1 Predefined from enhancement S
Type E-245
Standard Search Help For
Task List
Task List N/A PLKO-PLNAL CHAR 8 Predefined from enhancement S
Group E-245
Standard Search Help for Task
List
Task List N/A PLKO-PLNNR CHAR 2 Predefined from enhancement D&S
Group E-245
Counter Standard Search Help for Task
(text List
displayed (text displayed for task list -
for task PLKO-KTEXT)
list)
Follow On O QMEL- CHAR 12 Standard Search Help for D&S
Work ZZ_FOORDER Work Orders
Order
*Mandatory, Optional, Display
^Display on Screen, Store in Notification

20/10/2017 M-026
2.2.1.3 List of Actions/Events from Screen

M-026 20/10/2017
Event Action Matrix

Event Action Updates That Occur When This Event Is Initiated
Initial screen entry Initialisation On initialisation the screen fields will be blank
This screen will have different additional fields based
on the option chosen by the user.
The following screens are displayed based on the

Category chosen :
LS Lifting Services (section 2.2.1.4)

BS Building Services (section 2.2.1.5)
GE General Enquiry (section 2.2.1.6)
Category is selected Select Category KW Kelda Water Services (section 2.2.1.7)
BC Base Clearance (section 2.2.1.8)
RO Rounds (section 2.2.1.9)
PH Plant Hire (section 2.2.1.10)
BS Berthing Services (section 2.2.1.11)
ES Electrical Shore Connections (section 2.2.1.12)
MS Mechanical Shore Connections (section 2.2.1.13)
SS Soft Services (Cleaning) (section 2.2.1.14)
WS Waste Services (section 2.2.1.15)
The following checks are performed:
 Standard Warranty
Select Functional  The checks described in enhancement E-207 will be
Functional Location is selected
Location performed.
Messages will be displayed to the user, which will
indicate if any of the checks returned information.
The following checks are performed:
 Standard Warranty
Equipment is selected Select Equipment  The checks described in enhancement E-207 will be
performed.
Messages will be displayed to the user, which will
indicate if any of the checks returned information.
Clicking this button will perform the following:
1. If the Object Type and Damage Codes do not
match a record in the ZPM_DEFECT table, the
Notification is not created and an appropriate
Entry is saved Click Save error message is displayed. The details should
be left on the screen until the data record can
be created.
2. The Notification will be created in the backend
system and all data entered should be saved.

20/10/2017 M-026
3. If the New Work field is set to yes (in the

appropriate scripts) a Case is automatically
created with the Notification following the
procedure described in section 2.2.8
4. Create a Work Order automatically with the
Notification following the procedure in section
2.2.9 if the following is true:
a. The Notification did not generate an
alert based on enhancement E-207 or
warranty
b. The Notification is not an Enquiry
c. The New Work field is not set to yes
d. The category is not Plant Hire
NB, If the Object Type and Damage Codes
match a record in the ZPM_DEFECT table, but
the following fields are not populated, a
Notification is created but the Work Order
should not be created:
 ZPM_DEFECT-MAT
 ZPM_DEFECT-WORKCENTRE
 All of ZPM_DEFECT-TLTYPE &
ZPM_DEFECT-TLGROUP & ZPM_DEFECT-
TLCOUNTER
An appropriate message should be displayed
indicating this.
A confirmation message will be displayed to the user,

which will include the system generated Notification
number (QMEL-QMNUM), the Case Number () where
appropriate and the Work Order Number (QMEL-
AUFNR) where appropriate with any additional
messages.
Click Existing Clicking this button will take the user to the “Existing
Search Existing Notifications
Notification Notification” screen as defined in section 2.2.2.
Clicking the button will allow a document to be
Add an attachment Click “+”
attached and create a new Document link through BDS
2.2.1.4 Lifting Services

M-026 20/10/2017
Field M/D SAP Field Type Length Comments D/S

/O
Title M QMEL-QMTXT CHAR 40 D&S
Weight M QMEL-ZZ_WEIGHT CHAR 20 Free Text D&S
Dimension M QMEL- CHAR 20 Free Text D&S
s ZZ_DIMENSIONS
Ship Name M QMEL- CHAR 30 Dropdown : Ship Name D&S

ZZ_SHIPNAME
Customer O QMEL- CHAR 20 Free Text D&S

Business ZZ_CUSTBUSAREA
Area
Date M DATS 8 Calendar Selection D&S
Required Default value to Notification
QMEL- Required Start Date
ZZ_DATEREQD (QMEL-STRMN)
Description O CHAR N/A Text ID = “LTXT” D&S

of Task Language = “EN”
Name = QMEL-QMNUM
Long Text (including leading zeroes)
Object = “QMEL”
Ship M QMEL-ZZ_SHIPLOC CHAR 20 Free text D&S
Location

20/10/2017 M-026
Field M/D SAP Field Type Length Comments D/S

/O
Number M CHAR 1 Radio Button D&S
type -Work Grouped with QMEL-
Order QMEL- ZZ_NTUIN & QMEL-
Number ZZ_NTORDER ZZ_NTPROJECT

type –UIN Grouped with QMEL-
QMEL-ZZ_NTUIN ZZ_NTORDER & QMEL-
ZZ_NTPROJECT
type - QMEL- Grouped with QMEL-
Project ZZ_NTPROJECT ZZ_NTUIN & QMEL-
Code ZZ_NTORDER
Number M QMEL- CHAR 20 Free Text D&S
ZZ_SERVNUMBER
Slingers M QMEL- CHAR 1 Y/N D&S

Required ZZ_SLINGERS
MT M QMEL- CHAR 1 Y/N D&S

Transport ZZ_TRANSPORT
Required
2.2.1.5 Building Services

M-026 20/10/2017
Building Services
Field M/O/D SAP Field Type Length Comments D/S
Language = “EN”
Name = QMEL-QMNUM
(including leading zeroes)
Long Text Object = “QMEL”
Contact N/A IHPA-PARNR CHAR 12 Partner (IHPA- PARVW) = S
Person Z2 and Object Number =
QMEL-OBJNR.
Partners
Alternative O CHAR 80 Name displayed (DIADR- D&S
Point of NAME_LIST) from Z2
Contact QMEL- Business Partner
ZZ_APOCNAME If no match, allow direct
entry
Phone O CHAR 30 ADR2-TEL_NUM from Z2 D&S
business partner selected
QMEL- above
ZZ_APOCPHONE If no value, allow direct
entry
Email O CHAR 241 ADR6-SMTP_ADDR from Z2 D&S
above
QMEL- If no value, allow direct
ZZ_APOCEMAIL entry
New Work M QMEL- CHAR 1 Y/N

ZZ_NEWWORK
Work M AUFK-VAPLZ CHAR 8 Predefined from D &S

Centre enhancement E-245
Work Centre
Attachment O Link document through BDS

20/10/2017 M-026
2.2.1.6 General Enquiry
General Enquiry
Title M QMEL-QMTXT CHAR 40
Description O CHAR N/A Text ID = “LTXT”
Language = “EN”
Name = QMEL-QMNUM
2.2.1.7 Kelda Water Services

M-026 20/10/2017
Kelda Water Services

Language = “EN”
Name = QMEL-QMNUM
KWS O QMEL-ZZ_KWSREF CHAR 40
Reference
KWS O QMEL- CHAR 20
Priority ZZ_KWSPRIORITY
Fault Type O QMEL- CHAR 20

ZZ_KWSFAULT

QMEL-OBJNR.
Partners
Contact Business Partner
QMEL- If no match, allow direct
ZZ_APOCNAME entry

above
ZZ_APOCPHONE entry
Email O CHAR 241 ADR6-SMTP_ADDR from D&S

Z2 business partner
selected above
ZZ_APOCEMAIL entry
Attachment O Link document through

BDS
2.2.1.8 Base Clearance

20/10/2017 M-026
Base Clearance
Language = “EN”
Name = QMEL-QMNUM
Ship O QMEL- CHAR 40 Dropdown : Ship Name
ZZ_SHIPNAME
Ship UIN O QMEL-ZZ_SHIPUIN CHAR 20
Location O QMEL-ZZ_SHIPLOC CHAR 40
Date M DATS 8 Standard Search Help

Required (Calendar)
Default value to
QMEL- Notification Required Start
ZZ_DATEREQD Date (QMEL-STRMN)
2.2.1.9 Rounds

M-026 20/10/2017
Rounds
Work O AUFK-VAPLZ Predefined from
Centre enhancement E-245
Work Centre
Actionee O QMEL-ZZ_ACTIONEE CHAR 80 Free Text

Language = “EN”
Name = QMEL-QMNUM
Long Text (including leading zeroes)
Object = “QMEL”
Date M QMEL- DATS 8
Completed ZZ_DATECOMPL
By
Rounds Ref M QMEL- CHAR 20
No ZZ_ROUNDSREF
Attachment O Link document through

BDS
2.2.1.10 Plant Hire

20/10/2017 M-026

M-026 20/10/2017
Plant Hire
Field M/O/ SAP Field Type Length Comments D/S
D
Title M QMEL-QMTXT CHA 40
R
Sub M CHA 40 Dropdown : Sub Category
Category QMEL-ZZ_SUBCAT R
Description M QMEL- CHA 40
of Asset ZZ_ASSETDESC R
Required
KPI Passed O CHA 1 Y/N
QMEL-ZZ_KPIPASS R

20/10/2017 M-026

D
MEWP O Text ID = “LTXT”
Details Language = “EN”
Name = QMEL-QMNUM
+ “ZAQMELMEWP”
Object = “QMEL”
QMEL-ZZ_MEWP
Pressure O Text ID = “LTXT”
Washer Language = “EN”
Details Name = QMEL-QMNUM
QMEL- + “ZAQMELPRES”
ZZ_PRESSWASH Object = “QMEL”
Generator O Text ID = “LTXT”

Name = QMEL-QMNUM
QMEL- + “ZAQMELGENR”
ZZ_GENERATOR Object = “QMEL”
Compresso O Text ID = “LTXT”

r Details Language = “EN”
Name = QMEL-QMNUM
QMEL- + “ZAQMELCOMP”
ZZ_COMPRESSOR Object = “QMEL”
Fuel Tank O QMEL- CHA 1 Check Box

Required ZZ_FUELTANK R
Other O Text ID = “LTXT”

Language = “EN”
Name = QMEL-QMNUM
+ “ZAQMELOTHR”
QMEL-ZZ_OTHER Object = “QMEL”
Authorised M CHA 1 Check Box

QMEL-ZZ_AUTH R
Required M CHA 1 Check Box

to be QMEL-ZZ_LIFTABLE R
liftable

M-026 20/10/2017

D
Description O Text ID = “LTXT”
of Job Language = “EN”
Name = QMEL-QMNUM
Object = “QMEL”
New custom Text ID will

need creating to store this
information against a
Long Text Notification
Deliver To M QMEL- CHA 40 Free Text D&S

ZZ_DELIVERY R
Work M QMEL- CHA 12 Standard Search Help for D&S

Order ZZ_PHWORKORD R Work Order
Number
HSS M QMEL- CHA 40 D&S
Account ZZ_HSSNUMBER R
Number
Short O QMEL- CHA 40 D&S
Name ZZ_SHORTNAME R
Contact N/A IHPA-PARNR CHA 12 Partner (IHPA- PARVW) = S

Person R Z1 and Object Number =
QMEL-OBJNR.
Partners
1st Point of M CHA 80 Name displayed (DIADR- D&S
Contact R NAME_LIST) from Z1
Business Partner
If no match, allow direct
QMEL-ZZ_POCNAME entry
Phone M CHA 30 ADR2-TEL_NUM from Z1 D&S

R business partner selected
above
ZZ_POCPHONE entry
Emails O CHA 241 ADR6-SMTP_ADDR from D&S

R Z1 business partner
selected above
ZZ_POCEMAIL entry

20/10/2017 M-026

D
QMEL-OBJNR.
Partners
2nd Point of O CHA 80 Name displayed (DIADR- D&S
Contact R NAME_LIST) from Z2
Business Partner
ZZ_APOCNAME entry
Phone O CHA 30 ADR2-TEL_NUM from Z2 D&S

above
ZZ_APOCPHONE entry
Email O CHA 241 ADR6-SMTP_ADDR from D&S

R Z2 business partner
selected above
ZZ_APOCEMAIL entry
Line M QMEL- CHA 40 Free Text D&S

Manager ZZ_LINEMNGR R
Dates M DATS 8 Standard Search Help D&S

Required (Calendar)
Default value to
QMEL- Notification Required Start
ZZ_DATEREQD Date (QMEL-STRMN)
Auto Off M QMEL- CHA 1 Y/N D&S

Hire ZZ_AUTOOFFHIRE R
2.2.1.11 Berthing Services

M-026 20/10/2017
Berthing Services
Language = “EN”
Name = QMEL-QMNUM
Required M QMEL-ZZ_TIMEREQD TIMS 6 D&S
Start Time
2.2.1.12 Electrical Shore Connections
Electrical Shore Connections


20/10/2017 M-026

Language = “EN”
Name = QMEL-QMNUM
Connection M QMEL- CHAR 20 Free Text D&S
Location ZZ_CONNFROM
From
Location To ZZ_CONNTO
Voltage/Cur M QMEL- CHAR 20 Free Text D&S

rent rating ZZ_VOLTCURR
Size of Plug M QMEL-ZZ_PLUG CHAR 20 Free Text D&S
Required M DATS 8 Standard Search Help D&S

Start Date (Calendar)
QMEL-
Default value to
ZZ_DATEREQD
Notification Required Start
Date (QMEL-STRMN)
Required M TIMS 6 Standard Search Help D&S

Start Time QMEL- (Time)
ZZ_TIMEREQD Default value to
Date (QMEL-STRUR)
Project M CHAR 20 Free Text D&S
QMEL-
Number /
ZZ_ASSNUMB
Work Order
Number
QMEL-OBJNR.
Partners
ZZ_APOCNAME entry

above
ZZ_APOCPHONE entry

M-026 20/10/2017

Email O CHAR 241 ADR6-SMTP_ADDR from Z2 D&S
above
ZZ_APOCEMAIL entry
2.2.1.13 Mechanical Shore Connections
Mechanical Shore Connections

Language = “EN”
Name = QMEL-QMNUM
Location ZZ_CONNFROM
From
Connection M QMEL-ZZ_CONNTO CHAR 20 Free Text D&S
Location To
Required M DATS 8 Standard Search Help D&S
Start Date (Calendar)
QMEL-
Default value to
ZZ_DATEREQD
Date (QMEL-STRMN)

20/10/2017 M-026

Required M TIMS 6 Standard Search Help D&S
Start Time (Time)
QMEL-
Default value to
ZZ_TIMEREQD
Date (QMEL-STRUR)
Project M CHAR 20 Free Text D&S

QMEL-
Number /
ZZ_ASSNUMB
Work Order
Number
QMEL-OBJNR.
Partners
ZZ_APOCNAME entry

above
ZZ_APOCPHONE entry
Email O CHAR 241 ADR6-SMTP_ADDR from D&S

Z2 business partner
selected above
ZZ_APOCEMAIL entry
2.2.1.14 Soft Services (Cleaning)

M-026 20/10/2017
Soft Services (Cleaning)

Title M QMEL-QMTXT CHA 40 D&S
R
Description O CHA N/A Text ID = “LTXT” D&S
R Language = “EN”
Name = QMEL-QMNUM
QMEL-OBJNR.
Partners
Alternative O CHA 80 Name displayed (DIADR- D&S
Point of R NAME_LIST) from Z2
entry
above
ZZ_APOCPHONE entry
Email O CHA 241 ADR6-SMTP_ADDR from Z2 D&S

above
ZZ_APOCEMAIL entry
2.2.1.15 Waste Services

20/10/2017 M-026
Waste Services
D
Title M QMEL-QMTXT CHA 40 D&S
R
Description O CHA N/A Text ID = “LTXT” D&S
R Language = “EN”
Name = QMEL-QMNUM
Ship ETD M CHA 20 D&S
QMEL-ZZ_SHIPETD
R

QMEL-OBJNR.
Partners
Alternative O CHA 80 Name displayed (DIADR- D&S
Point of R NAME_LIST) from Z2
entry
above
ZZ_APOCPHONE entry

M-026 20/10/2017

D
Email O CHA 241 ADR6-SMTP_ADDR from Z2 D&S
above
ZZ_APOCEMAIL entry
Attachmen O Link document through

t BDS

20/10/2017 M-026
2.2.2 Search Existing Notification Screen
This screen will allow the user to select an existing Notification using the selection criteria on screen.

Selection Field Apply to SAP Field Requirements
Notification Number QMEL-QMNUM Text search, allowing the user to enter a whole or
partial Notification number.
Order Number QMEL-AUFNR
Reported By QMEL-ZZ_APOCNAME
Date Raised QMEL-QMDAT
Status User status from profile Allow the user to select multiple user statuses to
BUS00001 currently active on include in the search. Only the description of the
Notification status (TJ30T- TXT30) should be displayed to the
user.
See section 2.1.1.1 for dropdown list details.

M-026 20/10/2017
Event Action Matrix

Search Notifications Click Search When the Notification search is performed, use the
information entered in the selection screen to filter the
list of Notifications being displayed on the Worklist
Report information message if no results are returned
2.2.3 Worklist Screen
This screen will display a list of Notifications which the user is interested based on the selection criteria
in the previous screen. Additional search criteria can be applied (see section ).
The header of this list should display the total number of items in the list e.g. "Notifications (4)".
A text search box will also be available, which allow the user to filter the worklist based on the
Description field of each Notification (QMEL-QMTXT).

20/10/2017 M-026

The following fields should be displayed for each Notification in this list:
Selection Field Apply to SAP Field Requirements

Notification Number QMEL-QMNUM
Reported By QMEL-ZZ_POCNAME
User Status TJ30T-TXT30 The description of the numbered user status
currently active on the Notification.
Event Action Matrix

When initialising this screen, the selection criteria from
Initial screen entry Initialisation the previous screen should be used to populate the
worklist
Click a Notification Clicking a Notification in the Worklist sidebar will
Notification Selection in the Worklist trigger that Notification to be displayed in the Detail
Screen (section 2.2.5).
Click Sort button Clicking on the Sort button should display a list of all
Sort Worklist Entries fields which can be sorted by. Clicking on one will sort
the list according to the values in that field.
Click Filter button Clicking on the Filter button will launch the Filter sub-
Filter Worklist Entries screen (section 2.2.4). This will allow users to enter
additional search criteria and refresh the Worklist.
2.2.4 Worklist: Filter Screen
This screen will allow the user to modify the selection criteria which has been used to populate the
Worklist. When the user first launches this screen, it should show the search criteria which have been
applied from the previous selection screen e.g. Raised By: Ann McArthur, Status: Asbestos Alert.
This screen should contain the following selection fields:
Filter Field Apply to SAP Requirements
Field
Notification Number QMEL-QMNUM
Raised By QMEL-ZZ_POCNAME

M-026 20/10/2017
Notification Status TJ30T-TXT30 The description of the

numbered user status
currently active on the
Notification.
2.2.5 Detail Screen – Notification Tab
This screen will display the details of the selected Notification, along with giving access to any
attachments which have been created for the Notification. The Detail Screen will be read-only.

The detail screen will be split into 3 tabs – “Notification”, “Attachments” and “Work Order”
The Notification screen contains the following fields:
Header
Field SAP Field Type Length Comments
Notification QMEL-QMNUM CHAR 12 This should be displayed in the title bar of
Number the Detail Screen e.g. "Notification
100000089"
Description QMEL-QMTXT CHAR 40 In large font

20/10/2017 M-026

Reported By QMEL- CHAR 80
ZZ_POCNAME
Date Raised QMEL-QMDAT DATS 8
Notification QMEL-QMART DATS 8

Type
Status TJ30T-TXT30 CHAR 20 The description of the numbered user
status currently active on the Notification.
Start Date / QMEL-STRMN & DATS 8

Time QMEL-STRUR TIMS 6
End Date / QMEL- LTRMN & DATS 8
Time QMEL- LTRUR TIMS 6
Category QMEL- CHAR 30
ZZ_CATEGORY
Details

Work Order QMEL-AUFNR CHAR 12
Description QMEL-QMTXT CHAR 40
Reported by QMEL- CHAR 80

ZZ_POCNAME
Phone No QMEL- CHAR 30

ZZ_POCPHONE
Email address QMEL- CHAR 241

ZZ_POCEMAIL
Functional VIQMEL-TPLNR CHAR 30

Location
Equipment VIQMEL -EQUNR CHAR 18
Type of Object QMFE-OTEIL CHAR 4 Linked to QMFE-OTGRP, display text

description
Type of QMFE-FECOD CHAR 4 Linked to QMFE-FEGRP, display text

Damage description
Department QMEL-QMCOD CHAR 4 Linked to QMEL-QMGRP, display text

description
Priority QMEL-PRIOK CHAR 1 Text displayed - T356_T-PRIOKX

M-026 20/10/2017

Team Leader IHPA-PARNR Where Partner (IHPA- PARWV) = VW
Name displayed (DIADR-NAME_LIST)
Task List PLKO-KTEXT Where Task list is
Follow On QMEL-ZZFOORDER CHAR 12

Order
Additional fields based on Category:

Lifting Services
Weight QMEL-ZZ_WEIGHT CHAR 20
Dimensions QMEL- CHAR 20
ZZ_DIMENSIONS
Ship Name QMEL- CHAR 20 Dropdown : Ship Name

ZZ_SHIPNAME
Customer QMEL- CHAR 20

Business Area ZZ_CUSTBUSAREA
Date Required QMEL- DATS 8

ZZ_DATEREQD
Description of CHAR N/A Text ID = “LTXT”

Task Language = “EN”
Name = QMEL-QMNUM (including leading
zeroes)
Ship Location QMEL- CHAR 20 Free text

ZZ_SHIPLOC
Number type - CHAR 1 Radio Button

Work Order QMEL- Grouped with QMEL-ZZ_NTUIN & QMEL-
Number ZZ_NTORDER ZZ_NTPROJECT

UIN Grouped with QMEL-ZZ_NTORDER &
QMEL-ZZ_NTUIN QMEL-ZZ_NTPROJECT

Project Code QMEL- Grouped with QMEL-ZZ_NTUIN & QMEL-
ZZ_NTPROJECT ZZ_NTORDER
Number QMEL- CHAR 20

ZZ_SERVNUMBER

20/10/2017 M-026

Slingers QMEL- CHAR 1 Y/N
Required ZZ_SLINGERS
MT Transport QMEL- CHAR 1 Y/N

Required ZZ_TRANSPORT
Building Services
Description CHAR N/A Text ID = “LTXT”
Language = “EN”
zeroes)
Alternative QMEL- CHAR 80
Point of ZZ_APOCNAME
Contact
Phone QMEL- CHAR 30
ZZ_APOCPHONE
Email QMEL- CHAR 241

ZZ_APOCEMAIL
New Work QMEL- CHAR 1 Check Box

ZZ_NEWWORK
Work Centre AUFK-VAPLZ CHAR 8
General Enquiry
Language = “EN”
zeroes)
Kelda Water Services

Language = “EN”
zeroes)
KWS Reference QMEL-ZZ_KWSREF CHAR 40

M-026 20/10/2017

KWS Priority QMEL- CHAR 20
ZZ_KWSPRIORITY
Fault Type QMEL- CHAR 20

ZZ_KWSFAULT

Contact
Phone QMEL- CHAR 30
ZZ_APOCPHONE

ZZ_APOCEMAIL
Base Clearance
Language = “EN”
zeroes)
Ship QMEL- CHAR 40 Dropdown : Ship Name
ZZ_SHIPNAME
Ship UIN QMEL-ZZ_SHIPUIN CHAR 20
Location QMEL- CHAR 40

ZZ_SHIPLOC

ZZ_DATEREQD
Rounds
Work Centre AUFK-VAPLZ
Actionee QMEL- CHAR 80
ZZ_ACTIONEE

Language = “EN”
Long Text zeroes)
Object = “QMEL”
Date QMEL- DATS 8
Completed By ZZ_DATECOMPL

20/10/2017 M-026

Rounds Ref No QMEL- CHAR 20
ZZ_ROUNDSREF
Plant Hire
Sub Category QMEL-ZZ_SUBCAT CHAR 40 Dropdown : Sub Category
Description of QMEL- CHAR 40

Asset Required ZZ_ASSETDESC
KPI Passed QMEL-ZZ_KPIPASS CHAR 1 Y/N
MEWP Details Text ID = “LTXT”

Language = “EN”
zeroes) + “ZAQMELMEWP”
QMEL-ZZ_MEWP Object = “QMEL”
Pressure Text ID = “LTXT”

Washer Details Language = “EN”
QMEL- Name = QMEL-QMNUM (including leading
ZZ_PRESSWASH zeroes) + “ZAQMELPRES”
Object = “QMEL”
Generator Text ID = “LTXT”
ZZ_GENERATOR zeroes) + “ZAQMELGENR”
Object = “QMEL”
Compressor Text ID = “LTXT”
ZZ_COMPRESSOR zeroes) + “ZAQMELCOMP”
Object = “QMEL”
Fuel Tank QMEL- CHAR 1 Check Box
Required ZZ_FUELTANK
Other Text ID = “LTXT”

Language = “EN”
QMEL-ZZ_OTHER zeroes) + “ZAQMELOTHR”
Object = “QMEL”
Authorised QMEL-ZZ_AUTH CHAR 1 Y/N
Required to be QMEL- CHAR 1 Y/N

liftable ZZ_LIFTABLE

M-026 20/10/2017

Description of Text ID = “LTXT”
Job Language = “EN”
Long Text zeroes)
Object = “QMEL”
Deliver To QMEL- CHAR 40
ZZ_DELIVERY
Work Order QMEL- CHAR 12

Number ZZ_PHWORKORD
HSS Account QMEL- CHAR 40

Number ZZ_HSSNUMBER
Short Name QMEL- CHAR 40

ZZ_SHORTNAME
1st Point of QMEL- CHAR 80

Contact ZZ_POCNAME
Phone QMEL- CHAR 30

ZZ_POCPHONE
Emails QMEL- CHAR 241

ZZ_POCEMAIL
2nd Point of QMEL- CHAR 80

Contact ZZ_APOCNAME
Phone QMEL- CHAR 30

ZZ_APOCPHONE

ZZ_APOCEMAIL
Line Manager QMEL- CHAR 40

ZZ_LINEMNGR

ZZ_DATEREQD
Auto Off Hire QMEL- CHAR 1 Y/N

ZZ_AUTOOFFHIRE
Berthing Services

20/10/2017 M-026

Language = “EN”
zeroes)
Required Start QMEL- TIMS 6
Time ZZ_TIMEREQD
Electrical Shore Connections

Language = “EN”
zeroes)
Connection QMEL- CHAR 20
Location From ZZ_CONNFROM

Voltage/Current QMEL- CHAR 20

rating ZZ_VOLTCURR
Size of Plug QMEL-ZZ_PLUG CHAR 20

ZZ_DATEREQD

Time ZZ_TIMEREQD
Project Number QMEL- CHAR 20

/ Work Order ZZ_ASSNUMB
Number
Contact
Phone QMEL- CHAR 30
ZZ_APOCPHONE

ZZ_APOCEMAIL
Mechanical Shore Connections

M-026 20/10/2017

Language = “EN”
zeroes)
Location From ZZ_CONNFROM


ZZ_DATEREQD

Time ZZ_TIMEREQD
Project Number QMEL- CHAR 20

/ Work Order ZZ_ASSNUMB
Number
Contact
Phone QMEL- CHAR 30
ZZ_APOCPHONE

ZZ_APOCEMAIL
Soft Services (Cleaning)

Language = “EN”
zeroes)
Contact
Phone QMEL- CHAR 30
ZZ_APOCPHONE

ZZ_APOCEMAIL
Waste Services

20/10/2017 M-026

Language = “EN”
zeroes)
Ship ETD QMEL- CHAR 20
ZZ_SHIPETD

Contact
Phone QMEL- CHAR 30
ZZ_APOCPHONE

ZZ_APOCEMAIL
Event Action Matrix

When this screen is initialised, it should display the
data relating to the Notification currently selected in
Initial screen entry Initialisation
the Worklist. If no CRF is selected i.e. the worklist is
empty, this screen should be blank.
Clicking the Edit button should make the screens in the
Detail section editable. The Edit button should be
Update the Notification Click Edit
hidden if the Notification has a System Status of
“NOCO” – Notification Completed
Clicking the button will save any changes made to the
Notification back to the backend system. A message
Save the Notification Click Save will be displayed to the user confirming that the save
has been successful. Any record locks will then be
deleted.
Clicking the button will create a Work Order in the
backend system as detailed in section 2.2.9 . A
Create an Order Click Create Order confirmation message will be displayed to the user
which will include the system generated Work Order
number (QMEL-AUFNR).
Clicking the tab will display the attachments linked to
Display Attachments Click Attachment
the Notification as described in section 2.2.6
Clicking the tab will display the Work Order linked to
Display Work Order data Click Work Order

M-026 20/10/2017
2.2.6 Detail Screen – Attachments Tab
This tab is only displayed if there are any attachments found on the Notification. This screen will display
the details of the attachments linked to the selected Notification. The Detail Screen will be read-only.

The Attachment screen contains the following fields:
Details

Attachments Linked document through BDS
Event Action Matrix

Clicking the tab will display the Notification as
Display Notification data Click Notification
described in section 2.2.6
Clicking the tab will display the Work Order linked to
Display Work Order data Click Work Order the Notification as described in section 2.2.7
Clicking the button will allow a document to be

Add an attachment Click “+” attached and create a new Document link through BDS
2.2.7 Detail Screen – Work Order Tab
This tab is only displayed if there is a Work Order linked to the Notification. This screen will display the
details of the linked Work Order for the selected Notification. The Detail Screen will be read-only.

20/10/2017 M-026

The Work Order screen contains the following fields:
Details

Work Order AUFK-AUFNR CHAR 12
Description AUFK-KTEXT CHAR 40
Order Type AUFK-AUART CHAR 4 Display description
Order System TJ02T-TXT30 CHAR 30 The description of the numbered system

Status status currently active on the Notification.
Order User TJ30T-TXT30 CHAR 20 The description of the numbered user

Status status currently active on the Notification.
Main Work AUFK-VAPLZ CHAR 8

Centre
Basic Start AFKO-GSTRP DATS 8
Date
Basic Finish AFKO-GLTRP DATS 8
Date
Operation Details (could be multiple per Work Order)

Operation AFVC-VORNR CHAR 4
Number
Work Centre AFVC-ARBID CHAR 8 Description from CRHD table
Control Key AFVC-STEUS CHAR 4
Description AFVC-LTXA1 CHAR
Work Time AFVV-ARBEI & QUAN + 7+3 Work Time + Unit

AFVV-ARBEH UNIT
Number of Men AFVC-ANZLL INT1 3
Duration of AFVV-DAUNO & QUAN + 5+3 Duration + Unit

Work AFVV-DAUNE UNIT
System Status TJ02T-TXT30 CHAR 30 The description of the numbered system


M-026 20/10/2017

User Status TJ30T-TXT30 CHAR 30 The description of the numbered user
Event Action Matrix

Clicking the tab will display the Notification as
Display Notification Click Attachment
described in section 2.2.5
Clicking the tab will display the attachments linked to
Display Attachments Click Attachment
Clicking the button will open a new window displaying
Edit the Work Order Click Edit
the Work Order (AUFK-AUFNR) in transaction IW32
2.2.8 Create Case

The following fields will be used to create the Case during the Notification creation

Case Type SCMG_T_CASE_ATTR- CHAR 4
CASE_TYPE
Case SCMG_T_CASE_ATTR- CHAR 80
Description CASE_TITLE
Notification SCMG_T_CASE_ATTR- Specified Specified Specific custom Z Field will be defined in

Number ZZ_****** (Specified in E-219 in E-219 the FDD for E-219
in E-219)
Functional SCMG_T_CASE_ATTR- Specified Specified Specific custom Z Field will be defined in

Location ZZ_****** (Specified in E-219 in E-219 the FDD for E-219
in E-219)
Equipment SCMG_T_CASE_ATTR- Specified Specified Specific custom Z Field will be defined in

ZZ_****** (Specified in E-219 in E-219 the FDD for E-219
in E-219)
2.2.9 Create Order

Using the standard process to create a Work Order from a Notification, use the Notification fields to
populate the Work Order with the addition of the following fields:

20/10/2017 M-026

Order Type AUFK-AUART CHAR 4 Use the following logic:
Notification Type BH = Order Type NBH1
Notification Type BS = Order Type NBS1
Notification Type BW = Order Type NBW1
Notification Type BC = Order Type NBC1
Notification Type BE = Order Type NBH1
Maintenance AFIH-ILART CHAR 3 Use the Type of Object and Type of
Activity Type Damage codes in ZPM_DEFECT table to
determine ZPM_DEFECT-MAT
(enhancement E-245)
Work Centre AUFK-VAPLZ CHAR 8 Use the Type of Object and Type of
Damage codes in ZPM_DEFECT table to
determine ZPM_DEFECT-WORKCENTRE if
not on screen (enhancement E-245)
Basic Start AFKO-GSTRP DATS 8 If QMEL-ZZ_DATEREQD not blank, use
Date QMEL-ZZ_DATEREQD
Else, use QMEL-STRMN
Basic Start AFKO-GLTRP DATS 8 If QMEL-ZZ_TIMEREQD not blank, use
Time QMEL-ZZ_TIMEREQD
Else, use QMEL-STRUR
2.3 PERFORMANCE CONSIDERATIONS

No performance considerations have been identified.
2.4 AUTHORISATION PARAMETERS

None identified
2.5 SECURITY REQUIRMENTS

Users with the ECC composite roles for the Service Centre should be granted access to this application,
by the creation of equivalent Gateway roles.
2.6 EXISTING SAMPLE PROGRAM

SAP Program N/A
Name
SAP N/A
Menu/Transaction

M-026 20/10/2017
3 Extension Details
3.1 EXTENSION ATTRIBUTES
Attribute Value
Extension Type N/A
User-Exit Type N/A
Enhancement Framework Type N/A
/ Others
3.2 Exit Name
Description Value
Is there any EXIT N/A
available?
Describe the N/A
alternative found
Exit name N/A
Description N/A
3.3 BAdI
N/A
3.4 Function Group Enhancement

N/A
3.5 Class / Interface Enhancement

N/A
3.6 Source Code Plug Ins

N/A
3.7 Web Dynpro Enhancement

N/A
3.8 Associated Portal Development

N/A

20/10/2017 M-026
3.9 New Custom Table Requirement

3.9.1 Allowed Values Tables
The following tables will be used to filter the results of searches on standard fields down to the list of
values relevant to the Service Center requirements. For example, the Notification Type field is stored in
the standard Notification Type field, however, it is also used to hold EBS Phase 1 Notification Types
which are not relevant for the Service Center and so need to be filtered out.
A new bespoke transaction will be created for each table to allow table maintenance using SM30 without
the front screen table selection screen.
The contents of these tables should be client specific and therefore should be maintainable directly in
the production system.
Allowed Values: Table: Transaction:

Notification Type ZPM_NOTIFTYPES ZPMNOTIFTYPES
Field Name Data Data Length Check Key Field Remarks
Element Type Table
Notification QMART CHAR 2 TQ80 X
Type
Language SPRAS CHAR 1 T002C X
Description QMARTX CHAR 40 - Read-only. Text

description of Boat
retrieved from
TQ80_T-QMARTX.

Sub Category ZPM_SUBCAT ZPMSUBCAT
Field Name Data Data Length Check Key Remarks
Element Type Table Field
Sub Category TEXT20 CHAR 40 X
Description TEXT40 CHAR 40 The description of

each Sub Category

Ship Name ZPM_SHIPNAME ZPMSHIPNAME
Ship Name TPLNR CHAR 30 IFLOT X

M-026 20/10/2017

Ship Name ZPM_SHIPNAME ZPMSHIPNAME
Description PLTXT CHAR 40 - Read-only. Text description

of Boat retrieved from
IFLOTX- PLTXT.
3.9.2 Custom Case Table
Table 1: Case Types for Service Management Table (ZPM_NOTIFCASE)

The following table should be created within SAP. The information will be available for update using a
new transaction which will allow display and change functionality. The information in the table will be
used to manage the relationship between Notification Types and Case Types.
A new bespoke transaction (ZPMNOTIFCASE) will be created to allow table maintenance for
ZPM_NOTIFCASE using SM30 without the front screen table selection screen.
The contents of these tables should be client specific and therefore should be maintainable directly in
the production system.
Field Name Data Element Data Length Check Table Key Remarks
Type Field
Notification QMART CHAR 2 TQ80 X
Type
Case Type SCMGCASE_TYPE CHAR 4 SCMGCASETYPE X

20/10/2017 M-026
4 ADDITIONAL INFORMATION
4.1 Unit Test Plan

Description:
The Functional Team member will utilize this section to document unique test requirements.
This is an input to the development team in order to carry out the unit testing. The
Functional Team member will identify any unique scenarios and business transactions for
the object to be tested and identify the test data requirements. Although not part of the
Functional Specification, the Functional Team member is also responsible for creation and
maintenance of the unit test data required to support the unit test cases. Note: Document
any functional dependencies the tester needs to take into consideration (refer to section 1.6
and 1.8 – Dependencies & Other Objects Affected). Because the enhanced functionality
varies from scenario to scenario, outline the steps that should be tested during Unit Testing.
TA.DEV.011_Enhanc
ement Unit Test Template v1.1.xlsx
4.2 Information Security

Description:
Security will review the information contained within this specification and lead security
requirements implementation with the Functional Teams and technology.
Access to form, report, enhancement, portal, workflow object is dictated by the security role
authorizations assigned to the user. The authorizations would be based on the role defined
for executing the task/activity.
4.2.1 Information Classification

Description: This section has been pre-filled with certain defaults for the One AG project;
please review and collaborate with security team to update this section.:
General Information
Businesses Impacted:

M-026 20/10/2017
D
Information Classified by
a
whom:
t
e
Contact Information
Company Name Phone E-mail Address
List Potential
Information
Owners:
Architecture
Development Test Training

Environments: (impacted by this Func.
Production
Spec.):
Public (Internet) Facing Internal Only
3rd Party Hosted Company *

Architecture: (system exposure): Hosted
Identity & Access Management
During Project Yes Offshore? Yes List the 3rd Capgemini team
Parties:
3rd party system access No No
required?
Post Implementation Yes Offshore? Yes List the 3rd Capgemini team
Parties:
3rd party system access No No
required?
Business Impact Analysis
What may be impacted if the system or information/data is compromised? Check all that may apply.

20/10/2017 M-026
Company Reputation/Trust Regulatory
Associate Relations Compliance
Competitive Advantage Securities & Exchange Commission

(SEC)
Financial Impact
Payment Card Industry (PCI)
Productivity
Sarbanes-Oxley (SOX)
Supply Chain
Privacy Laws
Contractual (i.e. NDA’s, MSA’s)*
Input any additional details related to business impact in the event of compromise:
*NDA – Non-Disclosure Agreement, MSA-Master Service Agreement

M-026 20/10/2017
Information Classification
Action #1: Check the box below that represents the most restrictive classification.
Action #2: If Level 1 or 2 is selected, check the box below indicating data storage or data
transmission.
Information has been defaulted to level 3. Please review and update in collaboration with
the security team
Level 1 – Confidential – Secure Handling Required “SHR”

Confidential – Secure Handling Required represents the most sensitive data classification related to
individual personal identifiable information and personal financial account information. This information
considered critical to AG such that, if disclosed, may disrupt or impede business operations, and due to legal,
reputational, or operational concerns, requires additional security controls. Information in this category
includes, but is not limited to:
1. Social Security Number
2. Driver’s License Number or Government-issued Identification Number
3. Financial Account Number (card number or personal bank number)
4. Protected Health Information & Electronic Protected Health Information
SHR data stored? SHR data transmitted? SHR data stored and transmitted?
Level 2 – Confidential
Confidential represents the second most sensitive data classification related to operationally significant
business information. This information considered critical to AG such that, if disclosed, may disrupt or impede
business operations. Examples of Restricted Confidential include but are not limited to regulatory governed
data, trade secrets, mergers and acquisition discussions, product formulas and designs, corporate earnings
data prior to public announcements, reorganization details prior to announcements, current/closed company
investigations and litigation, detailed network diagrams that could jeopardize network security, strategic
development/marketing plans and information integral to the success and operations of the company.
This includes: Pre-release aggregated financial data relevant to U.S. Securities and Exchange Commission
oversight; AG’s own commercial bank account numbers (i.e. where AG makes deposits, pays checks and
executes ACH transfers for their own account)
Confidential data stored? Confidential data transmitted? Confidential data stored and
transmitted?
Level 3 – Internal AG Use Only
Internal AG Use Only represents the third most data. It represents information that is less critical to privacy
and business operations but still must not be publicly disclosed. This information is not approved for general
circulation outside AG.
This includes most transactional financial information.
Level 4 - Public
Public represents information that has been declared public knowledge by the information owner and can
freely be given to anyone without any possible impact to AG. As a result, no special data handling protections
are require

20/10/2017 M-026
4.2.2 Security Roles (Profiles and Authorizations)

This section should define the general security administration for this design. Security roles,
profiles and authorizations will be finalized after Blueprint. Define the general security for
this design including any organizational level restrictions required. List a Standard
TCode/Report/Object that most resembles the custom development. Outline general
authorization checks for special reports and/or enhancements due to data classifications and
any other special security considerations.
Please assign role for performing the activity/task using the form, report, enhancement,
portal and interface object. This could be the business user role (or depending on when this
document is written the actual SAP role). Please collaborate with the security team to fill
the document.
Security Requirements for Enhancements
Security Type Role Access Allowed

Screen Level < Role 1> <read, read/update>
Security
< Role 2>
Field Level < Role 1> <List restrictions on the fields on the form that
Security individuals with this role can either see. The
< Role 2>
fields like SSN number, Credit Card number, etc
that has sensitive information need to be listed
with the kind of access for query, display and
print.>
Button Security < Role 1> <Any restrictions on the buttons that someone
with this role can either see and/or invoke>
< Role 2>
Data Security < Role 1> <Any restrictions on the data that someone
with this role can either see and/or update>
< Role 2>
4.3 Audit
This section should define any audit solution for this design.
Transactional data and changes to master data within the SAP application are captured by
standard SAP in the CDHDR table. If there are additional requirements to capture audit history
on new custom tables defined for fulfilling the functional requirements in this Func. Spec., please
specify the same. The name of the custom tables and the detailed design would be described in
the Realization Phase of the project in the technical specs.

M-026 20/10/2017
Audit Trail Requirements
Audit Event Description Audit Trail Updates

<Event which <Description> <Audit message / fields audited>
causes the need
for an audit trail;
e.g., data is
changed>
4.4 Error Handling

20/10/2017 M-026
5 Exception Handling Rules

The following exceptions will be caught and will result in an error message being displayed; the user will
not be able to continue until the exception has been cleared.
No. Exception Message
1 Not all mandatory fields have "All mandatory fields must be complete
been populated when the user before saving."
clicks Save.
2 When the user clicks the 'Edit' "Notification currently locked by user
button, the Notification is &USER."
already locked by another user.
3 When the user clicks the 'Save', "Save unsuccessful, please try again."
the backend system reports that
the save was not successful.
Passed message through to the
UI5 screen to facilitate
investigation.
4 If the Object Type and Damage “The Defect table is not maintained for
Codes do not match a record in the Object Part / Damage selection”
the ZPM_DEFECT table, the
Notification is not created and
an appropriate error message is
displayed. The details should
be left on the screen until the
data record can be created.
5 When the user clicks the 'Save', "Order Create unsuccessful, process
the backend system reports that manually."
the Order creation was not
successful but Notification was
saved.
investigation.
5 When the user clicks the 'Save', "Case Create unsuccessful, process
the backend system reports that manually."
the Case creation was not
successful.
investigation.


BAES - FS - M-026 - App To Create Maintenance or Service Helpdesk Request

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BAES - FS - M-026 - App To Create Maintenance or Service Helpdesk Request

Uploaded by

Copyright:

Available Formats

NOT PROTECTIVELY MARKED

BAE SYSTEMS PROPRIETARY

App to create maintenance or service helpdesk

Public Access: Freedom of Information Act 2000, etc.

BAE Systems Maritime Services,

BAE SYSTEMS PROPRIETARY

THIS DOCUMENT IS THE PROPERTY OF

BAE Systems Surface Ships Limited

WITH PARTICULARS OF HOW AND WHERE FOUND.

THE UNAUTHORIZED RETENTION OR DESTRUCTION OF THE DOCUMENT MAY BE AN OFFENCE UNDER

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

Signature Frank McAleer

Title Business Process Owner, BAE Systems.

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

5 Exception Handling Rules 67

No table of figures entries found.

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

No Reference Title Version / Date

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

Title M-026 Service Centre App

Team Which Owns the Service Management

System Version S/4 HANA 1610 FPS02

Development Type UI5 Frontend

Estimated Complexity Very Complex

Release Phase 2 Work Package 2

Related Business 6.1.1 Work Request

Approver(s) & Date & Del Miller

1.2 Business Driver

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

1.3 Desired Functionality Overview

Number Description of Requirement

3. Create a Work Order

4. Create a Work Order

Only authorised users will be granted access to the application.

1.5 Project / Development Constraints

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

1.6 Performance Criteria

Performance Requirements for Conversions

1.7 Other Objects Affected

#E-217 – Additional fields on Functional Location and Equipment

#E-207 – Alert for Environmental Assets

#E-245 – Defect Code Search Enhancement

1.8 Application / Tile Name

1.8.1 Tile Details

Requirement Details (if applicable)

SAP Fiori Launch pad Tile Service Center

App Name Service Centre App

Group Service Center Operative

Tile Type Static App Launcher

Create/Edit/View Create / Edit / View

Wireframe link http://56ag6c.axshare.com

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

1.8.2 Field Mapping

1.8.3 Flow Diagram of Design (if applicable)

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

Has an Alert Is this New

Yes Yes Yes

Notification and Notification and

Unpublished Work Copyright 2017 BAE Systems. All Rights Reserved.

The following search helps/dropdowns are required for this application:

2.1.1.1 Dropdown Lists