SAP NW Basis Tips and Advices

Application Log / History of SAP Logical System Conversion (BDLS)

2012-01-04T11:55:00.000-08:00

You might be wondering that there is no option to view the history of the conversions which were made from transaction BDLS. To check the logs follow the below procedure,

1. Goto transaction SLG1
2. Object: CALE
3. SubObject: LOGSYSNAME
4. Enter the Date Criteria and Hit F8.

Thanks,
Kamesh

Install Apache Tomcat 6.0.32 (Linux)

2011-08-17T20:30:00.000-07:00

1) Download the Tomcat software from the location below,

http://apache.opensourceresources.org/tomcat/tomcat-6/v6.0.32/bin/apache-tomcat-6.0.32.tar.gz

2) Login to Putty and sudo to user "otxuser" (used to run application) and makesure JAVA_HOME environment variable is setup.

3) Change the permission of the file downloaded to be executable.
# chmod a+x apache-tomcat-6.0.32.tar.gz

4) Change to the directory in which Tomcat is to be installed.
# cd /home/otxuser

5) Run the self-extracting binary.
# tar xvfz apache-tomcat-6.0.32.tar.gz

6) Tomcat is installed into its own directory.

Path: /home/otxuser/apache-tomcat-6.0.32

7) Adapt the default Port Number by editing

/home/otxuser/apache-tomcat-6.0.32/conf/server.xml.

8) Shutdown Tomcat
# ./shutdown.sh

9) Start Tomcat
# ./startup.sh

10) Confirm that tomcat is running by checking the process.

# ps –ef | grep tomcat

Add remote Oracle Database in DBACOCKPIT

2011-08-08T19:03:00.000-07:00

Follow the below steps to add a remote oracle database in DBACOCKPIT.

Scenario:

System A wants to have the database information of System B added in DBACOCKPIT (System A).System A – DS1

System B – QE1

Steps:
1. Update the tnsnames.ora file at the below locations,

Application Server of System A:

/usr/sap/DS1/SYS/profile/oracle

Database Server of System A:

/oracle/DS1/112_64/network/admin

QE1,QE1.WORLD=

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS =

(COMMUNITY = SAP.WORLD)

(PROTOCOL = TCP)

(HOST = <hostname>)

(PORT = <listener_port>)

)

(CONNECT_DATA =

(SID = QE1)

(GLOBAL_NAME = QE1.WORLD)

)

2. Make sure tnsping QE1 is working fine from the database server & application server (if full oracle client is installed - if only instant client is installed then tnsping would not be available),

orads1> tnsping QE1
TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 08-AUG-2011 20:52:28
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
/oracle/DS1/112_64/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = <hostname>) (PORT = <listener_port>))) (CONNECT_DATA = (SID = QE1) (GLOBAL_NAME = QE1.WORLD)))
OK (10 msec)
orads1>

3. Goto transaction DBACOCKPIT in System A (DS1), Click the DB Connection on the left.

Enter System ID

Select Database Connection

Enter a name for the Database Connection

Enter the description for Administration Data

Click the Create Button next to Database Connection Name.

4. Enter the below details,

Connection Name - Should auto populate from previous screen
Database system - Oracle (Select from drop down)
Connection Maximum - 0
Connection Optimum - 0
User Name - SYSTEM
Password - <SYSTEM User Password>
Confirm - <Same as above>
Enter TNS NAME - SID or the connection string.
Click Save.

Click Save again

5. Connection to remote database is complete.

Add Custom Logo to SAP Initial Screen

2011-07-30T02:55:00.000-07:00

Goto transaction SMW0.

Select "Binary Data for WebRFC Application"

Click

Execute (F8) without entering anything on the resulting screen.

Settings -> Maintain MIME Types and Create an entry for the Extension of the Image to be uploaded.

Click

Enter an Object Name and its Description.

Clickand Browse for the Logo.

Save it as Local ($tmp) or in one of the Project Packages.

Goto Transaction /nSM30 or /nSM31 and Enter Table Name SSM_CUST and Click MAINTAIN.

Make an entry as below for START_IMAGE with the name of the Object created in SMW0.

SSO to CRM WebUI with user credentials of SAP GUI

2011-07-30T01:38:00.000-07:00

Follow the below steps to implement the SSO to CRM WebUI via, SAPGUI for Windows.

1) Implement Note: 1467488

With this note the ABAP report BSP_WD_APPL_STARTER gets an additional checkbox which enables the single sign-on mechanism. The SAP GUI user credentials will be used for the WebClient UI session as well.

This note has got the following manual steps to be performed.

TCode: SE38

Program: BSP_WD_APPL_STARTER

Goto -> Text Elements -> Text Symbols

Create the text symbol 009.

Short Text: Single sign-on

Activate your change.

TCode: SE91

Display the message of message class BSP_WD.

Create the message 027.

Short text in EN: The service '&1' is inactive. Use transaction SICF for activation

Save the message.

Once the above manual steps are performed, implement the SAP Note via, SNOTE.

2) Create a new variant ZSAP_CRMUI for the report BSP_WD_APPL_STARTER with the below settings,

BSP Application: CRM_UI_START

In Client: <xxx>

New Browser Window: <Check Mark>

Single sign-on: <Check Mark>

3) Goto tcode SE93 to make the changes shown as below to CRM_UI transaction.

In the default Values section,

Name of Screen Field: D_SREPOVARI-VARIANT

Value: ZSAP_CRMUI

4) Make sure the below parameters are in place,

Update SAP Kernel in Linux / Oracle

2011-07-30T01:18:00.000-07:00

Prelimiary Steps:

1) Stop SAP

2) Kill all processes of SAP

3) Stop DB

Extract Kernel:

1) Location of Kernel SAR Files: /<Any Location>/Kernel_<xx>

2) Make directory to extract the Kernel files.

mkdir Kernel<xx>

3) ./SAPCAR –xvf DBATL<>_<>.SAR -R ./Kernel<xx>

4) ./SAPCAR -xvf SAPEXEDB_<>.SAR -R ./Kernel<xx>

5) ./SAPCAR -xvf SAPEXE_<>.SAR -R ./Kernel<xx>

Replace Kernel:

1) cp –af /<Any Location>/Kernel_<xx>/Kernel<xx>/* /sapmnt/<SID>/exe/

2) cd /sapmnt/<SID>/exe

3) ./saproot.sh <SID> [Note: Execute this as user root]

Start DB and then Start SAP.

If SAP won't come up try the solution provided below in the APPENDIX.

APPENDIX:

Make sure after the Kernel update all of the below locations are of same Patch Level.

LOCATION 1: /sapmnt/<SID>/exe

LOCATION 2: /usr/sap/<SID>/<Instance>/exe

You would have replaced the kernel at LOCATION 1, but the kernel at LOCATION 2 will still remain at old level which will prevent the access to database. So replace the kernel at LOCATION 2, and then try start SAP it should work.

Assigns SLD Roles to Administrator Groups

2011-07-24T14:32:00.000-07:00

a. Start the SAP NetWeaver Administrator.

http://<hostname>:5<nn>00/nwa

Where <nn> is Instance Number.

Choose Configuration -> Security -> Identity Management

Add SAP_SLD_ADMINISTRATOR role to SAP_J2EE_ADMIN group.

Add SAP_SLD_ADMINISTRATOR role to SAP_SLD_ADMINISTRATOR group.

Add SAP_SLD_GUEST role to SAP_J2EE_GUEST group.

Add SAP_SLD_GUEST role to SAP_SLD_GUEST group.

Execution of User Management

2011-07-24T14:10:00.000-07:00

Create and assign PI dialog and service users.

User	Type	User Required for	Role
PILSADMIN	System	Change Management Server	SAP_XI_CMS_SERV_USER
PIDIRUSER	System	Integration Directory	SAP_XI_ID_SERV_USER
			SAP_XI_ID_SERV_USER_MAIN
			SAP_SLD_CONFIGURATOR
			SAP_BC_WEBSERVICE_PI_CFG_SRV
PIREPUSER	System	Enterprise Services Repository	SAP_XI_IR_SERV_USER
			SAP_XI_IR_SERV_USER_MAIN
			SAP_SLD_CONFIGURATOR
PILDUSER	System	System Landscape Directory	SAP_BC_AI_LANDSCAPE_DB_RFC
PIAPPLUSER	System	sender applications	SAP_XI_APPL_SERV_USER
			SAP_BC_WEBSERVICE_PI_CFG_SRV
PIRWBUSER	System	Runtime Workbench	SAP_XI_RWB_SERV_USER
			SAP_XI_RWB_SERV_USER_MAIN
			SAP_SLD_CONFIGURATOR
PIAFUSER	System	Advanced Adapter Engine	SAP_XI_AF_SERV_USER
			SAP_XI_AF_SERV_USER_MAIN
			SAP_SLD_CONFIGURATOR
			SAP_BC_WEBSERVICE_PI_CFG_SRV
PIISUSER	System	Integration Server	SAP_XI_IS_SERV_USER
			SAP_XI_IS_SERV_USER_MAIN
			SAP_SLD_CONFIGURATOR
PISUPER	Service	Super user with authorization for all involved tasks	SAP_BC_AI_LANDSCAPE_DB_RFC
			SAP_BC_ALM_ADMIN
			SAP_BC_ALM_ALERT_USER
			SAP_BC_ALM_CUST
			SAP_BC_BASIS_ADMIN
			SAP_BC_BASIS_MONITORING
			SAP_BC_WEBSERVICE_ADMIN
			SAP_NWA_FULL
			SAP_SLD_ADMINISTRATOR
			SAP_XI_ADMINISTRATOR
			SAP_XI_BPE_ADMINISTRATOR_ABAP
			SAP_XI_BPE_CONFIGURATOR_ABAP
			SAP_XI_BPE_MONITOR_ABAP
			SAP_XI_CONFIGURATOR
			SAP_XI_CONTENT_ORGANIZER
			SAP_XI_DEVELOPER
			SAP_XI_MONITOR
PI_JCO_RFC	System	RFC communication between ABAP and Java	SAP_BC_JSF_COMMUNICATION_RO
PIPPUSER	System	Principal Propagation	SAP_XI_APPL_SERV_USER
PICACHEUSER	System	Cache Update	PICACHEUSER
			SAP_BC_WEBSERVICE_PI_CFG_SRV
PI3RDAPIUSER	System	User for calling a Java Web service and is used to set up point-to-point connections	SAP_XI_CONFIGURATOR
			SAP_XI_CONFIGURATOR_EXT_J2EE
SAPJSF	Service	communication between AS ABAP and AS Java	SAP_BC_JSF_COMMUNICATION

Generates Profiles for ABAP Roles

2011-07-24T14:05:00.000-07:00

Goto Transaction SUPC as an administration user in Client 001.

a) Select All Roles -> In the Role field, search for SAP_XI_* -> Choose Execute.

Check that the following roles are present:

SAP_XI_ADMINISTRATOR_ABAP

SAP_XI_ADMINISTRATOR_J2EE

SAP_XI_APPL_SERV_USER

SAP_XI_BPE_ADMINISTRATOR_ABAP

SAP_XI_BPE_CONFIGURATOR_ABAP

SAP_XI_BPE_MONITOR_ABAP

SAP_XI_BPE_SERV_USER

SAP_XI_CMS_SERV_USER

SAP_XI_CONFIGURATOR_ABAP

SAP_XI_CONFIGURATOR_J2EE

SAP_XI_CONTENT_ORGANIZER_ABAP

SAP_XI_CONTENT_ORGANIZER_J2EE

SAP_XI_DEMOAPP

SAP_XI_DEVELOPER_ABAP

SAP_XI_DEVELOPER_J2EE

SAP_XI_DISPLAY_USER_ABAP

SAP_XI_DISPLAY_USER_J2EE

SAP_XI_ID_SERV_USER

SAP_XI_ID_SERV_USER_MAIN

SAP_XI_IR_SERV_USER

SAP_XI_IR_SERV_USER_MAIN

SAP_XI_IS_SERV_USER

SAP_XI_MESSAGE_MODIFY

SAP_XI_MONITOR_ABAP

SAP_XI_MONITOR_J2EE

SAP_XI_RWB_SERV_USER

SAP_XI_SUPPORT_ABAP

SAP_XI_SUPPORT_J2EE

Select the desired rows in the table and choose Generate profile.

b) Select All Roles -> In the Role field, search for SAP_BC_* -> Choose Execute.

Check that the following roles are present:

SAP_BC_AI_LANDSCAPE_DB_RFC

SAP_BC_JSF_COMMUNICATION_RO

SAP_BC_WEBSERVICE_PI_CFG_SRV

SAP_BC_ALM_*

SAP_BC_BASIS_*

Select the desired rows in the table and choose Generate profile.

c) Select All Roles -> In the Role field, search for SAP_SLD_* -> Choose Execute.

Check that the following roles are present:

SAP_SLD_ADMINISTRATOR

SAP_SLD_CONFIGURATOR

SAP_SLD_CONTENT_SYNC

SAP_SLD_DATA-SUPPLIER

SAP_SLD_DEVELOPER

SAP_SLD_GUEST

SAP_SLD_ORGANIZER

SAP_SLD_SUPPORT

Select the desired rows in the table and choose Generate profile.

Install SAP Business Objects 4.0 (SBOP BI PLATFORM 4.0) Linux/Oracle 11gR2

2011-07-24T13:07:00.000-07:00

Navigate to the software location and start the install script
$cd /swdc/SBOP_BI_PLATFORM_4.0/51040483/DATA_UNITS/BusinessObjectsServer_linux
./setup.sh

Specify the Destination Folder
/home/businessobjects/

Prerequisite Checking
The installation program checks for required components and conditions

Welcome to the SAP BusinessObjects Enterprise Installation Wizard

Accept the "Business Objects License Agreement"

Enter the Product Key Code for the installation

Select a language for the installation and press ENTER

Select a User Install or a System Install
1 - User Install - Regular BusinessObjects Enterprise Installation
2 - System Install - User Install Plus System Initialization Scripts
Note: System Install requires root access to run initialization scripts after install

Choose Install Type
1 - Full
2 - Custom / Expand
3 - Web Tier

Select Default or Existing Database
1 - Install and Use Default Database
2 - Use an Existing Database

Select existing CMS Database type
1 - MySQL
2 - IBM DB2
3 - Oracle
4 - MaxDB
5 - Sybase

Select existing Auditing Database type
1 - MySQL
2 - IBM DB2
3 - Oracle
4 - MaxDB
5 - Sybase
6 - No Auditing Database

Select Java Web Applications1 - Install Tomcat Application Server and Automatically Deploy Web Applications
and Services to it
2 - Manually Deploy to a PreInstalled Web Application Server

Configure LifeCycle Manager - Select a Version Control System for LifeCycle Manager
1 - Install and Use SubVersion
2 - Use an Existing Version Control system. You will need to manually
configure LifeCycle Manager to use your existing Version
Management System After Installation.

SIA and Smart Server Configuration
Server Intelligence Agent Node Name: SIA_<SID>
Server Intelligence Agent Port Number: 6410

Configure Central Management Server
CMS Port Number: 6400

Configure CMS Account
Administrator Account Password: <Standard Password>
Confirm Password: <Standard Password>
Cluster Key: <Standard Password>
Confirm Cluster Key: <Standard Password>
Note: Cluster Key is required to be able to cluster any node with CMS in future.
If in case you've forgot the Key use the below procedure to create a new one.
1 - Stop the Master SIA
2 - Under Properties, Click Change for Cluster Information
3 - It would then prompt for New Cluster Key

Configure CMS Repository Database - Oracle
Oracle TNSNAME: <DB_SID> [The Identifier from the tnsnames.ora located at the
/<Oracle Client Location>/network/admin at App Server]
Username: boecms
Password: <Standard Password>
Reset Existing Database (Y - Yes; N - No): Y

Configure CMS Auditing Database - Oracle
Oracle TNSNAME: <DB_SID> [The Identifier from the tnsnames.ora located at the
/<Oracle Client Location>/network/admin at App Server]
Username: boeaud
Password: <Standard Password>
Reset Existing Database (Y - Yes; N - No): Y

Configure Tomcat
Connection Port: 8080
Shutdown Port: 8005
Redirect Port: 8443

Subversion Configuration
Repository (LCM_Repository) Port: 3690
Repository User (LCM) Password: <Standard Password>
Confirm Password: <Standard Password>

Configure Connectivity to SMD (Solution Manager Diagnostics) Agent
1 - Do not configure Connectivity to SMD Agent
2 - Configure Connectivity to SMD Agent. You will be Prompted for Information.

Introscope Integration
1 - Do not Integrate Connectivity to Introscope Enterprise Manager.
2 - Integrate Connectivity to Introscope Enterprise Manager. You will be Prompted
for Information.

Start Installation

Business Objects Enterprise installation is complete

Unlock DDIC & SAP* in any Client

2011-07-22T00:17:00.000-07:00

Hi Folks,

There will be time where people tend to forget their mater password and hence are locked out of the client.
The following method will provide steps to fix that issue.

Example: User SAP* is locked out and password of User DDIC is unknown in Client 100 of an SAP System. There are no other users than DDIC / SAP*. How do you gain access to client 100?

1. Enable login/no_automatic_user_sapstar = 0 (transaction RZ10/RZ11). This will enable you to login to any client in the system as user sap* with password as pass.

2. If the above still doesn't work, execute the following SQL to delete SAP* User which system will create again.

> delete from sapsr3.usr02 where mandt='100' and bname = 'SAP*';

> commit;

This should allow now for sure user SAP* to login with password pass.

3. Just to unlock any user say DDIC if locked, execute the following SQL,

> update sapsr3.usr02 set uflag ='0' where bname like 'DDIC' and MANDT = '100';

> commit;

Now Enjoy with your System.

Setup Trusted Relationship between SAP Systems

2011-07-21T23:56:00.000-07:00

Hi Folks,

If you need to establish trusted relationship between SAP Systems you will need to follow the below steps.

Example: Consider there are 2 systems with System ID as KE1 & KC1 with client 100. I need to establish the trust relationship between KE1 & KC1.

1. In System KC1 (transaction SM59), create an RFC Destination.

Under the technical Settings tab

RFC Destination: KE1CLNT100_TRUST
Connection Type: 3 (ABAP Connection)
Description: Trusted RFC Connection for KE1 Client 100
Target Host: <Hostname of KE1>
System Number: <Instance Number of KE1>
Gateway Host: Recommend to provide the gateway host of KE1
Gateway Service: sapgw<nn> , where nn is instance number of KE1
Under the Logon & Security tab

Enter the Language: EN
Enter the Client: 100
User: User in KE1 with Administration Access (SAP_ALL/SAP_NEW) in Client 100
Password: Password of the above User
Trust Relationship: NO

Save the RFC Destination and test the RFC using Ctrl+F4 (Authorization Test)

2. In System KE1 (transaction SM59), create an RFC Destination.

Under the technical Settings tab

RFC Destination: KC1CLNT100_TRUST
Connection Type: 3 (ABAP Connection)
Description: Trusted RFC Connection for KC1 Client 100
Target Host: <Hostname of KC1>
System Number: <Instance Number of KC1>
Gateway Host: Recommend to provide the gateway host of KC1
Gateway Service: sapgw<nn> , where nn is instance number of KC1

Under the Logon & Security tab

Enter the Language: EN
Enter the Client: 100
User: User in KC1 with Administration Access (SAP_ALL/SAP_NEW) in Client 100
Password: Password of the above User
Trust Relationship: NO

Save the RFC Destination and test the RFC using Ctrl+F4 (Authorization Test)

3. In System KC1 (transaction: SMT1), Create an entry for trusted system by providing the RFC Destination KE1CLNT100_TRUST and click Save in the subsequent screen.

4. In System KE1 (transaction: SMT1), Create an entry for trusted system by providing the RFC Destination KC1CLNT100_TRUST and click Save in the subsequent screen.

5. In System KC1 edit the RFC Destination KE1CLNT100_TRUST under the Logon & Security Tab with the below details,
Language: EN
Client: 100
Check the Current User
Trust Relationship: YES

Save the RFC Destination and test the RFC using Ctrl+F4 (Authorization Test)

6. In System KE1 edit the RFC Destination KC1CLNT100_TRUST under the Logon & Security Tab with the below details,
Language: EN
Client: 100
Check the Current User
Trust Relationship: YES

Save the RFC Destination and test the RFC using Ctrl+F4 (Authorization Test)

7. The above RFC's will work if you have the s_rfcacl authorization object access with values mentioned in the respective Systems,

KE1:
RFC_SYSID : KC1

RFC_CLIENT: 100

RFC_USER : *

RFC_EQUSER: Y (for YES)

RFC_TCODE : *

RFC_INFO : *

ACTVT : 16

KC1:
RFC_SYSID : KE1

RFC_CLIENT: 100

RFC_USER : *

RFC_EQUSER: Y (for YES)

RFC_TCODE : *

RFC_INFO : *

ACTVT : 16

8. Trust Relationship is established successfully.

Setting Up SAP Logon Groups

2011-07-21T23:21:00.001-07:00

Hi Folks,

Follow the below steps to add an entry to your SAPLogon Pad for Logon Group login to SAP Systems.

Include the below entry in the Drive\Windows\System32\Drivers\etc\services file.

sapmsSID 36nn/tcp

SID - Where is the SAP System ID
nn - Instance Number of SAP System

After performing the above steps, follow the steps detailed below to include the SAPLogon entry.

1) Open SAPLogon Pad
2) Click New Item
3) Select User Specified system
4) For the Connection Type, Select from the drop-down box Group/Server Selection
5) Enter the description of the System
6) Enter the system ID
7) For the Message Server, Enter the hostname or IP of the Central Instance (Virtual Hostname incase of Cluster based systems) SAP system hosted under Application Server
8) If Required enter the details of the saprouter via with you 'll connect to SAP System.
9) Select the Group from the drop down list
10) Click Finish