Sei sulla pagina 1di 10

Instructional Material

Aruna Nemani

ERP Enterprise Resource Planning


HISTORY
1.
2.
3.
4.
5.

Re-Order Levels
MRP1 - Material Requirement Planning
MRP2 - Manufacturing Requirement Planning
ERP
- Real Time Information - JIT, ABC etc.
ERP2 - Real Time Collab Suppliers, Customers, Partners etc.

SAP/R3 Integrated Package


Systems Applications and Products in Data Processing
FICO / PP/ MM / SD / PM / QM / HR etc.
R/3-Real Time/3 Tier Arch(Presentation/Application/Database)
Server Landscape - Production / Quality / Development
ECC (ERP Central Component) ERP,CRM, SCM, SRM, etc.

Consultants
Functional

FICO / MM / PP / SD / CRM / SCM / HR etc.


Good Typing Skills
Good Communications Skills.
Sound Business / Process Knowledge.
In-depth-knowledge about the ERP module.
Analytical thinking skills.

Technical
ABAP

Advanced Business Application Programming.


4th Generation Language. SAP is coded in ABAP.

BASIS

DBA, Transport Management, Security,


Authorizations.

For Private Circulation only

SAP - 1

Instructional Material

Aruna Nemani

Topics Covered
FI - Financials
ES - Enterprise Structure (Gen/Basic Settings)
GL - General Ledger & F S V
AR - A/cs Receivables (Clearing & Dunning)
BoE - Bills of Exchange (TEST)
AP - A/cs Payables (Clearing & Stat of A/cs)
C&B - Cash & Bank (APP & BRS)
Taxes - EWT (TDS) & Sales Tax
FCV - Foreign Currency Valuation
INTG - Integration with MM&SD (Theory & Notes)

CO - Controlling
CO - Controlling Basic Settings
CCA - Cost Center A/cing with Planning
PCA - Profit Center A/cing with Planning
DAR - Distribution/Assessments/Repostings
IO - Internal Orders
Report Writer / Painter (Live Explanation)
Closing Activities and Tables
IM - Invesment Management

AM - Asset Management
Asset Accounting (AA) through IO & IM - Complete Life Cycle

Menu Bar/ Path - It is a path which allows a user to navigate through


the system.
Transaction Code T code is generally 4 character code that is
entered in the command field on the toolbar. They are not case
sensitive.
Be thorough with Business Processes

For Private Circulation only

SAP - 2

Instructional Material

Aruna Nemani

ASAP

Phase 0 - Evaluation
1. Agreed Process Change, and Technical Scope and Complexity
2. Agreed Project Approach
3. Agreed Project Plan and Commercial Arrangements
4. Agreed Benefits Realization Strategy
5. Hardware and Platform Requirements
Phase 1 Project Preparation
1. The Project Charter is approved
2. Project kick-off meetings are run
3. The detailed Project Plan is approved by Steering Committee
4. The project team is staffed and work space is created
5. Initial project hardware is confirmed

For Private Circulation only

SAP - 3

Instructional Material

Aruna Nemani

Phase 2 Business Blueprint


1. Trained project team
2. The installed Development System
3. Finalised global requirements and Enterprise data
4. Finalised and approved Business Blueprint
Phase 3 Realization
1. Trained project team in SAP R/3 and tools
2. Updated Business Blueprint
3. Production environment
4. Tested baseline and final configuration in SAP R/3
5. Written, tested, and confirmed enhancements, interfaces,
conversions, bolt-ones, reports and layout sets
6. Documented end-user procedures
7. Completed final integration testing
8. Security Authorisation Profiles
Phase 4 Final Preparation
1. System administration and help desk in place
2. Production System ready for go-live
3. Cut over plan is approved
4. Programs and configuration is transported to the production
system
5. Master and transaction data is converted to the production
system
6. End users are trained
Phase 5 Go live & Support
1. Live productive environment
2. Fully operational production support system
3. Confirmed business process results

For Private Circulation only

SAP - 4

Instructional Material

Aruna Nemani

Phase 6 Sustain
1. Optimized system performance
2. Implemented archiving process
3. Current system software is integrated
4. Post-implementation review is conducted

Clients are used to divide data in a SAP System into various data
areas for various purposes. If a company, for example, wants to use its
SAP System for both test and training purposes, a client is created for
each purpose. A client is identified via a three character code. Data
can be moved via transports and corrections from one client to
another. When logging on to the system, the user has to select a client
in which he/she wants to work. The users can then only access data in
this client.
Client in R/3

For Private Circulation only

SAP - 5

Instructional Material

Aruna Nemani

The R/3 System is a client system. A client is, in organizational


terms, an independent unit in the R/3 System. Each client has its own
data environment and therefore its own master data and transaction
data, assigned user master records and charts of accounts, and specific
customizing parameters.
SAP R/3

Client - A self-contained unit in an R/3 System with separate master


records and its own set of tables. The data in a Client may not be
accessed by another Client.
The Client is the highest hierarchical level in the SAP
Organizational Structure.
Each Client is a self-contained unit with separate master records
and a complete set of tables.
Specifications made or data entered at this level are valid for all
Company Codes attached to the Client.
A single Client allows central maintenance and ensures
standardized data.
Access authorization is assigned per Client. A User master
record must be created for each user in the Client where he or
she wishes to work.
Each user must specify a Client key when logging on to the system.

For Private Circulation only

SAP - 6

Instructional Material

Aruna Nemani

Main Screen

Menu Bar
Tool Bar
Button Bar

System ID
Server
Status Bar

INS / OVR

Message Bar

SAP Easy Access is the standard entry screen displayed after logon.
Using the menu path Extras Set start transaction you can select a
transaction of your choice to be the default entry screen after logon.
Enter a transaction code in the command field
A transaction code (T-Code) is assigned to each function in R/3
(not each screen).
You can access the assigned transaction code from any screen in
the R/3 System.
You can find the transaction code for the function you are working
in under the Status option of the System menu.
For example, to display Accounts receivable master data, enter
/n and the appropriate transaction code (in this case /nxd03).

For Private Circulation only

SAP - 7

Instructional Material

Aruna Nemani

Other possible entries:


/n ends the current transaction. /i ends the current session.
/osm04 creates a new session and goes to the transaction
specified (SM04)
The maximum number of sessions you can have open
simultaneously is 6.

Some important T Codes


SM01
Lock / Unlock T Codes
SM04
Display other Users
SM12
Unlock Entries
SM30
Table Maintenance / Changes
SM35
Process Sessions
SE09
Release Transport Requests
SE11
Database Tables
SE16
Data Browser
SE17
Analyse Table errors
SE38
ABAP Editor
SHDB
Batch Data Communication
SE91
Message Maintenance
LSMW
Legacy System Migration Workbench
SEARCH_SAP_MENU
Find Options
F1 & F4

Use F1 for help on fields, menus, functions and messages. F1 help


also provides technical information on the relevant field. This
includes, for example, the parameter ID, which you can use to
assign values to the field for your user.

Use F4 for information on what values you can enter. You can also
access F4 help for a selected field using the button immediately to
the right of that field. If input fields are marked with a small icon
with a checkmark, then you can only continue in that application by
entering a permitted value.

For Private Circulation only

SAP - 8

Instructional Material

Aruna Nemani

Three types of data in the system


1. Master data - core information that is shared across
applications. The information is constant over a long period of
time. Master records contain data that controls how transaction
data is posted and processed.
Example: G L Account, Customer, Vendor, Bank, Material
Account master records that are no longer needed, can be
archived; however, they typically remain in the system to assist
in daily transaction processing.
2. Transaction data - the day-to day information that is put into or
generated by the system. Transaction records are archived
periodically to enhance system performance. To be archived,
data must be extracted from the R/3 database, deleted and placed
in a file. This file can then be transferred to an archiving
system.
Example: Invoice, Payment, Credit Memo, Good Receipt
3. Table data - the data that is specifically configured for a clients
business.
Example: Payment Terms, Tolerance Settings, Pricing
conditions
Messages
Required Field
Information Message
Warning Message Continue the transaction.
Error Message
Fata Error - Program terminates.
For Private Circulation only

SAP - 9

Instructional Material

Aruna Nemani

Overview
FI Finance (External) & CO Controlling (Internal)

There are two target groups that use accounting information:

External users
These users usually require information that conforms to legal
requirements. This data is managed in the application component
FI (Financial Accounting).

Internal users:
These users come from all levels within the company. The need
information for the internal operations of the company. This
information is contained in the application component CO
(Controlling).

END..

For Private Circulation only

SAP - 10

Potrebbero piacerti anche