Equipment Functional Location Task List Review
October 14, 2022 | Author: Anonymous | Category: N/A
Short Description
Download Equipment Functional Location Task List Review...
Description
FUNCTIONAL DESIGN - ENHANCEMENTS
SAP/Shared Services Project FD.PTF.E.154 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
SAP/Shared Services Project
Project Name 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 acceptance)
Name / Signature
Business Owner
David Lloyd
IDC point of contact
Kunal Kate
Date
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 test))
Contents 1.0 1.1
Overview Overview...... ............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ................ ......... 4 Overview Overview & Scop Scope..... e............ .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ............. ............. .............. .............. ..............4 .......4
© Client Name
Status: Draft version 0.1
Page 2 of 13
FUNCTIONAL DESIGN - ENHANCEMENTS
1.2
Assumption Assumptions..... s............ .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ............. ............. ................4 .........4
1.3
SAP Mod Module ules s / Transact Transaction ions...... s............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ................. ..........4 4
1.4
Constrai Constraints... nts.......... .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ............. ............. ..................... .................... ...... 4
1.5
Depende Dependencie ncies..... s............ .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .................................4 ..........................4
1.6
Respons Responsible ible Organis Organisatio ations.... ns........... .............. .............. .............. .............. .............. .............. .............. .............. ............. ...................................5 .............................5
2.0
Detailed Detailed Function Functional al R Requ equirem irements. ents........ .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ...................... ................. .. 6
2.1
Function Functional al D Desig esign... n.......... .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ......... .. 6
2.2
Process Process Flow Diagram Diagram....... .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .........................6 ..................6
2.3
Existing Existing Sample Sample Pro Program gram...... ............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ...............7 ........7
2.4
Networks Networks Inte Integrat gration ion....... .............. .............. .............. .............. .............. ............. ............. .............. .............. .............. .............. .............. ............................. ......................7 7
2.5
Performa Performance nce Con Conside siderati rations.. ons......... .............. .............. .............. ............. ............. .............. .............. .............. .............. .............. .............. ......................7 ...............7
2.6
Reportin Reporting... g.......... .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ............... ........7 7
2.7
Enhancem Enhancement ent Layout... Layout.......... .............. .............. ............. ............. .............. .............. .............. .............. .............. .............. .............. ................................8 .........................8
3.0
Dialog Dialogue ue Program Program……… ……………… ………………… …………………… …………………… …………………… …………………… …………………… …………………… …………
4.0 Exit/ Enhancement………………………………………………………………………………………… 5.0 BAdI…………………………………………………………………………………………………………. 6.0 Additional Requirements………………………………………………………………………………….. 6.1
Processi Processing ng Requirem Requirements. ents........ .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ............... .......................... ..................7 7
6.2
Multi-sit Multi-site e Details... Details.......... .............. .............. .............. .............. .............. ............. ............. .............. .............. .............. .............. .............. .............. .............. ................... ............7 7
6.3
Messages Messages// Error Error handlin handling.... g........... .............. .............. .............. .............. ............. ............. .............. .............. .............. .................... ............................... ..................7 7
6.4
Reportin Reporting... g.......... .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ............... ........7 7
6.5
Performa Performance nce Consi Consider deratio ation.... n........... .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ..............7 .......7
6.6
Existing Existing Sample Sample Pro Program grams...... s............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ....................7 .............7
6.7 6.8
Authoriz Authorizatio ation n Checks..... Checks............ .............. .............. .............. .............. .............. .............. .............. .............. ............. ............. .............. .............................. .......................8 8 Others...... Others............. .............. .............. .............. .............. .............. .............. .............. .............. ............. ............. .............. .............. .............. .............. ........................ ................. ……8
7.0 7.1 8.0
Testing Testing R Requi equirem rements. ents........ .............. ............. ............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ................9 .........9 Key Busi Business ness Test Conditi Conditions. ons........ .............. .............. .............. .............. .............. .............. ............. ............. ............................ .................................. .............9 9 Outstand Outstanding ing Issue Issues..... s............ .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. .............. ............... .................... ............ 10
© Client Name
Status: Draft version 0.1
Page 3 of 13
FUNCTIONAL DESIGN - ENHANCEMENTS
1.0 Over Overview view 1.1 1.1 Ove verrview view & S Sco cope pe [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 Equipment documents for status INAC or DLFL. Functional Location Location is already created with status CRTD or INST, restrict to load the documents for status INAC or DLFL. documents 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. 1.3 3 SA SAP P Mo Modu dule les s/T Tra rans nsac acti tion ons s [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 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. 1.6 6 Re Resp spon onsi sibl ble e Org Organ anis isat atio ions ns
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 Functi Functional onal Requirements Requirements 2.1 2.1 Fu Func ncti tion onal al De Desi sign gn [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 When Equipm Equipment ent radio radio butt button on is selected selected a. Upload Upload fi files les (A (Allll file file size should should n not ot be m more ore th than an 10MB 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 shou should ld be able able tto o upl upload oad m multip ultiple le files files to the S SAP AP Server. Server. c. File must hav have e Eq Equipm uipment ent detai details ls al along ong with the document description which needs to be assigned to the Equipment and should be available in DMS Directories (AL11). d. File should should be u uploade ploaded d thr through ough option “Select upload Template (CSV File) e. Verify Equipment Equipment number and Equipm Equipment ent Descri Description ption maintaine maintained d in the template template file file with the EQUI- EQUNR and EQUI- EQKTU respectively. f. After su success ccessful ful executio execution, n, File s shou hould ld get get uplo uploade aded d into the the DMS DMS Documents Documents Tab Tab (New tab on the Equipment master) of Equipment Master. g. If the Equipme Equipment nt num number ber no nott availabl available, e, file sh shoul ould d not get uploa uploaded ded.. h. Table Table DRAW DRAW a and nd DRAT DRAT sho shoul uld d ge gett upd update ated. d. i. Docum Document ent type type sh shou ould ld be PMD PMD for for DM DMS S up uplo load ad.. j. Multiple Eq Equipmen uipmentt Data can also be u updated pdated th through rough the program program.. k. Update the Histo History ry table once d document ocument created and loaded on equipme equipment nt master ZPTF_PM_DOCHISTORY
2.
When When Function Functional al Loc Locatio ation n radio radio butt button on is selected selected – a. Upload Upload fi files les ((Size Size s shou hould ld not not be mor more e than than 10MB, 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 shou should ld be able able tto o upl upload oad m multip ultiple le files files to the S SAP AP Server. Server. c. File must must have Functiona Functionall Location Location de details tails alo along ng with the file details which needs to assign to the Functional Location and should be available in DMS Directories (AL11). d. File should should be u uploade ploaded d thr through ough option “Select upload Template (CSV File) e. Verify Functional Functional Location number and F Functional unctional Location Description maintained maintained in the file with IFLOT- TPLNR and IFLOT- PLTXT respectively. f.
© Client Name
After su success ccessful ful executio execution, n, File s shou hould ld get get uplo uploade aded d to the DMS DMS Documen Documents ts Tab of the Functional Location. Status: Draft version 0.1
Page 6 of 13
FUNCTIONAL DESIGN - ENHANCEMENTS
g. h. i. j. k.
3.
If Functional Functional Location Location n number umber not av available ailable,, file should not get uploaded. uploaded. Table Table DRAW DRAW a and nd DRAT DRAT sho shoul uld d ge gett upd update ated. d. Docum Document ent type type sh shou ould ld be PMD PMD for for DM DMS S up uplo load ad.. Multiple Fu Functional nctional Lo Location cation can al also so be upda updated ted through the program. program. Update the Histo History ry table once d document ocument created and loaded on equipme equipment nt master ZPTF_PM_DOCHISTORY
When When T Task ask List List rad radio io butto button n is is s sele electe cted d– a. Upload Upload fi files les ((Size Size s shou hould ld not not be mor more e than than 10MB, 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 shou should ld be able able tto o upl upload oad m multip ultiple le files files to the S SAP AP Server. Server. c. File must must have Task List details along with the file details details which which needs needs to assign to the Task List Operation as Document PRT and should be available in DMS Directories (AL11). d. File should should be u uploade ploaded d thr through ough option “Select upload Template (CSV File) e. Verify Verify Task List List (Ty (Typepe- A, A, E and T) must must be create created d before. 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 PLKOKTEXT respectively. f. After su success ccessful ful executio execution, n, File s shou hould ld get get uplo uploade aded d to the Task Task list Opera Operation tion PRT PRT tab. g. If Task List Group Group numbe numberr is not ava availab ilable, le, file shou should ld not get get uploade uploaded. d. h. Document Docu Typ Type e shoul should d be DRW (Eng (Engin/D in/Des. es. Drawing Drawing)) Existing Existing Document Document type for DMS ment upload. i. Mult Multiple iple Task List can also be updated updated thro through ugh the program program.. j. Update the H History istory table once d document ocument created created and loaded loaded on on equipment 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, Location s, 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 PathRefer the Repository D9 created with Document type ‘ZDMS_PM’. All document document classes are assigned assigned to the new document document type. Plant Authorization ValidationWhile uploading the document to the objects, we need to add validation based on the Plant authorization.
2.2 2.2 Pr Proc oces ess s Fl Flow ow D Dia iagr gram am [Please insert a flow diagram describing the enhancement procedure including screen sequences]
Same as above for Functional Location and Task List.
2. 2.3 3 Ex Exis isti ting ng Sa Samp mple le Pr Prog ogra ram m [If an existing program is available to be enhanced, provide details in this section]
NA
2. 2.4 4 Ne Netw twor orks ks Inte Integr grat atio ion n [Please provide details of any networks integration considerations} © Client Name
Status: Draft version 0.1
Page 8 of 13
FUNCTIONAL DESIGN - ENHANCEMENTS
NA
2. 2.5 5 Pe Perf rfor orma manc nce e Co Cons nsid ider erat atio ions ns [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 when uplo upload ad do docume cuments nts from Loca Locall data tto o SAP Server: Server:
2. Log Log sho should uld gen gener erate ate fo forr Val Valid idati ation on::
3. Log Log a afte fterr p pro rogr gram am execu executio tion: n:
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 2.7 En Enha hanc ncem emen entt L Lay ayou outt [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:
Eq Equi uip pment ment T Te emp. mp.csv
© Client Name
FU FUNC NCT TIONA IONALL TASK LIST TEMP.csv LOCATION TEMP.csv
Status: Draft version 0.1
Page 11 of 13
FUNCTIONAL DESIGN - ENHANCEMENTS
3.0 Testing Requireme Requirements nts 3. 3.1 1 Ke Key y Bu Busi sine ness ss T Tes estt Co Cond ndit itio ions ns [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 IA11/12 Create / Change Change Functional Functional Loc Task List IA01/02 - Create Equipment task list
00 004 4
Docu Docume ment nt shou should ld be cr crea eate ted da and nd avai availa labl ble e
Do Docu cume ment nt sh shou ould ld be ava avail ilab able le on AL AL11 Directory.
005
Test Test scen scenar ariios: Run pro progra gram Upload file
If data is accurate, output should be document created for Equipment, FL and Task List respectively 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 Outstandi Outstanding ng IIssues ssues (Please list any outstanding issu es which may impact ongoing development)
Issue No
© Client Name
Description
Assigned To
Status
Status: Draft version 0.1
Impact
Resolution
Page 13 of 13
View more...
Comments
