What is private mode? When does user switch to user mode?
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.
What is osp$ mean? What if user is given with this authorisation?
OPS$ is the mechanism the
Why do you use DDIC user not SAP* for Support Packs and SPam?
Do _NOT_ use neither DDIC nor SAP* for applying support packages. Copy DDIC to a separate user and use that user to apply them.
Can you kill a Job?
Yes - SM37 - select - kill
If you have a long running Job, how do you analyse?
Use transaction SE30.
How to uncar car/sar files in a single shot?
on Unix:
$ for i in *.SAR; do SAPCAR -xvf $i; done
When we should use Transactional RFC ?
A "transactional RFC" means, that either both parties agree that the data was correctly transfered - or not. There is no "half data transfer".
What is the use of Trusted system. I know that there is no need of UID and PWD to communicate with partner system. In what situation it is good to go for Trusted system ?
E. g. if you have an R/3 system and a BW system and don't want to maintain passwords. Same goes for CRM and a lot of other systems/applications.
Let me know if my understanding below is correct:
1) By default the RFC destination is synchronous
2) Asynchronous RFC is used incase if the system initiated the RFC call no need to wait for the response before it proceeds to something else.
Yes - that's right.
But keep in mind, that it's not only a technical issue whether to switch to asynchronous. The application must also be able to handle that correctly.
Which table contains the details related to Q defined in SPAM? Is there a way to revert back the Q defined? If yes, How?
There is a "delete" button when you define the queue. If you already started the import it's no more possible since the system will become inconsistent.
What is a developer key? and how to generate a developer key?
The developer key is a combination of you installation number, your license key (that you get from http://service.sap.com/licensekey) and the user name. You need this for each person that will make changes (Dictionary or programs) in the system.
What is XI3.0 ? EXPLAIN XI = Exchange Infrastructure - Part of Netweaver 2004.
SAP Exchange Infrastructure (SAP XI) is SAP's enterprise application integration (EAI) software, a component of the NetWeaver product group used to facilitate the exchange of information among a company's internal software and systems and those of external parties. Like other NetWeaver components, SAP XI is compatible with software products of other
companies.
SAP calls XI an integration broker because it mediates between entities with varying requirements in terms of connectivity, format, and protocols. According to SAP, XI reduces integration costs by providing a common repository for interfaces. The central component of SAP XI is the SAP Integration Server, which facilitates interaction between diverse operating systems and applications across internal and external networked computer systems.
How to see when were the optimizer stats last time run? We are using win2k, oracle 9, sapr346c.
Assumed DB=Oracle
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%';
SAP Basis FAQ
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
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 :
Using SAPROUTER : N
Trace Level (inBoound) : 0
Sendmail Command :
Codepage :
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 :
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 :
19. Hostname :
20. Gateway hostname:
21. Gateway server sapgw
22. Sendmail Command :
23. Update file : Y
Testing
1. Logon to SAP
2. Execute transaction SO01
3. Write a message and send it to
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.
1. Create a logical OS command 'zftp' using transaction SM69. Make sure that you enable 'comand line parameter allowed' checkbox
2. Create a shell script called 'zftp' with the following lines
RMTHOST=`echo $2 | tr '[A-Z]' '[a-z]'`
ftp -v $RMTHOST << EOF > /out/zftp.$$ 2>&1
lcd /out
put $1
bye
EOF
3. Use the SXPG_COMMAND_EXECUTE function module to call this script (zftp) with the filename you want to transfer as the parameter. Eg:
call function 'SXPG_COMMAND_EXECUTE'
exporting
commandname =
tables
exec_protocol =
exceptions
no_permission = 1
command_not_found = 2
parameters_too_long = 3
...
Enable web based online documentaion (R/3 4.0 or above)
1. Install Netscape webserver or use an existing web server (requires administrators privelege)
2. Create a directory called SAPDOCS4 under your web server document root.
3. Mount the CDROM containing online documentation on your PC or your UNIX server.
4. Recursively copy all files under /cdrom/docs/ to the SAPDOC4 directory under the web server root.
5. Create the following entries in your /usr/sap/SID/SYS/profile/DEFAULT.PFL
eu/iwb/installed_languages = EN
eu/iwb/help_type=2
eu/iwb/server_win32=webserver.domain.com
eu/iwb/path_win32=saphelp/helpdata
• Restart your SAP system
How to access an external database from ABAP via DBLINK (ORACLE)
1. Using transaction SE11, create a table (ZTABLE) with the same fields as the table in the external database, make sure that the type and lengths of the fields are identical.
2. Using transaction SE11, create a view (ZTABLE_VIEW, projection view) using BASIS table ZTABLE
3. Using SVRMGRL>
create dblink REMOTE_DB as connect to remote_user identified by password; (database link created)
drop table ZTABLE; (table dropped)
create synonym ZTABLE for ZTABLE@REMOTE_DB; (synonym created)
• Using transaction SE16 , type in ZTABLE_VIEW and hit RETURN
• Enter value in key fields and hit execute. (displays rows from the remote table)
Tips and Tricks
1. To see the complete text of an error/warning message on the SAPGUI status bar, right click on the message and drag left.
2. To prevent your spool requests getting deleted from the BASIS cleanup jobs, you need to uncheck the Delete after print checkbox in the print control screen, execute transaction SP01, find your spool#, click on Attributes and change the Delete After date
3. Short cuts using the OK-code box.
%sc Search in page
%pc Download do local file
p+ Page up
p- Page down
p++ Top of page
p-- End of page
Useful SAP System Administration Transactions
AL01 SAP Alert Monitor
AL02 Database alert monitor
AL03 Operating system alert monitor
AL04 Monitor call distribution
AL05 Monitor current workload
AL06 Performance: Upload/Download
AL07 EarlyWatch Report
AL08 Users Logged On
AL09 Data for database expertise
AL10 Download to Early Watch
AL11 Display SAP Directories
AL12 Display table buffer (Exp. session)
AL13 Display Shared Memory (Expert mode)
AL15 Customize SAPOSCOL destination
AL16 Local Alert Monitor for Operat.Syst.
AL17 Remote Alert Monitor for Operat. Syst.
AL18 Local File System Monitor
AL19 Remote File System Monitor
AL20 EarlyWatch Data Collector List
AL21 ABAP Program analysis
AL22 Dependent objects display
CREF Cross-reference
BD64
BSVW Linkage Status Update-Workflow Event
CMOD Enhancements
DB01 Analyze exclusive lock waits
DB02 Analyze tables and indexes
DB03 Parameter changes in database
DB11 Early Watch Profile Maintenance
DB12 Overview of Backup Logs
DB13 Database administration calendar
DB14 Show SAPDBA Action Logs
DB15 Data Archiving: Database Tables
DB16 DB System Check: Monitor
DB17 DB System Check: Configuration
DMIG Start Transaction for Data Migration
DB2 Select Database Activities
DB20 DB Cost-Based Optimizer: Tab. Stats
DB21 DB Cost-Based Optimizer: Config.
DB24 Database Operations Monitor
DB26 DB Profile:Monitor and Configuration
DB2J Manage JCL jobs for OS/390
DBCO Database Connection Maintenance
FILE Cross-Client File Names/Paths
NACE WFMC: Initial Customizing Screen
OAA1 SAP ArchiveLink: Maint.user st.syst
OAA3 SAP ArchiveLink protocols
OAA4 SAP ArchiveLink applic.maintenance
OAAD ArchiveLink Administration Documents
OAC2 SAP ArchiveLink: Globaldoc. types
OAC5 SAP ArchiveLink: Bar code entry
OACA SAP ArchiveLink workflow parameters
OAD0 SAP ArchiveLink: Objectlinks
OAD2 SAP ArchiveLink document classes
OAD3 SAP ArchiveLink: Link tables
OAD4 SAP ArchiveLink: Bar code types
OAD5 SAP ArchiveLink: Customizing Wizard
OADR SAP ArchiveLink: Print list search
OAM1 SAP ArchiveLink: Monitoring
OAOR SAP ArchiveLink: Storeddocuments
OARE SAP ArchiveLink:St.syst.return codes
OS01 LAN check with ping
OS03 O/S Parameter changes
OS04 Local System Configuration
OS05 Remote System Cconfiguration
OS06 Local Operating System Activity
OS07 Remote Operating SystemActivity
OSS1 Logon to Online ServiceSystem
OY18 Table history
OY08 Development Class Overview
PFCG Activity Group
PFUD Authorization Profile comparison
RLOG Data migration logging
RZ01 Job Scheduling Monitor
RZ02 Network Graphics for SAP Instances
RZ03 Presentation, Control SAP Instances
RZ04 Maintain SAP Instances
RZ06 Alerts Thresholds Maintenance
RZ08 SAP Alert Monitor
RZ10 Maintenance of profile parameters
RZ11 Profile parameter maintenance
RZ12 Maintain RFC Server Group Assignment
RZ20 CCMS Monitoring
RZ21 Customize CCMS Alert Monitor
SA38 ABAP/4 Reporting
SAD0 Address Management call
SADC Address: Maint. communication types
SALE Display ALE Customizing
SAINT Plug-in Installation
SARI Archive Information System
SAR3 Customizing Archiving
SAR4 Define Archiving Class
SAR5 Assign Archiving Class
SAR6 Archiving Time Generator
SARA Archive management
SARL Call of ArchiveLink Monitor
SARP Reporting (Tree Structure): Execute
SART Display Reporting Tree
SB01 Business Navigator - Component View
SB02 Business Navigator - Process flow vw
SBAS Assignments to Process Model Elemts
SC38 Start Report Immediately
SCAT Computer Aided Test Tool
SCC0 Client Copy
SCC1 Client Copy - Special Selections
SCC2 Client transport
SCC3 Client Copy Log
SCC4 Client administration
SCC5 Client Delete
SCC6 Client Import
SCC7 Client Import – Post Processing
SCC8 Client Export
SCC9 Remote Client Copy
SCCL Local Client Copy
SCDO Display Change DocumentObjects
SCMP View / Table Comparison
SCOM SAPcomm: Configuration
SCON SAPconnect - Administration
SCPF Generate enterprise IMG
SCPR1 Customizing Profiles : Maintenance Tool
SCPR2 Comparing Customizing profiles
SCUA Central User Administration : Distribution Model Assigment
SCUG Central User Administration Structure Display
SCUL
SCUM Central User Administration Field Selection
SCU0 Table Analyses And Comparison
SCU1 Table Comparison - Export to Tape
SCU2 Table Comparison Against Tape
SCU3 Table History
SD11 Data Modeler
SDBE Explain an SQL Statement
SECR Audit Information System
SE01 Transport and Correction System
SE02 Environment Analyzer
SE03 Transport Utilities
SE06 Set up Workbench Organizer
SE07 Transport System Status Display
SE09 Workbench Organizer (Initial Screen)
SE10 Customizing Organizer
SE11 Data Dictionary Maintenance
SE12 Data Dictionary Display
SE13 Maintain Technical Settings (Tables)
SE14 Convert Data Dictionary tables on Database Level
SE15 Repository Info System
SE16 Display Table Content
SE17 Generate Table Display
SE30 ABAP Objects Runtime Analysis
SE32 ABAP Text Element Maintenance
SE33 Context Builder
SE35 ABAP/4 Dialog Modules
SE36 Logical databases
SE37 ABAP Function Modules
SE38 ABAP Editor
SE39 Splitscreen Editor: Program Compare
SE40 MP: Standards Maint. and Translation
SE41 Menu Painter
SE43 Maintain Area Menu
SE51 Screen Painter
SE52 Parameterized screenpainter call
SE54 Generate table view
SE55 Internal table view maintenance call
SE56 internal call: display table view
SE57 internal delete table view call
SE61 R/3 Documentation
SE62 Industry Utilities
SE63 Translation: Initial Screen
SE71 SAPscript form
SE72 SAPscript Styles
SE73 SAPscript font maintenance (revised)
SE74 SAPscript format conversion
SE75 SAPscript Settings
SE76 SAPscript: Form Translation
SE77 SAPscript Translation Styles
SE78 SAPscript: Graphics administration
SE80 Object Navigator
SE81 Application Hierarchy
SE82 Application Hierarchy
SE84 R/3 Repository Information System
SE85 ABAP/4 Repository Information System
SE86 ABAP Repository Information System
SE88 Development Coordination Info System
SE89 Maintain Trees in Information System
SE91 Maintain Messages
SE92 New SysLog Msg Maintenance as of 46A
SE93 Maintain Transaction Codes
SE94 Customer enhancement simulation
SE95 Modification Browser
SEPS SAP Electronic Parcel Service
SERP Reporting: Change Tree Structure
SEU Repository Browser
SF01 Client-Specific File Names
SFAW Field Selection Maintenance
SIAC1 Web Object Administration
SHDB Record Batch Input
SICK Installation Check
SIN1 SAPBPT: Inbox
SINA SAPBPT: Maintain Standard Config.
SLG0 Application Log: ObjectMaintenance
SLIN ABAP: Extended Program Check
SM01 Lock Transactions
SM02 System Messages
SM04 User Overview
SM12 Display and Delete Locks
SM13 Display Update Records
SM14 Update Program Administration
SM21 System log
SM23 System Log Analysis
SM28 Installation Check
SM29 Model Transfer for Tables
SM30 Call Up View Maintenance
SM31 Table maintenance
SM31_OLD Old Table Maintenance
SM32 Maintain Table Parameter ID TAB
SM33 Display Table ParameterID TAB
SM34 Viewcluster maintenancecall
SM35 Batch Input Monitoring
SM36 Batch request
SM37 Background job overview
SM38 Queue Maintenance Transaction
SM39 Job analysis
SM49 Execute Logical Commands
SM50 Work Process Overview
SM51 List of SAP Servers
SM54 TXCOM maintenance
SM55 THOST maintenance
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM60 Borrow/Return Objects
SM61
SM62
SM63 Display/Maintain Operating Mode Sets
SM64 Release of an event
SM65 Background Processing Analysis Tool
SM66 System-wide Work Process Overview
SM67 Job scheduling
SM68 Job administration
SM69 Display/Maintain Logical Commands
SMEN Dynamic menu
SMGW Gateway Monitor
SMLG Maintain Logon Group
SMLI Language import utility
SMLT Language transport utility
SMOD SAP Enhancement Management
SMT1 Trusted Systems (Display <-> Maint.)
SMT2 Trusting systems (Display <->Maint.)
SMW0 SAP Web Repository
SMX Display Own Jobs
SNRO Number Range Objects
SO02 SAPoffice: Outbox
SO03 SAPoffice: Private Folders
SO04 SAPoffice: Shared Folders
SO05 SAPoffice: Private Trash
SO06 SAPoffice: Substitutionon/off
SO07 SAPoffice: Resubmission
SO10 SAPscript: Standard Texts
SO12 SAPoffice: User Master
SO13 SAPoffice: Substitute
SO15 SAPoffice: DistributionLists
SO16 SAPoffice: Profile
SO17 SAPoffice: Delete Shared Trash
SO18 SAPoffice: Shared Trash
SO19 SAPoffice: Default Documents
SO21 Maintain PC Work Directory
SO22 SAPoffice: Delete PC Temp. Files
SO23 SAPoffice: DistributionLists
SO24 SAPoffice: Maintenance of default PC
SO28 Maintain SOGR
SO30 SAPoffice: Reorg.
SO31 Reorganization (daily)
SO36 Create Automatic Forwarding
SO38 SAPoffice: Synchr. of Folder Auths.
SO40 SAPoffice: Cust. LayoutSet MAIL
SO41 SAPoffice: Cust. LayoutSet TELEFAX
SO42 SAPoffice: Cust.Layout Set TELEFAX_K
SO43 SAPoffice: Cust.Layout Set TELEFAX_M
SO44 SAPoffice: Cust. LayoutSet TELEX
SO70 Hypertext: Display/Maint. Structure
SO71 Test plan management
SO72 Maintain Hypertext Module
SO73 Import graphic into SAPfind
SO80 SAPfind: Free Text Retrieval Dialog
SO81 SAPfind: Free Text Indexing (Test)
SO82 SAPfind: Free Text Retrieval Batch
SO95 Pregenerated Search Queries - Selec.
SO99 Put Information System
SOA0 ArchiveLink Workflow document types
SOBJ Attribute Maintenance Objects
SOLE OLE Applications
SOLI Load OLE type info
SOPE Exclude Document Classes
SOTD SAPoffice: Maintain Object Types
SOY1 SAPoffice: Mass Maint. Users
SOY2 SAPoffice: Statistics data collect.
SOY3 SAPoffice: Statistics Evaluation
SOY4 SAPoffice: Access overview
SOY5 SAPoffice: Inbox overview
SOY6 SAPoffice: Document overview
SOY7 SAPoffice: Folder overview
SOY8 SAPoffice: Mass Archiving
SOY9 SAPoffice: Inbox Reorg.
SOYA SAPoffice: Change folder owner
SP00 Spool and Relate Area
SP01 Spool Control
SP02 Display output Requests
SP03 Spool: Load Formats
SP11 TemSe Contents
SP12 TemSe Administration
SPAD Spool Management
SPAM SAP Patch Manager (SPAM)
SPAU Display Modified DE Objects
SPCC Spool Consistency check
SPDD Display Modified DDIC objects
SPHA Telephony administration
SPIC Spool : Installation Check
SPRM Current Customizing
SPRO Customizing
SQ01 SAP Query: Maintain queries
SQ02 SAP Query: Maintain funct. areas
SQ03 SAP Query: Maintain user groups
SQ07 SAP Query: Language comparison
SQVI QuickViewer
SSAA System Administration Assistant
SSCA Appointment Diary: Administration
SRZL CCMS
SSM1 Session Manager generation call
SSM5 Create Activity Group
ST01 System Trace
ST02 Setups/Tune Buffers
ST03 Performance, SAP Statistics, Workload
ST04 Select activity of the databases
ST05 SQL Trace
ST06 Operating System Monitor
ST07 Application monitor
ST08 Network Monitor
ST09 Network Alert Monitor
ST10 Table Call Statistics
ST11 Display Developer Traces
ST12 Application Monitor
ST14 Application Analysis
ST22 ABAP Runtime Error Analysis
ST22 ABAP/4 Runtime Error Analysis
ST62 Create industry short texts
STAT Local transaction statistics
STMS Transport Management System
STUN Performance Monitoring
STW1 Test Workbench: Test catalog
STW2 Test workbench: Test plan
STW3 Test workbench: Test package
STW4 Test Workbench: Edit test package
STW5 C maintenance table TTPLA
STZAC Maintain time zone act.in client
STZAD Disp.time zone activat.in client
SUMM Global User Manager
SU01 Maintain User
SU01D Display users
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet Users
SU10 Mass changes to User Master
SU11 Maintain Authorizations
SU12 Mass Changes to User Master Records
SU2 Maintain User Parameter
SU20 Maintain Authorization Fields
SU21 Maintain Authorization Objects
SU22 Auth. object usage in transactions
SU24 Disables Authorization Checks
SU25 Imports SAP Check Indicators defaults
SU26 Adjust Authorization checks
SU30 Total checks in the area of auth.
SU52 Maintain own user parameters
SU53 Display check values
SU54 List for Session Manager
SU56 Analyze User Buffer
SUPC Profiles for activity groups
SUPF Integrated User Maintenance
SUPO Maintain Organization Levels
SUIM Repository Info System
SWDC Workflow Definition
SXDA Data Transfer Workbench
TU02 Display Active Parameters
USMM Customer measurement
----------------------------------------------------------
|Tcode|Transaktionstext |
----------------------------------------------------------
|ADOK |AM: System Administration Guide |
|BALE |Area Menu for Administration |
|BDMO |ALE CCMS Group Administration |
|CATSX|Time Sheet Admin.: Initial Screen |
|CICY |CTI Administration |
|CJV6 |Maintenance: Version administration |
|CN84 |PS: Archiving project - admin. |
|COA4 |PP: Archiving order - administration |
|CSADM|Content Server Administration |
|FC_BW|Administrator Workbench |
|FDTA |TemSe/REGUT Data Administration |
|FDTT |Treasury Data Medium Administration |
|FO86 |Change active admin.contract fees |
|FO8E |Create admin.contract event |
|FO8F |Change admin.contract event |
|FO8G |Display admin.contract event |
|FO8H |Admin.costs acct sttlmnt simulation |
|FOART|REsearch: Administration Web-User |
|HRCMP|Compensation Administration |
|HRCMP|Budget Administration: Display |
|HRCMP|Budget Administration: Change |
|IM_AR|Admin. of App. Request Archives |
|KA18 |Archive admin: assess., distr., ... |
|KE72 |Archive Administration: Line Items |
|KE73 |Archive Administration: Totals Recs |
|KPRO |KPRO Administration |
|OAAD |ArchiveLink Administration Documents |
|OG00 |Personnel Administration Customizing |
|OG01 |Personnel Administration Customizing |
|OMSM |CS MM Set Up Administrative Data |
|OOCM_|Compensation Administration Settings |
|OOML |Room Administration Mail Connection |
|OOPC |Administration: Personnel No. Check |
|OY22 |Create subadministrator Customizing |
|OYEA |IDoc administration |
|PA97 |Compensation administration - matrix |
|PA98 |Compensation Administration |
|PA99 |Compensation Admin. - Release Report |
|PACA |PF administration |
|PAT1 |Personnel Administration infosystem |
|PC00_|CBS survey salary administrations |
|PC00_|Tax Certificates - Administration 16 |
|PP26 |Plan Scenario Administration |
|PP2D |Administer Payroll Results |
|PSO5 |PD: Administration Tools |
|PUCA |PC administration for PF |
|PVSEA|Administer Search Engine |
|QD25 |Archiving Notifications: Admin. |
|S002 |Menu Administration |
|SA02 |Academic title (cent. addr. admin.) |
|SA04 |Name prefixes (centr. addr. admin.) |
|SA05 |Name suffix (centr. addr. admin.) |
|SA07 |Address groups (centr. addr. admin.) |
|SA08 |Person groups (centr. addr. admin.) |
|SA09 |Internat. versions address admin. |
|SA10 |Address admin. communication type |
|SARA |Archive Administration |
|SBPT |Administration Process Technology |
|SCC4 |Client Administration |
|SCON |SAPconnect - Administration |
|SCOT |SAPconnect - Administration |
|SCUA |Central User Administration |
|SCUM |Central User Administration |
|SE78 |SAPscript: Graphics administration |
|SECST|Administration of Secure Memory |
|SENG |Administration of External Indexes |
|SENGE|Explorer Index Administration |
|SIAC1|Web Object Administration |
|SLICE|Administer SAP Licenses |
|SLWA |Translation Environment Administratn |
|SM14 |Update Program Administration |
|SP12 |TemSe Administration |
|SPAD |Spool Administration |
|SPAT |Spool Administration (Test) |
|SPHA |Telephony administration |
|SPHB |SAPphone: System Administration |
|SSAA |System Administration Assistant |
|SSCA |Appointment Calendar: Administration |
|SSCA1|Appointment calendar: Administration |
|SSO2 |Workplace Single Sign-On Admin. |
|SSO2_|Workplace Administration SSO2 Ticket |
|STMA |Proposal Pool Administration |
|SURAD|Survey Administration |
|SURL_|Personalization for URL Gen. Admin. |
|SUUMD|Display User Administration |
|SWDC |Workflow Definition: Administration |
|SWEAD|Event Queue Administration |
|SWEQA|Event Queue Administration |
|SWEQA|Queue Administrator Maintenance |
|SWIA |Selection rep. for work items(admin) |
|SWRK |Administrtation using work areas |
|SWUF |Administration of Runtime System |
|SWUL |Customizing: Process Administrator |
|SWUX |SAPforms Administration |
|SYSAD|System Administration: Task List |
|S_ALR|IMG Activity: CIC_V_CCMCTIADMIN |
|S_ALR|IMG Activity: SIMG_EURO_ADMINUSER |
|S_BCE|IMG-Aktivität: BCDIGSI_ADMIN |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|S_PH0|InfoSet Query: Administration |
|TBD0 |Datafeed: Adminster Archives |
|TBD3 |Datafeed: Market data administration |
|TBD6 |Datafeed: Log file administration |
|WE46 |IDoc administration |
|WORKI|Administrtation using work areas |
----------------------------------------------------------
What the difference between tcode SE09 & SE10?
SE09 transaction is for workbench transport request wherein the developers can track their changes or modifications to the workbench objects .
Whereas SE10 is a customising transport request transaction.this is used for displaying customising requests. Sometimes this may be restricted to business analysts.
Proper way to delete a SAP client
Here goes:
1. log into the client to delete
2. go into SCC5 and delete client
3. log into another client and delete entry with SCC4
4. reorg database to recover database space.
Actually, if you check "on" the little "Delete Entry from T000" checkbox, you can skip step 3.
One other way of deleting a client which could give significant performance gain and save time is at OS level using - R3trans
To delete a client 200, you have to create a command file "del200" with following entries
Clientremove
Client = 200
Select *
Place the command file in /usr/sap/trans/bin
$ cd /usr/sap/trans/bin
$ R3trans –w
e.g $ R3trans -w del200.log -u 1 del200
To check the progress...
$ tail -f del200
Reorg the database post client delete
What is the best way to refresh QA from PRD?
How to make a system copy:
1. Take offline backup of both the server (source and target servers)
2. Verify the backup is successfully done.
3. Run the following command on source system.
a. Login as
b. svrmgrl
c. connect internal
d. alter database backup controlfile to trace;
e. exit;
f. Above command will generate a .trc file in /oracle/P01/saptrance/usertrace directory.
g. Copy the text from CREATE CONTROLFILE until the (;) and paste it in to any new .sql or controlfile.sql file.
h. Copy the controlfile.sql to target system.
i. Edit the file and replace the entire source SID to target SID.
j. Edit the reuse database command with the set database command
4. Copy the aft generated during the backup file from the source system to target system. (/oracle/
a. Change all the source
b. Only don't change the backup volume name it must be target system
c. Copy the above aft file name line from the source back
5. Shutdown the target server instance.
6. From this onwards all the command on the target system only.
a. Login as
b. run the SAPDBA
c. select J (Restore/Recovery)
d. select B (Full restore and recovery)
e. select A (Select backup of type)
f. Select the offline backup which you want to restore.
g. It will take some time to restore.
h. Once the database is restored login as
i. svrmgrl
j. connect internal;
k. startup nomount (if the database is already mounted shutdown it using the shutdown command)
l. run the following command
m. @controlfile.sql (file name of the control file contains the CREATE CONTROLFILE statement)
n. After the run the above command it should give the "Statement Processed)
o. alter database open resetlogs p. shutdown
q. Start the database and SAP services using startup.
7. After this you have to reconfigure the STMS.
8. All the jobs also you have to reconfigure and reschedule.
9. Reconfigure all the printers.
10. If you want to change the Client number then use the local copy tool and remove the original client after successfully import to new client.
Do you have a SAP Basis Question?
Problems in Heterogeneous Setup
We Planning to go for hetrogenius setup.
Development server - HP-UX11i,oracle9.2,sap47.
Production server - SUN Solaris with same oracle and sap version
My issue is that, will I face any problems in this setup?
Because right now developments are going on HP-UX.
Venkatesh
I am not in a hetro-geneous setup.
But a similar installation I have already visited, which one of the big installation in Bangalore, they used Sun solaris as dev and HP UX as PRD. But no problems. Logically SAP system just looks for where the data is stored and works on TCP/IP. It just does not matter where the database resides for development and production.
The transport mechanism just transports from the development client to productive client. So I assure you 100% you can plan this. This is supported by SAP.
You can even plan NT as development machine. It just works fine.
But some advantages are available if you have similar systems.
1. When updating patches for a particular os/db combination , you have a chance to see how it works, before trying
it on productive system.
2. You learn a lot on installation, sizing, many other related issues at the time of development, so that you can easily
sort it our at the time of installation of prd system.
The above cannot be told as advantageous, but take a note of these. After all it is a matter of cost + convenience!
I am on NT + SQL Server with SAP 4.7 Ent. and its works fantastic without any problems.
Steps For SAP Client Copy / System Refresh
Before doing a client copy, you need to prepare the following :-
1. Find the source client space with the client size custom program which can be implemented using the rel. note:
Find the space of the client - '0118823'. This will give you the size of the source client.
2. If your are on Unix OS, adjust all the file systems according to PRD file system to fit the PRD client in DEV
client based on space requirements also.
3. You can do the client copy by remote or export/import client.
Remote method is not preferred if you are doing a large client copy.
Do a client export/import.
4. To speed up the export/import, use R3trans export/import for the clustered tables.
Please find the rel. notes related to performance improvements for cluster tables in OSS.
5. Do import and post processing.
Note: Export may take 10 to 20 hr. for 50gb of data
import may take 4 days and post import will take 8 to 15 hr. for 50gb of data. And it all depends on
your system performance.
Please refer OSS rel. notes for the few RZ10 parameters which needs to be set for cluster tables to speed up the process.
Note :-
If it is a fresh installation, do this --
1. SCC4 --> Create client no. and fill other details.
2. Logon to the newly created client with SAP* and PASS as password.
3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client
4. Preferably do a test run initially to check if it can go well.
5. As a care check space in databases.
What are step and procedure to create a client & to take a client copy from source to target.
By: Kavitha.G
If you are copying from same system then flow the below steps:
1. Create the client in Tcode scc4.
2. Before that create a logical System in BD54.
3. Login in the newly created client with
user Name : sap* and password : pass
4. Use the Tcode sccl to copy the client.if you are not familiar with the client copy. Try a test run and then schedule it in background.
5. You can select the needed profile.
6. To view the log files use the tcode scc3.
If you are using different system then create a rfc connection in sm59.test the connection and then continue from the 1st step
You can also import and export a client. Use scc7 for importing from the client and scc8 fro exporting from the source client
What is system refresh when and why it is done?
System refresh and client copy can be the same thing. Normally when you want to refresh a system this normally means refreshing the clients using a client copy like SCCL or SCC8.
A system "copy" is very different as this is far more involved than a simple "client refresh"
Imagine you have a DEV and a PRD system and after 6 months the data in DEV is very old so you would perform a client copy SCC8 from PRD to DEV using a profile that copies the application data from PRD to DEV - it actually deletes the data and replaces it with data from PRD. If however your DEV system died and needed to be completely rebuilt, you would use "Homogeneous System Copy" - you install the OS, Database and SAP and then process the system copy - which makes a complete copy of PRD (all clients)
Client copy - a single client refresh from PRD to DEV - can be just application data, or user data, or configuration or any combination you choose system copy - all clients 100% copied PRD to DEV
The system refersh is nothing but the deletion of the client and replacing the data from other client. For example : you have clients 100, 200 and 300. Suppose when you want to refresh the client 100 you remove the client 100 and replace it with 200 0r 300 as per your reqiurement. Mostly the refresh of clients will be happen at the time of development stage.
System Refresh is a simplified term to Client Copy. Client Copy means copying the production client on to the quality to test the real data. As recommend by SAP this need to carried out every 3 months.
The process to carry out the same is as follows:
1. Create a client on quality system using txn scc4
2. Create a RFC between Production system and Quality System (need to create on quality system)
3. Login to the newly created client using sap* and pass as a password
4. Txn sccl to start the client copy. You can test the client copy by selecting the test run option. (test run will estimate the time taken for the activity).
Tips by : Shriniwas Yannam, Perala
Copy a Client into a Stand Alone System
How to copy a client into a stand alone system?
The scenario is I have a 2 system landscape. I want to copy an existing client from DEV to a standalone system for some demo purposes.
There is an option for Client TRANSPORT which will help you perhaps:
A client transport differs from a remote client copy in that it does not use RFC. Like a remote client copy, however, a client transport is used to copy data between different R/3 Systems.
A client transport consists of two steps. First, a client export extracts client data from the source client to files at the operating system level. Second, the data is imported from the operating systemfiles into the target client.
To perform a client export, proceed as follows:
Log on to the source client. From the R/3 initial screen, choose:
*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport*(r) *Client Export*. Select the data to be copied using a profile.
Indicate the target system to which the client will be copied. (The target system must be defined in TMS as part of the transport domain.)
Begin the client export. As copying is a lengthy process, use scheduled background processing. The client export performed in the source system
3 data files at operating system level:
. RT< number >; this file contains client-specific data
. RO< number >; this file contains Cross-client data
. RX< number >; this file contains SAPscript texts
Depending on the type of data selected through the client transport profile, the client copy command
files added to the buffer of the target system are
The client export change requests are not imported when an Import all takes place. Therefore, you must import these requests into the target client using TMS. You must import the data in the following order: first cross-client data, then client- specific data.
After the import process has completed, post-import activities are required possible for object generation steps. After completing the import, log on to the target client. From the R/3 initial screen, choose:
*Tools *(r) *Administration *(r) *Administration *(r) *Client Admin. *(r) *Client Transport *(r) *ImportEditing*
To display client transport logs, use the Transport Organizer.During client transport, a Repository consistency check can be performed by clicking the RFC system check button in Transaction SCC8. If inconsistencies are detected, a list of the ABAP Dictionary tables definitions missing in the target system is generated. This will help your recognize in advance formal problems that may occur during the import of the source data.
SAP Basis Tips by : Jaswant Purba
Copy users from DEV to PRD
1. Login to the client in your DEV system from where you want to copy.
2. Execute scc8. Select the profile sap_user.
Specify the target system.
Click on 'schedule as background job'.
3. Specify the background server name i.e. the server name where your DEV system is available.
4. Click on 'schedule job' button.
Verify the things and click on 'continue' button.
5. You will have options to specify the start time.
Specify to suit your convenience.
You can see the log in scc3.
6. Login to the destination client and execute scc6.
Specify the request number which was created during scc8.
You need to specify only one request number. Other(s) will be taken automatically.
Click on 'Prepare import'.
7. Specify the target client and click on 'Import'.
Log can be checked in scc3.
Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
1. How to lock the client from logon
2. How to see the all the users connected per day (with the activities they have done and resource utilization)
I cannot answer the first straight away, but the second questions, there are many available SAP transactions.
use STAT very useful and many options available if you use them correctly.
1. I don't know how how to lock the client, but you can lock the system with "tp locksys
2. STAT transaction
You can lock the system thro "tp locksys" (Transport Utility).
Check the other options of "tp" command for locking the specific client under the system thro "tp help".
With this solution I can lock the whole system, but not specified by client.
Send me in more detail....
There's no way to lock a client.
You have to lock all users from loging in of this specified client.
The way you do is by user administration setting the lock.
We can lock a client using SCCR_LOCK_CLIENT and unlock SCCR_UNLOCK_CLIENT functions.
Once we run this functions with a client as input , that client will be locked/unlocked. Actually this function set flag '' Client is locked temporarly for client copy" in client maintanance menu. And the client will be available for users other than DDIC and SAP*. If you try to login in that client as any user , system gives message that ' Client locked temporarly'..
Is there any t-code to lock a client?
There is no direct tcode to lock a client. the easiest way to lock a client is
1. run tcode SE37
2. type function module name - SCCR_LOCK_CLIENT
3. enter the Client No.
4. execute the function module.
SAP 4.7 Enterprise Install Failure "FRF-00007
SAP 4.7 Enterprise Install Failure "FRF-00007 Unable to open RFC connection"
During the Install of SAP 4.7 Enterprise the installation fails with "FRF-00007 Unable to open RFC connection" when you are prompted to enter the DDIC password.
The solution I found was that you need to stop the install then log ito SAP with the User SAP* with password - "06071992" then change the DDIC password to whatever you want.
Once done restart the install and continue to the stage where you need to install the DDIC password, enter the changed password and the installation will continue without errors.
The only OSS notes related to this was "Press the continue button" and the installation may continue, or restart the installation.
With Compliments from:
SAP Installation Procedure on WIN 2k Adv Server
With Compliments by: Bhanu Prakash Pogula
Email: bpogula@sify.com
INSTALLING HARD DISK ( IF U ARE TRYING TO
LOAD SAP ON A SEPARATE HDD)
Connect HDD with cable
Win 2000 installation.
1. Go to bios set up by pressing continuously clicking del on start.
2. change the first bootable device to CD.
3. insert the CD and RESTART system.
4. click any key to boot from CD.
5. click ENTER
6. click ENTER again
7. Click on C ( to continue)
8. click on F8 ( to agree)
9. partitions C: 4197Mb, D 12000Mb, E 6000Mb
10. select C drive
11. click ENTER to install
12. click ENTER again to continue
automatically restarts, set up continues.
13. click on NEXT
14. click on NEXT
15. click on NEXT
16. key RBDC9-VTRC8-D7972-J97JY-PRVMG
17. click on NEXT
18. TYPE no of concurrent connections 9
19. click on NEXT
20. TYPE COMPUTER NAME 46IDES
21. click on NEXT
22. remove IIS (deselect)
23. click on NEXT
24. enter date & time
25. click on NEXT
26. finish
WINDOWS CONFIGURATION
Creating partitions for new disk.
STARTà PROGRAMMESà ADMIN TOOLSà COMP MANAGEMENTà DISK MANAGEMENT
1. right click on unallocated space.
2. click on CREATE PARTITIONS,
3. click on NEXT
4. click on NEXT
5. type 11320 (partition size)
6. click on NEXT
7. click on NEXT
8. type file system NTFS
9. click on quick format
10. click on NEXT
11. click on FINISH
12. again right click on unallocated space
13. repeat the exercise from point 5 but for complete size
note
C drive contains operating system
E/D drive contain 46C software
S drive contains SAP software..
PERFORMANCE
MY COMPUTERà propertiesà advanced à performance optionsàchange,
1. Select S drive.
2. type initial =1600& max =1652
3. click on SET
4. click on OK
5. click on OK
6. click on OK
NETWORK SETTINGS
STARTàSETTINGSà CONTROL PANELà ADD/REMOVE HARD WARE,
1. click on NEXT
2. click on NEXT
3. select ad a new device
4. click on NEXT
5. select (now I want to select from Hardware list)
6. click on NEXT
7. select network adaptors,
8. click on NEXT
9. select MICROSOFT
10. click on NEXT
11. click on NEXT
12. click on FINISH
13. close all windows
14. right click on MY NETWORK PLACES,
15. go to properties,
16. right click on local area connections
17. should be able to see Microsoft loopback adaptor on the screen.
18. select properties
19. select TCP/IP
20. click on properties
21. select ( use the following IP addresses)
22. type IP addresses 198.1.1.1
23. subnet mass 255.255.255.0
24. click on OK
25. select show icon on Task bar
26. click on OK
27. close all windows.
HOST FILE CONFIGURATION
1. go to WINDOWS EXPLORER
2. select C drive, WIN NT, system 32 , DRIVERS, etc
3. double click on HOSTS
4. open with note pad
5. go to end of the page
6. type IP address 198.1.1.1
7. press TAB once
8. type 46cides
9. press TAB twice
10. click on SAVE
11. click on EXIT
12. RESTART sytem
Software contains three folders
1. 46cides ( a. KERNEL, b. ORACLE 817, c.ORACLE PATCHES
2. DB EXPORT
3. SAP GUI
ORACLE INSTALLATION
1. 46CIDESàoracle 817à NTài386àsetup run the set up by double clicking
2. click on NEXT
3. source path …………
destination path : S:\oracle\ora81
4. click on NEXT
5. click on NEXT
6. click on NEXT
7. type GLOBAL DATA BASE NAME : ORACLE
8. click on NEXT
9. click on INSTALL
10. click on OK
11. click on EXIT
12. click on YES
13. close all windows
14. startà programsàadmin toolsà services
15. select ORACLE SERVICES
16. select all ORACLE releated services ONE BY ONE.
ORACLE PATCHES
46CIDESà ORACLE PATCHESàPATCHà DISK1à INSTALLà WIN 32
1. set up (double click)
2. click on NEXT
3. click on NEXT
4. click on INSTALL
5. click on INSTALL
6. click on EXIT
KERNEL INSTALLATION
46CIDESàKERNELàNTà I386à MMC
1. double click on IMMC
2. click on NEXT
3. I agree
4. click on NEXT
5. click on NEXT
6. click on NEXT
7. click on FINISH
46CIDESàKERNELàNTà I386à NT PATCH
1. double click on R3DLLINS
2. click on Ok
3. close all windows
4. RESTART
46CIDESàKERNELàNTà COMMONà
1. double click on R3 SET UP
2. type SAP SYSTEM NAME IND
3. click on NEXT
4. click on NEXT
5. click on NEXT at 85%
6. click on NEXT automatically logs off
7. login and control+alt+del
CENTROL INSTANCE
Startàprogramsàsap system for INDà install CENTRAL INSTANCE
1. click on NEXT
2. type instance no OO,
3. click on NEXT
4. click on NEXT
5. click on NEXT
6. click on NEXT
7. click on NEXT
8. click on NEXT
9. click on NEXT
10. click on NEXT
11. click on NEXT
12. type LOCATION OF KERNEL CD E:\46cides\kernel
13. click on NEXT
14. password AAA
AAA
15. click on NEXT
16. password AAA
AAA
17. click on NEXT
18. select NO LDAP SUPPORTS
19. click on NEXT
20. click on NEXT
21. click on NEXT
22. click on NEXT
23. click on EXIT when finished
DATA BASE INSTANCE
Startà programsà SAP set up system for INDà install database instance
1. click on NEXT
2. click on NEXT
3. click on NEXT
4. click on NEXT
5. click on NEXT
6. click on NEXT
7. click on NEXT
8. click on NEXT
9. click on NEXT
10. click on NEXT
11. click on NEXT
12. click on NEXT
13. click on NEXT
14. click on NEXT
15. click on NEXT
16. type location of CDS for KERNEL : E:\ 46cides\KERNEL
for EXPORT : E:\DBEXPORT
17. click on NEXT
18. password AAA
AAA
19. click on NEXT
20. click on NEXT
21. click on NEXT
22. click on NEXT
23. click on EXIT at 32%
24. log off
25. log in
26. user à ind adm
27. passwordà AAA
28. OK
WINDOWS EXPLORERà C:\USERS\IND ADM\INSTALL\R3 SET UP FILE
1. double clik on R# set up file
2. select database R3S
3. open
4. type pass word AAA
AAA
5. click on NEXT
6. at 91% password AAA
AAA
7. at 93% start MMC
8. click on NEXT
9. at 100% EXIT
10. click on STOP MMC
11. restart system
POST INSTALLATION
E:\apgui320\gui\windows\win 32\setup(double click)
1. click on NEXT
2. click on INSTALL
3. click on FINISH
4. click on SAP logon
5. select NEW
6. type DESCRIPTION : 46CIDES
7. type application server : 46CIDES
8. type system no : 00
9. start MMC
10. close MMC
11. log in SAP
12. client 000, user sap* password 06071992
13. txn code SM28
14. ENTER ( TO CHECK ERROR)
15. RESULT : NO ERROR REPORTED ( in installation)
STMS
Description à Student
Click on SAVE
Go to overviewà transport routes
Select display change mode (second icon)
Configurationàstandard configurationà single system ( main menu)
Click on Enter
Configurationàdistributeàactivate
Click on Enter
F3 (to go back)
RZ 10
Utilitiesà import profiles of active servers
Click on Enter
Click on F3 (to go back)
Profile click on F4
Select INDà DVEMGS00à46CIDES
Select EXTEND MAINTà change
Select create paramaeters9 icon)
Type paramter name : rdisp/max-wprun-time
Type parameter value ; 3000
Copy icon
Go back
Click Yes
CREATE PARAMETER
Paramater name : abap\ field exit
Value ; YES
Select COPY icon, go back à YES
Create parameter
: login/system-client
: 800
select copy iconàgo back à yes
create parameter
:eu/iwb/installed/languages
:EN
select COPY icon – go back à YES
again go back
click on YES
click on SAVE
click on YES
click on ENTER
click on ENTER
(USER CREATION)
TXN : SU01
user : sapuser
select : create icon
address logon data
title go on clicking ENTER no of times
first name initial password : abc
last name repeat pass word : abc
DEFAULTS
Logon language : En
Output device ; LP01
Select : Out put immediately & decimal
PROFILES
Type 1. SAP – ALL
TYPE 2. SAP – NEW
SAVE
Log off from SAP
Login to SAP
type user : sapuser password : abc
new password : abap
repeat password : abap
txn : SALE
IMGàerror handlingàbasic work flow settings
Select AUTOMATIC CUSTOMIZING icon
Go back
Txn 00w4
Select DISPLAY CHANGE MODE icon
Create icon
CREATE
Prefix no 978
System ID IND
Client 000
Click on Save
Local object
Cancel X
CREATE
Prefix no 972
System ID IND
Client 800
Click on Save
Local object
Cancel X
TXN SE 38
Program name : Z FIRST
CREATE
ACCESS KEY : 36687663221261278694
TITLE : DEMO
TYPE : EXECUTOR
Click on SAVE
LOCAL OBJECT
Log off from SAP
Log into SAP
Client : 800
User : sap
Pass word : 06071992
RUN txn SU01 for 000 client
Log off from SAP
Log into SAP
Client : 800
User : sap
Pass word : abc
Click on ENTER
Enter new password : abap
Logoff
Stop MMC
Steps for Creating Package
How to create transport package in R/3?
By: Venkat
Steps for Creating Package:
1. Run the SE80 T-code in the R/3 system.
2. Click on Edit Objects option on the top of the window.
3. Select "Development Coordination" in the Object selection window.
4. Select "Package" radio button and provide the package name(like any name: "BIDEV").
5. Click on "Create" icon.
6. Fill the required details ( Short description, Appli.Component, Software Component)
7. Select "SAVE" Icon.
8. It will generate the10 digit New Transport Request: " BI7K900005"
9. Click on Continue.
Menu Path:
Go to SE80 -> Edit Object (button) -> Development Coordination Tab -> Enter Package name and then press the create button
Saposcol Is Not Running
Basis Ticket :
We have the ECC 5.0 installed on the HP UX. Whenever I am trying to run the t-code ST06 for the application server of the production, I am getting one message "SAPOSCOL is busy, try again". I am able to get the run the ST06 for other application servers.
The current version what we have for Saposcol is : Version: COLL 20.87 640 - hpxOscol 07/2003.
It will be a great favour if anybody can provide me the steps from the scrach in how to run the SAPOSCOL.
1) login as
2) check if your saposcol is running at unix level
ps -ef | grep saposcol
3) go to /sapmnt/NPD/exe
Check if saposcol file is existing
Check the owner and the permission of the file
To start SAPOSCOL with the command saposcol (or saposcol -l).
Saposcol can run independent of the SAP system, so you can try to start it individually using:
Try to start saposcol with command saposcol -l
You can know status of the saposcol by saposcol -s and stop it by saposcol -k
---
Try to check, if you have cleaned up Share memory present in /usr/sap/tmp/dev_coll & try to get latest patch of SAPOSCOL.
Shared memory cleanup can be done as follows:
1) Login with the user
saposcol -d
Collector > clean
Collector > quit
saposcol -k to stop the collector.
Before restarting
saposcol -d
Collector > leave (You should get a message Shared memory deleted)
Collector > quit
cd /usr/sap/tmp
mv coll.put coll.put.sav
cd
saposcol
"coll.put" ,if this file contains the old shared memory and should be deleted in order to get a clean start. Please look at the SAP Note 548699 and follow point 7 very carefully:
If you are unsuccessful in clearing shared memory, please try the following commands to clear the shared memory:
2)
$ saposcol -kc
$ saposcol -f
If this doesn't work, then try:
3)
cleanipc 99 remove on the O/S level (Check note #548699 first)
4) If not you have to do a OS level restart to fix the issue.
Also check if new saposcol can be applied as per Note 19227
Disable SAP USERS to logon multiple times
How to block a user id being logging in for more than twice? i.e. I must restrict the user to be logged in at a time not more than twice (Not sessions, Loggins only).
Set the parameter in RZ10.
login/multi_login_users = set to 1 to activate
login/disable_multi_gui_login = you can put a list of users that should be allow to logon multiple times
List the user IDs separated by commas ",".
Do not leave space characters between user IDs.
Restart the R/3 instance to see the changes.
Do you have a SAP Basis Question?
Hi Basis Sappers,
If you have a SAP Basis Administration question, please feel free to asked it in the SAP Basis forums.
Just send an email (with a relevant Subject Title) to the many helpful SAP Basis Peers in the forum.
The email for posting a new message is:
sapbasiscomponents@yahoogroups.com
If you are still not a member, just send a blank mail to:
sapbasiscomponents-subscribe@yahoogroups.com
Maximum No. Of SAP Session Per User
You set this Parameter : rdisp/max_alt_modes in transaction RZ10.
Add in the above parameter in the Instance Profile - Options Extended Maintenance.
Restart the R/3 instance.
The default maximum no. of sessions in 4.6x is set as 6 session per user.
Most company will reduced the number of session per user but not increase it.
Best regards,
SAP Basis, ABAP Programming and Other IMG Stuff
http://www.sap-img.com
Suppress Multi Login / Set Minimum Password Length
Suppress SAP Multi Login Message
You can suppress the multi login message by setting the parameter in the instance profile.
It is necessary if your company allows a single users to have multiple login and there tends to be cases where users will choose Options 1 which terminates the rest with the same user IDs. This can result in loss of data as the users may have not click the save button.
Use transaction code 'RZ10'.
Parameter name : login/multi_login_users
In this parameter, enter the name of all the users separated by "," comma for which you want to suppress the message while multi login with the same user IDs.
Take note that the multi login counter still counts even though you have suppress the message.
Currently to login into SAP, minimum password length = 3 characters.
How to define/change the minimum password to be 8 characters?
by: Rajdeep
To change parameter:
1.go to RZ10
2.Select instance profile---->Extended mantainence--->change
3.In next screen click on create parameter,type login/min_password_lng and click on change/display
4.Then it will show the default value
5.In the parameter field put ur parameter.SAVE the changes
6.Reboot the application server .
User Administration:
SU01 User Maintenance
SU01D User Display
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet users
SU10 User Mass Maintenance
SMLG Maintain Logon Group
SUPC Profiles for activity groups
SUIM Info system Authorizations
PFCG Profile Generator
PFUD User Master Data Reconciliation
Client Administration:
SCC3 Checking Client Copy Log
SCC4 Client Administration
SCC5 Client Delete
SCC7 Client Import Post-Processing
SCC8 Client Export
SCCL Local Client Copy
SCC9 Remote client copy
Database Administration:
DB01 Analyze exclusive lock waits
DB02 Analyze tables and indexes
DB12 DB Backup Monitor
DB13 DBA Planning Calendar
DB15 Data Archiving: Database Tables
Transport Management System:
STMS Transport Management System
SE01 Transport and Correction System
SE06 Set Up Workbench Organizer
SE07 CTS Status Display
SE09 Workbench Organizer
SE10 Customizing Organizer
SE11 ABAP/4 Dictionary Maintenance
SE16 Data Browser
SE80 Repository Browser
SM30 Call View Maintenance
SM31 Table Maintenance
Background Jobs Administration:
SM36 Define Background Job
SM37 Background Job Overview
SM39 Job Analysis
SM49 Execute External OS commands
SM62 Maintain Events
SM64 Release of an Event
SM65 Background Processing Analysis Tool
SM69 Maintain External OS Commands
Spool Administration:
SP01 Output Controller
SP11 TemSe directory
SP12 TemSe Administration
SPAD Spool Administration
Other Administration Tcodes:
AL11 Display SAP Directories
BD54 Maintain Logical Systems
OSS1 Logon to Online Service System
SALE IMG Application Link Enabling
SARA Archive Management
SICK Installation Check
SM14 Update Program Administration
SM35 Batch Input Monitoring
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SAINT SAP Add-on Installation Tool
SPAM SAP Patch Manager (SPAM)
SPAU Display modified DE objects
SPDD Display modified DDIC objects
ST11 Display Developer Traces
Daily monitoring TCodes:
AL08 Current Active Users
SM12 Display and Delete Locks
SM13 Display Update Records
SM21 System Log
SM50 Work Process Overview
SM51 List of SAP Servers
SM66 System Wide Work Process Overview
ST22 ABAP/4 Runtime Error Analysis
ST01 System Trace
ST02 Setups/Tune Buffers
ST04 Select DB activities
ST05 Performance trace
ST06 Operating System Monitor
ST10 Table call statistics
ST03 Performance, SAP Statistics, Workload
SU56 Analyze User Buffer
Other Monitoring Tcodes:
OS01 LAN check with ping
RZ01 Job Scheduling Monitor
RZ03 Presentation, Control SAP Instances
ST07 Application monitor
STAT Local transaction statistics
Other Useful Transactions Codes
AL22 Dependent objects display
BAOV Add-On Version Information
SA38 ABAP reporting
SE38 ABAP Editor
HIER Internal Application Component Hierarchy Maintenance
ICON Display Icons
WEDI IDoc and EDI Basis
WE02 IDoc display
WE07 IDoc statistics
WE20 Partner profiles
WE21 Port definition
WE46 IDoc administration
WE47 Status Maintenance
$TAB Refreshes the table buffers
$SYNC Refreshes all buffers, except the program buffer
How To Do the TMS Configuration?
We have two systems with version ECC 5.0
The SID is XY1 - Development & Quality
XY6 - Production
Now we need to configure TMS between these two systems by assigning XY1 as domain controller. I beleive we also need to establish an RFC Connection for this. Also explain how to update the local files of this systems?
How can I make thro it?
First decide which system you would like to define DOMIAN controller. Configure the Domain Controller Steps to configure
------------------
1. Login to the system with sap* in client 000
2. Goto SE06.
3. Click Post installation activities
4. Goto STMS
5. It will ask for Domain controller name.
6. Enter DOMAIN_
7. Click Save button
Steps to add the other system with Domain controller
----------------------------------------------------
1. Login to system with sap* in client 000
2. Goto SE06
3. Click Post installation activities
4. Goto STMS
5. It will ask for Domain controller name.
6. Enter System ID of the Domain controller
7. Enter DOMAIN_
8. Click Save button
9. Login to Domain controller system
10. Approve the added system.
SAP Basis Tips by : Chandrasekaran
The SID is XY1 - Development & Quality
XY6 - Production
Now we need to configure TMS between these two systems by assigning XY1 as domain controller. I beleive we also need to establish an RFC Connection for this. Also explain how to update the local files of this systems?
How can I make thro it?
First decide which system you would like to define DOMIAN controller. Configure the Domain Controller Steps to configure
------------------
1. Login to the system with sap* in client 000
2. Goto SE06.
3. Click Post installation activities
4. Goto STMS
5. It will ask for Domain controller name.
6. Enter DOMAIN_
7. Click Save button
Steps to add the other system with Domain controller
----------------------------------------------------
1. Login to system with sap* in client 000
2. Goto SE06
3. Click Post installation activities
4. Goto STMS
5. It will ask for Domain controller name.
6. Enter System ID of the Domain controller
7. Enter DOMAIN_
8. Click Save button
9. Login to Domain controller system
10. Approve the added system.
Post Installation Steps For ECC 5.0
What are the post installation steps after I have installed the Central Instance and Database instance?
Initial Consistency Check
SM28
1. Logon to the newly refreshed SAP system and run transaction SM28
2. Ensure that no errors are reported. Otherwise, take the necessary steps to correct the problems.
Edit Batch Jobs
1. Set the fields as follows
Job name: RDDIMPDP*
User name: *
Job Status: Released and Ready checked off, all others unchecked
Fr: 01/01/0001
To: 12/31/9999
Or after event: *
2. Press
3. Highlight the first job in the list and press the
4. Examine the Exec Target field.
a. If the box is empty, press
b. If the box is not empty, then clear out the contents so the field is blank and press
5. Repeat Steps 3 and 4 *for* each additonal job listed.
Workbench Organizer Reconfiguration
1. Logon on to client 000 of the newly refreshed system with DDIC.
SE06
1. Select the Database Copy or migration option
2. Press the Post-installation Processing button.
3. When prompted Do you want to re-install the CTS?, press the Yes button
4. When prompted *for* the Source System of Database Copy?, make sure that the
5. When prompted Change originals from PRD to QUA?, press the Yes button
6. When prompted Delete TMS Configuration?, press the Yes button
7. When prompted Delete old TMS configuration?, press the Yes button
8. When prompted Delete Old Versions of transport routes?, press the No button
TMS Configuration
1. Logon on to client 000 of the newly refreshed system.
STMS
1. Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed
2. The information on *this* screen is automatically filled out from information provided during the SAP installation and should be correct. If it correct, then enter a description *for* the system and press
3. From the Overview menu, select Transport Routes
4. From the Configuration menu, select Adjust with Controller
5. Press the Yes button when prompted *if* you want copy the transport routes from the controller.
Import Printers
1. Logon on to the production client of the newly refreshed system.
STMS
2. Press
3. Double click on the
4. From the Extras menu select Other Requests, then Add.
5. In the Transp. Request box, enter the transport number containing the printer definitions that was exported. Press
6. Select the transport that was just added to the queue and press
7. In the Target client box, enter the productive client of the newly created system. Press
8. Press the
Client Configuration
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Define client as follows:
Client role: Test
Changes and transports *for* client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5. Press
6. Repeat steps 4 through 6 *for* any additional clients
Set System Change Option
SE06
1. Press the System Change Option button.
2. Set the global setting to Modifiable
3. From the Edit menu, select Software Components Modifiable
4. From the Edit menu, select Namespaces Modifiable
5. Press
Import Users
STMS
1. Press
2. Double click on the
3. Press
4. Locate the transport in the list containing the user exports done before the start of the refresh.
If the transport is NOT in the list, then from the Extras menu, select Other requests then Add. Enter the transport number and press
5. Highlight the transport and press the Import request icon .
6. At the client *import* screen, enter the target client and then press the Import button
7. Press
SCC7
1. Run the Post Client Import Processing
2. The transport number should be the same as that of the transport started in STMS
3. Schedule the job to run in the background. Do NOT schedule it to run immediately. We need to modify the job before it can be released.
4. Press
SM37
1. Set the fields as follows
Job name: CLIENTIMPORT*
User name: *
Job Status: All options checked
Fr: 01/01/0001
To: 12/31/9999
Or after event: *
2. Highlight the job that was created by SCC7 and press
3. Press the Step button.
4. Select the RSCLXCOP line and press
5. In the User box, enter the background user *for* that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
6. Press
7. Press
8. Press the Start condition button.
9. Press the Immediate button.
10. Press
11. Press
12. Job will start immediately once saved. Press
13. Continue to press
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Set the Protection to Protection level 1
5. Press
6. Repeat steps 3 through 5 *for* any additional clients
Deleting Source System Profiles
RZ10
1. From the Utilities menu, select Import Profiles then Of Active Servers.
(Note: All application servers of the target system must be started)
2. If the Display Profile Check Log screen is displayed, press
3. Select the Profile field and press
4. From the list select one of the profiles associated with the source production system.
5. From the Profile menu, select Delete, then All versions, then of a profile.
6. When prompted, press the Yes button to delete all version of the profile
7. When prompted to delete the file at the operating system level, press the No button.
8. Repeat steps 3 through 7 *for* all additional profiles associated with the source system
Reconfigure Operation Modes
RZ04
1. From the Operation Mode menu, select Timetable
2. Select Normal Operation and press the Change button.
3. Highlight 00:00 in the left hand column and press the Delete Assignment button
4. If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.
5. Once all the assignments are deleted, press
6. If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.
7. Press
8. Right click on one of the listed Operation modes and select Delete
9. Press the Yes button to confirm the deletion.
10. Repeat steps 8 through 9 *for* any additional operation modes
11. Press
12. Enter a name and *short* description *for* the operation mode
13. Press
14. Press
15. From the Settings menu, select Based on current settings, then New Instances, then Set
16. Press
17. Press the Yes button to save
18. From the Operation Mode menu, select Timetable
19. Select Normal Operation and press the Change button.
20. Highlight the 00:00 at the top and press
21. Highlight the 00:00 at the bottom and press
22. Press the Assign button.
23. Press
24. Press
Delete Update Failures
SM13
1. Set the fields as follows
Client: *
User: *
From data: 01/01/0001
From time: 00:00:00
2. Press
3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing
4. Press the Continue button to confirm the deletion.
Delete Batch Input Sessions
SM35
1. From the Edit menu, select Select All
2. Press
3. Press the checkmark button to confirm
4. Press the Yes button to start the delete.
Reorganize Spool
SPAD
1. From the Administration menu select Clean-up Spool
2. Check all check boxes and enter 0 *for* minimum age
3. Press the Execute button
4. Once complete, press
5. From the Administration menu select Check Consistency
6. Press the Delete All button.
SP12
1. From the TemSe database menu, select Consistency check
2. When the check is complete, press the Delete All button.
Delete Invalid Background Control Objects
SM61
1. Press
2. Press the Cleanup List button.
Restrict Outgoing Email and Faxes
SCOT
1. Double click on the green Fax entry
2. From the Supported Address Types area, press the Set button that is beside Fax
3. In the Address area, ADJUST AS NECESSARY
4. Double click on the green SMTP entry
5. From the Supported Address Types area, press the Set button that is beside Internet
6. In the Address area, ADJUST AS NECESSARY
Adjust RFC connections.
SM59
1. Expand the TCP/IP connections section
2. Double click on the first entry listed
3. Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system.
Make changes as necessary.
4. Press the Test Connection button to test the connection
5. Press Press
6. Repeat steps 1 through 5 *for* each additional RFC connection
Convert Logical Systems
Under no circumstances perform *this* procedure on a Production system
BDLS
1. When warned to read the documentation, press the checkmark button.
2. In the Old logical system name box, press
3. Select one of the production Logical System names that needs be changed (i.e. WIIPRD400)
4. In the New logical system name, enter what that logical system name should be called on *this* newly refreshed system (i.e.WIITRN400) Note: Ignore Error/Warning about duplicate system by clicking on the check mark.
5. De-select the Test Run and Existence check on *new* names in tables options
6. From the Program menu, select Execute in background
7. Press the checkmark button when asked to select a spool device
8. Press the Immediate button when asked *for* the schedule
9. Press
10. Use SM37 to monitor the job
11. When job is complete, repeat steps 2 through 10 *for* any additional logical system names that need to be changed.
Adjust Logical Systems names
SALE
1. Expand Sending and Receiving Systems, then Logical Systems
2. Click on the execute icon beside Define Logical System
3. Press the checkmark button to confirm that the change is cross client
4. …
Allow Certains Settings to be modifiable
(Refer to Note 356483 *for* more Details)
SM54
1. Enter V_T001B in the Table/View box.
2. Select the Generated Objects option.
3. Press the Create/Change button.
4. Enter any access keys *if* requested
5. Change the Recording routine to no, or user, recording routine.
6. Press
7. Press
8. You are prompted *for* transport. Create a *new* local transport.
9. Repeat steps 1 through 8 *for* the following objects. You can specify the same transport you created above.
V_T001B_GL
V_T093B_01
V_T093B_02
BSI Configuration (R3 HR Systems only)
SM59
1. Expand TCP/IP Connections
2. Highlight BSI70-US-TAX and press the Change button
3. Change the program field to \\
4. Double check the target host and gateway point to the correct server
5. Press
6. Press the Test connection button to test. If the connect is not successful, take the necessary steps to resolve the issue.
SE38
1. In the Program field, enter RPUBTCU0
2. Press
3. Select option BSI version 7.0
4. Press
5. BSI should *return* tax calculations. If there are errors, take the necessary steps to resolve.
Reconfigure DB13 schedule
DB13
1. Using the print out created before the refresh, recreate the DB13 calendar.
Client Configuration
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Define clients as follows depending on client role
Development
Client role: Customizing
Changes and transports *for* client-specific object: Automatic recording of changes
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Quality Assurance
Client role: Test
Changes and transports *for* client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Training
Client role: Education
Changes and transports *for* client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Sandbox
Client role: Test
Changes and transports *for* client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5. Press
6. Repeat steps 4 through 6 *for* any additional clients
Set System Change Option
Skip *this* section of the system is a Development or Sandbox System.
SE06
1. Press the System Change Option button.
2. Set the global setting to Not Modifiable
3. Press
Release Background Jobs
Currently, all background jobs, except *for* system standard jobs have been placed on hold (status scheduled).
Where To Find Deleted Transport Request Logs
Is there any way to find out deleted transport requests logs?
If you have deleted from SAP level. Then you need to check at the OS level in /usr/sap/trans/log directory else you can check for the SLOG and ALOG folder also.
If total request has been deleted then you can also do the transport manually at OS level.
or
If you have simply deleted the the requests from import queue through "Extras-> Delete imported requests" in transaction STMS_IMPORT and have not deleted the logs at OS level, then you can check in "Goto-> Import History" in the same transaction to view the requests.
Just double click on the request you want and you enter the "Display Object List" screen for the particular request.
Here you can click on the secong "Spectacles" icon to display the transport steps of the request in each of your SAP system.
Just double click on a step, e.g. 'Import', 'Check Version','Export' etc. to display the log for that particular step.
You can also view the logs from operating system in the directory
What is ECC? Where to find the installation steps of ECC 5/6.0 with SQL as database and on windows platform with the steps including Solution Manager installation?
http://service.sap.com/instguides
ECC means Enterprise Central Component.
There are all the relevant installation guides. You NEED SAPNet access because without a registered and licensed SolMan installation number you will not be able to generate the SolMan key for the ECC installation.
Upgrade to 4.7
Have you gone through an upgrade to 4.7?
What are the difference or changes associated with 4.7.
If you are currently on 4.6C and are inching forward to upgrading to 4.7 then this information might be useful to you.
There is very little difference between 4.6 and 4.7, the only "steps" you should need are steps in SU25 ( skip step 1) Then go through all your role and perform a merge old new to bring in the new authorization objects
Just to forewarn you of a potential problem which have been encounter at the point of writing.
After updating/ modifying roles in step 2C, when going back into 2C to make sure all roles are now green, 70% have gone back to red!
The maintenance done is ok, but there seems to be a problem while trying to go back into the roles again to re-generate.
SAP recognizes them as needing "adjustment", so you cannot pick them up in mass generate in PFCG as they do not come in, even though the authorizations tab is red.
This problem is currently with SAP and it is confirmed that nothing have been done wrongly.
Generally, the work is quite manageable in the upgrade, but don't be surprised at how big the upgrade is when compared to upgrading from 46b to 46c.
If we have full software of 46c and 47E is it possible to upgrade 46c to 47E or there is a seperate 47E upgrade software need to be requested from SAP?
Where I can get the document with upgrade steps on the service market place?
It is of course possible and supported:
http://service.sap.com/inguides
--> SAP Components
--> SAP R/3 Enterprise
--> (choose your version)
at the bottom there is an "Upgrade guide" for Windows and Unix.
For Upgrades it is recommended to read ALL the notes mentioned in the
upgrade guide and to make sure one is using
- the correct version of the "tp" program
- the correct version of the "R3trans" program
- the correct version of the "R3up" program
All that is explained in the upgrade guide and in the corresponding notes.
If this is your first upgrade you should take a person, that has some experience on doing that for the first time.
Installation of SAP R/3
Currently we are going to install SAP on a new IBM server from the existing COMPAQ server. Where can I get the steps for that.
Configuration is :
OS - windows 2003 server
DB - Oracle 9i
SAP 4.7
http://service.sap.com/instguides
--> SAP Components
--> SAP R/3 Enterprise
--> SAP R/3 Enterprise Core 4.70 / Ext. Set 2.00 (SR1)
--> Inst. Guide - R/3 Enterprise 4.7 x 2.00 SR1 on Win: Oracle
The above url is the SAP Service Marketplace with all the information you need to install, configure and run system. You need to be a valid licensed customer with a user ID and PASSWORD to use that.
Without access you won't be able to successfully run any SAP systems because it has notes, patches etc.
Transport of ABAP Query
I am involved in this upgrade project to 4.7
The users are not able to find any reports (in QA System) which were there before the upgrade in SQ01. But they can see them in production which is not yet upgraded. They want me to copy all the reports to the QA system now....I dont have any idea how to do that.
I remember a similar problem upgrading to 4.6C from 4.5B ......
Take a look at OOS note 672784.
You can transport queries between systems in SQ02 (hit the lorry button) or run program RSAQR3TR.
You download the infosets, queries etc into a file and load them into whichever system you wish.
Just wanted to share my experience of transporting queries:
I needed to move a user group, 2 infosets and 3 queries from a 4.6 system to a 4.7 system.
When I tried doing this via the SQ* transactions I did not get the import/export option, so instead ran RSAQR3TR.
Step 1. Run RSAQR3TR in 'old' system. Select EXPORT and specify the objects to be transported.
(System includes these in an automatically created transport request)
Step 2. Release this transport and request it be transported to 'new' system.
(This results in the entries being populated in transport table AQTDB in 'new' system).
Step 3. Run RSAQR3TR in 'new' system. Select IMPORT and tick the Overwrite checkbox. Specify the transport number in the field labelled 'dataset with imports'.
(RSAQR3TR gives the message that stuff has been imported OK).
Step 4. In my example I still couldn't find the queries, so ran RSAQR3TR one more time, this time specifying 'Copy Standard Area -> Global Area'.
(Now my queries etc were available in new system).
Perhaps there are better ways, but after 1.5 days of struggling I was glad to get this far.
SAP Message : TP_CANNOT_CONNECT_SYSTEM
Using spam, trying to import SPAM UPDATE, I get the above message together with TP_INTERFACE_FAILURE.
1. tp works fine when I am doing transports (tp import devk90000 qas client=400 u1 or addtobuffer).
2. niping -t SELFTEST works fine
I worked through notes 44946 and 96907, but could not resolve the issue.
The support packages have been uploaded from the DEV box into the QAS queue. The DEV and QAS boxes are in the same centre on the network, by fibre. I am working on QAS.
I get this message in QAS:-
"SAP system is waiting for the inclus. in transport domain"
When trying to update the config from DEV client 000, I get this message:-
System DEV is unknown in the Transport Management System
Diagnosis
An error occurred in the TMS communication layer.
System: QAS.DOMAIN_DEV(000)
Function: TMS_CI_CHECK_ACCESSTOKEN
Error: UNKNOWN_SYSTEM (DEV)
System Response
The function terminates.
Procedure
Log this system on to the Transport Management System.
If this error occurs in the function TMS_CI_CHECK_ACCESSTOKEN, then the TMS configuration was deleted in the R/3 System QAS.DOMAIN_DEV(000).
Configure the TMS in this R/3 System again.
You need to:
1. logon to the transport domain controller with admin user in client 000.
2. Run STMS
3. System overview
4. select QAS
5. Menu line option "SAP system" --> "Approve"
6. Distribute configuration
When you are logged on the transport domain server and run STMS --> System Overview. Is QAS listed? If so, select it and perform the checks under "SAP Systems" in menu line.
If they are not successful you might want to try the following to configure the TMS on QAS from scratch.
First delete QAS from system overview on the domain server.
Then do the following steps...
In your QAS system in client 000.
Run tcode SE06 --> Database copy or Database migration --> Perform post-installation actions.
Then confirm that you want to delete all old CTS/TMS config and type in QAS as source system for the database copy.
Then run STMS again and type in the correct data for the transport domain controller.
Logon to the transport domain controller in client 000. Run STMS. Open system overview.
Choose the SID of the QAS system and click on "SAP System" in the menu and choose Approve.
This will add the QAS system to your TMS config again.
Perform the checks from menu line "SAP Systems" again.
It seems like a lot maybe, but it only takes a couple of minutes to perform.
We are in the process of implementing SAP for our overseas sales offices. However, the Server will be situated at our country. We want our overseas sales office to connect to our SAP Server through VPN. What should be the optimum internet bandwidth that they should use at their place to connect to our SAP server? Does SAP recommend any standard bandwidth for this process?
From our experience, there is no general rule that one can follow, as several factors will affect the connectivity
1. No of hops between your ISP and that of the remote site, the more hops the poorer the performance, even having large bandwidth may not improve the performance by much if there are numerous hops in between.
2. Is the Internet connectivity solely used for your VPN or other purposes such as web surfing, email etc, other traffic can consume large amount of traffic thus causing your SAP performance to be poorer
3. ISP's bandwidth to the public internet - If the ISP is heavily over subscribed, and has limited bandwidth connecting to the international network, you will find that you will not be able to get the international throughput you subscribed for as such, performance may be poor even you have paid for a line with a large bandwidth
4. No of users at your remote office using the VPN - In general the lines we use are 64kbps for sites with approx 3-5 users, we are also using ADSL lines with 512kbps connectivity and they enjoy close to local Lan performance for SAP.
See from which network IP address and host name a user has logged on
To see the network IP address from which a user has logged on,
perform the following steps:
Call transaction OS01,
click "Presentation Server" button, "Change View" button.
If you are using Citrix, you will not be able to view the user individual IP address as it will be the same Citrix IP address.
To check the speed and quality of the user's network connection,
select the desired presentation server and click "10 X Ping" button.
11/22/2007
No System name and transaction code in SM04
If you have more than one application server, use AL08 instead of SM04.
or
It is because they are at the logon screen which has established a connection.
You will notice that the transaction code shown when there is no user name is SESSION_MANAGER.
This shows you which workstations out there have the login screen up but have not yet entered a user name and password.
The transaction column shows the Last executed transaction code.
Sometimes your users will have multiple sessions open. If they do, to the system, it is the same as multiple logins as it relates to the resources used etc.
So the user name will show up more than once in AL08.
Under the application server they are logged into, each instance of that user name on that application server represents a session open.
For instance if you run AL08, you will have your name show up at least twice on the application server you are logged into.
One will show AL08 and the other will not have a transaction next to it.
Then you will notice your user name showing up on all other application servers with no transaction. This is because you are using AL08.
Monitor and Administrate 4 SAP Systems
If there are 4 systems installed SAP, how should I connect all of them in one network so that I can administrate the 4 systems with one among them as main server.
A D V E R T I S E M E N T
This should help you:
After installing an R/3 System, you can use transaction RZ20 to monitor the system. To monitor all systems of your system landscape centrally from one system, first customize the alert monitor by choosing Tools > CCMS > Configuration > Alert monitor or calling transaction RZ21.
Then, to specify the remote systems by System ID and RFC destination (which must have been created beforehand), choose Technical infrastructure > Create remote monitoring entry.
Next, to change your monitor definitions (you can only change your own monitors), choose Tools > CCMS > Control/Monitoring > Alert monitor or call transaction RZ20.
Activate the maintenance function by choosing Extras > Activate maintenance function.
Then, double click on the monitor and choose Monitoring change.
Parameter R3system defines which systems can be monitored by an alert monitor. Change parameter R3system from
It will help you monitor & use spome other activities centrally.
Brief Description About SAP Basis Implementation
Please give a brief description about implementation process carried out.
There is no standard Implementation process, it purely depends on which methodology person have adopted for implementation. I will give you broad view of implementation project... I am just starting from sizing of the servers ...
1. Identify the no of users and type of users
2. Design the technical system landscape of servers
3. Do the sizing based on users, documents created.
4. Convert your sizing requirement in to Hardware requiremnet
5. Consider the backup procedure also
6. Then start with the setup of development landscape
7. Define client strategy, transport strategy, User management.
8. Fix the support package levels.
9. Tune the system for performence
10. set up the QA systems
11. Define client copy strategy
12. Setup the PROD systems
13. Apply for Pre Golive report
14. Monitor system of db load
15. Apply post golive report
Solution Manager
What Is The Use of Solution Manager
What is the use of solution manager, and what we can do with solution manager?
A D V E R T I S E M E N T
Now a days solution manager is mandatory.
1. it is used for generating keys and downloading support packages
2. it is used to document user requirments and preparing senarios what needs to to be adopted using solution manager, where the blue print is the part of solution manager
3. it is used for reporting, solution desk,to manage the change requests and use to monitor entire landcape Central message processing in the SAP Solution Manager:
- Display customer data, problem description, priority, attached documents, Service Level Agreements (SLA)
- Assign processor
- Send messages to the creator and other processors
- Forward message to other processors or support units
- Create documents and URLs
- Attach documents
- Status assignment and monitoring
- Create a worklist with selection conditions
I have a requirement to install SAP Solution Manager Solution Support Enablement Package (SEP) in our solution manager 4.0. This SEP contains, RBE, TDMS, ...etc.,
I checked for the software download at market place but couldn't find the software package, can anyone help me to download this SEP for windows/oracle.
Look at following:
http://service.sap.com/swdc -> Download -> Installations and Upgrades -> Entry by Application Group -> Installations and Upgrades -> SAP Technology Components -> SAP Support Enablement Package - >SAP Support Enabl. Package 1.0
How to configure the service desk on Solution Manger 4.0. I want to cofigure Solution Manger only for service desk I have install Solution Manger 4.0. What is the Step please explain.
Check: http://service.sap.com/rkt-solman
There are tutors, PDFs and powerpoints to guide you through the configuration process.
If you have 3 or 4 client systems, must you install SAP solution manager for each one of these systems and manage them independently -or- 2. Can you install One Solution manager, that will manage all 3 these systems in one solution manager -or- 3. Do you install 3 Solution managers for each of the systems, then another one linked to the 3 individual solution managers, which then in turn manages the 3 systems in one.
In any System landscape only one solution manager is installated in one system and it will communicate with the other system using the RFC and collect the report from each and every system through (SDCCN).
Applying SP4 to Windows 2000 Server
You need to download a newer SAP kernel. You will need an OSS ID and password to access http://service.sap.com/patches. And you will need to know what R/3 version, database, and OS you currently use.
A D V E R T I S E M E N T
Once you are at the patches website, you will need to click in the navigation tree:
R/3 -> R/3 + ?Release number? -> Binary patches ->
SAP Kernel + ?Release number? + 32-Bit -> NT/I386.
Download everything from the database section and everything from the database independent section.
One of the files you downloaded should start with SAPCAR and end with a *.exe.
Rename this file to SAPCAR.EXE and place it in the c:\winnt\system32 directory.
Go to \usr\sap\
I usually create a \usr\sap\
Uncompress all the files you downloaded by opening a DOS box and typing:
SAPCAR -xvf
All files ending with .SAR or .CAR must be uncompressed. All the extracted files need to be moved to the \usr\sap\
Once everything has been downloaded, uncompressed, and moved into the exe\run directory, you can start the SAPOSCOL, the listener and the database services again. And then you should be able to start SAP. If there are any application servers for this database instance, the SAP software will update those kernels on startup.
If the SAP instance STILL does not come back up, you can take down everything again and restore the exe\run directory with your backup copy. Nothing will have been damaged.
________________________________________
SPAU and SPDD
When you apply a package, a large number of objects are changed.
If you have applied any OSS notes to objects in your system, the hot package may overwrite these objects.
SPDD is used to identify dictionary objects
and
SPAU (repository objects), will identify any objects where the hot package is overwriting changes you have made through OSS notes.
You must check all objects identified in SPAU and decide whether you need to reapply the OSS note or reset the code to the original SAP Code.
If, for instance, you are applying hot package 34, SPAU identifies an object where you have applied an OSS note. You must check the OSSs note and see if SAP have fixed that note in a hot package.
If the OSS note has been fixed in hot package 34, then you should reset the object to its original source code. This means that there is no repair flag set against this object again and it is now SAP standard code.
If, however, the object is not fixed until hot package 38, or there is no fix available you have to reapply the OSS note, otherwise users will encounter the problems they had before the note was applied.
You must transport all reapplied notes and Reset to SAP Standard objects after you apply your hot package to your QAS and PRD systems.
________________________________________
How to know the kernel version of a SAP R3 system?
-----Original Message-----
Subject: How to know the kernel version of a SAP R3 system
Hi all
Could someone tell me how can I find the Kernel version of a SAP R3 system ?
example, for those releases
SAP R3 4.0B, 4.5B, 4.6B, 4.6D and so on ....
Thanks for your help
-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system
From any screen choose System-->Status then click the 'other kernel info' icon (between Navigate and Cancel).
The same information can be found at OS level in the dispatcher trace file: /usr/sap/
Regards,
-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system
Hi,
Goto transaction sm51, and click (not double click) on the the Database
server and then click on release notes. there you will see the SAP R/3
kernel and patch level etc.
Regards
-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system
You can use the System ==> Status and then Other
Kernel Info button to get the details about the Kernel
Release, Patch levels etc.
Regards,
-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system
I think an even more convenient way to do this is to use SM51. Highlight
the server you are interested in and click on "Release Information". This
provides you a location to view all servers with out logging on to each
one. The answer below will give you information about the server you are
connected to only.
-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system
Also try "disp+work -v" on server.
-----Reply Message-----
Subject: RE: How to know the kernel version of a SAP R3 system
go to transaction SM51 -->release information
-----End of Message-----
Administration
AL11 Display SAP Directories
BD54 Maintain Logical Systems
OSS1 Logon to Online Service System
SALE IMG Application Link Enabling
SARA Archive Management
SCC3 Copy Analysis Log
SCC4 Client Administration
SCC5 Client Delete
SCC7 Client Import Post-Processing
SCC8 Client Export
SCC9 Remote client copy
SCCL Local Client Copy
SCU0 Customizing Cross-System Viewer
SICK Installation Check
SM01 Lock Transactions
SM02 System Messages
SM04 User Overview
SM12 Display and Delete Locks
SM13 Display Update Records
SM14 Update Program Administration
SM21 System Log
SM35 Batch Input Monitoring
SM50 Work Process Overview
SM51 List of SAP Servers
SM56 Number Range Buffer
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM66 System Wide Work Process Overview
SAINT SAP Add-on Installation Tool
SPAM SAP Patch Manager (SPAM)
SPAU Display modified DE objects
SPDD Display modified DDIC objects
ST11 Display Developer Traces
ST22 ABAP/4 Runtime Error Analysis
SU56 Analyze User Buffer
Alert Monitoring
AL01 SAP Alert Monitor
AL02 Database alert monitor
AL04 Monitor call distribution
AL05 Monitor current workload
AL16 Local Alert Monitor for Operat.Syst.
AL18 Local File System Monitor
RZ20 CCMS Monitoring
Configuration
FILE Cross-Client File Names/Paths
RZ04 Maintain Operation Modes and Instances
RZ10 Maintenance of Profile Parameters
RZ11 Profile parameter maintenance
SE93 Maintain Transaction Codes
SM63 Display/Maintain Operating Mode Sets
SPRO Customizing: Initial Screen
SWU3 Consistency check: Customizing
Database Administration
DB01 Analyze exclusive lockwaits
DB02 Analyze tables and indexes
DB12 DB Backup Monitor
DB13 DBA Planning Calendar
DB15 Data Archiving: Database Tables
Jobs
SM36 Define Background Job
SM37 Background Job Overview
SM39 Job Analysis
SM49 Execute External OS commands
SM62 Maintain Events
SM64 Release of an Event
SM65 Background Processing Analysis Tool
SM69 Maintain External OS Commands
Monitoring
AL08 Current Active Users
OS01 LAN check with ping
RZ01 Job Scheduling Monitor
RZ03 Presentation, Control SAP Instances
ST01 System Trace
ST02 Setups/Tune Buffers
ST04 Select DB activities
ST05 Performance trace
ST06 Operating System Monitor
ST10 Table call statistics
ST03 Performance, SAP Statistics, Workload
ST07 Application monitor
STAT Local transaction statistics
STUN Performance Monitoring (not available in R/3 4.6x)
Spool
SP01 Output Controller
SP11 TemSe directory
SP12 TemSe Administration
SPAD Spool Administration
Transports
SCC1 Client Copy - Special Selections
SE01 Transport Organizer
SE06 Set Up Workbench Organizer
SE07 CTS Status Display
SE09 Workbench Organizer
SE10 Customizing Organizer
SE11 ABAP/4 Dictionary Maintenance
SE16 Data Browser
SE80 Repository Browser
SM30 Call View Maintenance
SM31 Table Maintenance
STMS Transport Management System
User Administration
PFCG Profile Generator (Activity Group Maintenance)
PFUD User Master Data Reconciliation
SU01 User Maintenance
SU01D User Display
SU02 Maintain Authorization Profiles
SU03 Maintain Authorizations
SU05 Maintain Internet users
SU10 User Mass Maintenance
SMLG Maintain Logon Group
SUPC Profiles for activity groups
SUIM Infosystem Authorizations
Other Transactions
AL22 Dependent objects display
BAOV Add-On Version Information
SA38 ABAP reporting
SE38 ABAP Editor
HIER Internal Application Component Hierarchy Maintenance
ICON Display Icons
WEDI IDoc and EDI Basis
WE02 IDoc display
WE07 IDoc statistics
WE20 Partner profiles
WE21 Port definition
WE46 IDoc administration
WE47 Status Maintenance
$TAB Refreshes the table buffers
$SYNC Refreshes all buffers, except the program buffer
The recent releases from SAP are:
---> SAP ECC 6.0 SR1 / SR2 / SR3 IDES with EhP 3
---> SAP R/3 4.7 EE
---> SAP CRM 7.0 / 2007 / 5.0 with Live Cache
---> SAP SCM 7.0 / 2007 / 5.0
---> SAP SRM 7.0 / 2007 / 5.0
---> SAP BI 7.0 with SEM 6.0
---> SAP BIW 3.5 with SEM 3.1
---> SAP PI 7.1 (XI 7.1) / PI 7.0 (XI 7.0)
---> SAP EP 7.0
---> SAP MDM 7.1 / 5.5
---> SAP Solution Manager 7.0 / 4.0
---> SAP Netweaver 2004s / Netweaver7.0
---> SAP IS Utilities 6.0
---> SAP IS Retail 6.0
---> SAP IS Oil 6.0
---> SAP IS Discrete Industries & Mill Products 5.0
---> SAP IS Discrete Industries & Mill Products 4.7
---> SAP IS Campus Management 6.0
---> SAP IS CWM (Catch Weight Management) 6.03
---> SAP IS DFS (Defense Forces & Public Security) 6.03
---> SAP WEB AS (Web Application Server) 6.20
---> SAP Net Weaver Composition Environment (CE) 7.1
---> SAP Enterprise Services Repository for SAP Net Weaver CE 7.1
---> SAP Supply Network Collaboration 2007 (SNC)
---> SAP TDM (Test Data Migration Server) 3.0
---> SAP Business Objects
---> SAP Business One
---> SAP GRC Tools 5.3
---> SAP BPC 7.0 NW
---> SAP AFS 6.0
---> Oracle Applications 12i / 11i
---> ECC 6 <-> BI 7.0 with Integration
---> ECC 6 <-> PI 7.0 with Integration
---> ECC 6 <-> EP 7.0 with Integration
---> ECC 6 <-> SCM 5.0 with Integration
---> ECC 6 <-> CRM 6.0 with Integration
---> ECC 6 <-> SOLMAN 7.0 with Integration
---> ECC 6 with ESS <-> MSS Configuration
---> SAP BPC 7.0 Installation and Configuration
Set Up Your Development System
Questions Answered
• What kind of infrastructure is appropriate for my development?
• How does the Developer Studio support the central development infrastructure?
• Does the Developer Studio also support the also an individual development?
• What if I started developing locally, can I migrate my local components into the central infrastructure later on?
Introduction
Developer Studio and SAP NetWeaver Development Infrastrucure (NWDI) Integration
The Developer Studio provides full support when developing large-scale Java projects for standard technologies (J2EE, Java EE, Web services, etc.) and for SAP technologies (Web Dynpro, Java Dictionary, Composite Applications, etc.). The special feature of the SAP NetWeaver Developer Studio is that - in addition to providing toolsets for different Java development requirements - it is integrated consistently into a robust SAP development infrastructure. The combination of both aspects makes the Developer Studio a highly productive and comprehensive development environment that spans the whole development cycle of Java projects, including integration of a source management system, plus configuration and transport management.
SAP Component Model
In addition to the central infrastructure services (version control, central build, transport services), the SAP component model is a central part of the NWDI. This is based on the concept of the software and development components and is used to structure the software on the basis of individual components that define clear use relationships between each other and therefore form a prerequisite for modularization and reuse. However, developers work with projects in the Developer Studio as before. In other words, a development component is identified with a project in the Developer Studio and is also used to group development objects as suited to a certain type of project.
More information: SAP's Component Model
Development Process
Depending on whether or not, and to what extent, the NWDI is used during the development process, we can derive various use scenarios:
• Developing in a team using the full NWDI
• Developing locally with the SAP Component Model
• Developing locally without SAP Component Model - not applicable for composite applications!
Activities
Selecting Your Development Infrastructure
Development of composite applications is tightly coupled to the SAP Component Model and the SAP Component Model itself is coupled to with the NWDI. The first decision to be made is if you want to work locally or in a team environment using the full NWDI. The local development process gives you a quick start into component based development and you can extend you development environment any time.
More information: Local Development as a Start to Component Based Development
Once you have decided which development infrastructure you use, refer to the Prerequisites section that provides you with information about the features, capabilities and prerequisites that are required for this use case.
Setting Up the Development System for Local Development
To get local development going you need to perform the following steps:
1. Start the Developer Studio.
2. Choose Window Open Perspective Other... Development Infrastructure .
3. Choose Local Development.
4. From the context menu of Local Development choose New Development Configuration Create from Scratch .
5. Provide the parameters for your development configuration.
6. Optional: Distribute Development Configuration to team members using file sharing. Local development does not provide version and source control but you can share your development components with other developers.
Setting Up the Development System for Team Development
The NWDI provides a wizard that guides you though the different steps of setting up the development configuration.
More information: Wizard Based Configuration of DI (server), First Steps in Development Infrastructure (Developer Studio)
Next Steps
Set Up Your Development Project for the Composite Application
Which Table is the Developer Key Stored In
If you would like to look up at your developer key and save it and have it available for the next system refresh.
The table name is DEVACCESS and can be viewed with SE16 and SE11.
For new ABAP developer, you will be prompt for the developer if you are trying to create a program using the standard SAP naming convention.
Customer own created program should all start with a "Y" or "Z".
What is SAP Landscape?
By: Kunal
Landscape is like a server system or like a layout of the servers or some may even call it the architecture of the servers viz. SAP is divided into three different lanscape DEV, QAS and PROD.
- DEV would have multiple clients for ex: 190- Sandbox, 100- Golden, 180- Unit Test.
- QAS may again have mutiple clients for ex: 300- Integration Test, 700 to 710 Training.
- PROD may have something like a 200 Production.
These names and numbers are the implementer's discreet on how they want it or they have been using in their previous implementations or how is the client's business scenario.
Now whatever you do in the Sandbox doesn't affect the other servers or clients. Whenever you think you are satisfied with your configuration and you think you can use it moving forward, you RE-DO it in the golden client (remember, this is a very neat and clean client and you cannot use it for rough usage). As you re-do everything that you had thought was important and usable, you get a transport request pop up upon saving everytime. You save it under a transport request and give your description to it. Thus the configuration is transported to the Unit Test client (180 in this example).
You don't run any transaction or even use the SAP Easy Access screen on the 100 (golden) client. This is a configuration only client. Now upon a successful tranport by the Basis guy, you have all the configuration in the Testing client, just as it is in the Golden client. The configuration remains in sync between these two clients.
But in the Testing client you can not even access SPRO (Display IMG) screen. It's a transaction only client where you perform the unit test. Upon a satisfactory unit test, you move the good configuration to the next SERVER (DEV). The incorrect or unsatisfactory configuration is corrected in Golden (may again as well be practised in the sandbox prior to Golden) and accordingly transported back to 180 (Unit Test) until the unit test affected by that particular config is satisfactory.
The Golden client remains the 'database' (if you wanna call it that) or you may rather call it the 'ultimate' reference client for all the good, complete and final configuration that is being used in the implementation.
In summary:
Landscape : is the arrangement for the servers
IDES : is purely for education purpose and is NOT INCLUDED in the landscape.
DEVELOPMENT ---> QUALITY ----> PRODUCTION
DEVELOPMENT : is where the the consultants do the customization as per the company's requirement.
QUALITY : is where the core team members and other members test the customization.
PRODUCTION : is where the live data of the company is recorded.
A request will flow from Dev->Qual->Prod and not backwards.
1. Sandbox server: In the initial stages of any implementation project, You are given a sandbox server where you do all the configuration/customization as per the companies business process.
2. Development Server: - Once the BBP gets signed off, the configuration is done is development server and saved in workbench requests, to be transported to Production server.
3. Production Server: This is the last/ most refined client where the user will work after project GO LIVE. Any changes/ new develpoment is done is development client and the request is transported to production.
These three are landscape of any Company. They organised their office in these three way. Developer develop their program in Development server and then transport it to test server. In testing server tester check/test the program and then transport it to Production Server. Later it will deploy to client from production server.
Presentaion Server- Where SAP GUI have.
Application Server - Where SAP Installed.
Database Server - Where Database installed.
What is the meaning of "R" in R/3 systems?
R/3 stands for realtime three tier architecture. This is the kind of architrecture SAP R/3 system has.
R/3 means three layers are installed in Different system/server and they are connected with each other.
1) Presentation
2) Application
3) Database
Why do we call client 000 as golden client?
Golden client contains all the configuration data and master data so some extent. All the configuration settings are done in golden clients and then moved to other clients. Hence this client acts as a master record for all transaction settings, hence the name "Golden Client".
SAP BASIS (BC)
Security Components
Page 1 of 5
1.0 Introduction
SAP has done nothing less than change the entire systems landscape for enterprises. The benefits it can bring have led to widespread adoption across the globe. One of the key benefits SAP brings to an enterprise is the ability to integrate the data both within the enterprise, and between it and it’s partners / competitors. In many cases organizations today are both partners and competitors at the same time. Think of wholesalers and distributors, SAP and Oracle, AT&T and BT, or two oil giants who have an upstream joint venture. These companies use SAP to integrate process between themselves for their mutual benefit. This ability to integrate, however, brings with it a particular risk – that of exposing their data to the un-authorized outside world.
Entire companies have been built up around highly guarded intellectual property and process secrets ... and could easily fall if this was breached. Therefore, keeping the security of the organization intact is one of the vital aspects of any SAP implementation.
SAP BASIS addresses all security issues by incorporating an authorization module. With increased potential for security breaches in the computer systems around the world, BASIS consultants face a tough task of maintaining the integrity and administering the security of SAP systems. Interoperability features of a SAP system makes this task a bit more difficult.
2.0 SAP Security Components – The Big Picture
SAP security in an integrated environment can be viewed in the form of discrete components as shown below (figure 1).
Figure 1
Tight security is required for each of the above components (Network, Workstation, Operating System and Database) as a breach made in one area can compromise the entire system.
The scope of this article is SAP Application Security, which can be achieved with the help of SAP’s BASIS security application through the concept of authorization.
In SAP, security is administered for objects (profiles and authorizations). Users are only authorized to see or change the parts of the system required by their respective job responsibilities.
SAP BASIS (BC)
Authorization Concepts
Page 2 of 5
2.1 SAP Authorization Concept
The SAP authorization concept is based upon the logical relationship between a user ID and the range of system authorizations with which it can be associated. The architecture of the authorization system is based upon the utilization of several individuals but related logical components: Profiles, Objects, Fields, and Authorizations. The user ID refers exclusively to profiles. Each profile grants a set of specific system access authorizations to user. Figure 2 illustrates the hierarchical authorization concept in SAP.
Figure 2
2.2 Composite Profiles
Composite profiles refer to the various employee roles available in the corporation (for instance: Purchasing / Receiving Clerk or Accounts Agent). As the name suggests, composite profiles may contain multiple user IDs necessary to perform all the business operations associated with a particular role. A composite profile may encapsulate another composite profile(s). In practice, a model composite profile should be recognized for each possible role in the organization, which may be used to produce hybrid composite profiles. The over-existence of the hybrids can defy the very purpose of composite profiles and they should be created only when specific needs arise.
2.3 User Ids
User ids allow access to SAP applications. Each user must have a corresponding profile specifically assigned. In many situations, multiple composite profiles can be assigned to a user ID, depending on the role(s) an individual user is responsible for, in the business processes.
2.4 Authorizations
Authorizations are the key building blocks of SAP security. Authorization is the process of assigning values to fields present in authorization objects. In SAP, access to all system functionality is achieved through a complex array of authorizations. Sometimes users find that they lack the necessary authorizations to perform a certain function in the system, in which case the message: "You are not authorized..." is displayed at the bottom of the screen.
An authorization process may ask for second associated authorization process which in turn asks for third and so on. For example, the task of paying a vendor invoice may require 10 different authorizations.
SAP BASIS (BC)
Security Configuration
Page 3 of 5
3.0 Security Configuration in SAP
Security configuration and administration in SAP is a multi-phase process. Four key security components are required to ensure the adequate security, privacy, and integrity of information. The phases are as follows:
3.1 User Authentication
The first phase comprises confirmation of user identity and results in authentication of user. Unauthorized access to SAP system is prevented through this initial check. This ensures system integrity by regulating secure access through genuine user authentication.
3.2 Creating and Assigning Authorization Profiles
A Profile Generator (PG) is used to automatically generate and assign authorization profiles. This tool was released with SAP version 3.1g and above. The administrator can also create authorization profiles manually.
Note: Profile Generator can be retroactively installed in SAP versions 3.0f and above.
The authorization objects can be selected using the SAP Profile Generator. Administrators can automatically generate authorization profiles for function-specific access to SAP users after configuring initial settings.
The entire authorization functionality of SAP signifies a new approach to authorization. The administrator can define user authorization based on SAP functions. Based on the selected function, the PG groups objects in administrator-created authorization profiles.
Authorization profiles created by a Profile Generator are based on the given authorizations. It also speeds up the process and simplifies administrator/user communication facilitating both the administrator and users to use the same SAP function terminology. To auto-generate an Authorization profile, an Activity Group needs to be created.
Activity Groups contain simple profiles and usually represent employee or job roles. They are user-defined and allow administrator to organize and maintain system activities. Activity group when used as an information database reduces data entry time. Administrators can define activity groups in two steps:
1. Selecting the criteria, such as access controls.
2. Dividing the activities into appropriate groups.
For example, activities can be organized by functions, such as human resources, payroll, or administration or by job classes, such as computer programming activities, or accounting activities. A combination of function-specific activity and job-specific activity can also be implemented.
Security implementation with the new Profile Generator is based on the creation of activity groups or a collection of linked or associated activities, such as tasks, reports, and transactions.
Consider a business situation involving a company, ABC Inc. faced with transaction security hiccups in business dealings with its dealers. To address this problem, the company can create authorization profiles for its dealers using the profile generator features. This can be done by implementing the following instruction set:
• Instruction 1: A dealer activity group should be created. Name this activity group as Dealer.
• Instruction 2: All dealer-specific business transactions should be included in the activity group.
• Instruction 3: Generate an authorization profile for Dealers.
• Instruction 4: Assign Dealer to a "new user" or in your system and update master records.
Following this procedure will ensure complete functional access to the new user using the system as Dealer.
SAP BASIS (BC)
Auditing and Monitoring
Page 4 of 5
3.3 Auditing and Monitoring
In this subsequent phase, a track of the authorizations created (previous phase) is kept. Detailed accounts of system events are used to record the actions of a user corresponding to that unique user account identifier. Auditing/Monitoring activities should be in compliance with enterprise’s overall IT strategy and should be performed on a weekly, monthly, quarterly, and yearly basis.
Figure 3
There are some key tasks that should be included in a monitoring plan. The following reviews should be a part of an ideal monitoring plans.
Using System Logs and Security Audit Logs
The system log records critical information important events. Each individual application server maintains local log files to which the information is written periodically. The security audit log records areas such as successful and unsuccessful dialog log-on attempts, RFC log-on attempts, changes to user master records, and transaction starts.
Reviewing User Activity
All SAP system users must be continuously monitored so that their problems can be rectified as soon as they occur. The timely attention to user problems can reduce administration overheads.
For example, if a SAP administrator wants to check for unrecognizable user Ids or the users trying to use non-permitted transactions, administrator can execute transaction AL08 and review user activity.
Monitoring User access in BASIS User Group
The BASIS users in a SAP system have access to sensitive areas of an organization. Therefore it is vital to monitor their access. Following instructions can be performed to check the access of BASIS User group.
Instruction Set
• Enter transaction SUIM to view Repository Information of the system.
• Follow the Menu Path:
o User > Lists of users (according to selection criteria) > user IDS (Double Click).
Monitoring Change Requests
All change requests need to be properly reviewed and controlled prior to being applied. This formal process needs to be detailed enough to ensure that separation of duties and other control features are not breached. Strong integration knowledge of the SAP system is required for this review. Critical profiles, authorizations, and transactions need to be identified and treated even more carefully.
Checking Important Default SAP Profiles
Administrators must check that default profiles act a template for user defined profiles and are not directly used in production. Default profiles contain values, which apply to all application servers. These include: SAP_ALL, SAP_NEW, S_A.ADMIN, S_A.CUSTOMIZ, S_A.DEVELOP, S_A.DOKU, S_A.SYSTEM, S_A.USER, S_ENT_IMG_GE, S_WF_ALL, and P_ALL.
Changing Default SAP User ID’s
SAP comes with some pre-configure clients (independent business units). They are client 000, 001 and 066 in the non-IDES system. In the IDES system, client 800 is the default client. SAP installation process automatically creates default user Ids and their corresponding passwords. SAP administrators must ensure that they are not used to access the system. The following table explains default user Ids in various SAP clients.
User Ids Client Name User Function
SAP* 000 and 001 SAP* denotes the default super user and has all administrative powers.
DDIC 000 and 001 DDIC user is responsible for the maintenance of the ABAP/4 Dictionary and the software logistics.
EarlyWatch 066 The EarlyWatch user has access only to monitoring and performance data.
Instruction Set
• Change all default passwords and verifying the password change by logging into various client areas.
• Assign SAP* to the Super user group.
o Enter transaction SE16.
o Enter SAP* into the field called BNAME.
o Click "Execute" and verify.
• As a final step, check that the secret super user has been created (with a different user ID and password). All of the authorizations assigned to SAP* should then be removed (an empty profile list followed by a password change.
SAP BASIS (BC)
Auditing Information System (AIS)
Page 5 of 5
Auditing Information System (AIS)
SAP Audit Information System (AIS) serves as a centralized repository for reports, queries, and views of interest to auditors. It is designed to address the overall system configuration as well as SAP business processes and their related control features, providing audit and security practitioners with the critical information they need to conduct effective reviews of their SAP systems. SAP administrators can use AIS for security auditing. The AIS plays a supportive role in providing security services for SAP systems. The primary function of AIS is auditing but auditing features can derive the measures that help in developing the security policy for SAP systems.
3.4 Administration and Maintenance
A successful security set up of a SAP system concludes with proper management and administration of user IDs, password resetting, audit trails, audit logs, access control list, and personnel responsibilities.
Security administration in SAP includes maintenance of the overall SAP security environment using the SAP Profile Generator, creating user-level activity groups and creating user master records.
The concept of SAP security is flexible as well as complex. SAP has a multi-layered integrated framework. To ensure adequate protection, security measures must be factored into all layers of the SAP infrastructure. With client/server architecture, SAP systems include many components that exchange information, each of which constitutes a layer of the SAP security infrastructure. Security is often not a priority in an implementation and as a result, the default security is not strong. SAP security functionality could be enhanced using various measures as discussed above.
Enterprises must develop a security strategy to ensure a secure and functional SAP system. A business critical application like SAP needs continuous monitoring and improvement of its security features.
We hope you have enjoyed reading this tutorial. If you are interested in learning more, check out the online SAP training courses offered by Michael Management Corporation
Legacy System Migration Workbench (LSMW)
SAP Query Report Design
SAP Solution Manager (SOLMAN)
... also if you are interested in having your own SAP system available to you 24/7 then check out
their offer for month by month SAP Access
Chapter 1
Oracle and SAP
In this chapter:
Introduction to SAP
Oracle/SAP Naming Conventions
The Oracle Database Layer of SAP
Oracle/SAP Administrators and Tasks
Administering an Oracle/SAP system, and maximizing the performance of its database, is a formidable job. You need to fully understand how both the SAP and Oracle systems work in isolation, and you need to know how they work together. In subsequent chapters of this book, I'll describe the specifics of that interaction. You'll learn how to use the special Oracle/SAP utilities, how to deal with the limitations of conventional Oracle functions, and how to place and reorganize files. Furthermore, after reading this book, you'll know more about monitoring databases during operation, tuning them, running backup and recovery, and performing special operations for systems that use parallel technologies or that support unusually large databases.
This chapter presents the fundamentals of the SAP architecture and describes how Oracle fits into the SAP runtime system. It also explains fundamental Oracle/SAP concepts -- the client/server model, special Oracle/SAP naming conventions, administrator roles, and basic administrative operations. First, though, let's take a step back and look at what SAP is.
Introduction to SAP
The SAP system is a collection of software that performs standard business functions for corporations. The system has become very popular because it provides a complete solution to standard business requirements such as manufacturing, accounting, financial management, and human resources. It incorporates the concepts of enterprise resource planning (ERP) and business process reengineering (BPR) into an integrated solution for business applications.
SAP is a product developed and marketed by the German company SAP AG. SAP is a German acronym for "Systemanalyse und Programmentwicklung," which can be loosely translated into "Systems and Application Products." Founded in 1972 by IBM application developers, SAP AG originally developed application products for the European marketplace. For nearly two decades, the company grew slowly. Early versions of its software were mainframe-based and appealed particularly to very large European corporations. Within the United States, sales were mainly to the Fortune 500.
SAP's R/3 System
During the 1990s, companies of all sizes began to embrace the concept of ERP systems and to gravitate toward prewritten business applications. With the introduction of its client/server SAP R/3 system in 1992, SAP AG, which already had a sizeable lead in the ERP market, unveiled a system that was attractive to medium- and small-sized companies as well as to the large companies already using SAP software. The SAP R/3 system runs on virtually any hardware/software platform and can use many different database management systems. One SAP system might be based on an IBM AS/400 running OS/400 using DB2; another might be based on a Sun Solaris (a dialect of Unix) using the Oracle RDBMS; still another might be based on an IBM PC running Windows NT using SQL Server. While SAP can be run with many different database products, nearly 85% of SAP customers now choose Oracle because of its dominance in the database marketplace. SAP software has become very popular in the U.S., and the company is now the world's leading application package vendor. SAP competes directly with Oracle Applications products and PeopleSoft products in the ERP marketplace.
The SAP R/3 code is written in an interpretive language called ABAP. (ABAP is a German acronym that, loosely translated, means "Advanced Business Application Programming.") ABAP is very similar to COBOL in its syntax. Use of the ABAP language allows SAP customers to extend the functionality of the base product, as described in the next section.
SAP Application Products
The SAP R/3 application offers end users the ability to run their entire business from a single application vendor. Some SAP customers choose to run their entire enterprise from SAP, while others run SAP only for specific business processes, such as manufacturing or finance. SAP is designed to allow customers to choose their own set of business functions, and it is sold in many configurations--both as specific business functions and as enterprise-wide solutions.
An SAP customer can choose whatever applications meet his site's specific business requirements. In addition, the customer is free to customize his SAP installation, adding new database entities as well as new functionality. For example, a company may use an inventory method that is nonstandard but essential to the company's efficiency; the basic SAP functionality can be modified to accommodate the specific requirements of that inventory method. The result of all of this flexibility is that virtually every SAP installation has its own specific configuration and set of functions. However, there are costs associated with customizing SAP. An organization that makes thousands of customizations to its SAP application may find itself spending millions of dollars to upgrade SAP: when SAP is upgraded, every customization must be identified in the ABAP code, and these changes must be reapplied to the upgraded SAP software, increasing the cost of the upgrade.
SAP products are distributed as applications with functional modules inside each application. Applications are generally focused on particular business functions. The modules within each application perform specific business tasks such as capital investment management, personnel administration, and quality management. The major applications are financials, human resources, and logistics, described briefly in the following sections.
In addition to basic business functions, SAP also offers products in the following areas (see http://www.sap.com/products/ for details):
SAP Business Intelligence initiative
SAP Supply Chain Management initiative
SAP Customer Relationship Management initiative
SAP Electronic Commerce
SAP Human Resources
SAP Treasury
SAP Real Estate
SAP Environment, Health, & Safety
When an SAP application is purchased with Oracle, each of the modules is delivered with a complete Oracle schema consisting of thousands of tables and indexes. Because the end user may purchase one or more components of SAP, SAP delivers the definition for many more Oracle tables and indexes than will be used by the running application. It is not uncommon to see an SAP application where thousands of tables and indexes are allocated but never used by SAP.
SAP has also branched out from traditional online transaction processing (OLTP) products into data warehousing with its Business Information Warehouse (BIW) and Supply Chain Optimization, Planning, and Execution (SCOPE) products.
Financials applications
The SAP Financials applications contain all of the functionality needed for enterprise-wide financial management. The modules within the Financials applications include the following:
Financial Accounting (FI)
Provides a complete financial accounting solution, including income statements, balance sheets, journals, ledgers, and all areas of financial accounting.
Enterprise Controlling (EC)
Assists in controller tasks.
Capital Investment Management (IM)
Assists finance organizations in their capital investments and tracking.
Controlling (CO)
Assists the controller organization.
Treasury (TR)
Assists with transactions related to the U.S. Treasury.
Human Resources applications
The SAP Human Resources (HR) applications are designed to provide a fully functioning HR system. They include two primary modules:
Personnel Administration (PA)
Assists with all areas of personnel administration, including applicant tracking and personnel history.
Personnel Development (PD)
Assists with training and educational status of employees.
These systems handle all of the mundane HR tasks, such as personnel and payroll, and also a number of more esoteric HR functions, such as seminar and convention management.
Logistics applications
The SAP Logistics applications include SAP's most popular modules. Logistics was the first area of entry for SAP. This includes virtually every area of manufacturing, from the initial acquisition of raw materials to the delivery of finished goods. The modules in this area include the following products:
Materials Management (MM)
Manages raw materials, inventory, and all aspects of goods manufacturing.
Production Planning (PP)
Offers sophisticated tools for planning large production environments.
General Logistics (LO)
Manages logistics for companies that require large-scale deployment of goods and resources.
Sales and Distribution (SD)
Manages the inventory and distribution of finished goods.
Plant Maintenance (PM)
Manages the resources required for large manufacturing plants.
Quality Management (QM)
Captures and maintains quality control for manufacturing environments.
Project System (PS)
Assists with the scheduling of project tasks and interdependencies between tasks.
The SAP R/3 System Architecture
All SAP R/3 applications are delivered in a three-tier client/server architecture, shown in Figure 1-1.
Figure 1-1. The SAP three-tier client/server architecture
The three layers are:
Presentation layer
The PC-based GUI interface that is used by the end-user community.
Application layer
The SAP application servers that service requests for data and manage the interface to the presentation layer.
Database layer
The actual DBMS that communicates with the application servers to fulfill their requests for data.
A piece of "middleware" called BASIS links the application to the database and the operating system. BASIS is most commonly associated with the GUI interface to SAP (called SAPGUI), and the BASIS Administrator is an SAP professional who is responsible for configuring the SAP environment, including the GUI screens and the SAP application servers.
SAP end users log into their PCs using SAPGUI, and are connected to a specific application server. This application server has pre-established connections with the Oracle database, and it services all requests for data. As I mentioned earlier, the access language for Oracle data is SAP ABAP. ABAP generates Oracle SQL (Structured Query Language), which is then used to service the end user's request for data. The communication between the application servers and the database, and between the client and the application servers, is TCP/IP.
While SAP is available for many different hardware platforms and operating systems, the majority of SAP systems use Unix-based servers for hosting SAP and the Oracle database. For this reason, as mentioned in the Preface, this book assumes the use of Unix in most examples.
The application server
While SAP uses the generic term application server to define a computer that receives connections from SAP clients, the actual connections are managed by SAP dialog servers.
A dialog instance is a software program that is running the SAP kernel (similar to an Oracle instance), and it is the job of the dialog instance to execute the ABAP programs and manage the requests for data and services. While there is generally a one-to-one mapping between an application server and a dialog instance, it is possible to have more than one dialog instance on an application server.
The central instance
The central instance is a concept that is unique to SAP. The central instance is a combination of hardware and software. It contains a physical server (the application server) and numerous software components, including a message server, a database gateway (a pre-established connection between SAP and Oracle--or another database), and various update, enqueue, dialog, and spool facility software. In most generic SAP architectures, there are numerous application servers but only a single central instance. However, in addition to managing the SAP interfaces, the central instance can also serve as an application server.
Bear in mind that SAP is very flexible, and there are many different ways to configure an SAP architecture to meet your business needs. However, most companies that implement SAP wisely choose to alter their business practices to accommodate SAP. By avoiding customization of its SAP application, a company can more easily upgrade its SAP software.
TIP: In 1998 SAP AG announced that the company is planning a four-tiered client/server architecture that will isolate the database from the SAP applications. Under the four-tiered architecture, the database will be insulated from SAP by the use of an active database cache called liveCache. This expanded memory cache will act as a separate layer, further insulating the Oracle database from the SAP application and allowing for the real-time manipulation of database objects.
Work processes
Any computer is capable of running one or more application servers. The main purpose of a dialog instance is to intercept requests for work from the SAP clients and to execute ABAP programs to service the requests for data. In addition, a dialog instance contains a dispatcher task and a set of work processes (WPs). The WPs are Unix tasks that can easily be identified by logging on to the Unix server and entering the following command:
ps -ef|grep dw
All SAP WPs contain the string "dw" (an acronym for Dialog Work) in their process names. The dispatcher on an SAP dialog receives requests from the SAP users (see Figure 1-2). In cases where a computer is running more than one dialog instance, there is one dispatcher for each dialog instance.
Figure 1-2. The SAP Dialog instance configuration
The WP is the task that is charged with executing the application's tasks. As such, a WP consists of an ABAP language interpreter and processor, a task handler, and a means of connecting to the Oracle database. SAP defines several types of work processes, as follows:
Dialog (DIA)
Executes interactive dialogs
Batch (BTC)
Executes background tasks
Update (UPD)
Manages database updates
Enqueue (ENQ)
Manages resource locks
Spool (SPO)
Manages data formatting and printing
The WPs can be viewed from a variety of places via SAPGUI, the SAP management tool. In SAPGUI, each screen has a name, and the SAPGUI screen called SM50 shows the currently executing WPs on a dialog instance (see Figure 1-3). SAPGUI has more than 100 screens, but in this book I'll focus on the major database screens. See Chapter 2, Oracle/SAP Utilities, for a discussion of SAPGUI and SAPDBA, the primary SAP utilities.
Figure 1-3. SAPGUI transaction SM50 displaying SAP work processes
The SAP system administrator, commonly called the BASIS administrator, controls the number of WPs that are defined to each application server. (See the "Oracle/SAP Administrators and Tasks" section later in this chapter.) In addition, the BASIS administrator can define "op modes" that control the number and type of WPs for each application server. For example, the BASIS administrator might define a day mode consisting of more dialog WPs for interactive sessions, and a night mode consisting of more batch WPs for the evening batch processes. These op modes are automatically switched by SAP according to the timetable specified by the BASIS administrator.
Oracle/SAP Naming Conventions
In order to maintain control over a vast set of applications, SAP has devised a convention for naming common components. These conventions are more than suggestions; in many cases, deviation from the naming conventions may cause some management components of SAP (e.g., SAPDBA) to function improperly. Thus, it's very important that all SAP systems follow these naming conventions.
One firm rule relates to the Oracle table and index names. Obviously, the SAP table structures and table names cannot be changed without changing the ABAP programs that access these tables, and SAP strongly urges customers not to alter the Oracle entities without the express consent of SAP AG. However, the Oracle administrator does have control over the naming of some Oracle entities (tablespaces and datafiles) and their placement within the filesystems and disk devices. The main areas of concern for the Oracle administrator are the Oracle SID name, the name and location of the Oracle initialization file, and the names of the Oracle tablespaces and datafiles; these objects are described in the following sections.
The Oracle SID in SAP
SAP mandates that the Oracle SID (System IDentifier), specified in Unix and some other operating systems as ORACLE_SID, always begin with an uppercase "SA," followed by a single alphanumeric digit or a single uppercase alphabetic character. Thus, the SID may have the values SA0-SA9 or SAA-SAZ. These are the only allowable choices for Oracle database SIDs. Throughout this book, I've used the notation sapsid to refer to the Oracle SID established for your own database.
The Oracle Initialization File (INIT.ORA) in SAP
Within an SAP system, the Oracle initialization file must exist with a specific name in a specific directory; if it does not, the SAPGUI and SAPDBA utilities will not work properly. Within both Oracle documentation and third-party books, the initialization file is ususally referred to as INIT.ORA, and I've followed that convention in this book. Note, however, that the actual name of this file in your system will be INITsapsid.ORA, where sapsid is the Oracle SID for your database (described in the previous section) and has the name you've specified for it. For example, if your Oracle SID is SA9, your initialization file will have the name INITSA9.ORA. In SAP systems, the intialization file must be located in the directory oracle/
In addition to the basic initialization file, SAP allows configuration or subinitialization files to be called from the INIT.ORA file. Most Oracle administrators find it more convenient to place all of the Oracle initialization parameters in a single file; however, sometimes it makes sense to segregate different types of parameters into several files. For example, if your site is configured differently for transaction processing (during the day) and for batch processing (at night), you might include common initialization parameters in a single configuration (CONFIG.ORA) file but have separate INIT.ORA files for day and night processing. You'd restart with the appropriate INIT.ORA file for each time period. (This approach should not be confused with BASIS op modes.)
Within the INIT.ORA file, you must follow the SAP conventions for parameters summarized in Table 1-1.
Table 1-1: SAP Conventions for the INIT.ORA File
INIT.ORA Parameter Filesystem Destination
USER_DUMP_DEST /oracle/
LOG_ARCHIVE_DEST /oracle/
BACKGROUND_DUMP_DEST /oracle/
AUDIT_FILE_DEST /oracle/
CONTROL_FILES /oracle/
Oracle Tablespaces in SAP
In an SAP system, Oracle tablespace names always begin with the string "PSAP" and end with a "D" (data tablespace) or an "I" (index tablespace). Some of the common SAP tablespaces are PSAPCLUD, PSAPLOADD, and PSAPDICD.
A standard SAP system contains only a handful of tablespaces. These tablespaces are designed to contain all of the SAP tables, and are defined as a part of the default SAP installation. Figure 1-4 shows the sample tablespace descriptions for an SAP installation. Within an Oracle/SAP tablespace, many of the tablespaces will remain small--for example, the metadata information in the DICT tablespace.
Figure 1-4. Standard SAP tablespaces
SAP has segregated the Oracle tables into tablespaces according to their functions. As shown in Figure 1-4, each tablespace can be classified as a transaction tablespace, a BASIS tablespace, or an SAP system tablespace. Note that the SAP application has a system tablespace (called PSAPDICTD), just as the Oracle database has a system tablespace. The following sections describe these tablespaces. SAP folks disregard the leading PSAP in each tablespace and the ending "D" or "I" in each tablespace name. Hence, the PSAPSTABD tablespace is commonly referred to as STAB.
Transaction tablespaces
Transaction tablespaces hold the application data for individual transactions. These transaction tablespaces include the BTAB, STAB, and USER1 tablespaces:
BTAB
Holds the SAP transaction tables. These tables constitute the heart of SAP, and the Oracle administrator may choose to migrate the largest and most active tables into other tablespaces for improved data management.
STAB
Holds the SAP master data and transparent tables. These are normally the master reference tables for the SAP application holding commonly referenced application information.
USER1
Commonly defined to hold user customization tables that are not defined with the SAP software.
In an operational SAP database, these tablespaces will experience the highest read-write activity and will grow very large as your end users load SAP with their business data. Thus, you'll need to monitor these tablespaces very closely, since they may fill and cause the entire SAP application to stop. Many Oracle/SAP administrators run scripts to identify the largest and most active tables in these tablespaces and move these tables into separate tablespaces. These separate tablespaces are then segregated by disk for better overall I/O management. Oracle administrators sometimes use file striping for these tablespaces to balance the load across many disk devices, and thereby improve throughput. I'll describe SAP tablespace monitoring in some detail in Chapter 4, SAP Database Monitoring.
BASIS tablespaces
The BASIS tablespaces include BTABD, STABD, DICT, LOAD, PROT, and SOURCE. SAP uses these Oracle tablespaces to store data that is used to perform basic SAP system functions. For example:
PROT
Holds the output from ABAP reports while they are waiting to be printed, and contains spool, converter, and log tables.
SOURCE and LOAD
Contain the ABAP source code for reports and screens. In an SAP system, remember that ABAP is run in an interpretive mode, and the source code is gathered from these tablespaces at runtime for interpreting.
DICT
Contains the ABAP data dictionary, and consists of SAP metadata; in this sense, the DICT tablespace is very similar to the traditional Oracle SYSTEM tablespace.
System tablespaces
The most important SAP system tablespaces are POOL, CLU, and DOCU:
POOL
Used to store the SAP system pool tables. These are similar to the master data tables found in the STAB (transaction) tablespaces, but SAP considers them too small to require their own Oracle tables. The items from the POOL tablespaces are generally buffered and loaded into the memory of the dialog instance, so POOL is not heavily accessed except at SAP startup time.
CLU
Contains SAP cluster tables. Unlike Oracle clusters, SAP cluster tables are stored into Oracle tables with LONG RAW datatypes. The data within the LONG RAW columns are used by SAP as subtables, and each row within an SAP cluster table may contain data that is completely unrelated to the next row in the table. These pseudo-tables present a challenge to the Oracle administrator, especially when they must be reorganized, because you can't use Oracle's CREATE TABLE AS SELECT command with tables that contain LONG RAW columns. Consequently, reorganizations of the CLU tables must be performed with Oracle's slower Export/Import utilities. I'll discuss this topic in Chapter 5, Table, Tablespace, and Index Reorganization.
DOCU
Contains the document tables, including the sapscript and sapfind tables. This is a relatively small tablespace with fewer than 30 tables.
Oracle Files in SAP
In a typical Oracle configuration, you can map an Oracle tablespace to a single datafile or to many datafiles. Because of the large size of many SAP installations, an Oracle/SAP tablespace generally maps to many datafiles. In a production SAP environment, many of these tables will never be used, while other tables will grow very rapidly. Thus, in general, you should identify and segregate the highly active tables into separate tablespaces. Chapter 4 includes a script you can use to identify the SAP tables that are growing.
SAP is quite strict about the names for its default tablespaces, so you cannot change these names, but you can add new tablespaces. When you segregate SAP tables into a separate tablespace, however, you can name that tablespace anything you like. Although SAP gives you complete freedom in tablespace naming, SAP AG suggests that when a new tablespace contains a single table, the tablespace name be a permutation of the table name. For example, the table named VBAP could be moved into a tablespace with any of the following names: PSAPVBAPD, VBAPD, or VBAP. An SAP purist would preface the tablespace name with PSAP and end the tablespace with the letter "D." This is helpful in order to be consistent with the other SAP naming conventions, and it can also be helpful when using SAPGUI to view tablespace information.
Oracle system files
While many standard Oracle configurations generally follow Oracle's Optimal Flexible Architecture (OFA) standard, SAP has changed this standard somewhat, in an effort to create a "flat" file hierarchy (see Figure 1-5).
Figure 1-5. The Oracle/SAP file architecture
Note that $ORACLE_HOME is set to the same value as /oracle/
Oracle datafiles
Within SAP, Oracle database files are named somewhat differently from the way they're named in traditional Oracle databases. The default SAP installation uses datafile names in which the prefix matches the tablespace name. For the filename suffix, rather than using a dbf suffix, SAP requires that datafiles contain the datan suffix. In this way, the Oracle datafile called psappooli.data3, for example, will be instantly recognizable as the third datafile for the POOL data indexes.
Oracle indexes
SAP also follows a standard for index naming. All Oracle index names default to eight characters in length; they always begin with the table name, end with a number, and use between one and three underscore characters in between. All indexes that end with a zero represent the primary key indexes for the table, and all nonzero numbers represent secondary indexes. For example, you will be able to tell that VBEP_ _ _0 is the primary key index for the VBEP table, and that VLPMA_ _1 is the secondary index for the VLPMA table. To properly display indexes within SAPGUI, all new SAP indexes should begin with the table name and end with a unique numeric character. Also, it is important that the index names be eight characters long, using a variable number of underscore ( _ ) characters.
SAP Filesystems on Unix
In addition to the required Oracle filesystems, some SAP-specific filesystems are found on most of the SAP application servers. These filesystems are used to hold certain Unix files that are required for SAP to function in the Unix environment. These include the SAP executable programs, SAP configuration files, and other SAP system-related datafiles, as follows:
/usr/sap/trans
This directory contains the common transport directory, .sapconf, as well as other SAP and Oracle configuration files. For distributed Oracle systems, this directory may also contain the master tnsnames.ora and sqlnet.ora files.
/sapmnt/
This directory stores system-wide files for SAP, including executables, global files, and profiles.
/usr/sap/
This directory stores instance-specific files for each SAP dialog instance.
The Oracle Database Layer of SAP
As you know, SAP is designed to work with many database management systems; interfaces are available for Oracle, DB2, Informix, and several other database products. Since SAP is database-independent, the SAP architecture requires the database to be defined as a part of the initial SAP installation. Once defined, the SAP programs (ABAP programs) will generate SQL that is compliant with the target database product.
Native Oracle SQL is generated by the ABAP program at runtime, and the SQL is then passed to Oracle for execution. The dynamic nature of ABAP SQL greatly increases its flexibility, but it makes it very difficult for the Oracle administrator to provide SQL tuning for Oracle. Because the SQL is generated from the ABAP at runtime, there is no way to change the execution plan for SQL by adding hints as you would in a traditional Oracle system. I'll discuss this limitations of SQL tuning, and some strategies you can adopt to overcome it, in Chapter 6, SAP Tuning.
Viewing Connections to the Oracle Database
From Oracle's perspective, the SAP application looks just like any other application. The SAP instance predefines a set of database connections that are created when the SAP instance is started, and these connections are held for the life of the SAP instance. In the example that follows (see Example 1-1), I've issued the following Unix command to display the processes for the ORACLE_SID called SA9:
ps -ef|grep -i sa9
This command displays the Oracle background processes (arch, pmon, reco), as well as all of the preestablished connections to SAP.
Example 1-1: The SAP Connections to the Oracle Database
sa9adm 94456 1 0 08:54:43 - 0:00 ora_arch_SA9
sa9adm 106746 1 0 08:54:47 - 0:00 ora_ckpt_SA9
sa9adm 71153 1 0 08:54:39 - 0:00 ora_pmon_SA9
sa9adm 15100 1 0 08:54:51 - 0:00 ora_reco_SA9
orasa9 72915 1 0 09:33:18 - 0:00 oracleSA9 (LOCAL=NO)
sa9adm 12118 30211 0 08:57:35 - 0:00 oracleSA9 T:I,,5
sa9adm 24665 30211 0 08:57:35 - 0:00 oracleSA9 T:I,,5
sa9adm 26179 30211 0 08:56:42 - 0:00 oracleSA9 T:I,,5
sa9adm 27494 30211 0 08:58:05 - 0:00 oracleSA9 T:I,,5
sa9adm 29528 30211 0 08:57:35 - 0:00 oracleSA9 T:I,,5
sa9adm 31300 30211 0 08:56:42 - 0:00 oracleSA9 T:I,,5
sa9adm 40034 30211 0 08:58:05 - 0:00 oracleSA9 T:I,,5
sa9adm 52567 30211 0 08:57:35 - 0:00 oracleSA9 T:I,,5
sa9adm 73573 30211 0 08:58:05 - 0:00 oracleSA9 T:I,,5
sa9adm 74088 30211 0 08:58:05 - 0:00 oracleSA9 T:I,,5
sa9adm 74852 30211 0 08:58:05 - 0:00 oracleSA9 T:I,,5
sa9adm 82796 30211 0 08:58:06 - 0:00 oracleSA9 T:I,,5
sa9adm 93799 30211 0 08:58:05 - 0:00 oracleSA9 T:I,,5
Flow of Data from Oracle to SAP
One of the confounding aspects of the Oracle/SAP architecture is the many layers that exist in an SAP environment. On its way to the SAPGUI client, Oracle data must be read from disk into the local disk cache, transferred onto the database server Journal File System (JFS) cache, then transferred into the Oracle buffer cache. Once the data reaches Oracle, it is shipped to the application server, where it is cached again before making the final trip to the SAPGUI client.
As you may know, memory buffers are used to save data from a prior disk read so that they do not have to be reread the next time the data is required. In an Oracle/SAP configuration, there are many layers of data buffers, and each buffer caches much of the same data as its predecessor (see Figure 1-6). However, this redundant caching does not mean that all of the extra data buffers are wasted. As data makes the trip from the disk to the SAP client, the data cached in each buffer is successively refined. For example, at the disk level, a physical I/O may result in an entire track of data being stored on the disk array cache. As the data reaches Oracle, only a single database block is cached. Once the data reaches the SAP application server, only specific row information will be stored in the SAP buffer.
Figure 1-6. The path of data from Oracle to SAP clients
Oracle/SAP Administrators and Tasks
Who does what in an Oracle/SAP environment? If you are accustomed to traditional Oracle environments (those not using SAP), you might find yourself confused by the very different roles within an SAP environment. For example, many Oracle DBAs are dismayed to learn that the Oracle software is installed by the BASIS administrator when the SAP environment is first established, and that they do not have any direct control over the installation process.
The next sections briefly describe the different roles you'll encounter when using Oracle with SAP, as well as the functions for which each role is responsible.
SAP Functional Job Titles
In the Oracle/SAP technical arena, there are four major players:
• The BASIS administrator (BA)
• The Oracle administrator (DBA)
• The system administrator (SA)
• The network administrator (NA)
At many shops, these duties are shared--for example, the BA might also act as the DBA--but there are some generalities in job descriptions for these roles.
BASIS administrator
The BASIS administrator (BA) is responsible for the installation and maintenance of both SAP and Oracle. The BA is also responsible for the configuration of the SAP topology, the configuration of the application servers and central instance that make up the system, and the performance and tuning of the SAP application servers. In addition, the BA is charged with many administrative tasks that are typically performed by the DBA or SA in a generic Oracle database. For example, the BA is responsible for creating SAP users, maintaining passwords, defining printers and spools, and adjusting the number of work processes on each SAP dialog instance. A successful BA must have an intimate knowledge of the SAP environment and must act as a buffer between the end users and the DBA/SA staff.
Oracle administrator
The Oracle administrator (DBA) is responsible for ensuring that Oracle has been correctly installed by the BASIS administrator and for applying Oracle-specific maintenance patches.
TIP: Unlike administrators of traditional systems, the Oracle/SAP DBA generally contacts SAP AG headquarters before applying any patches to the Oracle database.
In addition, the DBA must ensure that the SAP objects (tables and indexes) don't fully consume their tablespaces. The DBA is also responsible for database monitoring, performance and tuning, and periodic table and index reorganization.
System administrator
The system administrator (SA) is responsible for ensuring that the host servers are properly installed and configured. The SA is also responsible for the monitoring and performance tuning of all hardware devices. This can be a major undertaking because many large SAP landscapes have dozens of application and database servers. At many shops, the SA must develop an Oracle backup and recovery plan and must perform the Oracle database backups. While the roles for backup and recovery are shared between the SA and the DBA, in many SAP shops the SA works on the backup software (e.g., ADSM or Legato), while the DBA works with the Oracle component of backup and recovery (e.g., Oracle Enterprise Backup Utility or Oracle Recovery Manager).
Network administrator
Because of all the connections between each layer of SAP, the network administrator (NA) has an especially important role in the Oracle/SAP environment. The NA must constantly monitor the network, looking for bottlenecks and ensuring the smooth flow of data among all of the servers.
SAP Job Functions
The day-to-day tasks within SAP are also very different from those within conventional Oracle databases. Because of the special characteristics of the SAP architecture, many functional roles normally performed by the Oracle DBA shift to other administrators.
Oracle software installation
The Oracle software is installed as a part of the SAP installation process, which is performed by the BA.
SAP user administration
All SAP user administration and user security is performed by the BA. The rationale for this assignment has to do with the way end users connect to the Oracle database. In SAP, all end-user connections from the SAP application servers to the Oracle database are done with Oracle SQL*Net connections. This means that there is no need for any Unix userids. Also, the pre-established connections with Oracle are made with a single user (schema owner) called SAP R/3, so there is no need for specific Oracle userids.
SAP security administration
While this job is the primary responsibility of the BA, the SA and DBA play ancillary roles. The BA is responsible for creating SAP users and maintaining their passwords. The BA is also charged with all SAP application security.
The SA ensures the appropriate file permissions and controls the master SAP Unix account
The DBA ensures SQL*Net security for the connections between the application servers and the database server, and controls the password for the Oracle schema owner, SAP R/3.
WARNING: A breach of security for the SAP R/3 Oracle user could be a major disaster. Since the sapr3 user owns the entire Oracle/SAP schema, any or all of the database entities could be deleted if the sapr3 password were exposed.
Backup and recovery
This function is generally split between the SA and the DBA. The DBA has overall responsibility for the integrity of the Oracle database, including the online redo logs. However, the SA is usually responsible for writing the backup scripts and ensuring that the Oracle/SAP database is successfully transferred to tape. If recovery is required, the DBA requests the disk media restore from the SA; from that point on, the DBA is responsible for the database roll-forward activities.
Oracle maintenance
The installation of Oracle patches is performed by the DBA, but only after being given the go-ahead by the SAP AG company representative. SAP is only certified for specific releases of Oracle, and some Oracle patch upgrades could produce unwanted results.
Printer management
This function is split between the BA and the SA. The SA must install and define the printer, but it is the job of the BA to define the printer and a spool to the SAP system.
Problem resolution
This is the most confusing function within SAP. Because of the complex nature of SAP, a response-time problem could be due to any number of factors -- database problems, network problems, hardware resource problems, SAP software problems, and many others. Thus, most SAP shops notify all of the administrators when a response-time problem occurs, and all parties work in parallel to examine the problem. The key to successful problem resolution within SAP is to ensure that all of the members of the technical team have a close and trusting working relationship.
