7138_TSCM_52-2_ª_parte_(24)
70 pág.

7138_TSCM_52-2_ª_parte_(24)


DisciplinaConsultoria737 materiais2.634 seguidores
Pré-visualização11 páginas
will be looking at less frequent basic transactions and 
conditions. 
- Examples: Create pick-pack requirements, transport routes and 
interest calculation rules, and define vendor dunning rules 
- Master data: Customer credit limits, material determination records. 
- Basic transactions (medium priority): Create Quotation, Create 
Collective MRP, and Create Vendor Down Payment Request 
\u2022 Cycle 3 - Refine the configuration and master data by running high 
priority business processes. 
- Examples: Cost center analysis and physical inventories, create a 
sales order with delivery or billing block, create a standard sales 
order, create a delivery note for that order, and post goods issue for 
that delivery. 
\u2022 Cycle 4 - Complete the refinement of the configuration by running 
business processes that include exception transactions, reports, user 
profiles and all business processes within a given function or R/3 
component, to ensure readiness for integration testing. 
4-4-2 Once you have identified what configuration takes place in which cycle, you 
can store this information in the BPML. 
 
© SAP AG TSCM52 24-147 
4-5 
4-5-1 Both unit testing and scenario testing are performed as part of the Baseline 
and Final configuration. 
Unit testing is the lowest level of testing where the program or transaction is 
tested and evaluated for errors. 
Scenario testing involves test chains of transactions that flow together, and 
which reflect important business processes. 
Integration testing is driven from the previous testing efforts (unit and 
scenario). The test cases and scenarios that were used for Baseline and Final 
configuration are enhanced for an integrated test, which represents business 
process flows with \u201ctouch points\u201d from beginning to end (end-to-end). 
4-5-2 In the Implementation Assistant [IA]: 
\u2192 Open the Roadmap by clicking the ! icon. Call up ValueSAP - 
Implementation and Implementation Roadmap 
\u2192 Open the Realization phase 
\u2192 Open the work package Final Integration Test 
\u2192 Open the activity with the Prepare Final Integration Test 
\u2192 Open the task Set up Test Team and Logistics 
On the right screen area, you can now view the description and steps 
recommended by ASAP to determine the Set up Test Team and Logistics. 
Define Integration Test Scope 
Define Integration Test Cases 
Create Final Integration Test Plan 
4-6 
4-6-1 Responsibility for the integration test becomes that of the business process 
owners and power users rather than consultants. This will help to instill a 
sense of ownership with the business process owner and should make it 
easier to ensure acceptance at the end of the phase. 
4-6-2 There should also be a change in the make-up of the testing teams between 
the configuration cycles and integration testing. As the test becomes more 
integrated, the test team should include team members from every enterprise 
area being tested. This will ensure that all processes are properly tested. 
Extended teams members should be involved to ensure you meet the 
company\u2019s business requirements. 
 
© SAP AG TSCM52 24-148 
4-7 In the Q&Adb: 
\u2192 Select the Reports structure item on the left side in the Q&Adb 
\u2192 Expand the Master Lists node by clicking the ! icon 
\u2192 Expand the BPML node by clicking the ! icon 
\u2192 Click on a BPML document 
\u2192 Select Open Report 
\u2192 Open the worksheet Baseline 
\u2192 Search for the Documentation Links columns (columns j-n) 
Line 2 contains the different document types: 
CI, BPP, Case procedure, Test Scenario, Project document 
4-8 The Business Process Master List (BPML), along with the Business Blueprint, is a 
key result of the second phase of the Roadmap. 
The Microsoft Excel tables contain the SAP scenarios, process groups, and 
processes that have been set in scope in the SAP Reference Structure, and are 
crucial for configuring your SAP System. 
In Realization, the third phase of the Roadmap, the BPML provides the basis for 
monitoring and steering test activities and for configuring your SAP System. It 
contains the titles of the structure items, and displays the status, the owner, links to 
documentation and links to the R/3 System. 
Amongst other things, the BPML allows you to: 
\u2022 Define the baseline and final scope, which form the basis for Baseline and 
Final configuration 
\u2022 Access the Project IMG and specific IMG activities assigned to structure items. 
\u2022 Access integration test plans, which help you carry out all required integration 
tests. 
 
 
 
© SAP AG TSCM52 24-149 
\uf8e9 SAP AG 1999
ASAP-Related Topics
z Upgrade Roadmap
z Global ASAP
 
 
 
 
© SAP AG TSCM52 24-150 
\uf8e9 SAP AG 2001
On completion of this unit, you will be able to:
z Outline the role and content of the ASAP
Roadmap for Upgrade
z Explain the purpose & function of Global ASAP
ASAP-Related: Unit Objectives
 
 
 
 
© SAP AG TSCM52 24-151 
\uf8e9 SAP AG 1999
ASAP-Related Topics Upgrade Roadmap
 Global ASAP
ASAP-Related: Overview (1)
 
 
 
 
© SAP AG TSCM52 24-152 
\uf8e9 SAP AG 1999
Defining the Points on the ASAP Upgrade Roadmap
Upgrade Project
Preparation
Business 
Blueprint
Realization of
DEV and QAS
Realization of
Production Go Live &
Support
\u2022 Initial Upgrade Project
Planning
\u2022 Upgrade Project
Procedures
\u2022 Technical Requirements
Planning
\u2022 Upgrade Preparation
\u2022 Analysis of the Productive R/3 System
\u2022 Gather Information on Functionality
of the new R/3 Release
\u2022 Analyze and Classify the use of new 
Standard Functionality
\u2022 Define Aims of the Upgrade Project
\u2022 Training for Upgrade Business Blueprint
\u2022 Upgrade and Test 
Development System (DEV)
\u2022 Upgrade and Test 
Quality Assurance System (QAS)
\u2022 Training Upgrade Realization
\u2022 Training Upgrade
Final Preparation
\u2022 Upgrade Production
System
\u2022Project Support
 
 
 
„ Phase 1: Upgrade Project Preparation - The purpose of this phase is to provide initial planning and 
preparation for your R/3 upgrade project. Although each upgrade project has unique objectives, 
scope and priorities, the steps in Phase 1 help identify and plan the primary topics that must be 
considered. 
„ Phase 2: Business Blueprint - The purpose of this phase is to establish a common understanding in 
your company about how the new R/3 release will handle your current business processes after the 
R/3 upgrade. 
„ Phase 3: Realization of DEV and QAS - The purpose of this phase is to perform the upgrade of all 
non-production R/3 Systems, which normally include development (DEV) and quality assurance 
(QAS) systems, and to ensure the quality of this upgrade process by comprehensive testing. You 
need to upgrade your DEV and QAS systems before performing the upgrade for your production 
system (PRD). Furthermore, you will develop your end user documentation and training in this 
phase. 
„ Phase 4: Realization of Production - The purpose of this phase is to complete the final preparation 
for the upgrade of the production R/3 System, and end user training, if necessary. On the successful 
completion of this phase, you are ready to run your business in your upgraded production R/3 
System. 
„ Phase 5: Go Live and Support - The purpose of this phase is the transition from your previous R/3 
System to a newly upgraded and improved R/3 System. Be aware that you must set up an ongoing 
support organization to service your R/3 users, both during the first few days of your upgraded 
production operations, and on an ongoing basis. 
 
© SAP AG TSCM52 24-153 
\uf8e9 SAP AG 2001
R/3 Upgrade of DEV System
Ma
in
te
na
nc
e
Ma
nu
al
SAP
Corrections
SAP
4.6BRelease
SAP
Release 4.6c
Worry free withWorry free with
R/3!R/3!
R/3
Home Sweet Home !Home Sweet Home !
I'm so glad we