Sap Basis
Sap Basis
Sap Basis
private mode is a mode where the heap data is getting exclusively allocated
by the user and is no more shared across the system. this happens when your
extended memory is exhausted.
select any table lets take mara here but you should do the same for mseg and
few others to see whether the dates match or not.run the following command
on the command prompt:-
select last_analyzed from dba_tables where table_name like '%mara%';
this gives you a straight answer .else you can always fish around in db14 for
seeing when the optimzer stats were updated.
*-- ankan
automatic cts
even though sap does not recommend automatic imports, it is the
most practical way of moving transports from a development system
to a qa environment or to a special development system (although i
wouldn't recommend auto imports to a production system for obvious
reasons).
there are various methods for doing this. the most effective and
simple method is using an os script (shell/perl etc.) scheduled using
cron for user sidadm. there are a couple of steps you need to take
before setting up automatic imports.
1. your entire project team should agree upon the overall strategy,
frequency of imports etc.
2. resolve any issues with transport approvals (many shops don't
care about traffic between dev and qa)
3. who is responsible for watching for errors and corrective actions
(an email to the developer works in this case)
configuring outbound sap to internet mail gateway (r/3 4.0 and
above)
step 1 (unix setup)
logon to your <db_server> as sidadm
change directory to /sapmnt/sid/global (or any directory globally
available across all application servers)
create the following entries in file sap_email_gateway.sh and save
the file
#!/bin/sh
gwconfig=/sapmnt/sid/global/sap_email_gateway.cfg
export gwconfig
/sapmnt/sid/exe/mlunxsnd $*
execute the command: mlosmadm sap_email_gateway.cfg (enter
the following information)
system name : sid
client : 200
username : mailadm
password : initpass
language : e
loadbalancing : y
message server : <central_instance_host_
group name : logon group1
using saprouter : n
trace level (inboound) : 0
sendmail command : <accept default>
codepage : <accept default
trace level (outbound) : 0
update file : y
step 2 (sap setup)
logon to sapsystem (sid) via sapgui
transaction su01, create user mailadm and password initpass,
usertype cpic
transaction sm59, click create
rfc destination : sap 4.5 internet mail gateway
connection type : t
description : internet email gateway
hit return
click explicit host
enter /sapmnt/p21/global/ sap_email_gateway.sh
save your entries
transaction scot, click edit--> create nodes
node : email
description : sap connect node for email (continue)
rfc destination: (choose sap 4.5 internet mail gateway from the pull
down menu)
choose radio button internet
address area : *domain (your intranet domain)
ccontinue
format : doc, dat, r3f, txt, raw,ppt,xls (continue)
continue
set further address types : n
minimum waiting : 5 minutes
check both node is in use', node can resolve path references
continue
choose goto--> schedule background job
enter name for the job & save
configuring outbound sap to internet mail gateway (upto r/3 3.1i)
sap can be configured to send and receive emails from different
sources. this section explains how to integrate sapoffice with an
external email system. this is in no way supplementing the online
documentation available on the online documentation cd supplied by
sap but simplyfies the process to the bare internet email must be
configured and running prior to this. email from sap is forwarded to
the users external email client such as eudora, outlook etc.
you can configure inbound and outbound forwarding. outbound flow
forwards a sap message (eg:update termination) via unix sendmail to
the intended recepient. inbound accepts a message from sendmail
and places it in the users sapoffice inbox. many sap shops prefer to
configure outbound only.
configuring outbound forwarding
sap configuration
1. create your rfc destination for outbound email using transaction
sm59
rfc destination : sap_internet_gateway
connection type :t
description : sap internet mail gateway
click on 'explicit host' if you want on demand gateway dameon
invocation.
program : /sapmnt/sid/exe/mlunxsnd
target host : enter hostname that runs your central instance.
click 'test connection' and you should see a successfull message.
choose menu tools-->administration-->management-->process
technology-->office-->office settings
click internet gateway
gateway destination : sap_internet_gateway
path for configuration file : /sapmnt/sid/exe/sap_mailsid.cfg
return address : <your company domain>.com
5. click internet settings and fill in the following fields
6. save the settings
7. click back
8. choose menu office-->addresses-->communication types
9. type in int over the comm. type and internet mail over
description.
10.. check maintain and send checkboxes and save your entries.
unix configuration
11.. cd /sapmnt/sid/exe
12..mlosadm sap_mailsid.cfg
13.client 000
14.username : mailadm
15.password : mailadm
16.language : e
17.system name : sid
18.system number : <instance_number>
19.hostname : <hostname>
20.gateway hostname: <central_instance_hostname>
21.gateway server sapgw<instance number>
22.sendmail command : <path_to_sendmail_command>
23.update file : y
testing
1. logon to sap
2. execute transaction so01
3. write a message and send it to <your_internet_email_address>
if you don't see the mail in your internet mailbox, go back
and review steps 1-12
ftp from abap
there are 2 ways of executing ftp from an abap (online or batch
mode),
initiated from the operating system. a script is available in the utility
repository that explains how to do this very easily.
initiated from the abap itself an example is given below.
welcome to the exciting world of sap r/3 basis. the term basis
(foundation) is no misnomer. all application modules of an sap r/3
system are integrated using the basis technology and comprise of
four major areas.
application administration: abap, security, correction and transport
system, implementation guide, workflow, sapoffice, external
interface configuration, upgrades etc. are some of the major sub-
areas.
database administration: database interface, space management,
performance, capacity planning, upgrades.
operating system administration: os and sap kernel,
communication, disk, memory, printers etc.
infrastructure administration such as hardware, network planning,
high availability, archiving, language support
automatic cts
even though sap does not recommend automatic imports, it is the most
practical way of moving transports from a development system to a qa
environment or to a special development system (although i wouldn't
recommend auto imports to a production system for obvious reasons).
there are various methods for doing this. the most effective and
simple method is using an os script (shell/perl etc.) scheculed using
cron for user sidadm. there are a couple of steps you need to take
before setting up automatic imports.
1. your entire project team should agree upon the overall strategy,
frequency of imports etc.
2. resolve any issues with transport approvals (many shops don't
care about traffic between dev and qa)
3. who is responsible for watching for errors and corrective actions (an
email to the developer works in this case)
why is it that when i use suim to see who can run certain transactions i
get a certain list of users. but one or more users are missing that i know
have access to run that transaction?
up to now the report did not take into account the transactions which
are executable due to customizing with the help of the su24 / su25
what is client 000 in sap r/3?
client 000 is defined as the sap standard and the customer
cannot change it. this client serves as a copy template for
the creation of further clients.
what are the different type of work process ?
the following work process in sap r/3
dialog (d): each dispatcher needs at least 2 dialog work
processes (not shown above)
spool (s): at least 1 per r/3 system (more than 1 per
dispatcher allowed)
update (v): at least 1 per r/3 system (more than 1 per
dispatcher allowed)
background (b): at least 2 per r/3 system (more than 1
per dispatcher allowed)
enqueue (e): exactly 1 per r/3 system (only 1 e work
process is required and allowed)
how do you start sap r/3?
to start r/3, run the shell script startsap from the home
directory of user <sid>adm.
startsap starts the saposcol process, which is the statistics
collector for operating system resource data, if it is not yet
running.
startsap calls the script startdb, which starts the
database if it is not already started.
startsap then starts the central instance.
solution: start mmc and select sap systems in the tree. then
close it and choose "yes" in the dialog "save console settings
to sapmmc?". now you won't get this annoying error on
every start.
t-codes
development transaction codes
s001 abap workbench
se09 workbenche organizer (transports)
se11 abap/4 dictionary
se16 data browser
se24 class builder
se30 abap runtime analyzes
se32 abap/4 text element maintenance
se35 abap/4 dialog modules maintenance
se36 logical databases
se37 function builder
2. monitoring
there are some oss notes, which we should implement manually, that
means we need to change the code
in the programs/objects ourselves according to the steps mentioned in
the problem.
i did not find any oss notes appropriate for my problem or bug. what i
have to do?
if the oss notes displayed are not helpful to solve your problem. you can
write to sap service describing your
problem. you problem will be answered by sap support team.
how to apply oss notes in my sap system? what is the t-code and what
are the steps. in next post we will
see it.
oss stands for on-line service system.
what is the use of oss?
in day-to day business customers who are using sap software
encounters problem or bugs with sap
software. to resolve the issues faced by customers sap has provided an
on-line solution.
what? sap software is having problems or bugs? yes, any software
product is not 100% pool-proof. sap is
continuously updating the versions for better performance and options.
there are some oss notes, which we should implement manually, that
means we need to change the code
in the programs/objects ourselves according to the steps mentioned in
the problem.
i did not find any oss notes appropriate for my problem or bug. what i
have to do?
if the oss notes displayed are not helpful to solve your problem. you can
write to sap service describing your
problem. you problem will be answered by sap support team.
how to apply oss notes in my sap system? what is the t-code and what
are the steps. in next post we will
see it.
types of consultants:
the most common question being asked in interviews is ' what are your
roles and responsibilities?'.
before answering the above question, let me explain the difference
between functional consultant and
technical consultant.
roles and responsibilities differ from functional consultant to technical
consultant.
functional consultant:
* functional consultants are responsible for designing the sap
implementation solution based on the
requirements of your company.
* functional consultants are business process experts.
* functional consultants normally use their process knowledge to
calculate the impact of the sap
implementation on the company's processes.
* functional consultants are thus concerned with sap functions and
processes that will generate the data
and output for business.
* functional consultants interact with end users of the company to gather
requirements and based on the
requirements they customize the sap implementation.
technical consultant:
* technical consultants are experts in information technology.
* technical consultants normally assist in configuration of the sap r3
installation. in many sap
implementations, technical consultants help in designing interfaces and
customizations in r3. finally, the
sap r3 technical consultants would be responsible for migration of data
from the legacy system to the new
sap erp implementation.
4) peer review
if you are a senior developer you can perform peer review. i.e review the
code written by your peers.
system landscape:
the system landscape contains all systems that were installed. the
customer can choose any landscape
according to the requirements.
if the customer is very big, one can implement four system landscapes.
mid size customers can go for two
system landscape.
now we will see different system landscapes:
the cts is the central tool for managing changes to customizing and
repository data that we make in the img
or abap workbench.
transport organizer:
development class:
development classes are used to group similar work objects that are
being developed in a project.
while creating development class we must assign it to the transport
layer.
defining transport layer and routes is sap basis administrator job. the
transport layer defines transport
route between the systems included in system landscape.
task:
how do you connect to sap servers which are at client side, if you are
working from offshore?
we can connect through internet or private lines. if you use internet, it
is not secure because of its
accessibility to public. private lines are costly for the companies. here
vpn comes into picture.
as the name itself tells us that it is secure. we will see what exactly it
is.
a virtual private network is a private communications network used
within a company, or by several
companies or organizations to communicate confidentially over non-
private network.
from the above definition it is clear that vpn also uses non-private
network like internet. but it creates a
virtual netwo
tell me the example vpn software names?
at&t and citrix. there are many vpn softwares in the market.
in general, you will be given with a user name and password for vpn.
by using the user name and
password you can connect to vpn.
then you have to use the sap user id and password to connect to the
sap server.
now it is clear that vpn user id different from sap user id.
types of projects:
we can divide the sap projects into three categories. they are
1) sap implementation projects
2) sap support projects
3) sap migration projects