Sei sulla pagina 1di 7

Planned Delivery May 2016

SAP 2.0 Implementation

Scope Statement
Version 15

Project Vision
ISG was recently acquired from Scholastic and is currently operating on Scholastic
business systems under a Transition Services Agreement (“TSA””) between Scholastic
and HMH. The company’s goal is to implement the ISG business on the new System
no later than May 2016. HMH intends for the balance of company’s business to migrate
to the System starting in 2017.

The project objective is to implement a new SAP HANA system configured to support
HMH’s long-term goal of operating its entire business on the System. The initial
implementation of the System will target only the recently acquired ISG business.

The key business driver for the May 2016 release is to facilitate the value realization of
the recent acquisition investment. The company has prioritized the migration of ISG to
the new System and the termination of the TSA with Scholastic, as soon as possible.

The overriding premise is to deliver the functionality to produce, sell, deliver, and collect
revenue for ISG specific products on the system by May 2016. This assumes there will
be no “combined kits” with both HMH and ISG products. “Combined orders” will be
received with line items made up of standalone ISG prpoducts, standalone HMH
products, ISG Kits or HMH Kits.

Project High-Level
In Scope
The May 2016 scope is determined to be the minimum set of requirements to enable
the end to end processes required to support the ISG business.

Guiding Principles for defining the scope of the 2016 release:


 Utilize SAP standard functionality as much as possible to meet business
requirements

469245039.docx 1
Planned Delivery May 2016

 Include only business requirements that minimally meet the needs to


successfully operate the ISG business
 Avoid where possible configurations that constrain future-state needs to operate
the entire business on the solution
 Workflows will be standard SAP workflows, including document image
attachments.

The following standard SAP functions are considered in scope. Specific descriptions of
the business functionality and processes that will be delivered as part of the May 2016
scope can be found in the Project’s Business Design Documents (BDDs)

Included in the functionality will be support for the following SAP standard functions:

1. Financial Accounting and Controlling


1.1. General Ledger
1.2. Accounts Receivable
1.3. Accounts Payable
1.4. Asset Accounting
1.5. Revenue Recognition (Standard RR, not RAR)
1.6. Cost Center Accounting
1.7. Profit Center Accounting
1.8. Internal Oder Accounting
1.9. Profitability Analysis
1.10.Simple Finance

2. Material Management
2.1. Procurement
2.2. Goods Movement
2.3. Material Master Data
2.4. Vendor Master Data

3. Project Systems
3.1. For Capital Projects only (no other projects)

4. Billing & Revenue Innovation Management (BRIM)


4.1. CRM, including solution quotes, contracts, and master agreements
4.2. Convergent Charging
4.3. Convergent invoicing
4.4. Product Configuration
4.5. Pricing

469245039.docx 2
Planned Delivery May 2016

4.6. Flexible Solutions Billing

5. Sales & Distribution


5.1. Available to Promise
5.2. Delivery Schedules
5.3. Billing plans
5.4. Foreign Trade (including GTS)
5.5. Consignment, and third party
5.6. Customer Master Data

6. Planning and Fulfillment


6.1. Sales & Operations Planning
6.2. Advanced Planning Optimization

7. Base System
7.1. Access Control via GRC (same Roles as current system)

Included in the scope will be the following interfaces to/from the SAP 2.0 platform:

1. Finance
1.1. Alliant (Royalty)
1.2. Sabrix
1.3. Paymetric
1.4. QAS – Quality Assurance System
1.5. Banks (including EDI Wire transfers)
1.6. Oanda (FX Rates)

2. Sales and Distribution


2.1. Support for dual SAP system order entry (1.0/2.0)
2.1.1. Splitting Esker orders between HMH and ISG product
2.1.2. Splitting Orders in SFDC between HMH and ISG product
2.2. Salesforce.com (SFDC)
2.3. Customer Care
2.4. Customer Master Data synchronization
2.5. Manual processing of Depository transactions
2.6. CLM Interface for Digital Access and entitlement mgmt (aka CAES/eGoods)
(CLM is addressing functionality needed in the HMH environment due to the
previous TMS to SAM Connect integration, as TMS Application will not
transition from Scholastic to HMH)
2.7. Esker Delivery Ware
2.8. Esker On-Demand
2.9. MDR – similar functions to current SAP 1.0 process

469245039.docx 3
Planned Delivery May 2016

3. Material Management
3.1. Ariba
3.2. Variant configuration (material variants and versioning)
3.3. LogPro (OTC interfaces)
3.4. LogPro (Inventory/SCM)

4. Tools and Reporting


4.1. Central DB
4.2. BW / BI Reporting and Integration with dual SAP BW instances
4.2.1. ISG reporting in new instance
4.2.2. Some required data from new SAP 2.0 instance sent back to BW 1.0 for
consolidated reporting
4.2.3. Current proposal is to load data from SAP 2.0 into BW 1.0 and utilize the
data interface to BPC from BW 1.0 to enable analysis and company wide
reporting on the ISG business
4.3. Winshuttle
4.4. Cronacle

Here’s the interface diagram showing SAP1.0 and SAP2.0


NOTE: the diagram below shows that MDR is in scope and MDM is not in scope (still
waiting on confirmation for these 2 items)

SAP 2.0 Interface


Diagram V6

Out of Scope for May 2016 Release

The following functionality is out of scope for the May 2016 release.

1. General
1.1. Any functionality not referenced as in scope
1.2. Additional functionality to the existing SAP 1.0 system
1.3. HMH legacy product specific support

2. Finance
2.1. SAP RAR for Revenue recognition
2.2. Sabrix in non US currency

3. Sales and Distribution


3.1. Support for automated feeds of ISG product in State Depositories
3.2. The ZOTCM custom report transaction from SAP 1.0

469245039.docx 4
Planned Delivery May 2016

3.3. Processing for customer Rebates


3.4. Promotions and deals (will support coupon codes only)
3.5. Price maintenance cockpit
3.6. Sales order approval
3.7. Standard rush orders
3.8. Linking AES (automatic export system declaration) to sales orders
3.9. Letters of credit
3.10.Trade
3.11.MDM (Informatica)

4. Material Master
4.1. IS Media
4.2. PLM Capabilities – Innovate, Promote, Launch, Grow, Decline
4.3. Changes to PIPS and MMR systems

5. Validation of Certification / capabilities or updates from CBTs

6. No HR supported functionality
6.1. Calendar availability for entire resource pool and Schedule planning for workforce on
service orders
6.2. Time Sheet entries for workforce on service orders
6.3. Evaluation of Candidates, Skills and Capabilities Management to aid staffing
6.4. Resource loading visibility at staffing level

7. Material Management
7.1. Scheduling agreements
7.2. Vendor sustainability (Vendor evaluation workflow)
7.3. Purchasing contracts will not be stored or used in workflow
7.4. Quality management (Vendor evaluation workflow)
7.5. Returns to vendor
7.6. Vendor consignment (Distribution of 3rd party material for Trade)
7.7. Vendor rebate agreements (coupons are in scope, but not promotions)
7.8. Scraping approval workflow
7.9. Dynamic discounting
7.10.Payments in Ariba
7.11.Tagetik

8. Data
8.1. Archiving (regularly running processes to remove no longer relevant or required
data from the system)
8.1.1. Out of scope because there won’t be any data relevant for archiving in
the first release

Additionally the following business systems and interfaces are excluded from the scope
of this project phase.

1. Banta (RRD)

469245039.docx 5
Planned Delivery May 2016

2. eCommerce / Web Presence (hmhco.com)


3. Riverside Publishing (legacy)
4. Heinemann
5. GSC Knowledge DB (this functionality replaced by SAP 2.0)
6. Marketing Content into HMHCO.com
7. Depository Automated Feeds
8. Punch-out (Milwaukee/Chicago)
9. EDI Multiple Source Order Channel
10. Catalyst (Scholastic’s vendor invoice system)
11. HOTS Integration
12. ONIX provides master data (add, changes, deletes) to resellers
13. BPC for ISG Data

Scope yet to be determined

The following functionality status is yet to be determined for the May 2016 release.

1. TBD
1.1. Concur for the 2.0 landscape

Legend

BW = Business Warehouse

Integrations

Esker = document management software


Alliant = Credit union??
Sabrix = Transaction tax management
Paymetric = integrated payment processing
Oanda = currency converter
SAP Ariba = procurement
Winshuttle = simplifies SAP business processes by providing automated solutions for
data movement, workflow applications and data governance.
Cronacle = simplifies the definition, monitoring and analysis of the completion of
business processes such as order-to-cash, procure-to-pay, and supply chain
management
Informatica= data management
Salesforce
Logpro = warehouse systems
Tagetik – perf management software

469245039.docx 6
Planned Delivery May 2016

Overlap between 1.0 & 2.0


- FICO

SAP APO - Advanced Planner and Optimizer is designed to help a company improve
production planning, pricing, scheduling, and product shipping.

469245039.docx 7