1. What Is the architecture of SAP ? What is the difference between R2 and R3?

Ans: In SAP R/3 means three tier architecture and is

1. DATA BASE LAYER

2. APPLICATION LAYER
3. PRESENTATION LAYER

R/2 has two layers

1. Data base layer

2. Presentation Layer

The Main difference between R/3 and R/ 2 is application Layer ( which act as a mediator between
data base layer and Presentation Layer and it acts as a traffic controller).

2. Tell me about End to End Implementation

Ans: SAP Project implementation done by ASAP Methodology (Accelerated SAP)

The road map of ASAP methodology has five phases of Implementation

1. Project Preparation phase

2. Business Blue print phase
3. Realization
4. Final preparation
5. GO live and support

3. Briefly Explain each phase of Implementation

I. Project Preparation phase
1. Project Planning
2. Project PERT Chart (PERT: program evaluation and Review Technic)
3. Preparing Scope Document (Scope or SoW: Statement of Work).
4. Implementation of Project Standards.
5. Project team skill development
6. Formation of Steering committee

II. Business Blue Print

1. Preparation of QADB
2. BBP Workshop / Requirement gathering workshop
3. Preparation of AS IS Business process document (Non SAP or Legacy Business
process)
4. Preparation of TOBE document/Future State Business process (FSBP). Business
process in SAP
5. Identifying the GAP (GAP: Business processes not in Standard SAP)
 6. GAP fit Analysis ( Through RICEFW : Reports, Interfaces, conversions, Enhancements,
Forms, Workflow. By ABAP or Third party tools.
7. Blue Print Sign off
8. Level one Training – Screen, Training to Top Management)
9. Readiness with Development Server (LANDSCAPE)

III. Realization:
1. Base line Configuration
2. Preparation of Configuration documents
3. Unit testing
4. Integration testing
5. Preparation of User Manuals
6. Level 2 Training, Training to End-users for UAT testing
7. RICEFW development and testing
8. Readiness to Final Preparation (Readiness of Quality Server).
9. Transport Request to Quality.
10. Uploading Master and Legacy data in Quality
11. User acceptance test by User and Sign-off
12. Readiness with Production Server

IV. Final Preparation

1. Transport requests to Production.

2. Upload of Master data in Production server
3. Cutover Strategy and Upload of Legacy data in Production server
(Cutover Strategy: A cut-off date (a date before go live, based on quantum of data,
eg: 2 – 3 days) is given to take the closing stock of the legacy data (Eg. Open stocks,
Open PO’s etc.) and uploaded in Production server, client is advised to key Legacy
transactions between cut-off date and Go live in an Excel and then keyed in
production server after GO-Live).

V. GO Live and Support:

1. Live transactions in production
2. Cutover period: Legacy data uploading or keying in Production.
3. Support for issues and errors in Production.
4. Making End Users familiar to system and transactions.

4. Explain Landscape

SAP has typical 3 system Landscape

Landscape : arrangements and design of Servers is called Landscape

3 System or 3 Servers are

1. Development Server
2. Quality Server
 3. Production Server

Development Quality Server Production Server

Client
Final preparation
ABAP Master data
developments are uploads and
done here Cutover strategy
Golden Client for open items
UAT is done here upload
Functional
Configuration done Live and Day to
here day Transactions
Testing Client done here

Unit testing done Production

here Support
Develop Server Quality Server Production Server

Transaction code for Client copy: SCC1

Transaction code for Transport of the object: STMS (only Basis consultants do this)

5. How many types of Testing are there?

There are Mainly three types of Testing while implantation
a) Unit testing (UT)
b) Integration Testing (IT)
c) User Acceptance testing (UAT)

Unit testing: While we do configuration , each config object is tested, if it is working correctly is
called unit testing

Integration testing: Testing of data flow from one module to other module by running complete
cycle.

FI MM , MM:PP, MM:SD, MM.PM etc

User acceptance testing: It is done in Realization phase in Quality server, User will test all the
processes in SAP and give signoff then the objects to production.

6. What is Transport request: Transport request is a kind of container with collection of

changes that are made in the Development system. It also records the type of change, the
purpose of change, request category and the target system.
Each TR contains one or more change jobs also known as tasks. Tasks are stored inside a TR, just like
Multiple files stored in a folder

TRs are of 2 types

1. Customization request
2. Work Bench Request.

Customization request is a client dependent and client specific.

Work bench request is a client independent or cross client.

TR has to be released before Transporting to another server.

7. How the data is copied from One client to another client and Transported from one server to
other server?

Ans: The data is copied from one client to other client by client copy done in target system in T.Code
SCC1

One server to other server by STMS

8. What is data conversion?

Ans: Data conversion is the uploading data from Legacy system to SAP system Ex: Master Data,
Cutover data

9: What are the data Conversion tools?

Ans: Data conversion tools are LSMW, BAPI, BADI, BDC.

LSMW: Legacy system Migration Workbench.

BAPI: Business Application Programming Interface.

BADI: Business Add In

BDC: Batch Data Conversion.

10: What is a cutover strategy?

It is a strategy in migrating the open transactional data from Legacy system to SAP system at the
time of Go Live. Cutover strategy can be adopted to minimize the open orders during the transition
by giving a cut-off date and uploading the data as of cut-off date before go live, the Transactions of
legacy system between cut-off date and go live date are collected and keyed in SAP system after Go-
live

Examples of cutover data: Financial balances, open balances, Open P.Os, Open stocks.
11.Can we transfer the Number Ranges?

No. we cannot transfer the Number Ranges.

12.Explain Procurement Cycle?

The process of buying Material and obtaining services from Vendors, Dealers, Manufacturers is
called procurement.

The Important steps in procurement cycle are

Determination of requirements

Requisition

Purchase order

Goods Receipts/ Invoice Receipts

Invoice Verification, Vendor Payment.

Determination of Requirement: Procurement process is triggered when there is a requirement.

Requirements are generated either manually from a user department or automatically through MRP.
Requirements are generated in the form of purchase requisition.

PR is converted into Purchase order for regular purchases if a regular source or vendor exist.

If a regular source does not exist source determination process is initiated by sending RFQs to the
various suppliers. Vendor is selected by quotation process by comparing quotes of vendors. PO is
raised on selected vendor if the requirements are for short period. For long time requirements
CONTRACT or a SCHEDULING AGREEMENT is created.

Vendor supplies the material, Goods Receipt is done, stocks are updated, book of accounts are
updated, material valuation takes place.

Vendor submits the invoice for the material supplied.

A invoice verification is done by 3 way Match concept by comparing PO price, GR Quantity with
Vendor Invoice Qty and Price.

13: What is Account Determination?

Ans: Automatic Account Determination is the process of Automatically determining the correct GL to
post the value of the material.

14.What are the Account Modifiers?

Ans: Account Modifier is also called as General Modifier. GL Postings is determined by general
modifiers to post to different GLs for Goods issue with different Movement Types. There are 3
General modifiers

GBB- Offset Inventory Posting

KON- Consignment posting

PRD- Price Difference.

14: What are the Special Procurements?

Ans:

1. Consignment
2. Subcontracting
3. Pipeline
4. Third Party
5. STO

15: At what Organization Levels Purchase Organization maintained?

Ans:

Enterprise or Client level

Company code level

Plant Level

16: At what Organization level the Material Master Data is maintained?

Ans:

Co.cd

Plant

Storage Location

Batch

17: What is the Maximum length allowed for the material master number and Material Description?

Ans: 18 characters for Number and 40 Character for Description.

18: What are the Control Functions of Material Master data? What it Controls?

Ans: Material Type - It Controls- Field Selection, No Ranges, Field Statuses

Industry Sector – It Controls- Screen Sequence.

19: Tables for Material Master?

MARA- General Material Data.

MARD- Storage Location Data.

MARC- Plant level Data

MCHB- Batch level data.

MAKT- Material Description

MBEW- Material Valuation

20: What are the control functions of Vendor Master and Tables?

Ans:

1 Vendor Account group

2 Purchase Organization

Tables for Vendor Master

LFA1- Vendor Master General Data

LFB1- Vendor Master Co.cd Data

LFM1- Vendor Master for Pur. Org data.

LFM2- Vendor Master Purchasing Data.

21: Examples of some Material types?

Ans:

ROH- Raw Material

FERT- Finished Goods.

HALB- Semi finished Goods

HAWA- Trading goods

VERP- Packaging material

DIEN- Services

PIPE- Pipeline material

LEIH- Returnable Transport packaging

HERS- Manufacturing Parts

HIBE- Operating Supplies

NLAG- Nonstock material

FHMI- Production Resource Tools

22: What is Info Record? How many types are there?

Latest Vendor price for material is maintained There are 4 types of Info Records

Standard

Subcontracting

Consignment

Pipeline
23: Tables for Info Record?

EINA- Info Record Main Data

EINE- Info Record Org. Data

KONH- Condition Header

KONP- Condition Item

24: What is Source List Table and PR Table?

Ans: Source List- EORD

PR Table- EBAN

25: