FUNCTIONAL DESIGN - ENHANCEMENTS

SAP/Shared Services Project

FD.PTF.E.154. PM Equipment / Functional Location / Task list (PRT)
DMS Functionality (GAP#30)

Version: 01

Status: Draft

Date: 02nd March 2020

Document Information

© Client Name Status: Draft version 0.1 Page 1 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

General Information

Project Name SAP/Shared Services Project

Document Location
Associated
Documentation

Document History

Date Name Dept. Change Status

20 Feb 2020 Kunal Kate PTF Initial Draft Draft

08-Mar 2020 David Lloyd PTF Initial review draft

Approval (Signature for Name / Signature Date

acceptance)

Business Owner David Lloyd

IDC point of contact Kunal Kate

SUN point of contact

Functional Design – Enhancement Definition

Business Process Team PTF
Business / Process David Lloyd
Owner
Functional Designer
Complexity
Planned Start Date
(Planned date for start of Technical
Design)

Planned End Date

(Planned date of handover from
IDC after unit test)

Contents

1.0 Overview...................................................................................................................................... 4

1.1 Overview & Scope.................................................................................................................... 4

© Client Name Status: Draft version 0.1 Page 2 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

1.2 Assumptions............................................................................................................................. 4
1.3 SAP Modules / Transactions.................................................................................................... 4
1.4 Constraints............................................................................................................................... 4
1.5 Dependencies.......................................................................................................................... 4
1.6 Responsible Organisations...................................................................................................... 5
2.0 Detailed Functional Requirements............................................................................................... 6

2.1 Functional Design..................................................................................................................... 6

2.2 Process Flow Diagram............................................................................................................. 6
2.3 Existing Sample Program......................................................................................................... 7
2.4 Networks Integration................................................................................................................ 7
2.5 Performance Considerations.................................................................................................... 7
2.6 Reporting.................................................................................................................................. 7
2.7 Enhancement Layout............................................................................................................... 8
3.0 Dialogue Program…………………………………………………………………………………………

4.0 Exit/
Enhancement…………………………………………………………………………………………

5.0

BAdI………………………………………………………………………………………………………….

6.0 Additional
Requirements…………………………………………………………………………………..

6.1 Processing Requirements........................................................................................................ 7

6.2 Multi-site Details....................................................................................................................... 7
6.3 Messages/ Error handling........................................................................................................ 7
6.4 Reporting.................................................................................................................................. 7
6.5 Performance Consideration...................................................................................................... 7
6.6 Existing Sample Programs....................................................................................................... 7
6.7 Authorization Checks............................................................................................................... 8
6.8 Others............................................................................................................................... ……8

7.0 Testing Requirements.................................................................................................................. 9

7.1 Key Business Test Conditions................................................................................................. 9

8.0 Outstanding Issues.................................................................................................................... 10

© Client Name Status: Draft version 0.1 Page 3 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

1.0 Overview

1.1 Overview & Scope

[Please provide a high-level description of the enhancement and the business requirement that will be
addressed.}

• BCE is having large volume of documents and need to upload to the specific
Equipment, Functional Location and Task List (General Task List, Functional
Location.)
• Need to Upload documents to the Equipment of Plant Maintenance in mass.
• Need to Upload documents to the Functional Locations of Plant Maintenance in
mass.
• Need to Upload documents to the Task List (PRT Overview of Operation) of Plant
Maintenance in mass.

1.2 Assumptions
[Please describe any assumptions that have been made in the process of completing this design}

 Equipment is already created with status CRTD or INST, restrict to load the documents for
status INAC or DLFL.
 Functional Location is already created with status CRTD or INST, restrict to load the
documents for status INAC or DLFL.
 Task List is already created for General maintenance task list (A), Task List for Functional
Location (T) and Equipment task list (E).
 Documents should be available to the User Local PC and can be uploaded based on the
Functional location, equipment and task list existing authorizations. It should allow different
type of documents like IMG, XLSX, DOCX, PDF etc.
 Document should be uploaded to the SAP Directory.
 .csv File must be created to create the CV01N document and object assignment.

1.3 SAP Modules / Transactions

[Please provide the SAP modules that will be involved in the enhancement.}

SAP Plant Maintenance

Transaction code – ZPTF_PM_DOC_LOAD

Transaction code Description – PM Document Load

IE01/02 – Create/Change Equipment

IL01/02 – Create/Change Functional Location

IA05/06 – Create/Change Task List.

IA11/12 – Create / Change Functional Loc Task List

IA01/02 Create Equipment task list

CV01N – Create Document

© Client Name Status: Draft version 0.1 Page 4 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

1.4 Constraints
[Please indicate any constraints that may impact development, such as limited access to legacy system, time
constraints or data restrictions etc]

All file size should not be more than 10MB and users can load multiple file at a time.

1.5 Dependencies
[Please indicate any dependencies that may impact development, in terms of requirements from internal or
external applications or teams]

 Document Validation (Excel Data) for Equipment, Functional Location, Task List.
 Documents should be available on local server.
 Excel Template
 File extensions should be acceptable to the SAP.

1.6 Responsible Organisations

Name Contact Details

Business Process Owner

SAP Process Owner

Source System Owner

Sign Off (Business & IT)

© Client Name Status: Draft version 0.1 Page 5 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

2.0 Detailed Functional Requirements

2.1 Functional Design

[Please provide a detailed description of the enhancement, outlining the business process involved and what
functionality the enhancement will and will not change.}

Create new Transaction and Program to Upload documents in Mass .

Transaction code – ZPTF_PM_DOC_LOAD

Transaction code Description – PM Document Load

Transaction must have Three Radio Buttons for Equipment, Functional Location and Task List.

Table should get updated after successful document upload.

Table name - ZPTF_PM_DOCHISTORY

Program should work for Foreground and Background.

Program Logic:

1. When Equipment radio button is selected -

a. Upload files (All file size should not be more than 10MB and users can load multiple file
at a time) from User Local data through the transaction from option “Select Files to be
uploaded”
b. User should be able to upload multiple files to the SAP Server.
c. File must have Equipment details along with the document description which needs to
be assigned to the Equipment and should be available in DMS Directories (AL11).
d. File should be uploaded through option “Select upload Template (CSV File)
e. Verify Equipment number and Equipment Description maintained in the template file
with the EQUI- EQUNR and EQUI- EQKTU respectively.
f. After successful execution, File should get uploaded into the DMS Documents Tab
(New tab on the Equipment master) of Equipment Master.
g. If the Equipment number not available, file should not get uploaded.
h. Table DRAW and DRAT should get updated.
i. Document type should be PMD for DMS upload.
j. Multiple Equipment Data can also be updated through the program.
k. Update the History table once document created and loaded on equipment master -
ZPTF_PM_DOCHISTORY

2. When Functional Location radio button is selected –

a. Upload files (Size should not be more than 10MB, and users can load multiple file at a
time) from user Local data through the transaction from option “Select Files to be
uploaded”
b. User should be able to upload multiple files to the SAP Server.
c. File must have Functional Location details along with the file details which needs to
assign to the Functional Location and should be available in DMS Directories (AL11).
d. File should be uploaded through option “Select upload Template (CSV File)
e. Verify Functional Location number and Functional Location Description maintained in
the file with IFLOT- TPLNR and IFLOT- PLTXT respectively.
f. After successful execution, File should get uploaded to the DMS Documents Tab of
the Functional Location.

© Client Name Status: Draft version 0.1 Page 6 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

g. If Functional Location number not available, file should not get uploaded.
h. Table DRAW and DRAT should get updated.
i. Document type should be PMD for DMS upload.
j. Multiple Functional Location can also be updated through the program.
k. Update the History table once document created and loaded on equipment master -
ZPTF_PM_DOCHISTORY

3. When Task List radio button is selected –

a. Upload files (Size should not be more than 10MB, and users can load multiple file at a
time) from user Local data through the transaction from option “Select Files to be
uploaded”
b. User should be able to upload multiple files to the SAP Server.
c. File must have Task List details along with the file details which needs to assign to the
Task List Operation as Document PRT and should be available in DMS Directories
(AL11).
d. File should be uploaded through option “Select upload Template (CSV File)
e. Verify Task List (Type- A, E and T) must be created before.
Pass Task List Type (PLKO- PLNTY) and verify Task List Group, Task List Group
Counter and Task List Description with PLKO- PLNNR, PLKO- PLNAL and PLKO-
KTEXT respectively.
f. After successful execution, File should get uploaded to the Task list Operation PRT
tab.
g. If Task List Group number is not available, file should not get uploaded.
h. Document Type should be DRW (Engin/Des. Drawing) Existing Document type for
DMS upload.
i. Multiple Task List can also be updated through the program.
j. Update the History table once document created and loaded on equipment master -
ZPTF_PM_DOCHISTORY

 Test functionality should work for Equipment, Functional Location and Task List.

 New document number should get generated when uploaded first time for every language.

 If document is already available for provided Objects (Equipment, Functional Locations, Task
List), then new version should be created and uploaded to the Objects (Equipment, Functional
Locations, Task List).

 Document Description should get updated as mentioned in the template file second column
followed by _ and Language.

 If Document Description column is maintained Blank in the template file should be updated as File
name followed by _ and Language in the CV02N.

 Directory Path-

We will create folders for Equipment, Functional Location and Task List in the below mentioned Path
on the application server, to load the files from user’s local PC to application server to create the
document and attach to the object.

© Client Name Status: Draft version 0.1 Page 7 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

Once Docuemnts created (CV01N) and assigned to respective objects, the files of application server
(AL11) should get deleted and move to Archive folders.

Archive Path-

Refer the Repository D9 created with Document type ‘ZDMS_PM’.

All document classes are assigned to the new document type.

Plant Authorization Validation-

While uploading the document to the objects, we need to add validation based on the Plant
authorization.

2.2 Process Flow Diagram

[Please insert a flow diagram describing the enhancement procedure including screen sequences]

Same as above for Functional Location and Task List.

2.3 Existing Sample Program

[If an existing program is available to be enhanced, provide details in this section]

NA

2.4 Networks Integration

[Please provide details of any networks integration considerations}

© Client Name Status: Draft version 0.1 Page 8 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

NA

2.5 Performance Considerations

[Please highlight any performance considerations that should be considered during the design, such as
restrictions to expected execution time]

NA

2.6 Reporting
[Please describe any reporting that is expected to be provided in support of this enhancement or any impact to
existing or custom reports that need to be amended due the enhancement}

Document number range as per the standard Document number ranges.

1. Log when upload documents from Local data to SAP Server:

2. Log should generate for Validation:

3. Log after program execution:

Log should generate for Equipment, Functional and Task List after successful upload of documents.

4. Table:

Selection Screen:

© Client Name Status: Draft version 0.1 Page 9 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

Output Screen:

2.7 Enhancement Layout

[Please describe any screen layouts or changes to existing screens that will form part of this enhancement.
Where available include a screen shot or diagram detailing exact report/enhancement layout required.]

Selection Screen:

© Client Name Status: Draft version 0.1 Page 10 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

Template Files for Objects:

Equipment Temp.csv FUNCTIONAL TASK LIST TEMP.csv

LOCATION TEMP.csv

© Client Name Status: Draft version 0.1 Page 11 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

3.0 Testing Requirements

3.1 Key Business Test Conditions

[Please indicate the business level test conditions that should be used to verify successful operations of the
enhancement]

ID Condition Expected results

001 Create Equipment IE01, IE02 – Equipment created.

002 Create Functional Location IL01, IL02 - Functional Location created.

003 Create Task List (Type-A) IA05, IA06 – Create / Change General Task
List
IA11/12 – Create / Change Functional Loc
Task List

IA01/02 - Create Equipment task list

004 Document should be created and available Document should be available on AL11
Directory.

005 Test scenarios: Run program If data is accurate, output should be

document created for Equipment, FL and
Upload file Task List respectively (Functional Location,
Equipment and General task list) and update
in the history table.

If data is not accurate, output should be No

data found and populate in red flag.

© Client Name Status: Draft version 0.1 Page 12 of 13

 FUNCTIONAL DESIGN - ENHANCEMENTS

4.0 Outstanding Issues

(Please list any outstanding issues which may impact ongoing development)

Issue Description Assigned To Status Impact Resolution

No

© Client Name Status: Draft version 0.1 Page 13 of 13