What is sap and when
the sap founded?
SAP
stands for: Systeme, Anwendungen, Produkte, German for "Systems
Applications and
Products." and was founded in 1972 by five former IBM employees in Mannheim, Germany. SAP provides the capability to manage financial, asset, and cost accounting, production operations
and materials, personnel, plants, and archived documents.
Products." and was founded in 1972 by five former IBM employees in Mannheim, Germany. SAP provides the capability to manage financial, asset, and cost accounting, production operations
and materials, personnel, plants, and archived documents.
What is ERP?
ERP
is a package with the techniques and concepts for the integrated management of
business as a whole, for effective use of management resources, to improve the
efficiency of an enterprise. Initially, ERP was targeted for manufacturing
industry mainly for planning and managing core business like production and
financial market. As the growth and merits of ERP package ERP software is
designed for basic process of a company from manufacturing to small shops with a
target of integrating information across the company.
Different types of
ERP?
SAP,
BAAN, JD Edwards, Oracle Financials, Siebel, PeopleSoft . Among all the ERPs
most of the companies implemented or trying to implement SAP because of number
of advantages over other ERP packages.
Why do you usually
choose to implement SAP?
There
are number of technical reasons numbers of companies are planning to implement
SAP. It’s highly configurable, highly secure data handling, min data
redundancy, max data consistency you can capitalize on economics of sales like
purchasing, tight integration-cross function.
What is IDES?
International
Demonstration and Education System. A sample application provided for faster
learning and implementation.
What is SAP R/3?
A
third generation set of highly integrated software modules that perform common
business function based on multinational leading practice. Takes care of any
enterprise however diverse in operation, spread over the world. In R/3 system
all the three servers like presentation, application server and database server
are located at different system.
What are
presentation, application and database servers in SAP R/3?
The
application layer of an R/3 System is made up of the application servers and
the message server. Application programs in an R/3 System are run on
application servers. The application servers communicate with the presentation
components, the database, and also with each other, using the message server.
All the data are stored in a centralized server. This server is called database
server.
How can an ERP such
as SAP help a business owner learn more about how business operates?
In
order to use an ERP system, a business person must understand the business
processes and how they work together from one functional area to the other.
This knowledge gives the student a much deeper understanding of how a business
operates. Using SAP as a tool to learn about ERP systems will require that the
people understand the business processes and how they integrate.
What is SAPS?
The
SAP Application Performance Standard (SAPS) is a hardware-independent unit that
describes the performance of a system configuration in the SAP environment.
SAP standard application workbench which is used to measure CPU . Like a standard CPU of 1.6ghz produces 800 to 1000 SAPS.
describes the performance of a system configuration in the SAP environment.
SAP standard application workbench which is used to measure CPU . Like a standard CPU of 1.6ghz produces 800 to 1000 SAPS.
In SAP how to
schedule background jobs at OS level?
Invoke a sap event using a OS script and then have a SAP background job set to run on a sap event. I say this assuming Unix and a job in crontab. I would guess the same thing could be done on a Windows system.
sapevt TRIGGER_NAME -t
pf=d:usrsapDEVsysprofileDEV_DVEBMGS00_SVRNAME nr
In SAP what is the
procedure to lock a client?
There is no direct tcode to lock a client. the easiest way to lock a client is
1. run tcode SE37
2. type function module name - SCCR_LOCK_CLIENT
3. enter the Client No.
4. execute the function module.
In SAP what is the
importance of the clients 000,001 and 006?
000 is also called as Master Client or Golden client. It contains cross client data & Companies Hardware configuration, Patches, Add-ons Plug-ins Etc
001 is the copy of the Master Client.
066 is called as Early Watch Client. If there is any problem with the SAP system then the early watch client throws the alerts.
In SAP what are
common transport errors?
Return code (4) indicates imported ended with warning.
Ex:
1. Generation of programs and screens
2. Columns missing and Rows missing.
Return code (8) indicates not imported ended with error
Ex:
1. Syntax error.
2. Program generation error.
3. Dictionary activation error.
4. Method execution error.
Return code (12) indicates import is cancelled.
Ex:
1. Import is cancelled due to object missing.
2. Objects are not active.
3. Program terminated due to job “RDDEXECL” is not working.
Return code (16) indicates import is cancelled.
Ex:
1. Import cancelled due to system down while importing.
2. Import cancelled due to user expires while importing
3. Import cancelled due to insufficient roles.
In SAP if a
background job runs more than the time it should be completed normally then
what are the actions to be performed?
First and foremost thing ,we need to inform that user who has scheduled, then we will get information about the background job. If the developer wants to kill the Job. Then go to sm50 and select the BTC work process cancel with core and secondly execute sm37 then select the BTC job kill.
What SAP tools you
use to install SAP patches?
SPAM is the sap tool used to install sap patches
In SAP what JAVA
tools you use to install JAVA Patches?
SDM Was used to Apply Patch to Java new version 700 Systems uses JSPM to apply Patches
In SAP what is early
watch report?
The SAP Early Watch Report gives you detailed information about system status, performance, configuration, system operation, database administration and trends.
In SAP how to install
multiple Central Instances on the same physical machine?
Assign different instance numbers, and listener name.
Can SAP Patches be
installed when other users are online?
SAP
Patches cannot be installed when user’s are online. When users are online they
may access DB/Tables which may be related to the patch being applied. Therefore
it is advisable
to apply patches when there are no users online
to apply patches when there are no users online
In SAP what is the
importance of Virtual system? - or - Need of Virtual system?
When we are implementing a Sap Project, the development server only available in the beginning, so developers perform their tasks which are assigned by project manager, when development project finished then developers need to release their tasks it is possible when we configure 2/3 system landscape with TMS configuration but now only one (dev) system available, so Virtual system created using tcode STMS and configure TMS. When live system is available we can replace virtual system by the live system i.e., (QAS). The main importance of virtual system simply when live system not available we can configure/create Virtual
system
In SAP what are the
differences between system refresh and client refresh?
Copying the entire DDIC, Repository objects and application data from one system (SID0) to another system (SID1) is said to be System Refresh
Copying the objects related to particular a client from one client to another client of same or different SID are said to be Client Refresh
This transaction is to
perform check the SAP system installation does not contain errors during the
process of installation, which if any needs to be attended. This is one time
activity after the installation only.
This
transaction is used for the control of transaction code in case the business
requires that the users who are authorized to carry the transactions are to be
stopped temporarily.
You enter the transaction code as indicated in the picture FS00 and then press Enter key which lists it in screen,
In
this transaction you can send messages to users who are logged in and new users
logging to the client. This message is a client specific and can also be
language specific or generic.
The
best ways to tune are:
Optimizing the system parameters as required
Optimizing the system parameters as required
- SAP System
parameters (for example, memory management)
- Database
parameters (like database buffer sizes)
- Operating
system and network parameters
Optimization
of workload distribution
- Number of
work processes, background scheduling and so on
Optimizing
the database disk layout through IO balancing
Verify hardware sizing by detecting hardware bottlenecks
Verify hardware sizing by detecting hardware bottlenecks
Because
of system bottlenecks programs will take more time to execute.
- Checking for
new SPAM updates, support packages and kernel patches
- Downloading
the new SPAM updates, support packages, and kernel patches
- Preparing
the new SPAM updates, support packages, and kernel patches for application
- Applying the
new SPAM updates, support packages, and kernel patches
- Mass
recompiling all programs used in patched components
This
transfer (by copying or mapping, as appropriate) of user context data into work
process memory is the mechanism known as a "roll in".
After the transaction finishes and the work process is no longer required, the user context data is rolled out of the work process, called "roll out".
CPU time is the amount of time during which a particular work process has active control of the central processing unit (CPU).
Response time in milliseconds: Starts when a user request enters the dispatcher queue; ends when the next screen is returned to the user. The response time does not include the time to transfer from the screen to the front end.
Wait time in milliseconds: This is the time a user request sits in the dispatcher queue. It starts when user request is entered in the dispatcher queue; and ends when the request starts being processed.
Roll-in time in milliseconds: The amount of time needed to roll user context information into the work process.
Load time in milliseconds: The time needed to load from the database and generate objects like ABAP source code, CUA, and screen information.
Processing time: This is equivalent to response time minus the sum of wait time, database request time, load time, roll time, and enqueue time.
Database request time: Starts when a database request is put through to the database interface; ends when the database interface has delivered the result.
CPU time in milliseconds: This is the CPU time used by the SAP work process
After the transaction finishes and the work process is no longer required, the user context data is rolled out of the work process, called "roll out".
CPU time is the amount of time during which a particular work process has active control of the central processing unit (CPU).
Response time in milliseconds: Starts when a user request enters the dispatcher queue; ends when the next screen is returned to the user. The response time does not include the time to transfer from the screen to the front end.
Wait time in milliseconds: This is the time a user request sits in the dispatcher queue. It starts when user request is entered in the dispatcher queue; and ends when the request starts being processed.
Roll-in time in milliseconds: The amount of time needed to roll user context information into the work process.
Load time in milliseconds: The time needed to load from the database and generate objects like ABAP source code, CUA, and screen information.
Processing time: This is equivalent to response time minus the sum of wait time, database request time, load time, roll time, and enqueue time.
Database request time: Starts when a database request is put through to the database interface; ends when the database interface has delivered the result.
CPU time in milliseconds: This is the CPU time used by the SAP work process
The easiest way to confirm that the SAP
instance has started successfully is to log on to the instance. If you try to
login and if refused connection, then check the logs in the
\usr\sap\\DVEBMGS00\work for applicable errors. Sort the files in descending
order by date. The most helpful files are normally stderr, dev_w0, dev_disp,
dev_ms, and dev_rfc.
The
number of instances increases the number of Oracle listener also increases but
saposcol will be only one. If you want to have only one Oracle listener
(OracleTNSListener) file you must deploy major changes to listener.ora and
tnsnames.ora files, either case which allows you to share one listener for
multiple instances. If you have multiple listeners due to multiple SAP
instances, remember that the key to having all your SAP instances happy with
Oracle is to have each Oracle instance use a different listener port. The
default Oracle is port 1521 during the Oracle database instance installation
and this is changed to 1527 during the SAP instance installation. So you want
to make sure that your listeners all have unique listener port numbers like
1527, 1528, 1529, etc. or 1527, 1537, 1547, etc.
Weekly Tasks:
- Check
database for free space (DB02)
- Have to
monitor the database growth (DB02)
- Check spool
for consistency by avoiding spool problems and that spool is properly
cleared (SP01)
- Verify all
properly approved transports imported into PRD (STMS)
- For Oracle,
run a check database and a update statistics job (DB13)
- For MSSQL,
run a check database integrity maintenance job and update statistics
maintenance
- Check file
system for adequate space (RZ20 - Technical Operations Templates -> Space
Management)
- Review space
usage and that sufficient free space exists in the file systems
- System
monitor Review for any events that should be added or deleted
- Check system
monitor alert mechanisms
- System
monitor Test e-mail
- Test paging
- Clean tape drive.
Tape drive Clean using cleaning cartridge
AL02
Database Alert
AL11 View the SAP File Structure on the server
AL16 Local Alert Monitor for Operating System
BD64 Maintenance of Distribution Model
DB02 Database Monitor
DB13 DBA Planning Calendar
DB20 Refresh Database Statistic by Table
OS06 Local Operating System Activity
OSS1 SAPNet Support – OSS Link
PFCG Security Role Maintenance
RZ10 System and Tuning Parameters
RZ11 Profile Parameter Maintenance
SAINT Add-On Installation
SALE Display ALE Customizing
SCC1 Client Copy - Special Selections
SCC3 Client Copy Log
SCC4 Client Administration
AL11 View the SAP File Structure on the server
AL16 Local Alert Monitor for Operating System
BD64 Maintenance of Distribution Model
DB02 Database Monitor
DB13 DBA Planning Calendar
DB20 Refresh Database Statistic by Table
OS06 Local Operating System Activity
OSS1 SAPNet Support – OSS Link
PFCG Security Role Maintenance
RZ10 System and Tuning Parameters
RZ11 Profile Parameter Maintenance
SAINT Add-On Installation
SALE Display ALE Customizing
SCC1 Client Copy - Special Selections
SCC3 Client Copy Log
SCC4 Client Administration
- Have to
check that the SAP System(s) is up
- Check for
the daily back ups executed successfully or not with out errors
- Check that
all application servers are up
- Check the
CCMS alert monitor (if applicable) (RZ20)
- Monitor the
work processes (SM50)
- Check for
failed updates, if any please take the necessary action(update terminates)
(SM13)
- Monitor the
System Log (SM50)
- Review for
cancelled and critical jobs (SM37)
- Check for
“old” locks (SM12)
- Monitor the
users on system (SM04)
- Check for
spool problems (SP01)
- Monitor job
log (SM35)
- Review and
resolve dumps (ST22)
- Review
workload statistics (ST03)
- Review
buffer statistics (ST02)
- Review error
log for problems (AL02 & ST04)
- Review UNIX
system logs for problems (AL16)
- Review
Windows system logs for problems (OS06)
The
above are some basis daily activities of Basis Admin.
The
following steps are commonly followed steps to install the SAP
- Make all
server configuration adjustments as specified in the SAP installation
guide.
- Download and
install JDK 1.4x – you can use JRE 1.4.x if you aren’t going to use the
ABAP add-on.
- Install the
database software.
- Patch the
database software.
- Run SAPinst
to install the CI and default DI instances.
- Run SAPinst
to install the DB instance.
- Run SAPinst
to install any additional DI instances.
- Download and
install the most current SAP kernel.
- Current the
TMS for the SAP instance.
- Download and
apply all outstanding SAP patches.
- Request and
apply the permanent license key.
- Do remaining
post-installation work such as connecting SAP Online Help, creating
clients, adding users, etc.
0 comments01:29 Posted
by Sriram
Labels: ecc 6.0 installation, ecc 6.0 video, sap, sap basis, sap basis installation video
Labels: ecc 6.0 installation, ecc 6.0 video, sap, sap basis, sap basis installation video
Installing
of ECC 6.0 in a video format with screen shots
Sap Landscape is like a
server system or like a layout of the servers. A SAP landscape can range from
one SAP instance with one client and one user who does all the input into the
instance via keyboard to dozens of instances with tons of clients and thousands
of users
with keyboard, Remote Function Calls and Automatic Link Exchange from alternative SAP instances, links to external databases, Electronic Data Interchange via flat file from banks, vendors, etc and so on.
with keyboard, Remote Function Calls and Automatic Link Exchange from alternative SAP instances, links to external databases, Electronic Data Interchange via flat file from banks, vendors, etc and so on.
A normal SAP landscape consists of a Development (DEV) instance DEV would have multiple clients for ex: 190- Sandbox, 000- Golden, 180- Unit Test, a Quality Assurance (QAS) or Test (TST) instance QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training and a Production instance (PRD) PROD may have something like client 200 Production.
Some very small implementations will have only a DEV and PRD instance, with the DEV instance
containing a QAS client for testing purposes. The SAP instances form the core of a SAP landscape. The other installed SAP products are peripheral to the SAP instances.
The dispatcher monitors all R/3 process. To do so it
manages different work process, to which it distributes the tasks pending in
the R/3 System.
User requests are assigned
to the dialog work process via the dispatcher. The dialog work process executes
one step and returns to the user, after which it is ready to accept the next
request. This request can be from the same or different user. Minimum 2 work
process is required.
Presentation: - Presentation layer is
located on a user computer. A program named sapgui is installed on a user
computer which accepts input from user and sends it to application server.
Application Layer: - Application Layer is a
platform where all SAP programs run. It consists of group of components such as
dispatcher, work processes, ABAP dialog processes, and screen interpreter
e.t.c. With the start of application server all of these components start at
the same time & shut down automatically when server is stopped. There can
be more then one application server in application layer and they can be
assigned to many computers. Every application server contain set of services
require to run R/3 system. Message server work as a communicator between these
application servers. Message server informs application servers about the
existing of other servers and it contains the information about the load
balancing.
Any other Information pls visit below website.