SAP-SD (SALES & Distribution)

1.Arictitecture of SAP:-

The SAP runs under the architecture of R/3. R/3----> means Real Time Three Tier Architecture

Application Layer
[]User 1

[]User2

[] User3 Data Base

 User system are also called as Presentation Layers(PL).

 what the end users requesting is taken by Application Layer (AL).
 Application Layer sends the request to Database (DB).
 This process is called R/3 Architecture.

Application Layer in the mediator between Presentation Layer and database, which takes all the request
from PL and deliver back the requested need to the respective PL in a sequence manner receives from
the database. Before to R/3 architecture took market, R/2 was used. R/2 in real time two type
architecture, In R/2 there was no application Layer. Only presentation layer and database layer. in this
scenario, all the clients are directly accessing to data base layer as a result system faces frequently
breakdowns and very low performance issues.

LANDSCAPE IN SAP

A landscape is a arrangements of servers. An client wants to implement sap, then they have to purchase
servers. Sap suggests to go for 3 servers.

Development Quality Production

Server Server Server

By T.N. Kumar
 MODULES IN SAP

(i) Functional modules:- (ii) Technical Modules:-

SD - Sales & Distribution ABAP,

FI- Financial BASIS,BI, BO, etc.,
Co- Controlling
MM-Material Management
PP-Production Planning
QM-Quality Management
HR- Human Resource
CRM- Customer Relationship Management..etc.,

As a functional consultant we first study client business process and then we configuration the client
business process into sap. Sap is a package which is already provided is standard configuration. As a
consultant we need to use the standard configurations and do the necessary changes as per the client
requirements. As a consultant we can be placed as either into implementation project or support project.

--> Implementation Project:- configuration the client business process newly into sap who will be using
some legacy system. Legacy system means -Non SAP.

--> Support Project:- handling the issues raised by the clients who already implement SAP.

=======================================================================================

IMPLEMENTATION PROCESS

 Roles and responsibility of a consultant in implementation project:-

Every implementation partners will have BDM's (business development managers). Firstly BDM's will
meet the clients who are not yet implemented sap and tries to convince the client, if the client is
convinced then client will ask for quotation. Then implementation partners will send the pre sales team
to client location, to do the basic study. After submitting the basic study, implementation partners will
prepare quotation and send it to the client place. If the client is satisfied with the quotation than client
will place an order for implementing SAP. Whenever implementation partners receives the order from
client to implement sap then they start the methodology called ASAP-methodology.

"ASAP" stands for --> Accelerated SAP. ASAP methodology consists of the guidelines to implement SAP.
That is step by step process of implementing SAP.

ASAP consists of 5 phases:-

1) Project Preparation
2) Business Blue Print
3) Realization
4) Final Preparation
5) Go lives & Support

By T.N. Kumar
 (1) PROJECT PREPARATION ( First Phase)

In the Project Preparation phase only the management from the implementation partners and the
management from the client will be involved.

IMPLEMENTATION PARTNERS CLIENT:-

BDM's- Business development managers VPIT- Vice president IT,
DH- Develop managers VP- Vice President,
PM- Project Managers PM- Project manager
TE- Technical Expert
TH- Technical Head

"As a consultant we do not involve in project preparation phase ,we involve from business blue print
phase".

(a) User License:- Any client wants to implement SAP ,they have to purchase License from SAP based on
number of end users. they decide on how many user licensed to be purchased from SAP. End user:- He
is the employee of the client who will do day to day transaction in SAP. Each user license cost
approximately 80,000/- And the client has to pay this amount to SAP to get the license.

Ex:- Suppose Client is - Asian Paints India Ltd.,

Head Office
500 end users

Plant-1 Plant-3
Plant-2
300 Users 200 Users
200 Users

Sales office-200 users

NOTE:- AMC- ANNUAL MAINTAINCE CONTRACT. client has to 22% of license cost to sap as AMC every
year.

By T.N. Kumar
(B) LANDSCAPE:-
 Landscape is a arrangement of servers. Any client if they want to implement SAP they have to
purchase servers.
 SAP suggest to purchase 3 servers. The servers are Development ,Quantity, Production
 Development server will be used to configure the client business process into SAP. It will be
consultant
 Quantity server will be used to test the scenario. Quantity server will be used by consultant and
core users. (NOTE:- Core users are the employers of the client who will be having good experience
and exposure in client business process EX:- GM, Sr.GM, etc)
 Production Server will be used for day to day live transaction in SAP. ( NOTE:- It will be used by
end Users/Users, etc).
 As a Consultant we do not have access to production server and user don't have access to
Development server.

1) How many servers to be Purchased?

Ans:- Normally SAP Suggest to buy 3 servers (Development, Quantity , Production). But few clients can
obtain for 2 servers (Development & Production) depending on their budget. Normally a server ranges
more than 50 lacks.

2) Where to Purchase the Server and who are the vendors?

Ans:- In the market IBM,DEL,HP,CISCO will supply the servers ,the client will do the negotiations with
these vendors and finally places order to one vendor and vendor supplies the server.

(C) INFRASTRUCTURE:- The number of new pc's will be purchased based on number of the user license.

Ex:- suppose client having 900 pc's but client has taken user license of 1500, so client has to take more
600 pc's. The server environment:-

 They decide where to keep the servers i.e. Head office or any plant.
 They maintain temperature requirements.
 They maintain security in server room and the VP-IT and technical experts have the authority
with password ,access cards ,etc,
 They decide on the server connectivity i.e. VPN. VPN- virtual private network.

D) IMPLEMENTATION PARTNERS:-
Implementation partners will list out all the consultants who are going to involve in this project.
Normally to a unknown client the team size is 15 consultants including in both technical and functional
consultant. Normally to a known client or MNC companies the team size is 50 consultant including both
technical and functional consultant. On the other side client will list out all the core -users who are
going to involve in this project. The client will choose one core user from each department here the
role of core uses in the implementation project is to share the client business process to consultant.

By T.N. Kumar
E) CONSULTANT FACILITIES:-

If it is domestic implementation project then all consultant will go to client place to implement sap. If it
is foreign client then from each module one consultant will go to client place and remaining people
works from off-shore. (note:- "off shore =implementation partner location). The normally project tenure
for implementing sap to domestic is 8 months. The normally project tenure for implementing sap to
MNC client in 13 months. When all the consultant are moving to client place for a period of 8 months
than client takes care for food expenses ,local travelling expenses, accommodations, work environments
and laptops.

F) GO - LIVE DATE:-

It is the data on which we handover the sap to client i.e. From the data onwards the client will start
using sap. After project preparation the management of implementation partners will come back to
office and conduct "KICK OFF" meeting. (kick off is nothing but starting off). Whenever we get a new
project management will conduct kick off meeting. In the kick off the meeting management will invite all
the consultants who are going to involve in the implementation project.

Features of kick off meeting:-

 Introduction about client and business
 Rules and regulations of the client
 Rules and Responsabilites of consultant
 Share of the core user information to consultant
 Share the go live days .
 Starting date of project

after kick off meeting all the consultant moves to client place for implementing SAP. when all the
consultant moves to client place than we start the 2nd phase of ASAP methodology i.e. BBP.

NOTE:- Activates In Project Preparation Phase:

1. User License
2. Landscape
3.Infrasturture
4.Implementation Partners.
5.Consultant facilities.
6.Go Live Date

By T.N. Kumar
 2) BUSINESS BLUE PRINT PHASE

As a consultant we involve from business blue print ( BBP) phase. The 1st day of implementation project
(client visit ) will have introduction with core users and they will take us for plant visit.

Activates:-
 REQUIREMENTS GATHERING :-we do requirement gathering based on the questioner provided by
the implementation partners. Every day we go to core user place as the time scheduled by the client. ex.
10 am -3 pm. Every day we have to ask the question in a sequence and whet ever core user
explains ,just note it downs as it is. Every day after completion of requirements gathering we come back
to our work place and prepare "As- Is " document. As- Is document consists of the present business
process of the client whatever core user explains. The requirements gathering activates we do almost
for 2 months

 BUSSINESS BLUE PRINT:-

After the completion requirement gathering we prepare business blue print document, we also call it as"
BBP "document. BBP document consists of As- Is & To-Be. To-Be document consists of the present
business process of the client and how is going to be in SAP. While preparing To-Be document we may
find some gaps.
GAPS:- any business process of the client if there is no solution from sap then we call it is Gap.
Whenever we find gap we prepare GAP-ANALYSIS DOCUMENT.

 BBP SIGN OFF: After completion of BBP document, we will send this document to core user for "sign off".
 After preparing BBP document we will send a mail to core user and cc to all (all project mangers of
implementation partners and client ) for core user conformation. Core user has to go through the
document ,if he find any changes he will send it back.
 Then we need to prepare one more version if the document and has to be sent to the core user
again. When everything is fine , core -user will send a conformation mail to consultant .
 After getting the conformation mail we take the sign off from the core user and takes the signature
on it. After taking the signature, one copy we submit to implementation partner and one copy we
submit to client. Without BBP sign off we are not suppose to move to the next phase of ASAP
methodology.
 The BBP documentation and BBP signs off documentation takes another 1 1/2 months process.
 The most critical phase of ASAP methodology is BBP, because the success of the project is totally
dependent on how accurate we gather the requirements from core users.
 In BBP phase we prepare 2 documents:- 1) BBP DOCUMENT & 2) GAP ANALYSIS DOCUMENT.

After completion of BBP SIGN OFF we will move to the next Phase of ASAP Methodology.
NOTE:- Activates In Business Blue Print Phase:-
1) Requirements Gathering As-Is
2) Business Blue Print - As-Is ,To-Be, GAP ANALYSIS

By T.N. Kumar
 3) Business Blue Print SIGN OFF -final documentation.
3) REALIZATION ( 3rd PHASE)

In this phase, configuration to be processed into SAP or mapping the client To-Be business to process
into SAP. In the realization phase we enter into development sever. Configuration will be classified into 2
types.

1.Base line configuration. 2. Final configuration

1. Base Line Configuration:- It is the configurations which is specific to one module for which no need to
depend on other module consultants.
2. Final Configuration:- It is the configuration for which we have to depend on the other module
consultants which we cannot do on our own.
 First we complete baseline configuration then we go for final configurations.
 Whenever we are doing configuration in development sever while saving system will ask for request
no.
 The request number will help to transport the configuration from one sever to another server .
 Transport request number into two types. 1) work bench request 2) customizing request
work bench request:- what all ABAPer will do that will be stored in work bench request.
Customizing request:-what all functions consultants will do that will be stored in customizing request.
All work bench request are cross client.

 Cross Client:-
 Cross client means if we do any configuration is one client automatically updates in other clients
with in a server.
 Normally a development server is divided into 3 cross client servers.
 They are sand box, configuration ,internal testing ,cross or technical testing.
 Sandbox server is used for practice (i.e. R&D purpose).
Configuration server is used for configuration purpose.
 Internal testing server or technical testing server is used for internal testing for functional
consultants and testing server for technical consultant.
 In case of ABAPers do any configuration is one cross client server it automatically updates in other
clients with in server.
 But in functional consultant we have to more the configurations manually form one cross client to
another.
 Consultant roles in transportation request:-
 First we release all the transport request and put in excel file and send this excel file to basis
consultant.
 Basis consultant will transport all the request from one server to another server.
 Each request consists of parent request and child request.
 Parent request will help to transport the configuration from one server to anther server.
 Child request will help to carry the configuration data from server to anther server.

By T.N. Kumar
  After implementing the configuration we will ask basis consultant to transport all the request
from development server to quality server.
 In quality server we start internal testing.

Here first we have to prepare test case document test scenario's document in test case document (test
scenario document ) if consists of:-
 What to test
 How to test
 Expected results
 Actual results
 Status
 Tested document number

Testing is of two types which are done is quality server, they are 1.Unit testing 2. Integration testing
 Unit testing:- it is testing specified to one module for which no need to depend on other module
consultant.
 Integration testing:- it is a testing for which we have to depend on other module consultant
after completion of the testing we prepare user - manual document.
 User-manual document: User manual document is a guidelines to end user. this document consists
of step by steps process of creating master data , and transaction data along with the screen shorts.
Then we prepare configuration document.

 Configuration document:-it consists of all the configuration made for the client along with the
screen shorts configuration help for KT purpose (knowledge transfer).
 In realization phase we prepare functional specification document (F.S.)
 Whenever we require the help of ABAPers we have to prepare functional specification document
and send it to ABAPers. The total phase for realization is 2 1/2 months.

After completion of documents we will move to the next phase of ASAP methodology.
Notes:-
1) Baseline configuration and final configuration.
2) Works bench request and customizing request.
3) Cross -client-sandbox, configuration, internal testing/technical testing
4) Transportation request-parent request, child request
5) Test case document/test scenario
6) User manual document
7) Configuration document
8) Functional specification document
9) Testing - unit testing, integration testing

By T.N. Kumar
 4. FINAL PREPARATION (Fourth Phase)

a) We give training to core- users:- we give training to core users and normally it takes 15-20 days and
after that he has to give the training to end users.

b) USER TESTING:-we ask core users to test the scenario's core user will test all the scenarios. If everything
is fine than he will give UAT-sign off document.(UAT-sign off-user acceptance test sign off). After getting
UAT signs off we transport all the request in quality server.

c) After transporting the request to production server than we start "cut-over activities". cut over
activities means uploading of master data and open transaction data from legacy to SAP. Ex:-Customer
Master, Material Master, Condition Master, etc.,

d) consultant role in cut over activities:- First consultant has to do recording and simultaneously prepare
excel sheet and this recording to ABAPer and send this excel file to core -user. Basing on recording
ABAPer will develop BDC (batch data communication) and give it to consultant . Core-user will fill the
data in excel and give if it consultant. Consultant will go to quantity server and do nock run, if everything
is fine consultant will go to production server and upload the data from legacy to sap.

e) Cut over strategy:- when we are actually planning to upload the data from legacy to sap . we request
client to stop the business to avoid data discrepancies.

f) Cut over period:- It is actually time taken to upload the data from Legacy to SAP. Normally it takes 2.3
days. After Uploading the data from Legacy to sap we move to the next phase if ASAP methodology in Go
Lives & Support, the time from for final preparation is 2 Months.

NOTE:- Activates In FINAL PREPARATION :-( 2 Months)

1) we giving training to server to core user.
2) user testing - UAT sign off
3) cut over activities -customer master, material master, condition master, etc.,
4) consultant role in cut over activities-batch communication mock run
5) cut -over strategy. cut-over period 2-3 days.

5.GO LIVE AND SUPPORT ( fifth phase)

Handing over SAP to Client from that data onwards client will start using SAP

After implementation and GO live we give 3 months of Post Production Support.

By T.N. Kumar
SUPPORT Project Process:

Handling the issues raised by the client who already implemented SAP.

Client
Implementation
Partner Support
Partner

After Implementation Client has option to give Support Contract to existing Implementation partner or
with new Support Partners. Whenever Support Partner gets a new support project both the client and
support partner has to enter into an agreement called SLA (Service level agreement) Is a Consultant we
should know some information of SLA.

Few information about SLA are:-

1) Priority of Issues: Generally the issues are Classified into 3 types,

 Height Priority --> Should be Solved with in 4 hrs

 Medium Priority --> Should be solved with in 24 hr
 Low Priority--> Should be Solved with in 48 hrs

If any issue is stopping the client business process than we treat if as high priority issue.

2) Change Request:-

--> Anything client is asking for which if there no present configuration than we treat it as change
request.

--> Whenever we get change request we have to prepare change request document.

Change request document consists:-

 Issue Details
 Expected Solutions
 Estimated Efforts
 Functional Man days - 20 days
 Technical Man Days- 12 days

--> After Preparing Change Request Document we need to send it to our Superior for review. After review
we will send this document to core -user for approval .After approval we will Start Working on the issues.

By T.N. Kumar
--> In the supports Project also management will conduct KICK OFF meeting. Size of the team will be 12
no's.(SD -2no's)

--> In the KICK OFF MEETING :-

1.Gives the introduction about the client &its business .

2.Rules and Regulations of Client.
3.Rules and Responsibility of Consultant of Consultant
4.core User information
5.Starting Data
--> After KICK off meeting all the Consultant will move to Client place for KT Process ( Knowledge Transfer )

K.T Process:- core -user will hand over Configuration document to consultants and consultant has to go
through the document and simultaneously do the system study . After System Study Consultant has to
prepare understanding the document and give Reverse K.T to core users After Reverse -KT Consultant will
come back and start handling the issues'

Ticketing Process:-

 When end user faces any problem raises on issue Which is called Ticketing issue.
 End user raises the issue to help desk.
 At the help desk core user receives the issues.
 The core user tries to solve the issues first if he is not able solve than he raises the issue in
ticketing.
 In the ticketing Tool Core user raises the issues and with Priority as high ,medium or low.
 There are different types of ticketing Tools ,they are
 REMEDY
 PERIGRIN
 GFS
 CETRIX
 SOLUTION MANAGER

 The support consultant coordinator receives the mails from ticketing tools with priority.
 The coordinator Analysis and Allocates the issues to respective consultant modules.
 The consultant receives the mail and replies to core user, end user and coordinator(cc).
 The Consultant has to replay with in 15 mins with acc knowledge mail to core user ,end- user, and
cc to coordinator.
 The status of Issues are as follows:-
 Open
 Being process
 Waiting for information
 Waiting for conformation
 Closed

By T.N. Kumar
 If the status is BEGING PROCESS than only the time starts
 If the status is other than BEGING PROCESS than the time stops
 After sending the acknowledgment consultants has to analysis the ticket issue
 In support we will have pre-production sever
 pre-production sever is a mirror image of production sever (we also call it has staging server)
 we tries to do the save what end user is doing if in production server
 If the end user is getting error in production server then we should also get the same error in pre-
production server
 After getting error we go to the development server ,and do the necessary configurations,
 Than we transport from development to quality server and ask the core user to test it and confirm.
 After confirmation we will transport the configuration from quality server to production server
 After transporting configuration to production server we will put the status as closed

LEVELS IN SUPPORT TEAM:-

Generally the level in the supports we will be classified in 3 levels i.e. level-1 level- 2 level- 3

 Level-1 --> High Priority Issues

 Level-2--> Medium & Low Priority
 Level-3--> Change Request& Enhancement(>5+exp)

We have level If our team size is more than 50 no's.

By T.N. Kumar