Marcus Wefers, ALM Solution Management, AGS, SAP AG
Best Practice Manual Testing of E2E processes using SAP Solution Manager 7.1 - Test Option 1
© 2014 SAP AG. All rights reserved. 3
Agenda
1. Approaches for manual testing of E2E Business Processes using SAP Solution Manager
2. Approach A: one Test Case covering the entire E2E Business Process
3. Approach B: individual Test Cases by business transaction composed into E2E Test Package
4. Comparison Approach A and B
5. Appendix
Business Process Documentation: Process Step Library and composition of E2E Business Processes
Test Data Container for business process „Order to Cash“
SAP Note and ABAP report to create access link for Test Data Container
Hybrid Approach C as combination of Approach A and B for very long E2E processes
Document types for Test Package Attachments
Executable Variants
Alternative approaches for manual testing of E2E
Business Processes using SAP Solution Manager
© 2014 SAP AG. All rights reserved. 5
Test Management Capabilities of test option 1 with SAP Solution Manager 7.1 SP07 or higher
Business Blueprint
Business Process
Change Analyzer
(BPCA)
WoC Test Management
• Manual Tests
• Automated Tests
SAP TDMS
Test Planning
eCATT
WoC Test Managment
Test Workbench
BW Reporting
Partner Logs and Reports
Test Status Reporting
Test script creation
Test system assignment
Test data assignment
Test Automation Framework
Test Case Assignment
other 3rd party test automation tools
Test Scope Optimization
Test Execution
HP QTP
SAP Solution Manager 7.1
Lean test system setup
CBTA (Component based Test Automation)
Business Blueprint
Test Planning
Test System Setup Test Execution and Reporting
Change
Deployment Change Impact Analysis
WS Certify
WoC Test Management
• Test Plan generation
• Tester assignment
This is the current state of planning and may be changed by SAP at any time.
© 2014 SAP AG. All rights reserved. 6
Manual Testing E2E Business Processes and involved testers
End to End Business Processes
Sales Order
Number
Sales
Order Delivery Billing
Goods
Issue Quotation
Transfer
Order
Delivery
Number Quotation
Number
Delivery
Number Delivery
Number
Tester 1 Tester 2 Tester 3
Purchase
Order
Goods
Receipt Payment
Purchase
Requistion
Invoice
Receipt
Order to Cash
Procure to Pay
Demand to Supply … … …
© 2014 SAP AG. All rights reserved. 7
Manual Testing Test Types and Test Scope Identification
Test Type Test Scope Identification Shared test management
infrastructure
Regression Test BPCA – Test Scope
Optimization (TSO)
• Business Blueprint
• Test Management
• Manual test cases
assigned to process steps /
business processes
• Automated test cases
• BPCA TBOMs
• BPCA TSO
• Test Data provisioning via
Test Data Container (TDC)
• …
User Acceptance Test Mostly manual selection of
test cases for new /adjusted
functionality
Integration Test BPCA TSO or full test scope
based on Blueprint attributes
or Test Case Keywords
© 2014 SAP AG. All rights reserved. 8
Manual Testing Motivation and Alternatives
Approach B
For each process step of an E2E
business process a single manual
test case is provided
Each manual test case is assigned
at the relevant process step of the
E2E business process in the
Business Blueprint
Motivation for Manual Testing Motivation
Test Managers require business process experts (BPx) to perform functional tests of E2E business processes.
Although automated tests can cover wide ranges of business processes, additional manual tests are required
for areas not covered by automated tests and for User Acceptance Tests (UAT).
Approach A
One manual test case for the entire
E2E business process
The test case is assigned at the
business process level of the
Business Blueprint
Recommended approach
Additional aspects
Test Scope Optimization based on
change impact analysis
Test execution by multiple Business
Process Experts (BPx)
BPCA TBOM generation
Handling of test data for manual
tests
© 2014 SAP AG. All rights reserved. 9
Manual Testing of E2E Business Processes
SAP Solution Manager - Business Blueprint with E2E Business Process: Order to Cash with variants
Manual Testing - Approach A
1 E2E test case assigned at
business process level
Manual Testing – Approach B
6 test cases assigned at
process step level of the
E2E business process
Approach A
1 E2E Test Case covering the entire Business Process
© 2014 SAP AG. All rights reserved. 11
Environment used in SAP internal test system Approach A
SAP Solman SI7 / 200
SAP ERP XUQ / 800
Project AGS_MW_01 (logical component Z_XUQ, System Role: Q)
Blueprint Business Scenario: ERP (XUQ) manual E2E tests - A
Business Process: Financials
Business Process: Procure-to-Pay V1
Business Process: Order-to-Cash V1 (Standard Order)
Business Process: Order-to-Cash V2 (Rush Order)
Test Data Container TDC: Z_ORDER_TO_CASH
BPCA Analysis BPCA Result ID: 383 (change event: Transport: SAPK-604DHINSAPAPPL)
Optimization Approach: OA_5 „Key Word filter for test cases using value RT1A“
Test Plan / Package Created via BPCA:
• Test Plan: Regression tests for E2E Bus.Processes using E2E process tests
• Test Packages: O2C, P2P, FIN
Created via WoC Test Mgmt – Test Plan Management
• Test Plan: Regression Test Plan E2E tests generated via Keywords RT1a
• no Test Packages created until now
© 2014 SAP AG. All rights reserved. 12
Manual Testing of E2E Business Processes
SAP Solution Manager - Business Blueprint with E2E Business Process: Order to Cash with variants
Manual Testing - Approach A
1 E2E test case assigned at
business process level
Manual Testing – Approach B
6 test cases assigned at
process step level of the
E2E business process
© 2014 SAP AG. All rights reserved. 13
Solution Documentation: Composition of E2E Business Processes
From Process Step Library ….
… to E2E Business Processes
Automatic generation
Manual composition of E2E business process
Decision on how to setup variants of Business Processes 0
For more details see Appendix: Process Step Library and composition of E2E Business Processes
© 2014 SAP AG. All rights reserved. 14
Solution Documentation: Composition of E2E Business Processes
Decision on how to setup variants of Business Processes 0
Blueprint:
Business Process level Transaction to start the entire business process
For more alternatives see Appendix: Executable Variants
© 2014 SAP AG. All rights reserved. 15
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Manual test case (docx, xlsx, …) describing test activities for all transaction of E2E Business Process 1
© 2014 SAP AG. All rights reserved. 16
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Manual E2E Test Case assigned to Business Process level (SOLAR02)
• Example business process Order to Cash with 2 process variants
• Assignment of one E2E Test Case – covering all executables of the BP variant - to each Business Process variant
2
E2E Test Case
for BP variant 1
including Test
Object assignment
(used as start
transaction during
test case execution)
BP variant 1
© 2014 SAP AG. All rights reserved. 17
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
Key Word assignment for manual tests (SOLAR02) 3
Open Attributes
Select Key Word
(Key Word definition on
SOLAR_PROJECT_ADMIN
Tab „Project Standards„
Sub-Tab „Keywords“
Assign test priority
© 2014 SAP AG. All rights reserved. 18
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
BPCA TBOM Generation
• Purpose: change impact analysis and test scope identification
4
Semi-dynamic TBOM generation
• Automatic TBOM generation for majority of
executables of process steps
• Available with SAP Solution Manager 7.1
SP10
• Prerequisite: UPL activated in managed
system
• Scope: for all process steps and
executables that can be tested individually,
thus E2E tests not required.
Approximately > 30% of your blueprint
Dynamic TBOM creation
• Manual TBOM generation at Business Process
(not process step) level by Business Process
Experts (BPx)
• BPx executes all executables like transactions of
the E2E Business Process while TBOM is
generated in the background.
• Note: process execution can be done one after the
other using „TBOM extentions“
• Scope: for all executables that can be tested only
as E2E business process. Example: O2C
© 2014 SAP AG. All rights reserved. 19
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
BPCA TBOM Generation. Step 1: semi-dynamic TBOM generation via background job 4
Workcenter Test Management
View Admininistration
TBOM Utilities
BPCA TBOM Utilities
Setting of parameters for background job for TBOM generation
Result: semi-dynamic TBOM for each executable (e.g. T-Code) assigned to Business Process / Steps
© 2014 SAP AG. All rights reserved. 20
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
BPCA TBOM Generation. Step 2: Dynamic TBOM generation via manual process execution 4
Step 1: select Business Process Variant and „Start“ transaction
Step 3: create dyn.TBOM for first transaction
Step 4 to n: continue with all remaining
transactions of the Business Process to capture
entire flow of Business Process variant
Note: you can pause and save in-between and
continue with TBOM generation at a later time
using TBOM Enhancement.
Step 2: Button „Attribute“
Result: dynamic TBOM for each E2E Business Process and assigned E2E test case at BP level
© 2014 SAP AG. All rights reserved. 21
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Data provisioning via Test Data Container (TDC)
• TDC definition: by Test Engineer or Business Process Expert (BPx)
• Test data provisioning: by BPx (manual planning in TDC or xls upload to TDC)
• Access: Work Center Test Management – View Extended Test Automation (T-Code: SECATT)
• SAP recommendation: 1 TDC for the entire business process (see Appendix for details)
5
© 2014 SAP AG. All rights reserved. 22
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Include link to test data within test script for smooth access for your users 5
1. Run ABAP report AGS_SMT_BUILD_TDC_NAV_URL and enter
Test Data Container (TDC) that includes suitable test data
2. Result of ABAP report: URL which allows direct access from test
script to test data of specified TDC
3. Use SAP Note 1927389 to create the ABAP report in your SAP
Solution Manager 7.1 when current SP level < SP11
4. Paste link into your test scripts (see Appendix for details)
Advantages
• Central maintenance of test data for all current and future test
cycles – no need to use xlsx files that contain valid test data for
only 1 test cycle
• Smooth access for tester directly from test script via URL to TDC,
which opens a second window during test execution
• Urgent changes to test data during the current test cycle can be
done centrally - no need to distribute xlsx files to testers
© 2014 SAP AG. All rights reserved. 23
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
Test Plan Generation - Alternatives 6
Test Cases assigned at Process Step level of Business Blueprint
2. TP Gen + Key Word Filter
Automatic selection of all
test cases with the relevant
Key Word value
3. TP Gen + BB Attribute Filter
Automatic selection of all test
cases assigned to process
steps with the relevant attribute
value
1. BPCA TSO + Key Word Filter
Automatic selection of E2E test
cases for Business Processes
impacted by change events plus
filter Key Word of test cases
4. TP Gen + manual selection
Test manager selects test
cases manually with
visualization of Business
Blueprint and available test
cases
WoC Test Mgmt BPCA
BPCA Test Scope Optimization Optimization Approach with filter:
Test Case – Key Word, e.g. RT1a
BPCA popup: TP Generation
WoC Test Mgmt
Test Plan Management
Create Test Plan
Test Plan filter:
Test Case Key Words with
value assigned to test
cases, e.g. RT1a
WoC Test Mgmt
Test Plan Management
Create Test Plan
Test Plan filter:
Business Blueprint Attributes,
e.g. custom attribute „Business
Process Prio“ with value 1
WoC Test Mgmt
Test Plan Management
Create Test Plan
Manual selection of suitable
test cases
© 2014 SAP AG. All rights reserved. 24
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
Test Plan Generation via BPCA Test Scope Optimization (TSO) 6.1
Step 1: Run BPCA for change event Step 2: continue with BPCA TSO
select BPCA result ID and button „Optimize Test Scope“
© 2014 SAP AG. All rights reserved. 25
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
Test Plan Generation via BPCA Test Scope Optimization (TSO) 6.1
Step 3: Activate filter using Test Case Key Words Step 4: BPCA TSO - Create Test Plan
Tip: Process Steps of E2E Business
Process w/o test cases will be excluded
© 2014 SAP AG. All rights reserved. 26
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
Test Plan Generation with filter Key Words assigned to test cases 6.2
Workcenter Test Management Test Plan Management
Filter: Key Word assigned to test cases
Value: Regression Test Priority 1 (RT1a)
© 2014 SAP AG. All rights reserved. 27
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
Test Package creation for selected Test Plan 7
Goal: set of test cases suitable for one tester or group of testers which execute the business process test
Path: Workcenter Test Management Test Plan Management Test Package Management
1.select Test Plan
2.generate Test Package
© 2014 SAP AG. All rights reserved. 28
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
Test Package: assignment of test persons
Path: WoC Test Mgmt TP Management Test Plan selection Test Package Management
7
• 1 Tester assignment:
this person has the know-
how to test the E2E business
process
• Multiple tester assignment:
a set of testers perform the
E2E business process test
based on their know-how of
assigned transactions
2.Popup for tester selection
1.Tester assignment
© 2014 SAP AG. All rights reserved. 29
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 1: Workcenter Test Managment – View: Tester Worklist 8
Tester 1
select Test Package
… and starts E2E
Test Case via „Run“
© 2014 SAP AG. All rights reserved. 30
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 2: Read Test Case Description 8
Tester 1
© 2014 SAP AG. All rights reserved. 31
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 3: view test data centrally stored in Test Data Container (TDC) 8
Second window with view of available test data stays open during test execution
TDC with test data for business process „Order to Cash“
Tester 1
© 2014 SAP AG. All rights reserved. 32
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 4: access System under Test (SUT) and execute transaction 8
Screen 1: test script – start test execution Screen 2: TDC test data
Screen 3: automatic launch of transaction that shall
be tested by user in pre-selected test system
Tester 1
Test execution
© 2014 SAP AG. All rights reserved. 33
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 5: test execution and test data provisioning 8
Screen 2: Test Data Container for business process O2C
Tester 1
Screen 3: Transaction „Create Quotation“ launched in test system
Test data for next
transaction of E2E
business process
© 2014 SAP AG. All rights reserved. 34
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 6 after test execution:
• change to Edit mode in Test Data Container
• add Quotation Number to Test Data Container – as handover information for next tester
8
Tester 1
Tip: define additional columns in TDC for test results – see Appendix for details
© 2014 SAP AG. All rights reserved. 35
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: step 7 (optional): documentation of test results
• create Test Note via „Copy Test Document“
8
Tester 1
© 2014 SAP AG. All rights reserved. 36
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 7 (optional): Test Note 8
Tester 1
Optional activity:
tester adds test results, such as screenshot
or document number created during test
execution.
© 2014 SAP AG. All rights reserved. 37
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 8: Test status and results 8
Tester 1
„Progress“
• Test status
• Comment: e.g.
„Test 1 completed
• Restrictions – if any
„Messages“
• create incident - if
required
„Results“
• screenshot of test
execution(optional)
© 2014 SAP AG. All rights reserved. 38
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 9: Tester Worklist - end of test case 1 execution 8
Tester 1
Test Case in
status: „being
processed“
„Comment“ used as handover information for Tester 2
© 2014 SAP AG. All rights reserved. 39
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 10: Tester No. 2 selects Test Package and executes E2E Test Case 8
Tester 2
Tester 2 views
all assigned Test
Packages
„Comment“ field includes information for Tester 2 to choose
E2E test case ready for him / her
© 2014 SAP AG. All rights reserved. 40
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 11: Reads test case description 8
Tester 2
© 2014 SAP AG. All rights reserved. 41
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 11: access Test Data Container 8
Test Data Container for O2C
Get result from previous test step.
Here: Quotation Number 20000138
Get test data for current test step.
Here: Sales doc. type “OR”
Tester 2
© 2014 SAP AG. All rights reserved. 42
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 12: access System under Test (SUT) and execute transaction 8
Screen 1: test script – start test execution Screen 2: TDC test data
Screen 3: automatic launch of transaction that shall
be tested by user in pre-selected test system
Tester 2
Test execution
Note: user needs to
manually call second
transaction (here: VA01),
since only the start
transaction is assigned to
the E2E tests
© 2014 SAP AG. All rights reserved. 43
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 13 test execution and test data provisioning 8
Screen 2: test data provisioning via Test Data Container Tester 2
Screen 3: Transaction „Create Sales Order“ launched in test system
© 2014 SAP AG. All rights reserved. 44
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 14: test result (Sales Order number) stored in TDC for next tester 8
Tester 2
© 2014 SAP AG. All rights reserved. 45
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 15: Test status, comment and results 8
„Progress“
• Test status
• Comment: e.g.
„Test 2 completed
• Restrictions – if any
„Messages“
• create incident - if
required
„Results“
• screenshot of test
execution(optional)
Tester 2
© 2014 SAP AG. All rights reserved. 46
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 16: (optional) Test result documentation via Test Note 8
Tester 2
© 2014 SAP AG. All rights reserved. 47
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Test Execution: Step 17: Second test case execution finished 8
Tester 2
Tester comment: „Sales Order ok – next test: Delivery“
© 2014 SAP AG. All rights reserved. 48
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
Approach A - Advantages
1. Smaller number of test cases since test cases are defined at BP variant level for areas like Logistics, not at process
step level (less creation and maintenance effort).
2. No need to define test sequences – Test Packages much easier to maintain (less effort)
3. Automatic Test Plan generation from BPCA Test Scope Optimization (TSO): correct E2E tests for E2E business
processes and their variants can be detected automatically by BPCA. No additional selection of test cases needed
to include all required test cases of the E2E business process (less effort, less error prone)
4. Easier handover of test results (Test Note visible to all testers, Tab Results including screenshots visible to all testers)
5. No Blueprint shortcut problem, since test cases are defined at Business Process level. (Test Plan generation using
Keywords assigned to test cases, can‘t be used when process steps in E2E Business Processes linked via shortcuts –
which is best practice)
Approach A - Challenges
1. No email notification for inform next tester of a test sequence. No icon „ready to test“ at Test Package level.
2. Automatic launch of transaction in test systems only works for first transaction of the E2E business process
Approach B
Individual Test Cases by business transaction
composed into E2E Test Package
© 2014 SAP AG. All rights reserved. 50
Environment used in SAP internal test system Approach B
SAP Solman SI7 / 200
SAP ERP XUQ / 800
Project AGS_MW_01B (logical component Z_XUQ, System Role: Q)
Blueprint Business Scenario: ERP (XUQ) manual E2E tests - B
Business Process: Financials
Business Process: Procure-to-Pay V1
Business Process: Order-to-Cash V1 (Standard Order)
Business Process: Order-to-Cash V2 (Rush Order)
Test Data Container TDC: Z_ORDER_TO_CASH
BPCA Analysis BPCA Result ID: 440 (change event: Transport: SAPK-604DHINSAPAPPL)
Optimization Approach: OA_5B „Key Word filter for test cases using value RT1“
Test Plan / Package Created via BPCA:
Test Plan: Regression Test Plan: multiple single test cases for E2E Business Process
• Test Packages: O2C Variant 1, P2P Variant 1, FIN
Created via WoC Test Mgmt – Test Plan Management
• Test Plan: not yet (see Appendix: available for project AGS_BS_IMP)
• Test Packages: not yet (see Appendix: available for project AGS_BS_IMP)
© 2014 SAP AG. All rights reserved. 51
Manual Testing of E2E Business Processes
SAP Solution Manager – Business Blueprint with E2E Business Process: Order to Cash – 1 Variant
Manual Testing - Approach A
1 E2E test case assigned
at business process level
Manual Testing – Approach B
6 test cases assigned at
process step level of the
E2E business process
© 2014 SAP AG. All rights reserved. 52
Solution Documentation: Composition of E2E Business Processes
From Process Step Library ….
… to E2E Business Processes
Automatic generation
Manual composition of E2E business process
Decision on how to setup variants of Business Processes 0
For more details see Appendix: Process Step Library and composition of E2E Business Processes
© 2014 SAP AG. All rights reserved. 53
Solution Documentation: Composition of E2E Business Processes
Decision on how to setup variants of Business Processes 0
Business Process
For more alternatives see Appendix: Executable Variants
Process Steps
© 2014 SAP AG. All rights reserved. 54
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Manual test case with description of test activities for 1 business transaction (docx, xlsx, …) 1
© 2014 SAP AG. All rights reserved. 55
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Manual test case assigned to process step level of the E2E business process (SOLAR02)
• Example process „Order to Cash“: six test cases are assigned – each at the process step level
• SAP recommendation: assign Test Object (e.g. transaction code) to the test case
• SAP recommendation: assignment of Key Word for test case, e.g. „Regression Test Priority 1“
2
© 2014 SAP AG. All rights reserved. 56
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Key Word assignment for manual tests (SOLAR02) 3
Open Attributes
Select Key Word
(Key Word definition on
SOLAR_PROJECT_ADMIN
Tab „Project Standards„
Sub-Tab „Keywords“
Assign test priority
© 2014 SAP AG. All rights reserved. 57
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
BPCA TBOM Generation (automated)
• Purpose: change impact analysis and test scope
identification
• SAP Solution Manager 7.1 SP10 (Nov 2013)
• For majority of the Business Blueprint: automatic
generation of semi-dynamic TBOMs
• for multi-purpose transactions embedded in E2E
process with high degree of variation:
• SOLAR01: Blueprint setup: create Executable Variants
to describe BP variants
• SOLAR01: BPCA TBOM: manual creation of dynamic
TBOM at process step level to capture process variants,
such as different document types
• Result: TBOM for each process step
Workcenter Test
Management
View
Admininistration
BPCA TBOM
Utilities
Setting of
parameters for
background job for
TBOM generation
4
© 2014 SAP AG. All rights reserved. 58
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
BPCA TBOM Generation (manual)
• Purpose: change impact analysis and test scope identification
• SAP Solution Manager 7.1
• Manual TBOM generation during manual test execution by tester
• Result: TBOM for each process step
4
User starts manual test execution from Tester Worklist, views test script, activates TBOM tracing (yellow frame) and executes test
© 2014 SAP AG. All rights reserved. 59
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Data provisioning via Test Data Container (TDC)
• TDC definition: by Test Engineer or Business Process Expert (BPx)
• Test data provisioning: by BPx (manual planning in TDC or xls upload to TDC)
• Access: Work Center Test Management – View Extended Test Automation (T-Code: SECATT)
• SAP recommendation: 1 TDC for the entire business process (see Appendix for details)
5
© 2014 SAP AG. All rights reserved. 60
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Include link to test data within test script for smooth access for your users 5
1. Run ABAP report AGS_SMT_BUILD_TDC_NAV_URL and name
Test Data Container (TDC) that includes suitable test data
2. Result of ABAP report: URL which allows direct access from test
script to test data of specified TDC
3. Use SAP Note 1927389 to create the ABAP report in your SAP
Solution Manager 7.1 when current SP level < SP11
4. Paste link into your test scripts (see Appendix 1)
Advantages
• Central maintenance of test data for all current and future test
cycles – no need to use xlsx files that contain valid test data for
only 1 test cycle
• Smooth access for tester directly from test script via URL to TDC,
which opens a second window during test execution
• Urgent changes to test data during the current test cycle can be
done centrally - no need to distribute xlsx files to testers
© 2014 SAP AG. All rights reserved. 61
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Plan Generation - Alternatives 6
Test Cases assigned at Process Step level of Business Blueprint
2. TP Gen + Key Word Filter
Automatic selection of all
test cases with the relevant
Key Word value
3. TP Gen + BB Attribute Filter
Automatic selection of all test
cases assigned to process
steps with the relevant attribute
value
1. BPCA TSO + Key Word Filter
Automatic selection of single test
cases for process steps
impacted by change events plus
filter Key Word of test cases
4. TP Gen + manual selection
Test manager selects test
cases manually with
visualization of Business
Blueprint and available test
cases
WoC Test Mgmt BPCA
BPCA Test Scope Optimization a) with filter: Test Case – KeyWords
b) Tab „BP Hierarchy“ – extend test
scope to cover complete E2E
Business Processes with test cases
BPCA popup: TP Generation
WoC Test Mgmt
Test Plan Management
Create Test Plan
Test Plan filter:
Test Case Key Words with
value assigned to test
cases, e.g. RT1
WoC Test Mgmt
Test Plan Management
Create Test Plan
Test Plan filter:
Business Blueprint Attributes,
e.g. custom attribute „Business
Process Prio“ with value 1
WoC Test Mgmt
Test Plan Management
Create Test Plan
Manual selection of suitable
test cases
© 2014 SAP AG. All rights reserved. 62
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Plan Generation via BPCA Test Scope Optimization (TSO) 6.1
Step 1: Run BPCA for change event Step 2: continue with BPCA TSO
select BPCA result ID and button „Optimize Test Scope“
© 2014 SAP AG. All rights reserved. 63
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Plan Generation via BPCA Test Scope Optimization (TSO) 6.1
© 2014 SAP AG. All rights reserved. 64
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Plan Generation via BPCA Test Scope Optimization (TSO) 6.1
Step 3: Activate filter using Test Case Key Words
Button „Add Attribute“
Tab „Test Case Options“
Open „Optimization Options“
Select Keyword for tool Test Organizer
and select value (here „RT1“) to filter
test cases for TSO
© 2014 SAP AG. All rights reserved. 65
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Plan Generation via BPCA Test Scope Optimization (TSO) 6.1
Step 4: extend test scope when BPCA identifies only selected test cases from the entire E2E Business Process
• Position cursor on BP
• Context menue (right
mouse): „Select node and
sub-nodes“ to select all
remaining test cases of the
business process
• Button: Apply and Save
Tab „Business Process Hierarchy“
© 2014 SAP AG. All rights reserved. 66
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Plan Generation via BPCA Test Scope Optimization (TSO) 6.1
Step 5: BPCA TSO button „Create Test Plan“
Work Center Test Mgmt: resulting Test Plan
© 2014 SAP AG. All rights reserved. 67
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Plan Generation with filter Key Words assigned to test cases 6.2
Workcenter Test Management Test Plan Management
Filter: Key Word assigned to test cases
Value: „RT1“ Regression tests with priority 1
Remark: Filter does not work for process steps using shortcuts - SAP Note 1816801
© 2014 SAP AG. All rights reserved. 68
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Plan Generation with filter Key Words assigned to test cases 6.2
Resulting Test Plan:
© 2014 SAP AG. All rights reserved. 69
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Package creation for selected Test Plan 7
Goal: set of test cases suitable for one tester or group of testers which execute the business process test
Path: Workcenter Test Management Test Plan Management Test Package Management
1.select Test Plan
2.generate Test Package
© 2014 SAP AG. All rights reserved. 70
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Package: assignment of test persons
Path: WoC Test Mgmt TP Management Test Plan selection Test Package Management
7
• 1 Tester assignment:
this person has the know-
how to test the entire end-to-
end business process
• Multiple tester assignment:
a set of multiple testers
perform the E2E business
process test based on their
know-how of assigned
transactions
2.Popup for tester selection
1.Tester assignment
© 2014 SAP AG. All rights reserved. 71
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Package: sequence of single tests for E2E tests based on SOLAR01 process steps
Path: Test Package Management select Test Package Button „Sequences“
7
• Test Package sequence „SQ1“ is defined semi-automatically by sequence of process steps of the
business process defined in the Business Blueprint (SOLAR01).
• Tester assignment to the entire Test Package or to specific Test Pack sequence steps
© 2014 SAP AG. All rights reserved. 72
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 1
Tester #1 opens Work Center „Test Management“ - view „Tester Worklist“ and checks whether
assigned Test Packages include test cases which are in status „ready to test“ for him / her
8
Tester 1 Column indicates Test Cases for
Tester 1 in status „ready to test“
© 2014 SAP AG. All rights reserved. 73
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 2: Tester Worklist - select Test Package and select first test case 8
Test sequence step 1 is ready for test execution
Tester 1
© 2014 SAP AG. All rights reserved. 74
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 3: Read Test Case Description 8
Tester 1
© 2014 SAP AG. All rights reserved. 75
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 4: view test data centrally stored in Test Data Container (TDC) 8
Second window with view of available test data
stays open during test execution
TDC with test data for process „Order to Cash“
Tester 1
© 2014 SAP AG. All rights reserved. 76
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 5: access System under Test (SUT) and execute transaction 8
Screen 1: test script – start test execution Screen 2: TDC test data
Screen 3: automatic launch of transaction that shall
be tested by user in pre-selected test system
Tester 1
Test execution
© 2014 SAP AG. All rights reserved. 77
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 6: test execution and test data provisioning 8
Screen 2: Test Data Container for business process O2C
Tester 1
Screen 3: Transaction „Create Quotation“ launched in test system
Test data for next
transaction of E2E
business process
© 2014 SAP AG. All rights reserved. 78
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 7 after test execution:
• change to Edit mode in Test Data Container
• add Quotation Number to Test Data Container – as handover information for next tester
8
Tester 1
Tip: define additional columns in TDC for test results – see Appendix for details
© 2014 SAP AG. All rights reserved. 79
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: step 8 (optional): documentation of test results
• create Test Note via „Copy Test Document“
8
Tester 1
© 2014 SAP AG. All rights reserved. 80
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 9 (optional): Test Note 8
Tester 1
Optional activity:
tester adds test results, such as screenshot
or document number created during test
execution.
© 2014 SAP AG. All rights reserved. 81
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 10: Test status and results 8
Tester 1
„Progress“
• Test status
• Comment: e.g.
„Test 1 completed
• Restrictions – if any
„Messages“
• create incident - if
required
„Results“
• screenshot of test
execution(optional)
© 2014 SAP AG. All rights reserved. 82
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 11: Tester Worklist - end of test case 1 execution 8
Tester 1
Test case 1: done
Test case 2: ready
to test
Test case status
in Test Package
© 2014 SAP AG. All rights reserved. 83
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 12 Tester No. 2 selects Test Package and executes Test Case 2 8
Tester 2
© 2014 SAP AG. All rights reserved. 84
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 13: Reads test case description 8
Tester 2
© 2014 SAP AG. All rights reserved. 85
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 14: access Test Data Container 8
Test Data Container for O2C
Get result from previous test step.
Here: Quotation Number 20000141
Get test data for current test step.
Here: Sales doc. type “OR”
Tester 2
© 2014 SAP AG. All rights reserved. 86
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 15: access System under Test (SUT) and execute transaction 8
Screen 1: test script – start test execution Screen 2: TDC test data
Screen 3: automatic launch of transaction that shall
be tested by user in pre-selected test system
Tester 2
Test execution
Note: user needs to
manually call second
transaction (here: VA01),
since only the start
transaction is assigned to
the E2E tests
© 2014 SAP AG. All rights reserved. 87
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 16 test execution and test data provisioning 8
Screen 2: test data provisioning via Test Data Container Tester 2
Screen 3: Transaction „Create Sales Order“ launched in test system
© 2014 SAP AG. All rights reserved. 88
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 17: test result (Sales Order number) stored in TDC for next tester 8
Tester 2
© 2014 SAP AG. All rights reserved. 89
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 18: Test status, comment and results 8
„Progress“
• Test status
• Comment: e.g.
„Test 2 completed
• Restrictions – if any
„Messages“
• create incident - if
required
„Results“
• screenshot of test
execution(optional)
Tester 2
© 2014 SAP AG. All rights reserved. 90
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 19: (optional) Test result documentation via Test Note 8
Tester 2
© 2014 SAP AG. All rights reserved. 91
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Test Execution: Step 20: Second test case execution finished 8
Tester 2
© 2014 SAP AG. All rights reserved. 92
Manual Testing – Approach B Individual Test Cases by business transaction composed into E2E Test Package
Alternative B - Advantages
1. Email notification for inform next tester of a test sequence. Icon „ready to test“ at Test Package level.
2. Automatic launch of transaction in test systems only works for each transaction of the E2E business process
Alternative B - Challenges
1. Higher number of test cases
2. Definition of sequences required which repeates the information altready provided in the E2E Business Process
(duplication, higher maintenance effort during initial creation and ongoing maintenance)
3. Test Plan generation using BPCA Test Scope Optimization: user needs to manually add process steps / test cases of
the remaining E2E process steps
4. Semi-automatic Test Plan generation using Keywords in combination with use of Blueprint Shortcuts not possible.
5. Handover of test results: information provided for individual test case at process step not visible for other testers
Comparison Approach A and Alternative B
© 2014 SAP AG. All rights reserved. 94
Comparison – Approach A versus Approach B
Approach A
1 E2E test case for E2E Business Process
Approach B
Multiple single test cases for E2E Business
Process
Advantages • Smaller number of test cases
• No need for redundant definition of test sequences
• Automatic Test Plan generation using BPCA TSO – no
need for manual test case selectons
• Easier handover of test results between involved
testers
• Email notifications for next tester and Workcenter with
icon „ready to test“ at Test Package level
• Executable linked to each test case to launch
executable in system under test
Disadvantages • No email notifications for next tester and WorkCenter
with icon „ready to test“ at Test Package level
• Only first transaction of E2E business process can be
assigned to E2E test to lauch executable in test system
• High number of test cases – existing functional tests at
executable level can only be reused to a certain degree
• Redundant process chain information in test sequence
• Automatic test plan generation using BPCA Test Scope
Optimization requires manual extention
• Test Plan generation cannot use Test Case Keywords
when using shortcuts in Business Blueprint
• Handover of test results between involved testers
Equal effort • Automatic batch job to generate semi-dynamic TBOMs
(which are used to identify test cases at Process Step
level that can be tested individually w/o E2E process
• Dynamic TBOM creation for business process variants
via manual execution or automated test cases
• Automatic batch job to generate semi-dynamic TBOMs
(which are used to identify test cases at Process Step
level that can be tested individually w/o E2E process
• Dynamic TBOM creation for business process variants
via manual execution or automated test cases
Appendix
Business Process Documentation: Process Step Library
and composition of E2E Business Processes
© 2014 SAP AG. All rights reserved. 96
Solution Documentation: Process Step Library
Process Step Library
• List of Process Steps by any grouping, e.g. by SAP Modules
• Assigned entities like Executables (e.g. transaction codes) and documentation
Example:
Process Steps and Transactions for SD
Automatic generation of Process Step Library
• Programm Z_Utility_Blueprint_Generation for selected customers provided by PM, RIG, COE
• See next pages for details
© 2014 SAP AG. All rights reserved. 97
E2E Business Blueprint versus SAP Module oriented Process Steps
Business Blueprint with E2E business processes
Alternatives to create E2E Business Blueprint
1. File upload using existing process documentation
2. Solution Documentation Assistant (tool) and Reverse
Business Process Documentation (service)
3. Data transfer from ARIS or HP QC (tool by ALM COE EMEA)
4. Manual documentation supported by BPR (SAP content)
Automated generation of SAP Module oriented Blueprint
1. Application: Scope and Effort Analyzer
Availability: SAP Solution Manager 7.1 SP11 (Q1 2014)
Blueprint items generated in background based on usage statistics of executables in PRD systems
Grouping by SAP Application Component Hierarchy (ACH)
Business Blueprint with process steps by SAP Modules
Sales
Order to Cash
Quotation
Sales Order
Delivery
Goods Issue
Billing
Procurement
Procure to Pay
LE Logistic Execution
LE-SHP Shipping
Delivery (VL01N)
Goods Issue (VL02N)
SD Sales & Distribution
SD-BIL Billing
Billing (VF01)
SD-SLS Sales
Quotation (VA21)
Sales Order (VA01)
E2E business process Process steps
grouped by
SAP Modules
© 2014 SAP AG. All rights reserved. 98
Solution Documentation: automatic generation of Process Step Libary SAP Utility Program to generate SAP Solman Project and SAP-Module oriented Blueprint
Purpose
• Auto-generation of SAP-Module oriented Blueprint based
on execution history (workload statistics)
Program name
• Z_Utility_Blueprint_Generation (not SAP standard)
Selection Screen
• Enter managed system / client
• …
• SAP SolMan projects that include BB and transactions /
reports to be excluded
Usage History
• Alt 1: read from managed system
• Alt 2: read from SAP SolMan InfoCube
Availability
For selected customers via PM, RIG, COE
Available for SAP SolMan 7.1 SP09 and SP10
© 2014 SAP AG. All rights reserved. 99
BPCA Prerequisite No 1: Business Blueprint SAP Utility Program to generate SAP Solman Project and SAP-Module oriented Blueprint
Result
• 3 level Blueprint hierarchy
• Level 1: SAP Module
• Level 2: ACH L2
• Level 3: Transaction or
Report
• Tab „Transaction“ with
assigned executable
Custom Code
• Node „Customer“
• Custom Code transactions
and reports are grouped by
development class
© 2014 SAP AG. All rights reserved. 100
Solution Documentation: Composition of E2E Business Processes
From Process Step Library ….
… to E2E Business Processes
Automatic generation
Manual composition of E2E business process
© 2014 SAP AG. All rights reserved. 101
Section 2 of Business Blueprint: E2E Business Processes Step 1: create business process
Create manually the business process
© 2014 SAP AG. All rights reserved. 102
Section 2 of Business Blueprint: E2E Business Processes Step 2: Copy business process step from Process Step Library to E2E Business Process
Copy business process step
• from Process Step Library (Section 1)
• to E2E Business Process (Section 2)
Process Step in Process Step Library
• Right mouse – „Copy“
© 2014 SAP AG. All rights reserved. 103
Section 2 of Business Blueprint: E2E Business Processes Step 3: Navigate to process area and insert Process Step to E2E Business Process
Copy Process Step from Process Step Library Navigate to E2E Business Process
and insert as Copy (Alt 1) or insert as Shortcut (Alt 2)
Result
© 2014 SAP AG. All rights reserved. 104
Section 2 of Business Blueprint: E2E Business Processes Step 4: Disband shortcuts
Right mouse: „Disband Shortcut“
• Take option to „Refer to Documents“ = document reference
original document stays at Process Step Library
• Take option „TBOM Copy“ since you may want to create
new TBOMs with more process variants
© 2014 SAP AG. All rights reserved. 105
Section 2 of Business Blueprint: E2E Business Processes Result after disbanding all shortcuts
From Process Step Library ….
… to E2E Business Processes
Automatic generation
Manual composition of E2E business process
Appendix
Test Data Container for entire Order to Cash Process
© 2014 SAP AG. All rights reserved. 107
Test Data Container (TDC) for entire Order to Cash process Transaction: SECATT
TDC structure definition
Process Step information
• Text to group test data
by process step
© 2014 SAP AG. All rights reserved. 108
Test Data Container (TDC) for entire Order to Cash process Transaction: SECATT
Test Data included in TDC
• grouped by Process Steps: Quotation, Sales Order, Outbound Delivery, Transfer Order, Goods Issue, Billing
• Additional result column for each business transaction to enter posted document number
Quotation Sales Order Delivery
Appendix
Link from manual test script to Test Data Container
© 2014 SAP AG. All rights reserved. 110
Generation of link to access Test Data Container (TDC) Purpose: access from manual test script to Test Data Container
Report AGS_SMT_BUILD_TDC_NAV_URL
• SAP Note 1927389 includes the code in case your SAP Solman system does not inlcude the ABAP report
• Input parameter: Test Data Container – select via value help (F4)
• Run report in SAP Solution Manager system which creates 2 snippets of the required link
Result
Alternative 1:
use buffered URL and
include in test scipts
via CTRL V
Alternative 2:
copy string with
CTRL Y plus CTRL C
and paste in test
script via CTRL V
© 2014 SAP AG. All rights reserved. 111
Generation of link to access Test Data Container (TDC) Purpose: access from manual test script to Test Data Container
Test Script
User clicks on link inside the test script which opens a second
window displaying the test data of the associated TDC
Appendix
Approach C – combination of Approach A and B
© 2014 SAP AG. All rights reserved. 113
Approach C Combination of Approach A and B for E2E processes with very high number of process steps
Approach C
• E2E business process separated into multiple business processes –each containing multiple process steps
• Suitable when using very long E2E Business Processes which cannot be covered by 1 tester group
• Test sequence used as handover from one business process test to next business process
• Each Test Package includes multiple tests which can be handled by one test team
Test Plan Test Package Test Package
E2E Business Process grouped into 3 processes containing multiple process steps
Test Package: Order To Cash
Sales Order
Logistics Execution
Billing
End-to-end Scenario Structure Tester 1
Tester 2
Tester 3
Test
Sequence
Appendix
Definition of document types used during test execution to
store document numbers via tab “Test Package
Attachment”
© 2014 SAP AG. All rights reserved. 115
Definition of new Document Types Transaction: SOLAR_PROJECT_ADMIN
Path: Tab: „Project Standards“ Tab „Documentation Types“
Define new Documentation Type
„Test Results via Test Package Attachment“
© 2014 SAP AG. All rights reserved. 116
Definition of new Document Types Transaction: SOLAR_PROJECT_ADMIN
Define Document Template
© 2014 SAP AG. All rights reserved. 117
Definition of new Document Types Transaction: SOLAR_PROJECT_ADMIN
• Line 1: Title
• Line 2: user can
enter Transaction
code info
• Line 3: Header
• Line 4 – n: used
during test case
execution to enter
test data variants
and posted
document numbers
Appendix
Use of “Executable Variants” instead of multiple Business
Processes to document business process variants
© 2014 SAP AG. All rights reserved. 119
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Decision on how to setup variants of Business Processes 0
Alt 1: multiple Business Processes Alt 2: Executable Variants*
Example: Example:
Sales
Order-to-Cash Variant a
Process Step 1a (transaction 1)
Process Step 2a (transaction 2)
….
Order-to-Cash Variant b
Process Step 1b (transaction 1)
Process Step 2b (transaction 2)
Procurement
Procure-to-Pay Variant a
…
Procure-tp-Pay Variant b
…
Sales
Order-to-Cash
Process Step 1 (transaction 1*, 1**)
Process Step 2 (transaction 2*, 2**)
Procurement
Procure-to-Pay
Process Step 1 (…)
Process Step 2 (…)
Remark:
executable * and ** might be the same transaction, but using
different document types or other types of differention or
navigation through the transaction.
* available with SAP Solution Manager 7.1 SP06
Assignment of Executable
Variants to allow BP variant-
specific TBOM assignment
© 2014 SAP AG. All rights reserved. 120
Manual Testing – Approach A 1 E2E Test Case covering the entire Business Process
Decision: documentation of Business Processes variants – Alt 2 0
Blueprint:
Business Process level
Button to create Executable Variant
Transaction to start the entire business process
Executable
Variants
(here for
Transaction
VA21) to
allow BP-
variant
specific
TBOM
assignment
© 2014 SAP AG. All rights reserved. 121
Manual Testing – Approach A
1 E2E Test Case covering the entire Business Process
BPCA TBOM Generation: Example: manual creation of TBOM for each Business Process Variant 4
Step 1: select BP and Executable Variant #1 Step 2: button „Attributes“
Step 3: create dyn.TBOM for first transaction
Step 4 to n: continue with all remaining
transactions of the Business Process to capture
entire flow of BP variant
Note: you can pause and save in between and
continue with TBOM generation at a later time
using TBOM extentions.
Appendix
Approach B using Project AGS_BS_IMP
© 2014 SAP AG. All rights reserved. 123
Environment used in SAP internal test system Approach B using SAP Solman Project AGS_BS_IMP
SAP Solman SI7 / 200
SAP ERP XUQ / 800
Project AGS_BS_IMP
Blueprint Business Scenario: ERP Logistics O2C (XUQ) / Process: 0_Order-to-Cash
Test Data Container TDC: Z_ORDER_TO_CASH_1
BPCA Analysis BPCA Result ID: 275
Optimization Approach: OA_4
Test Plan / Package Created via BPCA: • Test Plan: Test Plan from BPCA using Key Word Value RT1 (ERP system XUQ)
• Test package: no test package created
Created via test plan generation using Test Case Keywords • Test Plan: Test Plan E2E Process via Keywords
• Test Package: E2E Test Package O2C
• Sequence: SQ1
© 2014 SAP AG. All rights reserved. 43
No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered
trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or
registered trademarks of Adobe Systems Incorporated in the United States and/or other
countries.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
© 2014 SAP AG. All rights reserved.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World
Wide Web Consortium, Massachusetts Institute of Technology.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP AG in Germany and other
countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports,
Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and
services mentioned herein as well as their respective logos are trademarks or registered
trademarks of Business Objects Software Ltd. Business Objects is an
SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.