Posted by Della on December 8, 2009
Several days ago we are facing an error when uploading foto on tcode OAAD with this error :

Please make sure to do :
1. SICF –> restart content server interface (deactivate – activate)

2. SMICM –> make sure ICM Status = running

Also you have to look at the log trace file –> Goto –> Trace File –> Display All
When I check the log, I’ve got this error message :
Thr 1029 *** ERROR => Connection request from (-1/65535/0) to host: casapdev.capcx.com, service: 8020 failed (NIEHOST_UNKNOWN)
Thr 1029 *** ERROR => IcmJ2EEScheduleFunc: Connection to casapdev.capcx.com:8020 failed – please check host configuration (-8)
So, I have 2 problem:
1. Cannot connect to HTTP
2. Wrong hostname
Here is the steps to fix the problem :
1. SE16 –> Create the following entry in the SDOKPROF table:
NAME: USEHTTPPLG
VALUE: OFF
2. RZ10 -> Check icm/host_name_full –> should be blank (not casapdev.capcx.com)
3. Restart sap r3
But there is another error after we restarting the sap r3 –> “HTTP error: 401 Unauthorized”
what we are doing is :
1. Give authorization to client 230 on SICF –> Content Server

2. Activate certificate on OAC0

–> Environment –> CS Admin

Klik icon Activate
Finish
Posted in HTTP Error | Tagged: error when uploading photo on OAAD, error when uploading photo on OAOH, IF_HTTP_CLIENT->RECEIVE 1 ICM_HTTP_CONNECTION_FAILED, OAAD, OAOH, SICF, upload photo error + SAP | Leave a Comment »
Posted by Della on November 17, 2009
To disable multiple user logins within the same client implement this parameter in the instance profile:
Disable MultipleDisable Multiple Logins in the Same Client
To disable multipDisable Multiple Logins in the Same Client
To disable multiple user logins within the same client implement this parameter in the instance profile:
login/disable_multi_gui_login = 1
If you do not use this parameter in your system, users have the ability to ignore the warning window at the time they try to login to the same client.le user logins within the same client implement this parameter in the instance profile:
login/disable_multi_gui_login = 1
If you do not use this parameter in your system, users have the ability to ignore the warning window at the time they try to login to the same client. Logins in the Same Client
To disable multiple user logins within the same client implement this parameter in the instance profile:
login/disable_multi_gui_login = 1
If you do not use this parameter in your system, users have the ability to ignore the warning window at the time they try to login to the same client.
login/disable_multi_gui_login = 1
If you do not use this parameter in your system, users have the ability to ignore the warning window at the time they try to login to the same client.
How about exceptional logins?
In case you’re wondering how to allow multiple logins for certain key users you can implement parameter login/multi_login_users. You can list the user IDs that should be ignored if the parameter above is active in your system.
Posted in Others | Tagged: disable multiple logon, multiple logon, prevent logon | Leave a Comment »
Posted by Della on November 17, 2009
Do you need to do maintenance on a system and want to make sure nobody logs on to it while you’re working on it?
You can lock a system at the OS level by running: tp locksys pf=tpprofile
Example: To lock your DEV system enter this command: tp locksys DEV pf=saptranshostsapmnttransbintp_domain_dev.pfl
Users will get this message if they attempt to log on: “Upgrade still running. Logon not possible”.
Notice that the message is not exactly accurate. TP locksys is mainly used during release upgrades so the message is kind of generic. But, it works!
To unlock the system, run: tp unlocksys pf=tpprofile
Now you can tell your boss that you know how to keep the users off the system!
Only SAP* and DDIC can log on to any of the clients in the system that has been locked.
For detail information go to the following link http://sapdocs.info/sap/uncategorized/frequently-used-procedures-in-sap/
Posted in Others | Tagged: lock client | Leave a Comment »
Posted by Della on November 17, 2009
The Security Audit Log is a tool designed for auditors who need to take a detailed look at what occurs in the SAP System. By activating the audit log, you keep a record of those activities you consider relevant for auditing. You can then access this information for evaluation in the form of an audit analysis report.
The audit log’s main objective is to record:
- Security-related changes to the SAP System environment
(for example, changes to user master records)
- Information that provides a higher level of transparency
(for example, successful and unsuccessful logon attempts)
- Information that enables the reconstruction of a series of events
(for example, successful or unsuccessful transaction starts)
Specifically, you can record the following information in the Security Audit Log:
- Successful and unsuccessful dialog logon attempts
- Successful and unsuccessful RFC logon attempts
- RFC calls to function modules
- Successful and unsuccessful transaction starts
- Successful and unsuccessful report starts
- Changes to user master records
- Changes to the audit configuration
To configure the audit log –> sm19
To see the audit log –> sm20
To delete old log –> sm 18
Before you activate the audit log you have to setup several parameters in RZ10 :
rsau/enable: Set to 1 to activates audit logging
rsau/local/file: Name and location of the audit log file
rsau/max_diskspace/local: Max. space of the audit file. If maximum size is reached auditing stops.
rsau/selection_slots: Max. number of filters
rsau/enable: Set to 1 to activates audit loggingrsau/local/file: Name and location of the audit log filersau/max_diskspace/local: Max. space of the audit file. If maximum size is reached auditing stops.rsau/selection_slots: Max. number of filters
the maximum size of an audit file is 2 gigabytes for a single day, so the in case of profile parameter rsau/max_diskspace/local the min value is 1000000kb & maximum value is 2GB
For profile parameter rsau/max_diskspace/per_file minimum is 1MB & Maximum is 2 GB
For rsau/max_diskspace/per_day minimum value should be 3*per_file & maximum 1024 GB.So check these parameter.
For more detail see the following page http://help.sap.com/saphelp_nw04/helpdata/EN/2c/c59d37d373243de10000009b38f8cf/frameset.htm
Posted in Log File | Tagged: audit file, audit on SAP, SAP audit, SAP security audit, security audit, sm18, sm19, sm20 | Leave a Comment »
Posted by Della on October 1, 2009
to change professional user to limited users do the following step :
1. USMM
System Data :
–> Production
Clients :
–> choose the client you want to classify
Price Lists :
Choose mySAP.com Solution Suite
Then click User Classification –> F8
select users then click Classify Selected Users
done
Posted in Others | Tagged: limited user, professional user, user sap license | Leave a Comment »
Posted by Della on July 9, 2009
If some user can not export data to excel file while others can, so you have to check if there is a window like this before saving the data (for exampe YCAVQ0005)
When you click Export icon like this

Export to Spreadsheet
after you choose Spreadsheet, system will display a small window like this

Select Spreadsheet
after you klik OK, system will display

Save As
For some user there is no Select Spreadsheet window, and the saving data will failed like this

what should you do?
On the Export Spreadsheet screen, right click on a cell in the data section of your report, for example, on DN Number then Select Spreadsheet, after that the Select Spreadsheet window will appear
Posted in Others | Tagged: can not export to excel, error export XML, error when export data to excel, error when export data to XML, export to excel error, export to excel failed, select spreadsheet | Leave a Comment »
Posted by Della on June 23, 2009
Job name –> Program –> Variant –> Repeat interval
*** SAP_REORG_JOBS –> RSBTCDEL2 –> yes –> daily
*** SAP_REORG_SPOOL –> RSPO0041/1041 –> yes –> daily
*** SAP_REORG_BATCHINPUT –> RSBDCREO –> yes –> daily
*** SAP_REORG_ABAPDUMPS –> RSSNAPDL –> yes –> daily
*** SAP_REORG_JOBSTATISTIC –> RSBPSTDE –> yes –> monthly
***SAP_COLLECTOR_FOR_JOBSTATISTIC –> RSBPCOLL –> no –> daily
*** SAP_COLLECTOR_FOR_PERFMONITOR –> RSCOLL00 –> no –> hourly
*** SAP_COLLECTOR_FOR_NONE_R3_STAT –>RSN3_STAT_COLLECTOR –> no –> hourly
***SAP_REORG_PRIPARAMS –> RSBTCPRIDEL –> no –> monthly
***SAP_REORG_XMILOG –> RSXMILOGREORG –> yes –> weekly
*** SAP_CCMS_MONI_BATCH_DP –> RSAL_BATCH_TOOL_DISPATCHING –> no –> hourly
*** SAP_SPOOL_CONSISTENCY_CHECK –> SPO1043 –> yes –> daily
*** SAP_REORG_ORPHANED_JOBLOGS –> RSTS0024 –> yes –> weekly
Posted in background job | Tagged: background job | Leave a Comment »
Posted by Della on June 23, 2009
Here is a brief description about Full Backup, Incremental Backup, All Backup
backup_mode = full
This is a full database backup. It is also referred to as a level 0 backup. This backup contains all database files (for offline backup, as well as the online redo log files) and is used as the basis for your following incremental backups.
backup_mode = incr
This is an incremental database backup. It is also referred to as a level 1 backup. This backup contains only the Oracle blocks of all database files that have been changed since the last full backup (for offline backup, as well as the online redo log files).
Compare:
backup_mode = all
This is a whole database backup. This backup contains all database files (for offline backup as well as the online redo log files), yet it cannot serve as the basis for your following incremental backups. Therefore, the scope of the backup is the same as a full backup. The main difference to a full backup is that a full backup is additionally flagged as level 0 in the Oracle control file.
Full backups and whole backups are referred to as complete backups.
Partial (backup_mode = <Object_list>) and whole backups (backup_mode = all) are also referred to as normal backups because they cannot be part of an incremental backup strategy.
Normal and full backups can be performed with or without RMAN (see init<SID>.sap parameter tape_copy_cmd or disk_copy_cmd). Incremental backups are always performed with RMAN.
Posted in Backup | Tagged: all backup, full backup, incremental backup | Leave a Comment »
Posted by Della on June 23, 2009
Here is the step by step how to know the kernel version on your SAP System

click system - status

click arrow button beside navigate button

see Kernel Information
Posted in Patches | Tagged: how to know kernel version, kernel, kernel SAP, kernel version | Leave a Comment »
Posted by Della on June 8, 2009
On Friday (June, 5 2009) when I check file system on our CI server, I saw that our sapmnt/CAP almost full (againnn??), only 5% left
… and then I check our background job for SAP_REORG_JOBS to check what program that running this job, because this job supposed to delete old jobs.
The ABAP program that runs SAP_REORG_JOBS is RSBTCDEL!
Then I try to create the new one (in sm36) with RSBTCDEL2 program, but the step in sm36 couldn;t continue until you fill the variant for this jobs.
Today I found the website about how to create variant for RSBTCDEL2. Here it is how to create variant
Posted in Log File | Tagged: /sapmnt/, /sapmnt/ full, /sapmnt/SID, /sapmnt/SID full | Leave a Comment »