2. 2 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
PROJECT CHARTER
Project Charter
Title
SAP Enterprise Portal
Homepage Enhancement
Process
SAP Enterprise Portal
Homepage Loading
Process Owner Ng Swee Tiong
Problem Statement
The current SAP Enterprise Portal Homepage layout contains a Universal Worklist (UWL) that takes up a lot of processing time and
layout space. Consequently, the efficiency of work task solving of portal users may decrease as it takes a very long time for the
Homepage to complete loading.
Project Objective
To improve the efficiency of SAP Enterprise Portal Homepage by creating an iView that works as a replacement for UWL that reduces
the loading time of Homepage
Start Date 6th March 2015 (WW10) Team Members/Role
Ng Kwong Cheong
Sponsor Michael Orlando
Project Manager Ng Kwong Cheong
Team Lead / Mentor -
Scope In Scope
SAP Enterprise Portal
Out of Scope
-
Constraints Technical skills, time management
Expected Financial Impact
(or other key metrics)
Increased user’s efficiency of workflow management
Aligned with which
Strategic Goal (s)
Simplify The Business
3. 3 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
SOLUTION
1st stage: Development
• Create a new development track in NetWeaver Developer Infrastructure (NWDI) .
• Import required Software Components (SC) into the track from Change Management
Service(CMS) inbox.
• Create new Development Components (DC) using NetWeaver Developer Studio
(NWDS) in the track created from NWDI (* in this case, 1 Enterprise Portal application
and 1 External Library were created).
• Develop the source code in the DC’s and perform debugging/build to ensure no
compilation error.
2nd stage: Deployment
• Perform any changes necessary to the source code in NWDS.
• Perform a “Check In” to build the project in NWDI.
• Proceed to the development (DEV) portal which the project has deployed to.
• Create an iView based on the production, resources and tools (PRT) iView created
upon the success of the “Check In” of the DC.
• Insert the iView in the necessary SAP work page.
4. 4 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
SOLUTION
Flow Chart
5. 5 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
SOLUTION
New home page layout
MiniUWL iView
6. 6 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
SOLUTION
Old Home page loading completion time
Time
(estimate) :
16.46 s
7. 7 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
SOLUTION
Time
(estimate)
: 4.64 s
New Home page loading completion time
8. 8 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
BENEFITS
What Benefits To Whom It Benefits
(Approximately) 70% less processing
time for Homepage loading
completion
Enterprise Portal Homepage user
Easier to keep track of workflow
based on certain attributes
Enterprise Portal Homepage user
More layout space can be used for
Homepage design
Enterprise Portal Homepage
administrator
9. 9 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
SHARING BEST PRACTICES
Who will you share this process
improvement with?
How will you let them know?
SAP EP team
Knowledge Transfer
Documentation
10. 10 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
MY GOALS IN GRADUATE TRAINEE PROGRAM
Familiarize with the company’s organizational structure
Establish an effective social network among team members and other colleagues
Improve own technical and soft skills, at the same time learning new skillset
My Greatest Challenge and How I Overcame It
Challenge: Difficulty to adapt to a new working environment (team switching)
How I Overcame it:
• Counsel and guidance from team members
• Reference from reliable online resources
• Tasks prioritization
12. 12 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
CALCULATION: LOADING COMPLETION TIME
Old Home Page New Home Page
Time taken for loading completion :
16.46 seconds
Time taken for loading completion :
4.64 seconds
4.64 − 16.46
16.46
𝑥 100% = −71.81%
13. 13 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
STAKEHOLDER REGISTER
Name of
Stakeholder
Designation /
Department /
Location
Role in the
Project
Type of
Stakeholder
Type of
Communication
Expectations
Influence on
Project
Outcome
Internal /
External
Influencer /
Supporter /
Neutral
14. 14 | GT FINAL REPORT OUT | AUGUST 31, 2015 | CONFIDENTIAL
CAUSE-EFFECT ANALYSIS
<Cause 1> <Cause 2>
<Effect>
Most likely to be
the root cause
and you have the
ability to
fix/control
<Cause 1.1>
<Cause 1.2>
Bring more impact -> effects the efficiency / productivity of workflow (need mention business impact)
Add on:
What is UWL? – A type of workflow inbox used to perform assigned tasks (SAP Business workflow, KM, approvals, etc).
Advantages & Disadvantages of UWL
Adv: High degree of customization & personalization, supports multiple systems (ECC, SRM, etc) in one place
Disadv: high infrastructure requirements (must have EP to use), doesn’t support mobile devices, PERFORMANCE ISSUE OF POLLING MULTIPLE SYSTEMS, REQUIRE EXTRAORDINARY MEASURE (DELTA PULL) to overcome
Cause of long loading time of UWL – DELTA PULL to pull multiple systems into one spot
What is DELTA PULL?
DON’T READ PLAINLY. JUST BRIEFLY EXPLAIN THE TOOLS USED AND THE REASON IN USING THEM
What is NWDI? – server-based development landscape in Java environment, provides development environment and software support through entire lifecycle of a product. Helps DEV team to modify standard apps. (CHECK IN, DEPLOY). Allows management of resource files as well.
What is NWDS? – integrated development environment (IDE) of Java part of SAP technology. Used to develop business web app and SAP EP projects as well. Contains plug-ins a toolsets for SAP technology (Web Dynpro, Java Dictionary)
What are SC, DC and CMS?
SC: a collection of REUSABLE software, libraries (.jar) that helps in developing own software, etc allows to support new feature inside your app
DC: software unit that you develop. Always assigned to certain SC. Contains the information for the software unit, METADATA of the development
CMS: central system that manage process with different release steps to control software flow. Supports automated deployment of build results onto test servers and PROD.
Explain “Check In”
Explain the “deployment” – difference between actual deployment and current deployment
Describe the functional behavior of iView (what happens when new task appear, each row representations, color highlight, URL link to actual UWL)
Blue = New Task, Orange = High prio, Green = In progress, Yellow = Due today, Red = Overdue
Mention the spacing left for Announcement as well
Pin out the page which takes most loading time (Blue)