EBS Baseline Knowledge Transfer Document

Version No. 1

07-07-2015
 Vmware Inc

EBS Baseline Knowledge Transfer Document

Version No. 1

NAME SIGNATURE DATE COMPANY JOB

TITLE
Prepared By 07-07-2015 Apps QA
Lead
Reviewed By 07-09-2015 QA Lead
Approved By 07-09-2015 Delivery
Manager

VERSION HISTORY

Version Date Changed By Changes Made

No.
1 07-07- Created
2015
 Knowledge Transfer Document

Table of Contents

1. Introduction
2. Every task currently assigned
3. Every document we own or Contribute
4. Every system knowledge required
5. Every stakeholder We work with
6. Accesses and Credentials Required

1. Introduction

Objective

This document is intended to capture the understanding of the application gained by Baseline support team during
the Knowledge Acquisition phase. The objective is for Practice / Application support group Owners to assess the
understanding, comfort level and effectiveness of the Knowledge acquisition phase and decide the readiness of
proceeding to subsequent phases in the Knowledge acquisition phase gate review.

Project Intend

The purpose of the Baseline QA support Team is intended to provide full support to the Production support
Team and QA Team for the Baseline activities during the project release ,Q-end activities, hot fix releases and
the other changes through out the VMware system.

2. Every task currently assigned

1. Lead the EBS Team (includes EBS, Finance, Model N) both offshore and onsite.
2. Review the hot fix defects for all the releases, prepare the LOE,allocate the resources ,prepare the
target time for the completion of the RFCs.
3. Synchup with the Dev ,QA and Support Team on the progress of the defects.
4. Quarter end activities.
5. Baseline regression activities for all the integrated and hot fix releases.
6. On hand support on working on adhoc requests during PST hours.
7. On hand support on coordinating and working on the small timeline projects from management.
8. Regression impact analysis for all the releases and help in preparing the test strategy.
9. Production support for all the releases and post releases.
10. Attend KTs for the new projects handed over to baseline Team.
3. Every document we own or Contribute
1. Baseline Regression test cases.
2. EDI payloads and documents.
3. EBS Business process documents.
4. Proof of testing details.
5. Test strategy.

4. Every system knowledge required

1. EBS end to end process.
2. EBS backend knowledge.
3. ModelN process .
4. SFDC basic process knowledge.
5. EDI.
6. Portals basic knowledge.
7. CMT and ppm knowledge.

5. Every stakeholder we work with

1. Baseline QA Team (Manual and Automation Team).
2. Baseline Development Team.
3. Support Team.
4. Business Analyst for the business processes.
5. Project QA Team for the project details.

6. Accesses and Credentials Required

1. EBS production access for all the releases.
VM Customer Setup – US
VM OM Manager – US
VM Service Contracts Manager – US
Install Base Inquiry.
2. PPM access.
3. EBS test instance credentials.
4. SFDC test instance credentials.
5. ModelN test instance credentials.
6. Oracle database Appsrdonly credentials.
7. Vmshare access.