Академический Документы
Профессиональный Документы
Культура Документы
I. Implementation
II. Support
III. Upgrade
IV. Rollout
Implementation
Shifting from non SAP to SAP, Shifting from Legacy system to SAP System
Duration: 6 to 24 months
Support
Post Implementation support
Upgrade
Upgrading lower version to high version, upgrading every 4 th year renewal
Ex: ECC 4.7 to ECC 6.0 Ehp 8
Duration: 3 – 6 months
Functional Upgrade: New requirement, new features to be add
Technical upgrade: software upgrade
Rollout
Rolling out the solution from one country to another countries
Duration: 3 months
Legal statutory requirements, currency, time, language, local business process.
Country specifies are difference
1. Project Preparation - 4M
2. Business Blue Print - 6M
3. Realization - 6M
4. Final Preparation - 4M
5. Go live / Support - 4M
PHASE - I
Project Preparation
1. Project Introduction
2. Project Vision / Mission
3. Project Logo / Name
4. Project Objectives
5. Project Success Indicators
6. Project Scope
7. Partner Scope of work
8. Project Implementation Strategy
9. Client Deployment Strategy
10. SAP Configuration Standards
11. Testing Standards and Strategy
12. Training Methodology
13. Project Plan
14. Project Deliverables
15. Resource Planning and Allocation
16. Critical success factors
17. Finalization of Organization structure
18. Releasing of Project templates
19. Formation of steering commit
20. Signoff and Charter Approval
1. Project Introduction
Provided by: WIPRO and ITC
Brief of introduction about WIPRO Team & ITC Team
Conducting “Kick Off Meeting”
4. Project Objectives
Provided by: ITC
By Implementing SAP in ITC
- Increase Revenue by 10%
- Reduction in Production Shortage (100% shock available in market)
- Error Free Financial Statement, Ex: P&L, Balance sheet, Salaries etc.
- Credit Management
- High & Fast performing systems – Improve office productivity
- Optimal Stock maintenance
6. Project Scope
Provided by: WIPRO
We will decide which module can implement or not, based on client requirement.
- Geographical Scope: Plant wise which module is required which is not required.
- Module Scope: Concepts only which is required, ex: SD, MM, FI, CO, HR, BASIC, ABAP etc.
- Technical Scope: Installation of Software components, SAP Backup
Ex:
ECC – 10 – Development servers - 200
SMN – 05 – Solution manager - 111
ECQ – 11 – Quality servers - 300
ECP – 15 – Production servers - 400
CEO/Chairman
VP
CIO
Zonal Head-SD Zonal Head-FI Zonal Head-HR Zonal Head-MM Zonal Head-PP
Mr. Mr. Mr. Mr. Mr.
Super/Pow User Super/Pow User Super/Pow User Super/Pow User Super/Pow User
Mr. Mr. Mr. Mr. Mr.
End User End User End User End User End User
Mr. Mr. Mr. Mr. Mr.
Organization Structure of WIPRO (Implementation Partner)
CEO/Chairman
Mr.
VP
M.r
CIO
Mr.
SAP Del.Mgr
Mr. RamaKrishna
SAP Program.Mgr
Steering Committee
Mr.
Core Team-SDSr Core Team-FI Core Team-HR Core Team-MM Core Team-PP
Mr. Mr. Mr. Mr. Mr.
Associated Con. Associated Con. Associated Con. Associated Con. Associated Con.
Mr. Mr. Mr. Mr. Mr.
Jr. Consultant Jr. Consultant Jr. Consultant Jr. Consultant Jr. Consultant
Mr. Mr. Mr. Mr. Mr.
18. Releasing of Project templates
Provided by: ITC – Core team
We will finalize templates and schedule it to release the templates (empty format) to Clients.
Ex: ‘AS - IS’ template to collect the Current Business Process.
Also called CSBP – Current State Business Process. The document is consist of
- Current Business process in legacy system
- Pain point in Legacy System
- Current Reports and Future Expected Reports (with screen shots, hardcopies etc.)
Steering Committee
CIO CIO
Mr. Mr.
SAP Program.Mgr
SAP Proj. Mgr. Mr.
Mr.
- AS – IS documentation
- TO – BE documentation
- GAP – Documentation
- Functional Specifications
- Technical Specifications
- PPT – Presentation preparation
- WRICEF – Work Flows, Reports, Interface, Conversions, Enhancements, Forms
- Finalizing of Organization Structure in SAP – 15 to 20 days
- Finalizing of Integration process
PPT – Consist of all details Requirement, Scope, Business Benefits , Time, Budget Required etc…
Proposal submit to Steering Committee, if approved will move further. If not approved it is GAP.
WRICEF
WORK FLOW: work flowing from one person to other person or One department to other
department.
Ex: Leave Approval, Vendor payment, Credit Management
REPORTS: Output
INTERFACE: Interface or connectivity between NON-SAP to SAP or any other devices etc. done by
ABAPER.
ENHANCEMENT: Adding new field in existing screen, adding new screen to the existing process etc.
is called ENHANCEMENT.
Input:
Process:
Step Process Remarks
Output:
Reports:
Sno Name of the Report Type of Report Description Priority
H – High
M – Medium
L – Low
C – Critical
N – Not Critical (for Go-Live)
Solution types:
A – ABAP Development
D – Direct
E – Enhancement
G – GAP
W – Workaround
Ex – External Process
Standard Analysis
Project Scope:
ECC 6.0
EHP 4
CRM 7.0
BI / BO 7.0
ECC 6.0
CRM 7.0
1. Data Upload
2. End user Training (to Core Team)
3. Authorization Matrix
4. User Acceptance Test (UAT)
5. Cut over Strategy
Data Upload
It upload all master data, Data uploading using by two methods:
1. Legacy System Migration Work Bench (LSMW)
2. Batch Data Conversion Program (BDC)
LSMW: When master data a first time (initial) loading into SAP System is required LSMW process. It
is 14 step process given by SAP.
BDC: Is not a standard program, program will change base requirement. ABAPER will write the
program. It is used to upload
- Small data
- Error data
- Delta data
- Missing data
- Transactional data from source file (XLS etc.) to SAP
Server: Production
Legacy SAP
Client: 100
System System
After LSMW over we do BDC for Missing data, error, small data etc. Functional Consultant will
prepared in XLS format with SAP Fields and give to client to upload the data as per format.
Along with XLS format, Functional Consultant will prepare Functional Specification document and
hand over to technical consultant to write BDC Program.
Technical Consultant will write the BDC Program and he will prepare Technical Specification
document.
BDC Program will executed by FC with TCODE: SE37, Ex.: Program: ZSDERDATA
End user Training (to Core Team)
Train a Trainer
Duration: 15 days
Jr. Consultant Roles
- Prepare training material, end user manual
- Training Schedule: time line of training date & time
- Training: Actual training start
- Evaluation: check whether end user doing right process or not
Authorization Matrix
We will prepare authorization to particular person or department wise, which screen can access,
which screen should not access is authorization.
Jr. Consultant will prepare XLS format with field of TCODE of their module wise.
That XLS file will give to Core team to fill the data Responsible person name, Role. Based on XLS file
Basis, Core team, Jr. consultant will create the Authorization of transactions.
Testing will done after Authorization Matrix is over with user name & password.
Cutover Activities:
1. Identifying Open Items
2. Preparing FS as per SAP fields to write BDC Program (Jr. con)
3. Writing BDC program (ABAPER)
4. Executing BDC Program (Jr. Cons)
5. Scheduling cutover time / period
6. Test the transactional data as per legacy system check
Go live is date …. Starting using SAP system at client premises, stopping legacy system officially.
First Transaction Code enter by who is inagrating SAP System.
KT – Knowledge Transfer
All documents till now what we prepared we have to handover to client. For future references, in
case support project who ay going to do support project in future this will help them.
11. Which ODC are you working from (offshore client center ODC-Offshore Development Center)
53. Who will do Unit Testing? Jr. Consultant & Testing partners
61. How do you transport request move from your development server to other servers?
65. Have you done any testing tell me testing procedure & what are the test types used in your
project?
71. Have you prepared user education documents? NO (only IDES SAP)
80. What is hyper Care? Post GO LIVE support period is called Hyper Care
82. What are all the FS Documents created so for? FS-Reports, FS-Forms, FS for output
determination: Collect sample formats of output from Core team
FS- for cutover strategy: Identify the open items prepare the FS as per the SAP fields for
Transactional Data to ABAPER to write BDC Program.
SUPPORT PROJECT
Ticket = INCEDENT (in TSRM) end user / Help desk will create issue in TSRM
Ex:
Pricing in sales order – SD - IN232401
Error in Salary - HR - IN232402
Plant error in PO - MM - IN232403
Posting error in GL - FI - IN232404
Very slow SYSTEMS - BASIS – IN232405
Status of Incidents:
- Open
- Assigned
- In progress
- SLA HOLD
- SLA Resolved
- SLA Closed
Module wise or
End user raises the issue Jr. Con will dispatch toProcess wise
Individual Pickup or TL will assign
Development Cycle
Priority / Severity
Priority 1 – 15 m - 4 hrs
Priority 2 – 4 hrs - 8 hrs
Priority 3 – 16 hrs - 32 hrs
Priority 4 – 24 hrs - 48 hrs
Acknowledge SLA: The maximum time limit given to acknowledge the ticket is Acknowledge SLA.
Resolution SLA: The maximum time limit given to resolve the issue.
What is SLA?
Ans.: Service Level Agreement
What is your SLA?
Ans.: 96%
What is your Team SLA
Ans.: 98%
What is your Project SLA?
Ans.: 98%
Definition of Priority:
Login: SDSS004
Password: xxxxxx
Log: day to day work details what we did, how did collect the information etc., we need to update
every day morning or evening. Working log / Communication Log
Affected Person Ticket History: with the above issue, who are all affected employees list we can see.
Third party data: If the issue with the legacy system or third party ex: scanner, printer etc.
We need to reaise a ticket to third party, update the ticket no. also update the STATUS: SLA HOLD
Warm Handover: One shift to other shift handling over the ticket. We need to mention details in
LOG tab.
CHANGE REQUEST (CR)
Development Cycle
- CCB-Change Control Board is management from both sides ITC and TCS. Once approve only we
move to Development Cycle.
- Test will be done Development Server with Testing client (220) and Integration Testing in Quality
with client (300).
- Each CR will have FS, TS, Test Suite/case/script etc.
CQ – CLEAR QUEST
TRAINING
Must ATTEND 80 hrs. online training and 8 days class room training in TCS per year.
You must GIVE 40 hrs. online training and 4 days class room training in TCS per year.
ATTENDING - MEETING
SDM – Service Delivery Meeting
We need to check every day morning any issue in Batch jobs by go TCODE : SM37
Red color - error
Yellow color – Processing
Green – Success
SOLUTION MANAGER:
Solution Manager manage Solution given by SAP.
We used this software in implementation & Support projects.
It is free from SAP & IDES Version along with Commercial Version
30. What is Batch job monitoring? Can you explain any one batch job?
31. Scheduling any job work / process automatically by the system is called Batch jobs.
Batch job will run by BDC Program written by ABAPER.
Ex.:
1. Sales Order Confirmation has to sent by email every day night after 9 pm.
2. Dispatch intimation has to send by email every day night after 11 pm.
3. Original Invoice copy should print every day night at 6 am. Etc.
Q. While doing return delivery system will propose PGR. Where is the control?
document category is “T” then while creating delivery system propose post goods receive (PGR).
Q. While creating default W/O order reference how system is determining movement type
information?
System consider default order type ‘DL’ whenever order required field is “Not sales order required”
i.e. for LO and NL. System consider default order type “DL” to determine movement type while
doing PGI.
Q. My user is increasing the quantities in delivery document more than order quantity, i want to
restrict that. Where is the control?
Ans. - Check over delivery– maintains “B”, but also check over delivery tolerance or unlimited
tolerance in customer shipping point.
Q. Where is the control when you create return invoice the accounting entry is
Revenue A/c.....Dr.
To, Customer A/c....Cr.
Ans.- SD Document category – “O” – Credit memo
Q. Where is the control that when we create proforma invoice and there is no accounting entry?
Ans. SD document category – “U”.
Q: When you create Credit invoice system generate what is the accounting document and the
accounting entry?
Ans.: Customer A/c.......Dr
To, Revenue A/c.....Cr.
Q. Any condition table if you save it in local object then how to get it back into request?
Ans. Go to change mode of condition table [V/04] click on go to object directly entry mention the
package number save it.
Q. Can i have two base price condition types active in a single sales document? Where is the control?
Ans. No – condition class [B].
Q. Client requirement is, there is a condition type which is manual which user enters manually into
sales document but after entering condition type. System should not allow to change the amount or
value. Where is thecontrol?
Ans. [ ] amount and [ ] value in particular condition type.