SAP - Course Content Notes - 2020
SAP - Course Content Notes - 2020
ERP is a way to integrate data and process of an organization into one single system.
Software solution the enterprises needs taking the process of an organization goals tightly
WHAT IS SAP
SAP started in 1972 by five former IBM employees in Mannheim, Germany, states that it is the
world’s largest inter-enterprise software company and world’s fourth largest independent software
supplier, overall.
SAP have a very high level of integration among its individual applications which guarantee
consistency of data through out the system and company itself.
SAP HISTORY
In 1972, five former IBM employees launch a company called Systems, Applications, and Products in
Data Processing in Mannheim, Germany. One Year later the first financial accounting software is
complete, forming the basis for the continuous development of other software components in what
later come to be known as the “R/1” system.
The SAP “R/2” system attains the high level of stability of the previous generation of programs.
SAP “R/3” system is unleashed on the market. By 1996, the company has earned 1,089 new SAP R/3
customers. At the end of the year, SAP R/3 has been installed in more than 9,000 systems
worldwide.
With the internet, the user becomes the focus of software applications. Currently, more than 12
million user work each day with SAP solutions. There are now 121,000 installation worldwide, more
than 1,500 SAP partners, over 25 industry specific business solutions and more than 41,200
customers in 120 countries. SAP is the world’s third largest independent software vendor.
1. Functional Modules
2. Technical Modules
ADVANTAGES HOW
1 Reliable Information Access Common DBMS consistent and accurate data,
improved reports.
2 Avoid data and operations redundancy Modules access same data from the central
database, avoid multiple data input, and
upgrade operations.
3 Delivery and cycle time reduction Minimizes retrieving and reporting delays.
4 Cost Reduction Time savings, improved control by enterprise
wide analysis of organizational decisions.
5 Easy Adaptability Changes in business process easy to adapt and
restructure.
6 Improved Scalability Structure and modular design with “add-ons.”
7 Improved Maintenance Vendor supported long term contract as part of
the system procurement.
8 Global Outreach Extended modules such as CRM and SCM.
9 E-Commerce, E-Business Internet commerce, collaborative culture.
ERP DISADVANTAGES
DISADVANTAGES HOW
1 Time Consuming Minimize sensitive issues, internal politics and
raise general consensus.
2 Expensive Cost may vary from thousands of dollars to
millions. Business process reengineering cost
may be extremely high.
3 Conformity of the modules The architecture and components of the
selected system should confirm to the business
process. Culture and strategic goals of the
organization.
4 Vendor dependence Single-Vendor v/s Multi-Vendor consideration,
operation for “best of breeds,” long term
committed support.
5 Features and complexity ERP system may have too many features and
modules so the user needs to consider carefully
and implement the needful only.
6 Scalability and global outreach Look for vendor investment in R & D, Long term
commitment to product and services, consider
internet enabled system.
7 Extended ERP capability Consider middle-ware “add-ons” facilities and
extended modules such as CRM and SCM.
WHAT IS ASAP METHODOLOGY
ASAP stands for Accelerated SAP. It is one of the important Software Development Life Cycle (SDLC)
used for SAP Implementation Projects. It is one of the best ERP system. SAP projects are long and
intense. They require lots of effort and many resources from developers and managers. It can be
really tricky if SAP projects are not planned in a proper form. SAP itself gives a proper methodology
to design the project so it will give reliable results.
The ASAP Methodology prescribes a correct pathway for SAP implementation projects. It consists of
six steps, the 6 major phases of SAP implementation: Pre Sales, Preparation, Business Blueprint,
Realization, Going Live and Post Production. Here are six phases of a SAP implementation project.
1. Pre-Sale of ERP
In this pre-sale phase, ERP (SAP) tries to get the project from the client. Most clients consider more
than one option for their business and then give all options are try to see which one provides the
best result. In most cases, clients get the ERP software license directly from the software companies.
This step may or may not include a test to check which ERP system is most suitable for the client.
2. Project Preparation
In which the project team is identified and mobilized, the project standards are defined and the
project work environment is set up. Once a client decided has decided on its ERP system, then they
prepare the landscape of the project. In this step server information, project cost, resources, Subject
Matter Experts (SME) and business team are decided by the Project Management Organization
(PMO). It consist of project managers, a steering committee, core business members, and sponsors.
A project team studies legacy system and gathers information regarding core systems, interfaces,
what interfaces the client wants, what is necessary, what is nice to have etc. The core team carries
out “as is” studying, a study of the current system and its process. The project management team
also hires resources and carries out project planning and outline.
3. Business Blueprint
In which the business process are defined and the business blueprint document is designed. In this
phase, the core team does “GAP analysis,” an analysis of the differences between the system as is
and the system to be studied. Allocated resources write down the rules and requirements for the
new system. Integration points, interfaces and process maps are finalized. Functional consultants
write the functional specification. If needed technical specifications are written down for developers
to do further configuration. A testing also started working on preparing testing steps and scenarios.
Financial specifications and technical specifications are created in this step for further development
and configurations.
4. Realization
In which the system is configured , knowledge transfer occurs, extensive testing unit is completed
and data mappings & data requirements are defined. In the realization step, functional consultants
carry out configuration. Development is done for the required customization. Testing is carried out
by the core team. Basis configuration is carried out by security team. A basis team moves all
configuration from one server to another for testing purposes. Testing is mostly done in the quality
control server. All the configurations upload master data across all modules (sample load of few
parts or entire data end as per client wants). Unit testing and integration testing has been done by
testing team. Unit testing, integration testing and day in the life testing happen at this stage.
5. Pre-Goes-Live-Phase
In which final integration testing, stress testing and conversion testing are conducted and all end-
users are trained. After that the data is migrated from the legacy system, the new system is
activated. In this step, all configurations from the golden client will be moved to other services.
Uploading master data into the new system is done mostly using LSMW, BAPI, BADI. Cut over
activities are done only when we stop the legacy system and start using the SAP system. End-user
training and user documentation are carried out in this pre-go-live stage. After all cut-over activities,
SAP implementation goes live in a production environment.
6. Post-Production Support
In this step, the team helps the client to solve if any production issue came regarding configuration,
master data change, or transaction issues. Also the team will provide training to end-users and
super-users. All the support documentation work has been completed in this step.
SAP LANDSCAPS
QUALITY
DEVELOPMENT PRODUCTION
CONTROL
CLIENTS CLIENTS CLIENTS
110- Configuration 210- Quality Test 310- Production
120- Sandbox 220- Training-1
130- Development Test 230- Training-2
ENTERPRISE STRUCTURE
1. COMPANY
Definition- The smallest organizational unit for which individual financial statement can be drawn up
according to the relevant commercial law. A company can consist one or more company codes. All
company codes with in a company must use the same transaction chart of accounts and same
financial year breakdown. The company code currencies can be different. A company has one local
currency in which its transaction figures are recorded.
Path- (Display IMG - Enterprise Structure - Definition - Financial Accounting - Define Company)
T-Code- (OX15)
Company- TATA
PO Box- 100
Country- IN
Language- EN
Currency- INR
(Save or Ctrl+S)
2. COMPANY CODE
Definition- The smallest organizational unit of Financial Accounting for which a complete self-
contained set of accounts can be drawn up for purpose of external reporting
Path- (Display IMG - Enterprise Structure - Definition - Financial Accounting - Edit, Copy, Delete,
Check Company Code)
T-Code- (OX02)
Country- IN
Language- EN
(Save or Ctrl+S)
(Save or Ctrl+S)
3. BUSINESS AREA
Definition- It is used to get financial reports in different die mentions. It can be graphical or product
line.
Path- (Display IMG - Enterprise Structure - Definition - Financial Accounting - Define Business Area)
T-Code- (OX03)
(Save or Ctrl+S)
Definition- It is a top hierarchy of customer credit management. Here we define limit of customer. It
is include one or more company codes. It is not possible to divide a company code into several credit
control areas.
Path- (Display IMG - Enterprise Structure - Definition - Financial Accounting - Define Credit Control
Area)
T-Code- (OB45)
Process- Click on Define Credit Control Area - Click on New Entries
Currency- INR
(Save or Ctrl+S)
(Save or Ctrl+S)
Path- (Display IMG - Enterprise Structure - Assignment - Financial Accounting - Assign Company Code
To Company)
T-Code- (OX16)
Press Enter
(Save or Ctrl+S)
Path- (Display IMG - Enterprise Structure - Assignment - Financial Accounting - Assign Company Code
To Credit Control Area)
T-Code- (OB38)
Process- Click on Assign Company Code to Credit Control Area - Click on Position
(Save or Ctrl+S)
Definition- Fiscal year variant is used to define Fiscal Year. Fiscal year financial year of a company.
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) - Fiscal
Year Posting Period - Maintain Fiscal Year Variant)
T-Code- (OB29)
There are standard fiscal year V3 available in our system for April’ 2019 to March’ 2020.
FI Year Variant- V3
Press Enter
Press Enter
Click to continue
(Save or Ctrl+S)
T-Code- (OB37)
Process- Click on Assign Company Code to Fiscal Year Variant - Click on Position
Press Enter
(Save or Ctrl+S)
Definition- It is describe the specifications for a posting period. Each company code refers to exactly
one variant. Therefore, as many company codes require can use the same variant.
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) - Ledger
- Fiscal Year Posting Period - Posting Periods - Define Variant for Open Posting Periods)
T-Code- (OBBO)
Process- Click on Define Variant for Open Posting Periods - Click on New Entries
(Save or Ctrl+S)
Definition- Here we assign company code to variant for open posting period.
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) - Ledger
- Fiscal Year Posting Period - Assign Company Code To Fiscal Year Variant)
T-Code- (OBBP)
Process- Click on Assign Company Code to Variant for Open Posting Period - Click on Position
(Save or Ctrl+S)
Definition- It is describe the specifications for a posting period. Each company code refers to exactly
one variant. Therefore, as many company codes require can use the same variant.
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) - Ledger
- Fiscal Year Posting Period - Posting Periods - Open & Close Posting Periods)
T-Code- (OB52)
Process- Click on Open & Close Posting Periods - Click on New Entries
Press Enter
(Save or Ctrl+S)
Definition- Field Status Group are used to control G/L Accounts at transaction level.
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) - Ledger
- Fields - Define Field Status Variant)
T-Code- (OBC4)
Press Enter
Click to continue
(Save or Ctrl+S)
Path- (Display IMG – Financial Accounting (New) - Financial Accounting Global Setting (New) - Ledger
– Fields - Assign Company Code To Fields Status Variant)
T-Code- (OBC5)
Process- Click on Assign Company Code to Variant for Open Posting Period - Click on Position
Press Enter
(Save or Ctrl+S)
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) –
Document – Document Types – Define Document Types for Entry View)
T-Code- (OBA7)
Definition- It is uniquely identifies every transaction with in a fiscal year in a company code.
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) –
Document – Document Types – Define Document Types for Entry View – Define Document Number
Range)
T-Code- (FBN1)
Press Enter
(Save or Ctrl+S)
Definition-
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) –
Document – Document Types – Define Document Types for Entry View – Copy To Company Code)
T-Code- (OBH1)
General Selections
Click on Execute
Yes
Definition-
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) –
Document – Document Types – Define Document Types for Entry View – Copy To Fiscal Year)
T-Code- (OBH2)
General Selections
Yes
Definition- It is used to determine maximum limits of posting document amount and discount
percentage for employee is authorised to post.
Path- (Display IMG - Financial Accounting (New) - Financial Accounting Global Setting (New) –
Document – Tolerance Group – Define Tolerance Group For Employees)
T-Code- (OBA4)