TYPES OF PROJECTS

PROJECT PREPARATION: -
 Communication tools-outlook, discussion rooms.
 System landscape- how many servers they need to decide.
 Team introduction- all teams introduction.
 Business Overview- will happen for 2 days where all the details they will tell are company
codes, plants, and what they have.
 Kick-of-meetings-All meetings start from here.
 Budgeting- how many are working and how many are traveling like that all will decide.
BUSINESS BLUEPRINT: -
 Requirement-gathering- consultants will collect all the business requirements to fit into
SAP. Ex-SD consultants will connect with SD Users. MM will connect with the MM user so
that we can collect all the business information.
 AS-IS & TO-BE study AS-IS will be explained by the business core users and we need to
explain to them that this process will work this way.
 GAPS-ABAP-RICEFW-REPORTS, INTERFACES, CONVERSIONS, ENHANCEMENTS, FORMS.
 NOTE THE BUSINESS BLUEPRINT WE DON’T NEED AN ABAPER HE WILL JOIN AT THE END OF
THE BUSINESS BLUEPRINT STAGE OR REALIZATION PHASE.
 Flat files for data migration- they will fill the data in the format you give. All
module consultants will give to the respective users.
Realization:-
 Baseline configurations will do all the configurations in the golden configure and then
move it to unit testing by using SCC1 and the client is 120 for golden configurations.
 Unit testing- Once you move the configurations, we will do the unit testing in client 140.
 GAPS- Once you come to GAPS the ABPER will come into the picture.
 Functional specification- a document where we have detailed requirement
deception and the salutation or the salutation LOGIC which are going to make.
 Technical specification- once you prepare a Functional specification the ABPER will
prepare the technical specification.
FINAL PREPARATION: -
 Move all changes to Quality- Once you test all the scenarios what are changes, we
have done in the unit testing that all realize to Quality by using TR.
 Collect flat files for data migration - Using LSMW or BDC will load the data into the
system.
 Integration testing is a type of software testing in which a software application's
different units, modules, or components are tested as a combined entity. Like FI,
MM, SD, and PP all come and test all the scenarios’ bases.
We will test by creating orderdeliverbilling then check whether the document
is posted into GL or not. Like that, we test all the scenarios.
 Final configuration- you are done with all the configuration if we miss anything in the
realization phase or do not work on any configuration then go back to development
and make that configuration move its quality and test it again as a final test.
 User manual/Training- in this, we will create a manual for all the processes like how
to create IN, QT, OR, DELIVERY, and BILLING, step by step.
 UAT- Now the user will do the user accept testing in the UAT.
 Cutover activity- The activity we need to do for the go-live preparation only.
 Note cutover activities will be done over -the weekend/holidays/business outage
just before going live. Because of the mismatch in the data that they have given.
 GOLIVE & HYPER CARE: -
Go live date-Mondays only.
Cutover activity: -
1. Move TR’S-1step in go-live and it will be done by the BASIC team move the TR’S.
2. Move the TRs by SEQUENCE order only because the ex-1st TR is v/08 and the 2nd TR
is OVKK, if we move the 2nd TR 1st then the v/08 will not be available so it will give
you an error so always we need to the TR’S by order only.
3. 1st workbench then only the basic team will send the TRs.
This TR and WB move all come under cutover activity.
Q- How did you transport the number ranges?
ANS- We are not transporting the number ranges we have to create them manually by
longlining each server. And the basic team will give you access to create it manually.
It will be issued at the audit level so we are not moving the TRS of number ranges.
Also with the calendar, we are not moving just we are creating manually in each server.

4. Smoke testing- just to see and come back without saving ex-go to create an order
and check all the fetching or not and come back without saving, like all screens
without saving.
After going live- the user will do all the work. And we will give HYPER CARE support for
1 month or 2 weeks.
5. We can not move LSMW from QTY to PROD by using TR’S we need to EXPORT from
QTY and save in a local file or a shared file and then go to the PROD server and
IMPORT THE FILE in LSMW T-code.

ROLLOUT PROJECTS: -

REGULATION TESTING- Testing existing functionality to check if there is any impact with the new changes.
 SUPPORT PROJECTS
Support
Production Support (PS)
Application Maintenance Service (AMS)
Application Maintenance Contract (AMC)
Production Maintenance (PM)

Q- Why do we need to give support in production?

A- There are lots of errors, issues, problems, and bug fixing while we are in the Live projects.

Tickets
Incidents Change Requests (CRs)
The existing design worked fine just
before but not working now A new Business Request
Issues Change Request
Bugfix Request
Problems New Request
Errors New Requirement
Charge for it

Data error or a process error

Fix it in the Production system
In 95% of cases there is a TR
Invoice not posting to accounting Incident Not a CR
VL01N is not working Incident Not a CR
Upload price master data for 1 lak
records Not an Incident It’s a CR
Change payment terms for 1,000
customers Not an Incident It’s a CR
New Sales office Not an Incident It’s a CR
New shipping point with
determination Not an Incident It’s a CR
Output is not triggered in the order Incident It’s a CR
FFID- FIRE FITER ID the basic team provides you to log in to the production system. If we are unable to
resolve the ticket then once the basic team is then we can log into the system but it will record everything
when we log in with FFID.

what if you are unable to solve the issue?

ANS- I will replicate it into the qty and try to resolve the issue for the invoice not posting then go qty and try
with the same customer and material and try to deliver an invoice once the issue is done inform the
customer and ask to do that same in the production.

Change request-No SLA

Q- How you are handling CRs?
A-We are handling emails and trackers with Excel.
Q-In The interviewer, if they ask how many clients.
We have 1 client on each server. development 1 client, quality 1 client, production 1 client.

Note TRs will move from QTY to PROD on Thursday only because after we move on this day if we find any
errors on Fridays, we can fix it on the weekend and reset the issue before Monday.

Upgradation projects-Migration projects