Roles in SAP

- End User Role

- Consultant Role (Functional & Technical Consultant)

SAP is an ERP (Enterprise Resource Planning)

- HR
- Sales & Marketing
- Finance
- Procurement
- Warehouse / Inventory
- Logistic / Supply Chain
- Production Planning

- BI / BW (Reporting)

- ABAP / Coding
- Basis (System Setup, Networking, Connectivity)

End User (are someone who may not necessarily understand How SAP works and have no
knowledge of what technical team can do)

Functional Consultant (are someone who understands business process / terminology, they
also know how SAP works, they know what technical team can do but don’t know how to do
technical work themselves) – Has the overall ownership of the delivery.

Technical Consultant (are someone who doesn’t understand business process / terminology,
but they know how SAP works, they know technical details and can change the core by coding)

Techno-Functional (It’s a combination of Functional & Technical consultant, someone who

understand business process, who also knows how SAP works, who know how to do technical
changes in SAP as well)

Testing Consultant (They know how SAP application works, should understand how business
processes work, don’t need to know how to make Functional and Technical changes) – Performs task
as if an end user.
 Types Projects

- Implementation (Fresh end to end project)

- Roll-out (Extending the existing functionality for a new Site keeping in mind the local
difference)
- Support (AMS – Application Management Support, continue supporting user on their
existing SAP system)
 Incident Ticket – Issue Fixing
 Change Request – Small new change (Not considered as Roll-out)

SAP Landscape

Development System:

- You do all your new changes in Development system

- You perform Unit Test in development system
- New changes usually create a TR (Transport Request) for the change
- Upon successfully unit test the TR is transported to Quality System
- Dev / Development system usually has very less data to perform testing

Quality System / Test System:

- You do not have change access in Quality system.

- You perform Integration & regression Testing in Quality / Test system
- Upon successful testing you move / Transport the TR to Production / Pre-Production (Pre-
Prod) system
- Quality system has more data for testing than Development system but less than Pre-Prod &
production system
- UAT (User Acceptance Testing) is performed by User in Quality system
Pre-Prod / Day in a Life System:

- You do not have change access in Pre-Prod system

- This is an optional system not many companies have this in their landscape
- This has more data to test than Quality & Development system but may have same or little
less data than production system

Production / Live system:

- This is the live system used by business to perform their daily task
- You do not have change access in Production system
- Being a Functional Consultant, you should never try to perform any test in Production
system

Transport Request

- Any change created in Development system generates a Transport Request (TR)

- The TR is transported from Development to Quality and then from Quality to Pre-Prod and /
or Production

Access Category

- Create
- Change
- Display

Roles & Authorization

1. End User
o Data Entry Access
 Quality (Create, Change & Display)
 Pre-Prod (Create, Change & Display)
 Prod (Create, Change & Display)
2. Functional Consultant
o Date Entry Access
 Development (Create, Change & Display)
 Quality (Create, Change & Display)
 Pre-Prod (Create, Change & Display)
 Prod (Display only)
o Configuration Access
 Development (Create, Change & Display)
 Quality (Display)
 Pre-Prod (Display)
 Prod (Display)
 3. Technical Consultant
o Date Entry Access
 Development (Create, Change & Display)
 Quality (Create, Change & Display)
 Pre-Prod (Create, Change & Display)
 Prod (Display only)

o Configuration Access
 Development (Create, Change & Display)
 Quality (Display)
 Pre-Prod (Display)
 Prod (Display)

o Coding Access
 Development (Create, Change, Display, Debugging)
 Quality (Display, Debugging)
 Pre-Prod (Display, Debugging)
 Prod (Display, Debugging)

4. Tester
o Date Entry Access
 Quality (Create, Change & Display)
 Pre-Prod (Create, Change & Display)
 Prod (Display only)

Types of Testing:

1. Unit Test
o Testing the change in Development
o Performed by Functional and / or Technical

2. Integration Testing
o Connecting process test (End to end cycle)
o Performed by Functional, Technical, Tester
o Testing done in Quality system
o Is done after Unit Test but before regression & UAT testing

3. Regression Testing
o Full system checks to know the change has not broken any other process
o Regression Test is mostly automated (whether automation regression testing is not
available Functional / tester should perform Positive & Negative testing for the
change)
o Testing done in Quality / Pre-Prod system
Positive Testing – To prove, where applicable, the change is working as expected

Negative Testing – To prove, where not-applicable, the change has not impacted the existing process

4. UAT (User Acceptance Testing)

o User performs the testing in Quality / Pre-Prod
o The testing is performed after successful Integration testing
o Where Regression Testing is automated, UAT is done before regression testing
o Where Regression Testing is manually done by Functional / Test Consultant, UAT is
done after regression testing.

Testing Sequence

1. Unit Test
2. Integration Test
3. Regression Test (Non-Automation)
4. UAT Test

Or

1. Unit Test
2. Integration Test
3. UAT Test
4. Regression Test (Automated)

Components of any Software

1. GUI
2. Security / Authorization
3. Master Data
4. Database (is a data storage system)
5. Application
6. Coding
7. Prints / Output Form
8. On premises / Cloud

Yellow – Important to Focus

Gray – Try to understand the basics

Important:

1. Never make changes on standard SAP Templates.

 2. If you need any change, ALWAYS copy the existing standard Template and rename the new
one to start with letter “Y” or “Z”

Data Base
Master Data Application Data Configuration Data

Master Data – Is used to fill the Application (Helps in filling application easily)

Application Data – Transaction Data

Configuration Data – Use to modify Application & Master Data formatting

Data Base – All the above data is stored in the data base
Who is selling,

how is he selling

what is he selling?
Master Data Types

1. Customer Material Info Record

2. Customer Master
3. Material Master

Vendor Master (SAP MM)

Customer (below are mandatory partners) / Business Partner

- Sold-To Party (who places the order)

- Ship-To Party (Where order is delivered)
- Bill-To Party (Who will receive the invoice)
- Payer (Who pays for the invoice)

Note – Which fields are mandatory to fill for each partner depends on the account group

Customer Master Structure

General Data | Company Code Data | Sales Area Data

Material (Product you are selling)

- Raw material
- Semi-finished
- Finished Products
- Service Material

Customer General Company Code Sales Area

Master
Rahul Rahul address, email etc.. UK (Country Setting) London
Rahul Rahul address, email etc.. India (Country Setting) Mumbai
Rahul Rahul address, email etc.. India (Country Setting) Delhi
Rahul Rahul address, email etc.. India (Country Setting) Bangalore

Customer General Company Code Sales Area

Master
UK (Country Setting) London
Rahul Rahul address, email etc.. India (Country Setting) Mumbai
India (Country Setting) Delhi
India (Country Setting) Bangalore