Support Test Planning During the Blueprint Phase with Transaction Variants

  • by D. Russell Sloan, Implementation and Governance Specialist — SAP Solution Manager, IBM Global Business Services
  • July 28, 2014
During the business blueprint phase, variations in business processes are identified. How these variations affect end-to-end test scenarios is information that is often lost between the design phase and integration testing. Using transaction variants is a way to get a jump start on end-to-end integration test design.
Learning Objectives

Reading this article you will:

  • Learn how to activate and use the transaction variants feature during the business blueprint phase to capture and track process variations as well as aid in end-to-end test planning
  • Understand the importance of establishing and using naming conventions for transaction variants for consistency across teams and to add value to the variants for use in testing, reporting, and other project needs
Key Concept

Transaction variants are one way to identify process variations that should be used when constructing integration test scenarios for end-to-end process testing. They can identify when the same transactions need to be run in different ways to meet the requirements of variations in business processes. Activating and using the transaction variants feature during the business blueprint phase can help test planning and execution. Transaction variants also enable the association of variation-specific documents, such as work instructions or test execution directions.

During the business blueprint phase, many detail design sessions are held to understand all the nuances of business processes to meet business needs. During these sessions, it often becomes evident that many processes have variations based on the differing contexts within which the process may operate within the business unit. These variations represent the circumstances when the process is basically the same at a general level, but at the more detailed level, there are extra or different activities that must be performed within the business transaction to complete the process in accordance with business requirements.

To capture these detailed variations, Solution Manager provides a feature that allows project teams to create and map these variations to the Business Process Hierarchy (BPH) as transaction variants.

D. Russell Sloan

D. Russell Sloan is a specialist in project and program governance for IBM. He focuses on the use of SAP Solution Manager for global rollout projects for IBM’s largest customers, having worked with SAP software since 1996. Russell has degrees in accounting and information systems and has been a team and project leader for SAP projects for more than 14 years. He has been developing and deploying software systems for over 30 years.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.