70 pág.


DisciplinaConsultoria921 materiais3.305 seguidores
Pré-visualização11 páginas
by Business Process owner.
Trigger: Successful Final Configuration test
Application Development complete
Inputs: Business Process Master List
 Test Scenarios
 Development List
Overview of Final Integration Test
„ Like Final Configuration and Confirmation of which it is the extension, Final Integration Test 
involves Test Case playback. The goal is to examine the cross-functional and key integration points 
across the business processes followed by periodic processing and development. It is a simulation of 
live operation. 
© SAP AG TSCM52 24-97 
\uf8e9 SAP AG 2001
Final Integration Test
Prepare Final Integration Test
Conduct Final Integration Test
n Testing Strategy White Paper
n List of Predefined Test Scenarios
n Test Scenario Template
n Test Scenario Instructions
„ Set up Test Team and Logistics - Prepare for the final integration test. 
y Involve extended team members in this test. They can provide a fresh outlook and closer 
knowledge of the business process concerned. 
„ Define Integration Test Scope - Define the integration test goals and scope. 
y An important point is that you must choose which criteria will be used to consider the integration 
test complete. 
„ Define Integration Test Cases - Determine and define test cases in the integration test plan. 
y There are many cases in your business environment. To test them all using end-to-end scenarios is 
not practical. A method of selecting end-to-end scenarios and limited scenarios, or touch-point 
scenario, such as inter-company transactions, is used for integration testing. 
„ Create Final Integration Test Plan - Create a detailed final integration test plan. 
y The final integration testing is a critical task in your implementation. Your test plan must include 
the following processes and components: Business processes, Output, Reports, Interfaces, 
Conversions, Enhancements, Technical setup (Printer, fax), and Authorization. 
„ Approve Final Integration Test Plan - Obtain approval of the test plan from the business process 
owners and members of the test team. 
y All members must have the same goals to get commitment to the plans. When approvals are 
obtained, integration testing can begin. 
© SAP AG TSCM52 24-98 
\uf8e9 SAP AG 1999
Integration Worksheets
Integration Test
Documentation Links
Testing Dates
Level 1, Level 2, Level 3, Level 4
CI, Test Scenario
High, Medium, Low
Test Leader, Writer, Tester
Test Docs Completed, Plan, Actual
Status Doc\u2019d, Config\u2019d, Tested, Retest, Approved, Hold
„ Integration Test Scope 
Level 1 - Structure Item from Q&Adb 
Level 2 - Corresponds to Enterprise area level for business process 
Level 3 - Corresponds to Scenario level for business process 
Level 4 - Corresponds to Process Group level for business process 
„ Status - The current status of the particular level in the scope 
„ Priority - Set the priority level of the particular Integration Test level 
„ Responsibilities 
y Test Leader - Person responsible for coordinating all testing activities 
y Writer - Person responsible for writing test scenarios and any associated test materials 
y Tester - Person responsible for testing 
„ Testing Dates 
y Test Docs Completed - Completion dates for test scenarios and all associated test material 
y Plan - Planned completion dates for the tests 
y Actual - Actual completion dates of the tests 
„ Comments column included for notes and additional information documentation 
© SAP AG TSCM52 24-99 
\uf8e9 SAP AG 1999
Integration Test 1 (IT1)
SOP MPS MRP Plannedorder
Delivery CustomerBilling
Resource controlling
Logistics controlling Sales, Production, Purchasing, Warehouse
Order Customer
Financial Accounting
IT1 focuses on the internal integration testing
„ The purpose of the first cycle of integration testing is to check all cross functional integration points 
(limited or focused drill-down scenarios) for high-frequency and impact business processes, and to 
finalize the entire system configuration. The focus is testing that data crosses from one function 
(SAP module) to another. \u2018Focused Drill-down scenarios' was also the method used during Final 
Configuration where many iterations of different cases were processed quickly. 
„ Examples of integration points are: 
y Creation of a delivery note to be passed to MM (Materials Management) for warehouse processing 
y Running of MRP (Materials Resource Planning) in MM to automatically generate production 
orders in PP (Production Planning) 
y Creation of customer billing documents in SD (Sales & Distribution) to be passed to FI (Financial 
© SAP AG TSCM52 24-100 
\uf8e9 SAP AG 1999
Integration Test 2 (IT2)
Integration 2
Cross Functional
Integration Points
Cross Functional
Integration Points End-to-End Critical 
Business Flows
End-to-End Critical 
Business Flows
Take sales order, pass to
mfg, MRP, mfging, receipt
into Finished Goods,
shipping & billing
Take sales order, pass to
mfg, MRP, mfging, receipt
into Finished Goods,
shipping & billing
Integration 1Integration 1
\u2022 Delivery note passed
to MM for Warehouse
\u2022 Billing passed to FI for
payment processing
\u2022 Delivery note passed
to MM for Warehouse
\u2022 Billing passed to FI for
payment processing
Issues Database
Issue Input
Issues DatabaseIssues Database
„ Testing critical business flows as defined in the Business Blueprint from start to finish (end-to-end) 
is the purpose of Integration 2. These end-to-end scenarios, extended to form the business cases for 
testing, cover the test cases of Final Integration as well as periodic processing and development. 
They can be formed by linking focused drill-down scenarios from Integration 1. 
„ A sample end-to-end scenario would be the taking of a sales order, the passing of the demand to 
manufacturing, MRP (Materials Resource Planning), manufacturing of the product, receipt into 
Finished Goods, shipping to the customer, invoicing, billing and receipt processing. 
„ As in the cycles of Final Configuration and Confirmation, any issues occurring in each of the 
Integration 1 and 2 cycles must be added to the issue log, and issues resolved must be closed in the 
„ There is a change in the make-up of the testing teams between configuration cycles and integration 
testing. Testing is no longer function by function, but is now cross-functional. Therefore, the test 
teams for each business process must include members from each enterprise process area being 
„ This change in testing team make-up ties in with the knowledge transfer from Consultant (TeamSAP 
Members) to Customer (SAP Project Team Members) reaching its apex during the cycles of Final 
Integration Testing. Responsibility for the integration test becomes that of the Business Process 
Owners and Power Users. This instills a sense of ownership in the Business Process Users, which 
should make it easier to get acceptance at the end of the phase. 
© SAP AG TSCM52 24-101 
\uf8e9 SAP AG 2001
Phase 3: Realization - Work Packages (6)
Project ManagementProject Management
Organizational Change ManagementOrganizational Change Management
Training in the Realization PhaseTraining in the Realization