"SAP ERP" is the marketing-driven rebranding of SAP R/3 as
"SAP ERP", based on the original interpreted kernel developed in
1967.
SAP ERP, a closely integrated suite of components included in SAP
Business Suite software, it is an Enterprise Resource Planning product capable
of integrating multiple business applications with each applicant is
representing a specific business area.
SAP processes a product that is capable of great depth in specific
application area.
SAP GRAPHICAL USER INTERFACE:-
SAP has also developed a
user interface called the SAP graphical user interface (SAPGUI), which runs on
Windows 3.1/95/98/NT, Motif, OS/2 presentation manager, and Macintosh. All
SAPGUIs look identical, regardless of the operating system on which they are
running. This interface varies according to the version of SAP or SAPGUI you
are running; however, the difference in appearance is minimal. The appearance of the screens and means is
configurable.
THE APPLICATION INTEGRATION:-
SAP is an “Enterprise
Resource Planning” (ERP) software product capable of integrating multiple
business applications, with each application representing a specific business
area. These applications update and process transactions in real time, thus
allowing seemingly effortless integration and communication between areas of a
business.
CUSTOMIZING TOOLS:-
The cornerstone of SAP
is its ability to be configured to meet the needs of your business. This is done by customizing or adapting the
system to your business requirements, which is the process of mapping SAP to
your business process. Since SAP
version 3, the “Reference Implementation Guide” (IMG) for R/3 customizing has
been available. Until this version,
customizing had to be done in the menu paths of the system with considerably
more hassle. This IMG screen is the
backbone for SAP and the entries placed in it determine how the system
functions. We will be using this screen extensively for the purpose of
configuring the FICO module.
R/3 Applications overview:-
R/3 applications are
categorized into 3 core functional areas: Logistics, Financial, and Human
Resources of these three functional areas, there is a further subdivision into
applications or modules.
LIST OF MODULES:-
A) ENVIRONMENTS FOR SAP
1. Supported Hardware for SAP ERP
SAP can be installed on the following systems. The functionality and
programming technique is same for all systems.
HP, IBM, Sun, AT&T, AS400, Bull, Sequent, SNI, Compaq Digital
2. Supported Database for SAP ERP
SAP is a back-end-free ERP system. That means the following Database can
be used in SAP software. The functionality/programming technique is same for
all database system.
Oracle, MS SQL,
Informix, Sybase , Adabas D , DB2 for AIX , DB2/400
3. Supported Operating System for SAP
SAP can be installed on the following platforms (Operating systems):
MS Windows NT, OS/400, Unix, Solaris, AIX, HP UX, Sinux
B) COMPLETE SAP MODULES:
SAP R/3 is arranged into distinct modules like :
_ Technical Modules
_ Functional Modules
_ Cross Applications
based on their functionality
1.SAP Basis
2.ABAP/4 Programming
3.SAP FI (Financial Accounting)
3.1.General Ledger Accounting (FI - GL)
3.2.Special Ledger (FI - SL)
3.3.Extended Ledger
3.4.Accounts Payable (FI- AP)
3.5.Accounts Receivable (FI - AR)
3.6.Asset Accounting (FI - AA)
3.7.Bank Accounting
3.8.Funds Management (FI - FM)
3.9.Travel Management (FI-TM)
3.10.Consolidation
4.SAP CO (Controlling)
4.1.Cost Centre Accounting (CO - CCA)
4.2.Overhead Cost Controlling (CO - OM)
4.3.Activity Based Coding (CO - ABC)
4.4.Product Cost Controlling (CO - PC)
4.5.Profitability Analysis (CO - PA)
5.3.Profit Center Accounting (EC - PCA)
4.6.Material Ledger (CO - ML)
5. SAP EC (Enterprise Controlling)
6. SAP TR (Treasury)
7. SAP IM (Investment Management)
8. SAP HR (Human Resource)
9. SAP SD (Sales and Distribution)
10. SAP Logistics Information System
11. SAP MM (Materials Management)
12. SAP PM (Plant Maintenance)
13. SAP PP (Production Planning)
14. SAP QM - Quality Management
SYSTEM LANDSCAPE:-
‘System Landscape,’ in SAP, refers
to a number of systems and their deployment within an SAP installation. The
various systems may be designated as Development, Test, and Production Clients.
“Development Quality Control Production “
R/3 ARCHITECTURE:-
SAP R/3 is based on a 3-tier Client-Server model, represented by the:
- Database Layer
- Application Layer
- Presentation Layer
In a 3-tier Client server model, all the above three layers run on three
different machines.
The Database Layer consists of an RDBMS (Relational Database Management
System), which accepts the database requests from the Application Layer, and
sends the data back to the Application Layer, which in turn passes it on to the
Presentation Layer.
The Application Layer
or the server interprets the ABAP/4 programs, receiving the inputs from them
and providing the processed output to them.
The Presentation Server or ‘Presentation Layer’ is what is installed on
the typical workstation of a user. This is nothing but the SAPGUI, which when
started provides the user with the interface of SAP R/3 menus. This interface
accepts the inputs from the user, passes them on to the Application Server,
processes the inputs and sends back the output. If database processing is
required, the Application Server sends the details to the Database Layer,
receives the data, and then processes it at the Application Layer level and
sends back the output to the Presentation Layer where the SAPGUI may format the
data before displaying it on the screen.
SAP R/3 System Architecture
“DATABASE <-- APPLICATION <-- PRESENTATION” layer.
The R/3 System
architecture allows you to separate application from the presentation and the database.
This is the prerequisite for distributing load onto several application servers
in client/serverconfigurations. Therefore, the system can be distributed, in
hardware terms, at three different levels.This architecture means that the
installed host service can be adjusted without any problems(scalability),
especially where load profiles have changed as a result of increasing user
numbers, or because additional components have been used. R/3 System
scalability provides you with flexibility when choosing hardware and software.
‘INSTANCE’
An ‘Instance’ is an administrative unit that groups together components
of an SAP R/3 system or simply an Application Server, which has its own set of
work processes. A Client can contain many instances. Loosely defined, an
instance refers to a server.
Sometimes the database is also referred to as an ‘instance.’ In this case
it is called the ‘Central Instance.’
‘R/3 DATA DICTIONARY’?
The ‘Data Dictionary’ is a collection of logical structures of various
objects (Tables, Views, or Structures) used in application development in SAP,
which shows how they are mapped to the underlying RDBMS in Tables/Views.
‘SAP BUSINESS OBJECT’?
An ‘SAP Business Object’ is similar to real-world business objects such
as Sales Order, Invoice, Employee, etc., which consist of various
tables/programs that are related to each other in a business context. All the
business objects are maintained in the ‘BOR (Business Object Repository).’
The various
characteristics of an object are called ‘Attributes.’ For example, the business
object Sales Order is characterized by the following attributes:
- Date of the order
- Items of the order
- Prices of various items of
the order
- Name of the customer to whom
the order belongs to
The application program or programs used by the system to change or
manipulate a business object are known as Method(s). For example, a program
could be used to (a) check the availability of stock to deliver, (b)
trace the shipment route, (c) check the item prices, (d) validate
the order date, etc.
So, attributes and methods collectively represent business objects in
SAP.
There are certain tables, in SAP, which when changed will not affect
similar tables in other Clients. These are known as ‘Client-Dependent’ tables.
All Client-dependent tables have Mandt as their first field.
On the other hand, if a change made in one Client is reflected in another
table across various Clients, then such a table is called ‘Client-Independent.’
In this case, the first field of the table will not be ‘Mandt.’ You need to be
extra careful when changing the settings or content of these tables as this
will affect all the Clients.
There are nine types of ABAP/4 programs in SAP:
- 1 Executable
Programs (ABAP Reports)
- I INCLUDE Program
- M Module
Pool/Dialogue programs
- S Sub-Routine
Pool
- J Interface Pool
- K Class Pool
- T Type Pool
- F Function Group
- X XSLT Program
‘INTERNAL TABLES’:-
‘Internal Tables’ are
standard data type objects which exist only during the Runtime of an ABAP/4
program. They are used to perform table calculations on subsets of database
tables and for re-organizing the contents of database tables according to a
user’s need. Internal tables fulfil the need for arrays in ABAP/4.
There are three types of internal tables:
- Standard Tables with a
‘linear’ index. The key is always ‘non-unique.’
- Sorted Tables with either a
‘unique’ or ‘non-unique’ key.
- Hashed Tables (they do not
have a linear index) with the key defined always as ‘unique.’
‘LOGICAL DATABASE’?
A ‘Logical Database’ is a special data-retrieval program delivered by
SAP, with its own dynamic Selection Screens. You need to code only the
processing logic (GET, CHECK, etc., statements). The logical database consists
of a ‘read’ program in which the structure of the local database is reproduced
with a selection screen.
Advantages:
- Check functions to validate
that user input is complete and correct.
- Meaningful data selection.
- Central authorization checks
for database accesses.
- Excellent read access
performance while retaining the hierarchical data view determined by the
application logic.
‘BDC’ PROGRAMMING
‘BDC (Batch Data Conversion)’ is an automated procedure for transferring
large volumes of external or legacy data into the SAP system using batch input
programming. There are three ways to do this:
- Call Transaction Method
- Session Method
Irrespective of the method, the techniques use the following steps:
- Identify the screens of the
transaction that the program will process.
- Write a program to build the
BDC table that will be used to submit the data (i.e., text file) to SAP.
- Submit the BDC table to the
system in the ‘batch mode’ or as a ‘single transaction’ by the CALL
TRANSACTION command.
The ‘Call Transaction’ method cannot be used when you want to process
multiple transactions. Instead, use the ‘BDC-insert function’ to achieve this.
‘BAPI’:-
The ‘BAPI (Business Application Programming Interface)’ is SAP’s
standardized application interface for integrating third party applications
with SAP’s business processes and data thereby providing an entry into the R/3
system. A BAPI may be used to create a ‘business object’ or to change the
attributes of a business object. Note that the assignment of a BAPI to a
business object is always 1-to-1.
A BAPI Explorer helps you to move around the collection of BAPIs in the
system, which is grouped both hierarchically and alphabetically. For each BAPI
in the explorer, you are provided with several tabs for details, documentation,
tools, and projects (to create new BAPIs).
- Create a Purchase Order
- Change a Purchase Requisition
- Create a Customer
- Display an Invoice
‘ALE (Application Link Enabling)’ is used to support the construction and
operation of distributed applications, through the exchange of data messages
ensuring data consistency across loosely coupled SAP applications, using both
‘synchronous’ and ‘asynchronous’ communications without the need for a central
database.
ALE is comprised of three layers:
- Application services
- Distribution services
- Communication services
ALE helps to:
- Distribute applications
across several SAP systems, such that centralized/decentralized functions
can operate in the same company area.
- Maintain and distribute
master data elements from a central system.
- Maintain and distribute
control data objects from a central system with the synchronized
configuration data (important to decentralize functions yet keep them
integrated).
- Link R/2 and R/3 systems.
- Link SAP and external
systems, via IDocs (Intermediate Documents).
A ‘Remote Function
Call (RFC)’ is a call to a ‘function module’ running in a system different from
the ‘calling-system.’ The remote function can also be called from within the
same system (as a ‘remote call’), but usually the ‘calling-system’ and the
‘called-system’ will be in different systems.
An RFC helps to take care of the following communication:
- Communications between two
independent SAP systems.
- Client-server communications
between an external Client and an SAP system acting as the server.
- Client-server communications
between an SAP System acting as the Client and an external server.
‘OLE’?
For the Windows front-end, SAP provides interfaces based on Microsoft’s ‘Object
Linking and Embedding’ Technology (OLE Automation) for embedding objects such
as Microsoft Excel files.
‘MATCH CODE’ IN SAP?
‘Match Codes’ (now known as Search Help with release 4.6) help to search
and retrieve data when the key of a record is not known. The technique involves
(a) creating a ‘Match Code Object’ (now known as a ‘Search Help Object’)
and (b) specifying a ‘Match Code ID.’ The system helps you to access the
match codes (search help) in the following ways:
- Keeping the cursor in the
field, and then pressing ‘F4.’
- Keeping the cursor in the
field, clicking the ‘right’ button on the mouse, and then selecting
‘possible entries.’
- Keeping the cursor in the
field, and then clicking on the ‘magnifying glass.’
‘DRILL-DOWN’ REPORT?
A ‘Drill-Down Report,’ also called an Interactive Report, is a report
with more detail. Imagine that you are looking at a Balance Sheet, presented as
a ‘drill-down’ report.
The topmost list, also known as the ‘Basic List,’ contains the top-level
information such as current assets, fixed assets, etc., under the grouping
‘assets’ on one side of the Balance Sheet. The ‘drill-down’ functionality helps
you select a line item from the Basic List
(e.g., fixed assets) and ‘drill-down’ further to a detailed list (‘secondary
list’) which displays various components of the fixed assets such as land,
buildings, machinery, etc. You may ‘drill-down’ even further by doubleclicking
the ‘building’ line, which will bring up the next detailed list and so on.
You will be able to create a ‘drill-down’ report with a maximum ‘drill’
level of 20; that is, including the Basic List you will have a total of 21
levels in a single ‘drill-down’ report.
‘ALV’ PROGRAMMING IN ABAP?
SAP provides a set of ‘ABAP List viewer (ALV)’ function modules, which
can be used to enhance the readability and functionality of any report output.
This is particularly useful in a situation where the output of a report
contains columns extending 255 characters in length. In such cases, this set of
ALV functions can help the user to choose and arrange columns from a report
output and also save different variants for report display. This is very
efficient for dynamically sorting and arranging the columns and provides a wide
array of display options.
‘DYNPRO’?
‘DynPro’ in SAP refers
to Dynamic Programming relating to the screens and ‘flow logic,’ which controls
the processing and display of these screens. On a broader scale, a screen is
also referred to as a ‘DynPro.’
‘ABAP/4 QUERY’?
‘ABAP/4 Query’ (also known as an SAP Query or Query) is a powerful tool
used to generate simple reports without any coding. Typically, an ABAP/4 query
is created first by defining a User Group and a Functional Group. The
functional group can either be created with reference to a ‘logical’ table or a
database table. Once the functional group is defined, the user group is
assigned to the functional group. The last step is to create the query on the
functional group that is generated.
An ABAP/4 Query can be used to create the following three types of
reports:
- Basic Lists: Reports with
basic formatting without any calculated fields.
- Statistics: Reports with statistical
functions such as average, percentages, etc.
- Ranked Lists: Ranked lists
are used for analytical purposes.
‘SAPSCRIPT’?
‘SAPscript’ is the SAP System’s own text-processing system. SAPscript is
tightly integrated and used for many text-processing tasks. SAP Standard Styles
and Layout Sets are always held in Client 000.
Layout Sets are used for the Page Layout of SAPscript documents. A
‘layout set’ has the following elements:
- Header Data: Data related to
development (created by, development class, etc.) and the layout set
information (which elements are used) are both stored in the header data.
A start page must be entered here.
- Paragraph Formats: Paragraph
formats are required in layout sets. However, they are also used for word
processing in layout sets, for example, to format text elements.
- Character Formats: You can
also use character formats to format texts or paragraphs. Unlike paragraph
formats, however, they are used to format text within a paragraph.
- Windows: Windows are names
and window types, which are not physically positioned until they
are allocated to pages and units of measurement are specified.
- Pages: Pages are defined to
provide the system with a start and end point in text formatting.
- Page Windows: Page windows
are the combination of windows and pages, where the dimensions of a window
and its position on a page are specified.
‘ENHANCEMENTS’?
The standard R/3 application may not offer some of the functionality you
need for a particular customer or for a particular situation. The R/3 ‘Enhancement’
functionality allows you to add your own functionality to SAP’s standard
business applications or modify the standard one to suit the particular need.
The enhancement may be done through: Customer exits
Customers’ potential requirements, which do not form a part of the
standard software, are incorporated in the standard R/3 as empty modification
‘shells.’ Customers can then fill these with their own coding. SAP guarantees
that all such exists will remain valid across all future releases. The customer
exits include:
- Menu Exits
- Screen Exits
- Function Module Exits
- Keyword Exits
These are ABAP/4 Dictionary Enhancements (creation of table appends),
Text Enhancements (customer-specific keywords and documentation for data elements),
and Field Exits (creation of additional coding for data elements).
‘SCREEN PAINTER’ FROM ‘MENU
PAINTER.’
‘Screen Painter’ is an ABAP Workbench tool used to create or modify the
screens for your transactions. The screen painter allows you to make
modifications to screen attributes, the flow control logic, or the layout.
‘Menu Painter’ is a tool used to design the interface components. Status,
Menu Bars, Menu Lists, F-key settings, Functions, and Titles are the components
of Menu Painter.
Both the screen painter and menu painter are graphical interfaces of
ABAP/4 applications.
‘MODIFICATION ASSISTANT’?
The ‘Modification Assistant’ is the tool that offers you support when
making modifications to the standard, by branching to a ‘special modification
mode’ whenever you are modifying objects from the standard in an ABAP workbench
editor. Originals are initially protected in this mode and can only be changed
with the help of the additional ‘pushbuttons’ that are placed at your disposal.
All changes that you make to the system are logged with the help of the
Modification Assistant. This provides you with a detailed overview of
modifications that is easy to read and that dramatically reduces the amount of
effort needed to upgrade your system.
The Modification Assistant offers support in the following areas:
- ABAP Editor
- Class Builder
- Screen Painter
- Menu Painter
- Text Element maintenance
- Function Builder
- ABAP Dictionary
If an object can be edited using the Modification Assistant, a dialogue
box appears the first time that you attempt to edit that object informing you
that editing functions are limited in modification mode. This dialogue box
appears exactly once per user for each of the various kinds of transport
objects.
‘SPOOL REQUEST’?
‘Spool Requests’ are generated during ‘dialogue’ or ‘background’
processing and placed in the spool database with information about the printer
and print format. The actual data is placed in the Tem Se (Temporary Sequential
objects).
‘CTS’?
The ‘Change and
Transport System (CTS)’ is a tool that helps to organize development projects
(in the ABAP workbench) and customize data (in customizing), and then
move/transport these changes between the SAP Systems/Clients in your system
landscape. An example is moving the configuration settings from ‘development’
to ‘test’ and finally to the ‘production’ Client. The changes (such as the
creation of a new Company Code, changing a document type, etc.) are assigned to
a ‘transport request’ and transported by the Basis or System Administrator.
‘TRANSPORT’?
A ‘Transport’ in SAP is nothing but the transfer of R/3 System components
from one system to another. The components to be transported are specified in
the object list of a transport request.
Each ‘transport’ consists of an ‘export process’ and an ‘import process’:
- The export process reads
objects from the source system and stores them in a data file at the
operating system level.
- The import process reads
objects from the data file and writes them to the database of the target
system.
The system maintains a ‘transport log’ of all actions during export and
import. The ‘transport organizer’ helps to manage the transports in SAP.
Look at Table TPLOG (go there using the Transaction Code SE16) and input
the transport name in the CMDSTRING field with ′*.′ Example: *PZDK980001*
An ‘Authorization’ is the process of giving someone permission to do or
have something. In multi-user SAP systems, a SAP Basis Administrator defines
for the system which users are allowed access to the system and what privileges
of use each user gets (such as access to transactions, etc.).
‘LSMW.’
The ‘LSMW (Legacy System Migration Workbench)’ is a free SAP-based tool
that supports the one-time or periodic transfers of data from non-SAP systems
to SAP. The LSMW can be used in conjunction with the Data Transfer Workbench.
The LSMW
assists in organizing your data migration project and guides you through the
process by using a clear sequence of steps. The most common conversion rules
are predefined. Reusable conversion rules assure consistent data conversion for
different data objects.
The LSMW performs the following steps:
- Reads the legacy data from
one or several files (such as spreadsheets or sequential files)
- Converts the data from source
format to target format
- Imports the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc, etc.)
There are two ways to do this:
- Export/Import method. With
this method, you have the flexibility of subprojects or objects that need
to be transported. Use the Menu Path ‘LSMW>Extras>Export project.’
- Transport request. With this
method, you will not be able to select the objects, and the project as a
whole is transported. Use the Menu Path ‘LSMW>Extras >Create change
request.’
‘SAPNET’?
The ‘SAPNet’ R/3
Front-end provides a remote connection to SAP’s service and support group to
provide assistance in the event of an implementation project system or
production system problem. Additionally, the SAPNet R/3 Front-end provides
information on the latest high-priority SAP system information, including error
alarm messages that help you prevent problems before they occur. You can also
find release, installation, upgrade, and migration information. This
functionality is included in the standard SAP R/3 Basis System. Connection is
made using ISDN or a leased line through the project’s telecommunications
service provider.
THE BUSINESS FRAMEWORK:-
The Business Framework
Architecture works using business components, that is, configurable
software modules, and it offers enterprises a flexible business
infrastructure. This means that
enterprise software can react quickly to new business demands, and can be
changed or enhanced
simply without disturbing the flow of business. Business components
interact in the Business
Framework Architecture via open BAPIs.
The benefits of the Business Framework Architecture include the ability
to easily change and
configure dynamically business processes independently of usual releases,
easy integration of
Internet and Intranet components in their business processes, simple
connection between R/3 and
third-party software, customers’ own developments and evolutionary
implementation of the latest
technology,and separate upgrade of components without interrupting the
business operation.
NAVIGATION:-
The R/3 System is a client system. The client concept enables the joint
operation, in one system, of
several enterprises that are independent of each other in business terms.
During each user session you
can only access the data of the client selected during the logon.
ñ 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.
ñ You can also create a Favorites list of the transactions, reports, files
and Web sites you use most.
ñ A role describes a set of logically linked transactions. These
transactions represent the range of
functions users typically need at their workstations.
ñ Activity groups (user roles) have to be set up using the Profile
Generator so that users of the SAP
ñ System can work with user-specific or position-related menus.
BUSINESS SCENARIOS-MAIN ELEMENT:
BUSINESS SCENARIO:
Business-related grouping of business
processes localized in a specific
organizational area that share some similar goals in an enterprise, such
as purchasing, services,
balance sheet preparation, production, personnel administration, and so
on.
ORGANIZATIONAL UNIT: Organizational grouping of enterprise areas which,
for legal reasons or for
other specific business-related reasons or purposes, are grouped
together. Organizational units
include legal company entities, sales offices, and profit centers.
MASTER DATA: Data which is used long-term in the R/3 System for several
business processes.
Examples include customers, materials, and vendors.
TRANSACTIONS: Application programs which execute business processes in
the R/3 System such as creating a customer order, posting an incoming payment,
or approving a leave request.
DOCUMENT: A data record that is generated when a transaction is carried
out.
REPORTS: Program which reads certain data elements and displays them in a
list.
The highest-level
element of all organizational units is the “client”. The client can be an
enterprise/an Organization group with several subsidiaries.
A Company Code is a unit
included in the balance sheet of a legally-independent enterprise. It is
the central organizational element of Financial Accounting.
The Controlling Area is
the business unit where Cost Accounting is carried out. Usually there is a
relationship between the controlling area and the company code. For the purpose
of company wide
cost accounting, one controlling area can handle cost accounting for
several company codes
in one enterprise.
MASTER DATA:-
Data records that remain
in the database for a long period of time are called master data. Master data
includes creditors, vendors, materials, accounts, and so on.
ñ Master data is created centrally and can be used in all
applications.-From document to analysis.
ñ Documents are captured and stored on R/3 with various amounts of
information.
Examples: Sales Orders,Purchase
Orders,Production Order,Material Documents,Accounting Documents
ñ Output is any type of communication of data.
Types
of output: file, Fax, Email, Printout, Screen
ñ Reports/Lists are information that is derived from a source and presented
to the user in some output type. You can generate reports directly from the
online transactions or from the other sources of summarized data such as the
Business Information Warehouse, Executive Information System or the various
module Information Systems.
LOGISTIC INFORMATION SYSTEM:-
All of the LIS data is
stored in information structures.
ñ Transactions from the R/3 applications that are performed daily are
aggregated for LIS for statistical purposes. Data from other systems can also be
used in LIS.
ñ The reports most frequently used can be accessed from the SAP standard
menu.
ñ Distinction is made between different reporting types:
Standard reports: List of document, master data, etc. and combinations of
these objects
(characteristics) to be selected in the report request.
Reporting via information systems in the applications: Standard analyses
from FIS (Financials), LIS (Logistics), HIS (Human Resources). Reporting via
information systems with separate databases and tools for generating
flexible report structures: EIS (Executive Information System) and the
Business Information
Warehouse.
