IDES ECC 6.0 EHP6 IS-OIL/IS-RETAIL SRM7.0,CRM EHP2,ISU,SCM, BO4 SAP Remote Access Available: 1/8/12

PAID REMOTE SAP BASIS SUPPROT

Website : www.sapbasis.in

SAP IDES SERVER Remote Full Access 24x7x365 just 500 /Month or $20 .

SAP IDES IS-OIL 6.0 / IS -RETAIL Remote Full Access 800 /Month or $30

SAP IDES SRM 7.0 + ECC 6.0 EHP6 Remote Full Acess 1300/ Month or $ 50

SAP IDES CRM 7.0 + ECC 6.0 EHP6 + ISU Remote Full Acess 1300/ Month or $50
SAP SCM +APO Server Full Access 1000 /Month

SAP BO4 Remote Access 1300 /Month $ 50

Please Contact : support@sapbasis.in /+919052825025

SAP OIL and GAS Certification Material @ $ 50 USD

SAP OIL & GAS CERTIFICATION TRAINING

Following Materials You Will Learn@HOME : ( All Below 9+ Courses -Latest and OLD VERSION COURSES )

=================================================

IOG100 - Primary & Secondary Distribution with SAP Oil & GasEHP6 ( v097 - Col97 ) - Latest

IOG150 - Oil & Gas Industry Supply ChainIOG320 - Oil & Gas Exchanges Business

IOG330 - Bulk Transportation and Shipment Costing

IOG340 - Trading & Scheduling with SAP for Oil & Gas - EHP6 ( v097 - Col97 )- Latest

IOG350 - Service Station Retailing

IOGW40 - Joint Venture Accounting (JVA)

IOGW50 - Offshore Logistics Management (IS-Oil)SAP OIL & GAS Overview - Presentation

GET BELOW - 4 Alternative Study Courses For FREE :

SCM500 - Processes in Procurement ( Col92 - 2009/Q2 )

SCM600 - Sales & Distribution Processes ( Col92 - 2009/Q2 )

SCM601 - Processes in Logistics Execution ( Col92 - 2009/Q2 )

SCM611 - Shipments ( Col92 - 2009/Q2 )

Friday, January 13, 2012

Search for SAP Basis Transaciton codes

SAP Administrator Daily Activities

SAP Administrator Daily Activities
SAP DAILY ACTIVITIES
1] Check that all the application servers are up:
sm51 SAP Servers
sm04/al08 Logon Users
2] Check that daily backup are executed without errors
db12 Backup logs: overview
3] SAP standard background jobs are running successfully. Review for cancelled and critical jobs.
sm37 Background jobs--- Check for successful completion of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.
4] Operating system Monitoring
st06
5] Extents monitoring
db02 Database monitoring--Check for max-extents reached
6] Check work-processes(started from sm51)
sm50 Process overview-- All work processes with a running or waiting status.
7] Check system log
sm21 System log-- Set date and time to before the last log review. Check for errors ,warning, security, message-bends, database events.
8] Review workload statistics
st03 Workload analysis of
sto2 tune summary instance
9] Look for any failed updates
sm13 update records
10] check for old locks
sm12 lock entry list
11] Check for spool problems
sp01 spool request screen-- check for spool that are in request for over an hour.
12] Review and resolve dumps
st22 ABAP Dump analysis
13] Checking .trc file in SAP trace directory for block corruption on daily basis.
C:\ORacle\sid\saptrace
14] Archive backup
brarchive -f force -cds -c
Insert the archive backup tape
15] Review NT system logs for problem
-> NT system log- look 4 errors or failures
-> NT security log- failed logon 2 sap servers
-> NT Application log -look 4 errors or failures

Tcodes used for Daily System Monitoring

Tcodes used for Daily System Monitoring
After running daily system monitoring transaction, what should we check for:
In st22 look for the core dumps if any and report to the respective consultants and try to know why it happened.
In sm21 try to check for errors.
In sp01 try to see if any spool jobs have failed.
In st02 look if any swaps are happening, swaps are not good for performance.
In st04 look for Database alert logs and Performance.
In st03 look for ratio hits.
In sm59 look for connectivety tesing if there are other systems also connected to your SAP R/3 system
In db13 look if the jobs have run successfully.
In sm37 look for any cancelled scheduled job and take action appropriately.
In sm12 look for any pending locks from the previous days.
In sm13 look for any hanged updates, or updates pending for long or updates in PRIV mode.

How to know or get the Kernel Version of SAP system

Posted by Basis-Consultant | 1:21 PM | Basis, how to's, Security | 1 comments »

There are many ways through which you can get the Version Number of SAP Kernel.
One of the method is from any window in the top menu go to
system--> status and click on the other kernel info button which is between the navigate and cancel buttons.

Another method is to login as administrator and enter the following disp+work -v. in command field on left top corner. This will show you the kernel version of SAP.

You can also check the log or trace files at os level /usr/sap/work/dev_disp.

You can also get this kernel information from sm51 screen. Go to transaction sm51 then click on database server (single click only. Not double click) and then click on release notes. Then you will see the kernel information and patch level.

Backup profile for SAP ECC6 + Oracle

Backup profile for SAP ECC6 + Oracle
This is my sample backup profile (initSID.sap) for taking disk backup on path /local/
backup_mode = all
restore_mode = all
backup_type = online
backup_dev_type = disk
backup_root_dir = /local/BKP
stage_root_dir = /oracle/SID/sapbackup
compress = yes
compress_cmd = "compress -c $ > $"
uncompress_cmd = "uncompress -c $ > $"
compress_dir = /oracle/SID/sapreorg
archive_function = save
archive_copy_dir = /local/arch
archive_stage_dir = /local/arch
tape_copy_cmd = cpio
disk_copy_cmd = copy
stage_copy_cmd = rcp
cpio_flags = -ovB
cpio_in_flags = -iuvB
cpio_disk_flags = -pdcu
dd_flags = "obs=64k bs=64k"
dd_in_flags = "ibs=64k bs=64k"
saveset_members = 1
copy_out_cmd = "dd ibs=8k obs=64k of=$"
copy_in_cmd = "dd ibs=64k obs=8k if=$"
rewind = "mt -f $ rew"
rewind_offline = "mt -f $ offline"
tape_pos_cmd = "mt -f $ fsf $"
tape_size = 1200M
exec_parallel = 0
tape_address = /dev/rmt/0mn
tape_address_rew = /dev/rmt/0m
volume_archive = (SIDA01, SIDA02, SIDA03, SIDA04, SIDA05,
SIDA06, SIDA07, SIDA08, SIDA09, SIDA10,
SIDA11, SIDA12, SIDA13, SIDA14, SIDA15,
SIDA16, SIDA17, SIDA18, SIDA19, SIDA20,
SIDA21, SIDA22, SIDA23, SIDA24, SIDA25,
SIDA26, SIDA27, SIDA28, SIDA29, SIDA30)
volume_backup = (SIDB01, SIDB02, SIDB03, SIDB04, SIDB05,
SIDB06, SIDB07, SIDB08, SIDB09, SIDB10,
SIDB11, SIDB12, SIDB13, SIDB14, SIDB15,
SIDB16, SIDB17, SIDB18, SIDB19, SIDB20,
SIDB21, SIDB22, SIDB23, SIDB24, SIDB25,
SIDB26, SIDB27, SIDB28, SIDB29, SIDB30)
expir_period = 30
tape_use_count = 100

SAP Kernel Upgrade

SAP Kernel Upgrade
SAP Kernel Upgrade Tutorial step by Step:
1. Login as root
2. Make new backup directory
cd /
mkdir SIDkernel_10102007
3. Create latest kernel backup
cp -pr /sapmnt/SID/exe/* /SIDkernel_10102007
4. Compare size of the original kernel and the backup
du -sk /sapmnt/SID/exe/
=>840413 /sapmnt/SID/exe
du -sk /SIDkernel_10102007
=>840413 /SIDkernel_10102007
5. Make new shadow kernel directory
cd /
mkdir newkernel_175
6. Copy the new downloaded kernel files into /newkernel_175
7. Unpack the new downloaded kernel in folder /newkernel_175
/sapmant/SID/exe/SAPCAR -xvf SAPEXE_175-20000221.SAR
/sapmant/SID/exe/SAPCAR -xvf SAPEXEDB_175-20000223.SAR
8. Login as sidadm
9. Stop the SAP System
stopsap
10. Stop saposcol
saposcol -k
11. Go to the current kernel directory
Login as root
cd /sapmnt/SID/exe
12. Copy all extracted support packages into this folder
cp -pr /newkernel_175/* /sapmnt/SID/exe13.
13. Change file permission of files into kernel folder
cd /sapmnt/SID/exe
chown SIDadm:sapsys ./*
14. Copy back the original file from backup saproot.sh into this folder.
cp -p /SIDkernel_10102007/saproot.sh /sapmnt/SID/exe
15. Login as SIDadm with root privilege
Login as SIDadm
su root
16. Go to the current kernel directory
cd /sapmnt/SID/exe
Then execute:
./saproot.sh SID
Solaris Error (refer SAP Note 420417):
# ./saproot.sh SID
> ./saproot.sh: whoami: not found
> ./saproot.sh: test: argument expected
Solution:
#PATH=/usr/ucb:$PATH
#./saproot.sh <SID>
Again execute:
disp+work
17. Start the saposcol service
Login as sidadm
saposcol
18. Start the SAP system
startsap

How lock and unlock client in sap to prevent user login

How lock unlock client in sap to prevent user login
This is a workaround to lock a client to prevent user to login during patching or any maintenance activity of SAP R/3 (ECC 6.0). Example with detaile are given below:-
Client locking:-----------
SE37->SCCR_LOCK_CLIENT
Press Run/Test (look like ZIP file button)
enter your Client No. i.e. 210/300/500/900 etc
Press Execute button only.
Done
Client Unlocking:-----------
Client lock-> SE37->SCCR_UNLOCK_CLIENT
Press Run/Test (look like ZIP file button)
enter your Client No. i.e. 210/300/500/900 etc
Press Execute button only.
Done
Best of Luck

Enable Audit to sys user to SYSLOG in Oracle 10g

Enable Audit to sys user to SYSLOG in Oracle 10g
Workaround to Enable Audit to sys user to SYSLOG
Oracle 9i onward, we have new feature to enable audit for sysdba privilege users. Record Audition writes to the system audit log.
This is an example to audit sys user to SYSLOG utility.
Edit syslog.conf and insert below line.
vi /etc/syslog.conf
Step 1
# vi /etc/syslog.conf
user.notice /var/log/syslog-orcl
# touch /var/log/syslog-orcl
Syntax to Restart syslog etc/init.d/syslog restart
Step 2
# /etc/init.d/syslog restart
Shutting down kernel logger: [ OK ]
Shutting down system logger: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
Syntax to Modify AUDIT_SYSLOG_LEVEL initialization parameter on Database
AUDIT_SYSLOG_LEVEL = facility.level
Here the value of facility can be any of the below:
USER, LOCAL0-LOCAL7, SYSLOG, DAEMON, KERN, MAIL, AUTH, LPR, NEWS, UUCP or CRON.
The value of level can be any of the following: NOTICE, INFO, DEBUG, WARNING, ERR, CRIT, ALERT, EMERG .
Examples:
SYS> show parameter AUDIT_SYSLOG_LEVEL
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
audit_syslog_level string
SYS> alter system set audit_syslog_level='user.notice' scope=spfile;
System altered.
Restart Oracle instance
SYS> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS> startup
ORACLE instance started.
Total System Global Area 810053632 bytes
Fixed Size 2217712 bytes
Variable Size 645925136 bytes
Database Buffers 155189248 bytes
Redo Buffers 6721536 bytes
Database mounted.
Database opened.
Where and How to see log file?
# tail -f /var/log/syslog-orcl
Feb 27 11:37:39 RHEL5-ORQS Oracle Audit[18624]: LENGTH : '155' ACTION :[7] 'STARTUP' DATABASE USER:[1] '/' PRIVILEGE :[4] 'NONE' CLIENT USER:[6] 'oracle' CLIENT TERMINAL:[13] 'Not Available' STATUS:[1] '0' DBID:[0] ''
Feb 27 11:37:39 RHEL5-ORQS Oracle Audit[18827]: LENGTH : '148' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'oracle' CLIENT TERMINAL:[5] 'pts/1' STATUS:[1] '0' DBID:[0] ''
Test to Logon by sys: $ sqlplus "/ as sysdba"
SYS>
Syslog after logging as sysdba
# tail -f /var/log/syslog-orcl
Feb 27 11:40:12 RHEL5-ORQS Oracle Audit[19269]: LENGTH : '159' ACTION :[7] 'CONNECT' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'oracle' CLIENT TERMINAL:[5] 'pts/1' STATUS:[1] '0' DBID:[10] '1233539256'
Syntax to Audit sys operation (audit_sys_operations=true):
Example to display current value
SYS> show parameter audit_sys_operations
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
audit_sys_operations boolean FALSE
Example to enable Audit or set true
SYS> alter system set audit_sys_operations=TRUE scope=spfile;
System altered.
SYS> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SYS> startup
ORACLE instance started.
Total System Global Area 810053632 bytes
Fixed Size 2217712 bytes
Variable Size 645925136 bytes
Database Buffers 155189248 bytes
Redo Buffers 6721536 bytes
Database mounted.
Database opened.
Test Query with sysdba privilage: SYS> select count(*) from v$session;
COUNT(*)
----------
105
1 row selected.
Syslog after logging as sysdba
# tail -f /var/log/syslog-orcl
Feb 27 11:49:19 RHEL5-ORQS Oracle Audit[20698]: LENGTH : '183' ACTION :[30] 'select count(*) from v$session' DATABASE USER:[1] '/' PRIVILEGE :[6] 'SYSDBA' CLIENT USER:[6] 'oracle' CLIENT TERMINAL:[5] 'pts/1' STATUS:[1] '0' DBID:[10] '1233539256'
Enjoy it........................

How to auto start or run SAP Instance?

How to auto start or run SAP Instance?
This solution is only applicable to windows server.
1. RZ10
2. Select Startup profile
3. Create parameter autostart
4. Put value 1
5. Copy
6. Save and activate
7. Logout
8. Stop Instance
9. Restart Server
This time it will automatically start SAP Instance.

Regards,
Alihamed.sa

Tuesday, January 10, 2012

Email configuration in sap , Incoming Mail or Inbound mail configuration in SAP ECC 6.0 hp-ux Servers or windows servers

Incoming Email Configuration In SAP Document in below Url Please download it.

http://okfiles.net/file/0S3IJ

Email configuration in sap , Incoming Mail or Inbound mail configuration in SAP ECC 6.0 hp-ux Servers or windows servers

Email configuration in sap

Incomming mail or inbound mail configuration SAP ECC6.0 .

Rz10 tcode

Create below prameters.

1) Tcode sicf

Create a smail “service user id” . which client will recevie email.

Profile S_A.SCON.

Tcode : scot

Connection between Exchange server to SAP Server.

1) Create DNS record on domain dns server.

Create A record in DNS server

2) Create MX record finding mail server

3) Add a 192.168.1.68:25000 port to ironport.

Regards,

Alihamed.sa
+919912803500
myhomebasis@gmail.com