User name : eccabap42

Password : abap123
GOLADARI
Nandan@54
-> SAP Business suite 7 includes SAP ERP 6 (Enterprise Resourse Planning), CRM 7.0
(Customer Relationship Management), SCM 7.0 (Supply Chain Management), SRM 7.0
(Supplier Relationship Management) and PLM 7.0 (Product Lifecycle Management)
-> ABAP programs use OpenSQL to interact with underlying database via a database
interface
-> Transaction Codes
1. SM52 - Provides overview of configured Java VMC
2. SM53 - Java VMC administration
3. SMICM - ICM Administration
4. SICF - Manage ICF services
5. SM50 - SAP workprocess overview
6. SM51 - SAP application server overview
7. SM66 - Global workprocess overview
8. SMGW - Gateway monitor
9. SMMS - Message server monitor
10. SM01 - Transaction codes list
11. RZ10 - Edit SAP system profile parameters
12. RZ11 - Display SAP profile paramters
13. DD02L - SAP Tables
14. DD02T - SAP Tables Text
15. ST11 - Log the trace files in the /usr/sap/<SID>/DVEBMGS<XX>/Work
Directory
16. SM59 - Used to create new RFC cunnection or alter existing
17. SCOT - Settup SAPConnect
18. SU01 - Maintain email addresses of the users to whom SAPConnect will send
emails.
19. SOST - Monitor sent jobs
20. WE81 - Shows all message types
21. SE11 - Data Disctionary
22. SE93 - List of Transaction codes in TSTC table

- login/disable_multi_gui_login (Instance profile parameter to disable multiple

gui logins)

-> startsap [DB|R3|ALL]

-> stopsap [DB|R3|ALL]
-> The following sequence is used to read system parameters during SAP start-up
1. SAP Kernal code
2. Default profile
3. Instance Profile

-> SAP profiles are operating system files that contain SAP instance setup
information.
1. Start Profile - This parameter file will define which SAP services will be
started.
2. Default Profile - This paramter file will define the profile parameters
applicable for all instances of the system.
3. Instance Profile - This paramter file define the profile for the specific
instance, which allows individual applications to be configured differently for
specific tasks and users.

-> Verifying the system started correctly:

1. startsap.log file in home directory should report that all services and
processes are started
2. startdb.log - database starts without any errors are per startdb.log file
in home directory
3. Check at operating system level for the SAP processes. Check the
dispatcher and the work processes, message server, enqueue server, gateway, icman
and oracle database processes are up and running.
4. Check the last line in the available.log file in the following location
/usr/sap/<SID>/<instance name>/work/
The last line will have status entry saying the system is available or
unavailable.
-> Java System Log Files
1. dev_jstart - Log file for JSTART
2. dev_bootstrap - Bootstrap startup framework log file
3. jvm_bootstrap.out - Output file for JVM
4. dev_jcontrol - JControl log file
5. dev_dispatcher - Dispatcher trace file.
6. jvm_dispatcher.out - Output file for JVM dispatcher node
7. std_serverO.out - Output of the server process.
8. Available.log - Logs the start and end times of system availability.
9. The location of important log files for a single-stack java instance and
dual stack instance as follows:
- For the Java Central Instance the default location of the log files
is /usr/sap/<SID>/JC<XX>/Work directory where XX = system number
- For the dual stack central instance the default location of the log
files is /usr/sap/<SID>/DVEBMGS<XX>/Work directory where XX=system number

-> SAP table TSTC lists all transaction codes of a SAP system

-> The simplest Java cluster architechture installation involves the following
components:
1. Java central instance with a dispatcher and atleast one server process
2. Software Deployment Manager (SDM)
3. Central Services Instance
- It comproses Message server and Enqueue Server
- Message server
- Event notification in the Java Cluster
- Load balancing
- Broadcasting messages in the Java Cluster
- Enqueue Server
- Managing locks in Java Cluster
- Managing Synchronization in the Java Cluster
4. Database

-> Start and stop of SAP NW AS Java

1. Database is started
2. Central Services instance is started
3. Central instance is started
4. Dialog instance is started
-> Shutdown sequence is exactly opposite of the startup sequence

-> Java startup Framework for NW 7.0

Step 1:
- startsap comman will start jcontrol process.
- JControl starts signal handling and connects to the Java message server.
- JControl starts the JLaunch bootstrap process by reading the
bootstrap.properties file in the /usr/sap/<SID>/<instance>/j2ee/cluster/bootstrap
directory.
- JLaunch creates VM and loads it into its own address space.
Step 2:
- The bootstrap program syncronizes the binary data form the java database
with the file system.
Step 3:
- The bootstrap program read the database and writes the file
instance.properties to the file system in the directory
/usr/sap/<SID>/JC00/j2ee/cluster.
- This file will have the information on the java cluster elements that need
to be started.
Step 4:
- JControl reads the instance.properties file
Step 5:
- JControl starts the JLaunch for the cluster elements defined in the
instance.properties file
- Each JLaunch starts VM and loads it in its address space and starts the
cluster elements.
Step 6:
- The JLaunch cluster element starts offline configuration manager to read
the Java Enterprise runtime properties and saves it in database hash tables.
- JLaunch stops the offline configuration manager and reads the saved
properties in the database and starts the Java Enterprise runtime.
- The service framework and all configured services are started.
Step 7:
- The JCMON process monitors the status of all started cluster elements and
takes actions such as restarting terminated processes.
-> Verifying SAP Java system started properly
1. Verify if JControl system is started at the operating system level.
- ps -ef | grep jcontrol
2. Verify if JLaunch process is started at the operating system level.
- ps -ef | grep jlaunch
3. Verify if dispatcher, SDM and Server 0...n are in "Running" status in
JCMON.
- jcomon pf=DEV_JC00_indus
4. Verify using the URL http://<server:port>/index.html.
5. For dual stack systems, the Java system status can be verified by using
SMICM transaction code.
6. The last entry in the /usr/sap/<SID>/<instance>/work/available.log shows
the current status of the server.

-> Java startup Framework for NW 7.1

Step 1:
- The startsap comman will start the JSTART process
- JSTART takes the role of Java instance controller(JIC)
- To check the JSTART process ps -ef | grep jstart
Step 2:
- JIC will read the instance profile and get the JAVA SDK details.
- JIC starts signal handling and opens the control port to receive any stop
signals.
Step 3:
- JIC first starts reading the profile parameters jstart/startupNodeFiles and
jstart/instanceNodeFiles from the instance profile, searching for runLevel=1
propert.
- "OFFLINE DEPLOYMENT" corresponds to runLevel = 1
- jstart/startupNodeFiles profile parameter provides the name of the file
that contains the node definitions for the bootstrap and offline deployment phases.
The default value of this parameter is $
(DIR_EXECUTABLE)/startup.properties.
- jstart/instanceNodeFiles profile parameter provides the node list that will
constitute the Java instance. This is derived at runtime.
Step 4:
- JIC starts another JSTART process as a child process with parameters from
the OFFLINE DEPLOYMENT node and waits
 - The child JSTART ptocess performs as a Java Process, creates JVM and loads
it into its address space and starts the OFFLINE DEPLOYMENT program.
- The OFFLINE DEPLOYMENT program executes the deployment steps in the
database.
Step 5:
- JIC reads the instance profile again searching for runLevel = 2
- "BOOTSTRAP" node corresponds to runLevel=2
- JIC starts another JSTART process as a child process with parameters from
the BOOTSTRAP node and waits.
- The child JSTART process performs as a Java process, creates JVM and loads
it into its address space and starts the BOOTSTRAP program.
- The BOOTSTRAP process synchronizes the binary data from the Java database
to the file system and updates the instance.properties file.
Step 6:
- JIC reads the recently updated instance.properties and startup.properties
file searching for runLevel=3 or without any runLevel.
- This corresponds to ICM and JAVA server process.
- ICM is started.
- Java server processes are started.
- A child process is started in each of the cases and similar JVM actions are
carried over as in the preceding steps.
Step 7:
- The JIC process monitors the status of all the started cluster elements and
takes actions such as restarting the termiated processes.

-> to check JSMON - JSMON pf=DX1_JC00_indus

-> RFC : Remote Function Call(RFC) is SAPs communication interface.RFC

communication between SAP business solutions involves an RFC client and an RFC
server.
RFC server provides function modules. RFC cliet calls one of the
function modules, pass on the data and gets reply back from RFC server.
-> Setting up an RFC connection:
- TCode SM59 is used to create new connection or alter existing connection.
- RFC connection types "3"(Connecgts to another ABAP system) and "T"(TCP/IP
connection) are most often used.
- Create RFC connection - Connection test - Authorization test
- RFC connection "T" refers to starting an external system using TCP/IP. One
example of such need in SAP system landscape integration scenario is with in the
SAP process integration application.
In this scenarion PI ABAP components integrate with PI Java components
using this connection.
- SAP PI ABAP system integrates with SAP PI Java system referred to as the
System Landscape Directory (SLD) using an RFC connection called SAPSLDAPI
-> SAPconnect: SAPConnect allows a SAP ABAP system to send external communications
to the systems such as a SAP-certified fax, page and e-mail solutions.
- SAPConnect can be setup using TCode SCOT
-> Applicarion Link Enabling(ALE)/Electronic Data Interchange(EDI)
- The basis ALE(SAP-to-SAP business data exchange) and EDI(SAP-to-EDI system
business data exchange) communication mechanism is the Intermediate Documents
(IDOC).
- An IDOC acts as a data container facilitating business data exchange
between SAP systems and non-SAP systems.
- The basis of IDOC generation is message type. Message types identify the
usage of specific business data.
- One example of standard message type is "CREMAS". CREMAS is vendor master
data distribution message type.
- TCode WE81 shows all the message types.
-> SAProuter: SAProuter is a SAP program that is used to securely connect to the
SAP support.
- SAProuter program is installed in both customer site and SAP support
organization.
- SAProuter program is installed inside the firewall and acts as an
application level gateway

-> SAP solution manager

- SAP solution manager is recommended as a central system for all
administration and monitoring activities of SAP system landscape of an
organization.
- Change and Transport Management
- Service desk functionality
- Monitoring and Reporting capabilities
- Central User Administration(CUA)
- hosting central System Landscape Directory(SLD)
- Enterprise wide Netweaver administration
- End to end root cause analysis with tools such as Solution Manager
Diagnostics(SMD)
- Wily Introscope

-> SAP solution integration with EDI and other External Vendors
- SAP solution Manager integrates and exchanges data with external vendors
EDI systems using integration products such as Gentran.
- Gentran is one of the leading EDI and data translation solutions.

-> Enterprise Service Repository(ESR)

- ESR is a repository for the enterprise service inventory of assests built
by an organization over time.
- This includes tools such as Enterprise Services Builder and Services
Registry.
- Enterprise Services Builder is used to build the services based on
Enterprise SOA standards.
- The services are then published in the Services Registry for enterprise
wide consumption.

-> System Landscape Directory(SLD)

- SLD is a central provider of all software product and component definitions
to the ESR.
- New software product and component definitions are created in SLD and
exposed to ESR to begin the development of the service interface.

-> Integration Directory

- Integration Directory is the central configuration tool that helps in
configuring message processing, communication and security and routing rules for
message flow.

-> Configuring and Monitoring

- Runtime workbench and Netweaver Administrator(NWA) are two tools provided
by SAP for monitoring and adminstrating the PI solutions.
###################################################################################
###################################################################################
######

-> SAP Installation

-> Product Availability Matrix (PAM)

- PAM is a online resource provided by SAP so that customers can check the
availability of the given SAP product and supported operating systems
 and the databases.
- PAM can be accessed by using SAP portal https://service.sap.com/pam
- PAM also provides vital information such as other software dependencies and
requirements, maintenance start and end dates, new product ramp-up
release dates, and release related OSS (Online Service System) notes

-> Installation Definitions:

- Central Instance:
- The Central Instance refers to the application services for the SAP
system, including enqueue and message services that are located on a single hots
machine.
The central instance has multiple work processing for the dialog,
update, and background services.
The machine on which it runs is called the central host.
- Database Instance:
- The instance associated with the underlying database onf the SAP
application is referred to as a database instance.
- Central System Installation:
- If the SAP central instance and database are installed on the same
physical host, then it is referred to as a Cental System Installation.
- Usually small SAP installations and non-production systems are
installed in this type.
- Distributed System Installation:
- In a distributed system installation, the Cental instance and
database instance are installed in two differents hosts.
- Usually the distributed systel installations are used for large SAP
installations and for Production Installations.
- Dialog Instance:
- Aditional application server instances installed for scalability and
load balancing purposes are referred to dialog instances.
- Dialog instances have additional dialog, batch, spool and update work
processes. These are joined to the central system.
- SID:
- SID is the system identifier for the SAP system.
- It consists of 3 alphanumeric uppercase characters, first character
must be a letter and SID should not include any of the reserved words.
- System Number:
- The system number is an identifier used for internal SAP processes.
you are allowed to choose any 2 digit number from 00 to 98.
- SAPInst:
- SAPInst is the SAP installation tool used to build the SAP
application.
- This tool is delivered along with the downloaded SAP software.
- SAPInst drives the entire installation based on the chosen install
scenario.

-> SAP System Install Build Specifications

- It is best practice to write a formal build specification with all the
naming conventions and provide it to UNIX, storage and database teams, so that
they will start allocating the needed storage space and building the
underlying opentating system(OS) file system that is needed for the database and
SAP installation.
- Additional information such as swap space requirements, UNIX kernel
parameters, OS patches and swap information is included in the build specification
as per the instructions and operating system specific OSS notes provided in
the install guide.
- User accounts <SAPSID>adm and ora<SAPSID> can be created before the start
of the installation as per instructions in the install manual and your organization
standards.
-> ECC - ERP Central Component

-> Change and Transport System

- Administering and controlling of new development requests
- Modifying and correcting repository objects
- Recording and auditing of all configuration settings and changes
- Managing the transport of development packages
- Locking of objects to avoid parallel work
- Performing version management
- Documenting changes
- Assuring teamwork development and workflow control
- Transporting of objects and settings changes among systems
- Logging of transport results
- Setting the system and client change options
- Performing client copy functions
- Recording of where and by whom changes are made
- Configuring the systems landscape
- Assisting in maintaining consistency of changes throughout the SAP
landscape

To Do
1. Client Administration
000
001
006

Create Client
Client Copy (Remote/Local)
Client Import/Export

Client copy pre-requisites:

1. Export the users from the Target Client with TCode SCC8
2. Disconnect and lock business users - SU10
3. Suspend all background jobs - SA38-> BTCTRNS1
4. Check database space using DB02
5.

-> CPIC : CPIC stands for Common Programming Interface Communication and includes
standard functions and services for program-to-program
communication with the ABAP programming language.
-> Transaction: A transaction is an operation that lets a user make changes to a
database. In SAP a set of dialog steps makes a transaction.
-> The SAP client is defined as a self-contained unit in an SAP instance with its
own dataset and set of tables

No-Periodic Job
Periodic Job
Event Based job

-> SAPCAR
- To list the contents of SAR files.
sapcar -tvf <your-SAR-file>
- To extract the contents of SAR files
sapcar -xvf <your-SAR-file>
- To compress files to SAR files
sapcar -cvf <your-SAR-file> <file-to-compress>

Kernnal Directory - /usr/sap/sid/sys/exe/uc/ntdamd64

stopsap.exe name=<> nr=00 SAPDIAHOST=<>

SE38 -> to check latest program changes

SM51 -> check workprocesses
ASCS vs SCS Instance
ABAP Stack - Dispatcher Monotor -> dpmon pf=<profile name>
jsmon Stack Monitoring -> jsmon pf = <profile name>

5<>13 port for restart

http:\\<hostname>:5<system number>13
-> kernal information
- cmd > disp+work
- SM51 - Release Notes
- System Status
-> SM50
-> SM21
-> ST22
-> ABAP dump Analysis
-> ST06
-> SM12
-> SM13
-> ST06
-> SP01
-> SMJW
-> SM04
-> AL08
-> SM66
-> DB13
-> ST03
-> ST02 - Hit Ratio, roll area, page area, heap area, extended memory, swaps
-> ST07
-> ST11
-> RZ04
-> AL11
-> SMICM
-> WE08
-> ST01/ST05
-> CAB - Change Authority Board
-> SE16 - table detailsf

-> Memory allocation sequence to dialog workprocess in SAP

April 4

-> sappfpar pf=DAFAULT.PFL

-> Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP Web
Application Server ABAP 6.40 SR1
- When a homogeneous system copy is performed, the target SAP system is
installed on the same operating system and the same database system
as the source SAP system. The contents of the database are copied from the
source to the target system. During a heterogeneous system copy,
the operating system or the database system is changed. Migration is a
synonym for heterogeneous system copy.

-> Transport Management

- Data file, Cofile
- Buffer
- Bin Directory - Profile and config files
-> SE01
-> STMS

-> Access Key

Consolidation Transport Route

Delivery Transport Route

SSCR Keys

Greenfield Implementation: Fresh SAP implementation

Brownfield Implementation : Upgrade or Migration of existing implementation

System Refresh:
- System from which copy is being done is Source System
- System in which data to be copied is Target System

Monitoring:
- Why?
- To ensure that system is working efficiently.
- To ensure system security and stability.
- To take preventive actions for a smooth business process

- CCMS : Computing center management system

- CCMS monitoring infrastructure consists of three functional areas: Data
Collection, Data Storage and Data Analysis
- CCMS TCode:RZ20
- CTS : Change and Transport SystemFtable

Kernal Upgrade:
1. Download the media and extract the archive into a directory.
2. Take backup of current Kernel
3. Shutdown the system
4. Copy new Kernal files to usr/sap/<SID>/SYS/exe/uc
5. Restart the system,sapcpe program will copy kernel files from the central
repositories to the local exe directory.

Spool Overflow:
1. There is a limit to the number of spool requests that can be created in SAP
System. The standard SAP system will have a limit of 32000
2. Run SAP programs RSPO0041 or RSPO1041 to delete any spool request that are no
longer needed
3. Increase Spool request limit using the TCode SNRO. Adjust the upper limit of
interval SPO_NUM

ABAP Dumps:
1. TSV_TNEW_PAGE_ALLOC_FAILED - Process goes to PRIV mode due to lack of memory
2. TSV_TNEW_OCCURS_NO_ROLL_MEMORY - Roll buffer has been exausted, we can check
roll buffer with ST02-> History-> Page
Roll buffer can be increased
with parameter rdisp/ROLL_MAXFS
3. CALL_FUNCTION_SIGNON_INCOMPL - RFC call with incorrect or missing data
4. CALL_FUNCTION_NOT_FOUND - Buffered function has errors
5. Message_Type_X - GUI error

Kernel Latest Version - 753

DB Refresh:
 1) Take full offline backup of database using BRTOOLS/DB13.
Brbackup –u –p init<sid>.sap –d disk –t offline –m all
2) Generate the control file
SQL> alter database backup controlfile to trace;
Get the trace file from user trace directory and modify the file as
following
è Rename the file to control.sql.
è Remove all the content above the line STARTUP NOMOUNT and below
CHARACTER SET URF8;
è Replace NORESETLOGS with RESETLOGS.
è Replace ARCHIVELOG with NOARCHIVELOG.
è Replace S_sid with T_sid.
3) Change the S_sid with T_sid in b***.afd backup log file.
4) Change the S_sid with T_sid in the first file of backup folder
and rename to target sid.
5) Restore the database using the command
Brrestore –u 0b b***.afd -d disk –k yes -m all
6) Login to database start the database(startup nomount).
7) Run @contro.sql file.
SQL>select status from v$instance; it is in mounted state.
SQL>alter database open resetlogs; now it goes to open status.
SQL> select username from dba_users;
8) Now copy ORADBUSR.SQL file from installation folder copy to sap
backup directory and run.
SQL> @ORADBUSR.SQL
Enter value for 1: schema owner ID SAPSR3
2: file system NT
3: host name
4: SAP SID
Now again check the users
SQL>select username from dba_users;
Now you can see target system users only. Remove the source system
users.
9) Drop user
OPS$HOSTNAME\SIDADM cascade.
10) Now provide the permission to the target system users.
SQL> grant connect sapdba to “OPS$Hostname/SIDADM”;SAPSERVICESID;
SQL>grant dba to “OPS$Hostname/SIDADM”;SAPSERVICESID;
11) Now start the SAP system and is working or not.