Escolar Documentos
Profissional Documentos
Cultura Documentos
Approach
The blueprinting phase
The realization phase
The implementation phase
Wrap-up
The approach
Methodology
Lessons learned
Source:
SAP
Scope:
Scope:Sets
Setsthe
theinitial
initialdefinition
definitionofofthe
theproject.
project.
Project
Projectteam
teamorganization:
organization:Sets
Setsthe
thewho
whoofof
the
theproject.
project. This
Thisdecides
decideswho
whowill
willbe
beinvolved
involved
and
what
is
their
goal.
and what is their goal.
Standards
Standardsand
andprocedures:
procedures:Sets
Setsthe
thewhy
why
and
andhow
howof
ofthe
theproject.
project. Standardizing
Standardizinghow
how
meetings
meetingsare
arerun,
run,documents
documentsare
arehandled,
handled,etc
etc
means
meansthat
thateveryone
everyoneunderstands
understandswhat
whatisisgoing
going
on.
on.
Source: Pauline Woods-Wilson
Note
SAP standard
Single, pragmatic, and standardized
methodology
Evolved out of 20 years of experience
Manageable scope, cost, and common
expectations
Common language
Preconfigure documentation and tools
What is ASAP?
Fill
Fillin
inthe
theBlank
Blank
Versus
Versus
Start
Startfrom
fromScratch
Scratch
Workshop Agenda
Questionnaires
End-User Procedures
Test Plans
Technical Procedures
Made Easy guidebooks (printout, data transfer, system
administration)
Note
These are lessons learned the hard way!! Dont re-invent the
wheel but learn from others.
10
Upgrade Projects
e-Learning
New in
2004
Test Organizer
Customizing
Synchronization
Tool
Source: SAP
Solution Monitoring
Service Level
Reporting
Content
Services
Best Practice
Documents
Roadmaps
Service Delivery
Platform
Landscape Reporting
Support Desk
Implementation
Platform
Implementation
Content
Change Request
Management
Gateway to SAP
SAP Support
11
Create contact
group and contact
list for business
input and
requirements
Name
Joe Jones
Joseph Jones
Joe Jones
Joe Jones
Joe Jones
Joseph Jones
Joe Jones
Joe Jones
Joe Jones
Joseph Jones
Joe Jones
Joseph Jones
Joe Jones
Organization
MYORG Ltd
Your ORG Ltd
MYORG Ltd
MYORG Ltd
MYORG Ltd
Your ORG Ltd
MYORG Ltd
MYORG Ltd
MYORG Ltd
Your ORG Ltd
MYORG Ltd
Your ORG Ltd
MYORG Ltd
Create a tool to
collect info
requests
and business
input
Phone Number
918-123-1234
918-123-1234
123-123-1234
918-123-1234
918-123-1238
918-123-1239
918-123-1234
918-123-1234
918-123-1234
918-123-1234
918-123-1234
918-123-1234
123-123-1234
Conduct
information
gathering
using the
tool
Disposition
the info.
requests to
BW or R/3
Consolidate
requirements
and write
functional
specs
D1
Is repo rt
documentatio n
com ple te?
Yes
D1a
Isth is a true
re po rting
need
No
Communicate to
bus . leader
Yes
No
D2
Is this
an Intraday
report?
Request ad diti on al
input from Bus in es s
Team membe r
No
D2.5
Do es data exist
in "i n-scope" models
Infocube/ODS
Yes
Yes
Yes
D6
Doe s
Standard BW
conten t
exis t?
Ye s
BW
is selected as
Reporting Tool and
documented in doc.
to ol
Communicate fina l
disposition
No
D3
Significant
number
of users?
D4
Is the r ep ort
system
resource
intensive?
No
Yes
No
D7
Is it less
exp ensive to
create in
R/3?
BW
is selected as
Re porting Tool
a nd documented
in th e documentation tool
Co mmunicate final
disposition
D8
Is BW cost
effective?
No
R/3 is selected as
Reporting Tool
and documented
in doc. tool
Communicate final
disposition
Yes
D9
R/3 Tool
Selection
Process
BW
is selected as
reporting tool and Change
Request is submitted if
the scope changed
No
Standard
R/3
Yes
R/3
is s elected as
Re port ing Tool
and d ocu mented
i n do c. tool
Com municate final
dis position
No
R/3
is selected as
Reporting Tool
a nd documented
in doc. tool
A2
Total Cost of
Ownership
Analysis
D5
Does
Standa rd R /3
content
exist?
No
Yes
is s ele ctedas
R/3
is s elected as
Re port ing Tool
and do cum ent ed
Responsible
Team membe r
acquires/do cum ents
additional informati on
BW
is selected as
Reporting Tool and
documented in doc.
tool
Communicate final
disposition
Communicate final
disposition
ABAP/
Custom
Report
Writer
Q uery
Other
A3
Sub-Process Report Cons ol ida tio n &
eliminate if approp riate (w innowing)
R/3 team make fina l di sp osition
Don't
Forget
A4
Baseline re ports
There is more than one way to collect this information, however, a formal
process should exist to capture requirements and to communicate what
is being developed.
We will now examine the most common form of RAD
(Rapid Application Development).
12
Ask for 1-2 days of uninterrupted time and provide lunch on-site
Remove cell phones, PDA and pagers and emails
Invite power users, casual users, today's report writers, and
managers
Keep a rapid pace and a manageable number of attendees (no
more than 20)
Focus on shared information needs and conduct multiple
sessions if needed
Don't get trapped in details; give people a chance to provide
feedback in writing and follow up later with individuals
13
Benefits include:
14
Note
Best
Practice
15
16
Document requirements in
a standardized format
Prioritize requirements
Consolidate requirements
Support follow-up
discussions and reviews.
Tool
P117
of 2
Other uses:
Tool
P218
of 2
Warning
There are many tools that can report on R/3 data and you
might have static reports that truly belongs in R/3 and which
would not be cost effective to move to BW
Make cost-effective decisions; just because the report is not
in BW does not mean it cannot be in a portal or on the web
Not all reports belong in BW; avoid using BW as a "dumping
group"
You need to make conscious decisions on what reporting
needs you are going to meet and how you want to accomplish
this
19
20
cu
D1
Is report
documentation
complete?
Yes
Tool
D1a
Is this a true
reporting
need
No
Communicate to
bus. leader
Yes
No
D2
Is this
an Intraday
report?
Request additional
input from Business
Team member
No
D2.5
Does data exist
in "in-scope" models
Infocube/ODS
Yes
Yes
Yes
D6
Does
Standard BW
content
exist?
Yes
BW is selected as
Reporting Tool and
documented in doc.
tool
Communicate final
disposition
No
No
D7
Is it less
expensive to
create in
R/3?
BW is selected as
Reporting Tool
and documented
in the documentation tool
Communicate final
disposition
D8
Is BW cost
effective?
Communicate final
disposition
R/3 is selected as
Reporting Tool
and documented
in doc. tool
Communicate final
disposition
Yes
D9
R/3 Tool
Selection
Process
BW is selected as
reporting tool and Change
Request is submitted if
the scope changed
No
Standard
R/3
Yes
R/3 is selected as
Reporting Tool
and documented
in doc. tool
No
No
R/3 is selected as
Reporting Tool
and documented
in doc. tool
Yes
A2
Total Cost of
Ownership
Analysis
Communicate final
disposition
D5
Does
Standard R/3
content
exist?
D4
Is the report
system
resource
intensive?
No
Yes
R/3 is selected as
Reporting Tool
and documented
Responsible
Team member
acquires/documents
additional information
No
D3
Significant
number
of users?
BW is selected as
Reporting Tool and
documented in doc.
tool
Communicate final
disposition
Communicate final
disposition
ABAP/
Custom
Report
Writer
Query
Other
A3
Sub-Process Report Consolidation &
eliminate if appropriate (winnowing)
R/3 team make final disposition
A4
Baseline reports
21
Now That You Have Identified the In-Scope Reports, Whats Next?
Obtain a copy of each of the current reports that are in-scope (not all).
Legacy reports may be a great source to document the data needs; they
can be used to illustrate how data is currently being summarized and
viewed in the organization
Consolidate the requirements and look for "low-hanging fruit"
Create a physical folder with paper copies of "in-scope" legacy reports;
make sure that the development team has access to them and reduce the
time spent in meetings with the business community
Great
Feature
Many requirements
can be met by a
single BW report
22
Flow Overview
BW Report object:
Business
Reporting
Requirements
Reports
Query Name:
Fixed format:
Free format:
Number of users:
Target Users:
Time Granularity
Historical data:
Peak time usage:
Data Volume:
Frequency:
SAP Roles:
Test Criteria:
Jump Targets:
BW Reports
An example from a very large manufacturing company
23
An
Example
24
An
Example
25
Flat Reporting
Formatted
Print
Form based
Static
Predictable access
OLAP Reporting
Drill Down
OR
OR
26
The approach
The blueprinting phase
Deliverables
Core Activities
2.1 Project Management Business Blueprint
2.2 Organizational Change Management
2.3 Project Team Training Business Blueprint
2.4 Develop System Environment
2.5 Organizational Structure Definition
2.6 Business Process Definition
2.7 Quality Check Business Blueprint
Map
Mapthe
thefunctional
functionalrequirements
requirementsto
tothe
the
standard
standardcontent
contentand
andsee
seewhat
whatcan
canbe
be
leveraged
leveragedand
andwhat
whatneeds
needsto
tobe
be
extended.
extended.
Create
Createdetailed
detailedtechnical
technical
specifications
specificationsand
anddesigns
designsofof
infocubes,
infocubes,masterdata,
masterdata,ODSs
ODSsand
and
high-level
high-levelarchitectural
architecturaldesigns.
designs.
Create
Createuser
useracceptance
acceptancegroup(s)
group(s)and
and
have
havethem
themreview
reviewand
andgive
givefeedback
feedback
on
onthe
thesystem
systemas
asititisisdeveloped.
developed.
28
As a guiding principle we
map requirements to
standard content before we
start customizing.
31%
Some observations on
higher level objects.
36%
33%
BW Content available:
InfoObjects 11,772
ODS objects 349
InfoCube
605
MultiCubes
121
Roles
861
Queries
3,299
Workbooks 1,979
29
Storage
BW functional requirement:
Storage
Requirements
Material
Material number
Material entered
Material group
Item category
Product hierarchy
EAN/UPC
BW logical model:
Unit
Logistics
Plant
Shipping/receiving point
Currency Key
Unit of Measure
Base unit of measure
Sales unit of measure
Volume unit of measure
Weight unit of measure
Billing
Customer
Sold-to
Ship-to
Bill-to
Payer
Customer class
Customer group
~ Custome r country
~ Custome r region
~ Custome r postal code
~ Custome r industry code 1
End user
Organization
Company code
Division
Distribution channel
Sales organization
Sales group
Personnel
Sales rep number
Accounting
Cost center
Profit center
Controlling area
Account assignme nt group
Billing information
Billing document
Billing item
Billing type
Billing category
Billing date
Creation date
Cancel indicator
Output me dium
~ Batch billing indicator
Debit/credit re ason code
Biling category
Reference document
Payment terms
Cancelled billing document
Divison for the order header
Pricing procedure
Document details
Sa les order document type
Sales deal
Sales docuement
Time
Calendar year
Calendar month
Calendar week
Calendar day
LEGEND
Standard content
BW InfoCubes
30
1. Write functional
requirements
3. Map your
requirements to the
delivered content and
identify gaps.
Unit
Logistics
Plant
Shipping/receiving point
Currency Key
Unit of Measure
Base unit of measure
Sales unit of measure
Volume unit of measure
Weight unit of measure
Billing
Customer
Sold-to
Ship-to
Bill-to
Payer
Customer class
Customer group
~ Customer country
~ Customer region
~ Customer postal code
~ Customer industry code 1
End user
Organization
Company code
Division
Distribution channel
Sales organization
Sales group
Personnel
Sales rep number
Accounting
Cost center
Profit center
Controlling area
Account a ssignme nt group
Billing information
Billing document
Billing item
Billing type
Billing category
Billing date
Creation date
Cancel indicator
Output me dium
~ Batch billing indicator
Debit/cre dit re ason code
Biling category
Reference document
Payment terms
Cancelle d billing docume nt
Divison for the order header
Pricing proce dure
Document details
Sales order docume nt type
Sales deal
Sales docuement
Time
Calendar
Calendar
Calendar
Calendar
year
month
week
day
LEGEND
Delivered in standard extractors
Delivered in LO extractor
Not in delivered Content -but in R-3
31
The approach
The blueprinting phase
The realization phase
Development
DevelopmentPrograms:
Programs:Provide
Provide
details
of
added
programming
details of added programming
structures
structures
End
EndUser
UserTraining
TrainingMaterial
Material
Configuration
Configurationand
andTesting
TestingPlans:
Plans:
Define
how
the
configuration
Define how the configurationwill
willbe
be
implemented
and
how
it
will
be
implemented and how it will be
tested
tested
Source: Pauline Woods-Wilson
33
34
Test Plan
Test Execution
Problem Resolution
35
December 2003
January 2004
s,
a
g
r
o
f
p
to sto
e
m
i
t
o
n
"There's dy late"
rea
we're al
Schedule Facilities
Prioritize Test Areas (Queries)
Send out Meeting Notice
Execute System Test
Document Results
Problem Resolution
Activities
Tasks
1
2
3
4
5
6
7
8
9
12
10
2
3
9
4
8
7
Timing
36
Deliver
Cost and Profitability
Order
Manufacturing
Plan and scheduling
Demand planning
Source
Environment
preparation
4/2
4/1
3/31
3/30
3/29
3/28
3/27
3/26
3/25
3/24
3/23
3/22
3/21
3/20
3/19
3/18
3/17
3/16
3/15
3/14
3/13
3/12
3/11
3/10
3/9
3/8
3/7
3/6
3/5
3/4
3/3
3/2
3/1
Resolving
outstanding
issues and retesting
Preparations
38
People
Logisitics
39
March 2004 29-Mar 5-Apr 12-Apr 19-Apr 26-Apr 3-May 10-May 17-May
Progress meeting
40
Performance Testing
Test Signoffs
Signoff procedure
42
Wrap-up
43
Core Activities
44
Types of training:
Web-based
All users
Training
Tutorials
Instructor-led
On-site
Power users
Executives
Vendor-based
Developers
Support staff
45
46
CHANGE
Issue
Should a set of
Ambassadors be part of
the rollout-strategy?
CONTINUE
TOP-DOWN
APPROACH
Issue
Note
BOTTOM-UP
APPROACH
Focus on a bottom up
approach where the DW project
will prioritize supporting and
delivering DW solutions, but
where businesses are actively
involved in developing reports.
47
No
(10%)
50%
50%
Successful
Successful
Note
Yes
(90%)
70%
70%
Successful
Successful
48
The
Thelast
lastdeliverable
deliverablefor
forthe
the
implementation
ensures
implementation ensureshigh
highsystem
system
performance
through
monitoring
performance through monitoringand
and
feedback
feedback
Source: Pauline Woods-Wilson
We
Weneed
needtotoexecute
executeissue
issueresolution
resolution
plans
and
contingency
plans
plans and contingency plans
Core Activities
5.1 Production Support
5.2 Project End
AAlessons
lessonslearned
learnedsession
sessionshould
shouldbe
be
held
at
the
end
of
the
project
to
assure
held at the end of the project to assure
organizational
organizationalawareness
awarenessand
andeducation
education
The
Thesupport
supportorganization
organizationwill
willtake
takeover
overthe
the
system
after
a
pre-determined
time
period.
system after a pre-determined time period.
Some
Someteam
teammembers
membersmay
maytransition
transitioninto
into
their
new
roles
as
support
staff
their new roles as support staff
This
Thisisisaacritical
criticaltime
timewhen
whenaaSWAT
SWATteam
team
that
thatquickly
quicklyaddresses
addressesuser
userconcerns
concernscan
can
make
all
the
difference
in
how
the
system
make all the difference in how the system
isisreceived
receivedamong
amongthe
theusers
users
49
Alignment
Are we doing
the right
things?
Are we doing
them the right way?
Integration
Benefits
Are we getting
the benefits?
Are we getting
them done well?
Capability/Efficiency
50
The approach
The blueprinting phase
The realization phase
The implementation phase
Wrap-up
51
Multi-Channel Access
Portal
Collaboration
Information Integration
Business
Intelligence
Knowledge
Management
Process Integration
Integration
Broker
Business Process
Management
People Integration
Application Platform
J2EE
ABAP
andOS
OS Abstraction
Abstraction
DBDBand
.NET
WebSphere
52
Resources
a)
b)
Download it at:
53
Your Turn!!!