HOUGHTON MIFFLIN HARCOURT

SAP DOCUMENT OF UNDERSTANDING

1|Page
 TABLE OF CONTENTS

OBJECTIVE………………………………………………………………………………………………………………………………….3

INTRODUCTION/OVERVIEW OF SAP…………………………………………………………………………………………..3

SCOPE………………………………………………………………………………………………………………………………………..3

FUNCTIONS TO BE TESTED………………………………………………………………………………………………………….3

TESTING METHODOLOGY……………………………………………………………………………………………………………3

SALESFORCE TEAM STRUCTURE………………………………………………………………………………………………….3

ENTITIES USED IN SALESFORCE……………………………………………………………………………………………………4

HOW TO CREAE ORDERS……………………………………………………………………………………………………………..5

SALESFORCE AND SAP INTEGRATION DIAGRAM…………………………………………………………………………..6

CREATING PDRF MANUALLY AND AUTOMATION PROCESS………………………………………………………….6

ENVIRONMENTS………………………………………………………………………………………………………………………….7

RELEASE TIMEFRAME…………………………………………………………………………………………………………………..7

TOOLS USED FOR TESTING…………………………………………………………………………………………………………..7

TYPES OF TESTING………………………………………………………………………………………………………………………..7

TESTING PROCESS…………………………………………………………………………………………………………………………7

AUTOMATION TOOL……………………………………………………………………………………………………………………..8

TEST CASES……………………………………………………………………………………………………………………………………8

DEFECTS………………………………………………………………………………………………………………………………………..8

DEFINITION OF DONE……………………………………………………………………………………………………………………8

DEFINITION READY……………………………………………………………………………………………………………………….8

METRICS/REPORTS……………………………………………………………………………………………………………………….8

SAP LINKS…………..………………………………………………………………………………………………………………………..8

PEOPLE AND ROLES………………………………………………………………………………………………………………………9

ACRONYMS…………………………………………………………………………………………………………………………………..9

2|Page
OBJECTIVE
Objective of document of Understanding is to define the understanding obtained from Knowledge
Transfer session from Cognizant to Qualitest to continue supporting Houghton Mifflin Harcourt testing
activities successfully.

INTRODUCTION/ OVERVIEW OF SAP

SAP is an integrated business software to process all functionalities of an organization in order to obtain
a unified solution. The original SAP idea was to provide customers with the ability to interact with a
common corporate database for a comprehensive range of applications. In Houghton Mifflin Customer
Relationship Management (CRM) only digital products such as subscription and licenses are handled.
 Products objects stores information of all products of HMH. They are funneled through SAP and
cannot be created directly from Salesforce.
 Opportunities object stores information about all the successful complete detail with the
customers along with the future potential revenue generating deals. Each opportunity is
associated with account and contact holds information about amount, current stage etc.

SCOPE
The document mainly targets the UI testing and validating data in SAP as per Requirements
Specifications provided by Cognizant.

FUNCTIONS TO BE TESTED
 SAP User Interface
 Salesforce integration to SAP
 SAP to LogPro
 SAP to CLM
 CLM to SAMC

TESTING METHODOLOGY
The testing methodology followed by Houghton Mifflin for SAP is Waterfall. There is ongoing discussion
of moving to an Agile methodology. This is yet to be confirmed.

SALESFORCE TEAM STRUCTURE

Currently there are two teams in SAP. SAP 1.0 and SAP 2.0

 SAP 1.0 – 1 PM, 1 BA, 1 Lead Architect, 2 Solution Architects, 2 Developers and 1 Tester (7 total)
 Supporting freeze changes
 There are approximately 6-7 intakes (Change Request) in 1.0
 No High priorities are in SAP 1.0. They are all medium size priorities

3|Page
 QA is not involved, because the intakes are all small effort, which is being supported by Unit
and Integration testing.
 SAP 2.0 – 1 PM, 1 BA, 1 Lead Architect, 2 Solution Architects, 2-3 Developers and 1 Tester (7 – 8
total). SAP 2.0 is the upgrade being made to SAP 1.0.
 Supporting intakes (Change Request)
 Tickets (defects) are those that were found in the June release.
 There are approximately 10 active tickets (Prod defects) in 2.0.

MODULES IN SAP
 SAP BRIM Creation of SPIO’s (Sample, Pilot and Implementation)
 SAP CRM Roles Program Offering
 Products
 Item Categories
 Standard Solution Quotation creation with standalone Digital, Physical and
Service items
 Digital, Physical and Service items process flow
SFDC and Esker are third party systems that integration with SAP.
Esker has the knowledge and expertise that customers using SAP want and need.
Esker's automation solutions have SAP-certified integration, which ensures a
smooth flow of business information through SAP software using a single, integrated
point of support.
 SAP technology and application expertise
 Solutions developed, tested and preconfigured for SAP
 SAP master data and routines leveraged when automating order and invoice
processing
 Direct access to orders and invoices in SAP
 Outbound mail and fax communication status back in SAP
Salesforce will be impacted by purchase orders created in Esker.

HOW TO CREATE ORDERS

Esker

 Create CP in SF
 CPO will create a ESKER system
 Submitting it to SF CPO will be created.

Creating FSB Invoicing

a. Create Invoice Group

4|Page
b. Create/Display Invoice Package
c. Park and Post Legal Invoices
d. Package History"

Cancellations – Processing a cancellation order

a. Digital Standalone
b. Digital Kit
c. Sales Package/Mixed Kit"

PRODUCT TYPES
 Physical – Books
 Services – Scheduling trainers performed (services being performed)
 Digital – e-version books

PRODUCT GROUPING
 Standalone – Individual
 Kits – Digital and Physical
 Packages – All 3 (Physical, Services and Digital)

SALESFORCE AND SAP INTEGRATION

SAP 2.0
Architecture_6.pdf

SAP INTEGRATIONS

SFDC SAP logPro

SAMC

CLM

MIDDLEWARE IN SAP
 APACHE
 CAMEL

SAP DATABASE
 1.0 - Non Hanna database

5|Page
  2.0 - Hanna database

FUNCTIONALITIES
1.0 – Lower Version
 80% Business revenue
 Established approximately 6-8 years
 No CRM
 Will be used as Master Data Source for SAP 2.0
2.0 Primary Version
 ISG
 Functional and Technical activities
 CRM

CREATING PDRF MANUALLY and AUTOMATION PROCESS (SAP 1.0 & SAP 2.0)
PDRF is an event that is created when a customer request for any type of training on a product.
Manual process for PDRF is created SAP 1.0
 Create a CP
 Product search -> Add products
 Add quantity for the product
 In PDRF tab just add related opportunity to CP
 Create Purchase order and submit to SAP
 Once template pdrf is created submit it to approval.
 Once it is approved click on create PDRF and create.
CREATING PDRF AUTOMATION PROCESS (SAP 1.0 > SALESFORCE 1.0)
Automation process for PDRF for SAP 1.0:
 Create CP and CPO
 Submit to SAP. Automatically PDRF will be created by executing some back jobs.
 Automatically PDRF will be created in Salesforce. If there is any rejection it can be done in SAP.
CREATING PDRF MANUALLY (SAP 2.0 > SALESFORCEF 2.0)

PDRF in SAP 2.0:

Salesforce is same like SAP 1.0. In SAP 2.0 the product which we select should be IFG product. Service
order, service contract then PDRF is created in sales force. We will be getting service request number
with it.
CREATING PDRF AUTOMATION PROCESS (SAP 2.0 > SALESFORCE 2.0)

Automation process PDRF for SAP 2.0

Change the status and check whether the PDRF status will be changed.

6|Page
ENVIRONMENTS
Currently there are 2 environment for SAP 1.0 and 4 environments for SAP 2.0
 SAP 1.0
 ECC System
 QA
 SAP 2.0
 ECC System
 CRM
 CC
 QA

RELEASE TIMEFRAME
Release is the 3rd Sunday of every month for both SAP 1.0 and SAP 2.0. There is no Release Manager
who owns and organize the release. Dev and BA are the ones involved in the implementation. No
support from testers currently.
SAP Release Calendar

SAP_Releases_2017.p
ptx

TOOLS USED FOR TESTING

 JIRA
 Spira
 Shared drive

TYPES OF TESTING
 Functional
 Regression
 Minimal Automation

TESTING PROCESS
SAP has a manual and automation testing process.

AUTOMATION TOOL
 HMH is utilizing a tool name Worksoft for their automation need on SAP.

Modules with Automated Test Scripts

 SD – 67 test scripts – 100% Automation Test Coverage
 MM – 60 test scripts – 100% Automation Test Coverage

7|Page
  FICO – 37 test scripts - 97% Automation Test Coverage
 CRM – 14 test scripts - 86% Automation Test Coverage
 E2E – 48 test scripts – 100% Automation Test Coverage

100% Regression Automation Test Coverage – 17 test scripts

TEST CASES
See total number of manual test cases by module below;

 SD – 83 test cases
 MM – 172 test cases
 FICO – 147 test cases
 CRM – 33 test cases
 E2E – 626 test cases

DEFECTS
 Defects leaked into production (By severity) None
 Passed/Failed/Blocked Test cases percentage --
 Rejected Defects – None
 RCA- Origin of Defects

METRICS/TRACEABILITY
 Rate of test case creation (By time unit)
1. Manual test case one per day (24hrs)
2. Automation -
 Requirements coverage percentage – 100%
 Percentage of cases traced to user stories (Or requirements) – 98%

SALESFORCE LINKS

8|Page
SFDC Share Path for Regular Releases: https://today.hmhco.com/teams/ECRM/Project
%20Deliverables/Forms/AllItems.aspx

SB5 to salesforce: https://hmhco--sb5.cs17.my.salesforce.com

Spira for Test management: https://hmhit.spiraservice.net

Jira for Sprint Activities: https://jira.hmhco.com/secure/Dashboard.jspa

Share bath for Sprint Activities: https://hmhco.account.box.com/

PEOPLE AND ROLES

Valentin Torres
Rich Pulsper Tech Lead
Siva Tech Lead
Aravind Vijayaraman Lead Project Manager
Bryan Meade Product Manager

ACRONYMS
HMH Houghton Mifflin Harcourt
CRM Customer Relationship Management
SAP Systems Applications Products
CLM Customer Lifecycle Management
UI User Interface
SPIO Sample Pilot and Implementation
CC Conversion Charges
CI Conversion Invoicing
Rev Rec Revenue Recognition
CPO Customer Purchase Order
SAMC Sam Connect
SFDC Salesforce Dot Com
IT Integration Testing
BTS Back to School
SC Solution Contract
SO Service Order
SAO Sales Order
CPO Cost Proposal Order
SQ Solution Quotation
FI Finance
BI Business Intelligence
QA Quality Assurance
UAT User Acceptance Testing

9|Page
10 | P a g e