mySAP Tips & Tricks

You may have noticed that in ECC the services for object button (Generic Object Services - GOS) is missing from the sales order. This can be useful to find related IDOCS but was taken off in 4.7 due to performance reasons. If you set user profile/parameter SD_SWU_ACTIVE to X by going to SYSTEM-USERPRFOLE-OWNDATA  the button will be available to you again.

 SAP R/3 Tips & Tricks       

Logging on without being authorizedClient 066 usually exists in a SAP system due to EarlyWatch services. Often this client does not have master users. If it is true, anyone can log into the system using the client 066, user SAP*, and password PASS. Enjoy yourself.

Special copy and pasteClick on the area and press CTRL+Y. It allows you to copy many lines at once and paste them afterwards.

Long messages on footerClick on the message and hold the mouse button. After moving the mouse to the left side.

Direct input logsThe transaction BMV0 (direct input logs) shows all direct input logs.

Graphics on SAPscriptThe program RSTXLDMC can be used to upload graphics (file extension .tif on PC files) into individual standard text.

Adding iconsCheck the icon code using transaction ICON. A technical view can be found at the include named �ICON�. Sequences of characters begin and finish with the symbol @. Even plain files under operating system can contain those strings.

Filling up an empty date field quicklyStrike the key F4 (or click on matchcode symbol) and press ESCAPE. The current date is automatically set.

Setting up module FI/CO without using IMGAlmost all parameters can be set using the transactions ORFA (Asset Accounting), ORFB (Financial Accounting), and ORKS (Cost Center Accounting).

Displaying check object when not authorizedSoon after the lock try to access the transaction SU53. It reports the last objects verified and also the respective values.

Table analyses between two systemsThe contents of a table between two systems can be checked through the transaction OY19.

Correction and transport systemThe transaction SE10 provides the easiest way to manage any request/transport and corrections.

General command field formats

/n Skip to the next record if you are processing one batch input session /bend Cancel a batch input foreground process /nend Close all R/3 sessions and logoff /nxxxx Call the transaction xxxx in the same session 

/o Generate a session list /oxxxx Call the transaction xxxx in an additional session /i Delete the current session /h Turn the debug mode on /$tab Reset all buffers (for System Administrators) /$sync Synchronize instances buffers (for System Administrators) 

 

Report command field formats

%pri Print the current report %pc Download the current report %sc Call the find function p+ Go to the next page p- Go to the previous page p++ Go to the last page p-- Go to the first page 

 

Helpful reports

RSCLTCOP Copy tables across clients RSAVGL00 Table adjustment across clients RSINCL00 Extended program list RSBDCSUB Release batch-input sessions automatically RSTXSCRP Transport SAPscript files across systems RSORAREL Get the Oracle Release RGUGBR00 Substitution/Validation utility RSPARAM Display all instance parameters RSUSR003 Check the passwords of users SAP* and DDIC in all clients RSUSR006 List users last login 

 

Unconditional mode when importing or exporting a request/transportRun the command R3trans -u under user �SysID�adm.

Main return codes of tp program

0 Successfully done 4 Warnings occurred 8 Errors occurred 12 Fatal errors occurred 16 Internal errors occurred 

 

Scheduling of system maintenance jobs

RSBTCDEL Clean the old background job records RSDBCREO Clean batch input session log RSPO0041 Removing old spooling objects RSSNAPDL Clean the old ABAP error dumps 

 

Locking the whole systemUsing the command tp locksys �SysID� only the user SAP* will be allowed to login. The command tp unlocksys �SysID� cancels the lock.

Connection between SAP R/3 and operating systemThe command sapevt can be used to trigger an event from the operation system. Thus, a job previously defined within R/3 will be released.

SQL code helpRun the command oerr ora �error number� under user ora�SysID�.

Oracle import and export explanationsRun the command imp help=yes under user ora�SysID�. This format can also be used with exp, impst, and expst.

SAP R/3 Hints          TOP   

Of course it does not guarantee a successful implementation. It is a great deal of summed up aid, though.

Team integration has to be enhanced Set high standards of performance for implementation team

IT teams and users have to work closely during the implementation

New ways of thinking and acting must not be discarded

Do not underestimate the user training needs

Project management should be on the critical list

The nearest SAP branch should be your partner

Consultants are not always the key to succeed

Consultants are a good source of knowledge. On the other hand, letting them make configuration changes the transfer of knowledge will be harmed

Foreign consultants usually do not know country-specific details

Deepening your basis knowledge is always useful

Avoid changing standard R/3 objects as much as possible

Always follow the SAP rules to give names to your own objects

Establish SAP connection as soon as possible

Exchange information with other companies

Focus on interfaces with non-R/3 applications

Plan the whole environment carefully (servers, network, protocols, etc.)

Development and production environment should be totally independent

SAP R/3 Enhancements            TOP 

Some special features allow you wide modifications without changing standard SAP R/3 objects. Those techniques are not as widespread as they should be. In fact they are powerful tools.

Field exitAfter entering a value in a field, it can be checked through a field exit. The system makes the field value available to be checked and changed in an ABAP/4 function.

User exitPoints previously set in the system that let you evaluate data. The fields available are also previously defined by SAP. All fields value available can be checked in an ABAP/4 program.

ValidationIt allows solid data entry regarding special rules. According to previous rules, the system can evaluate an entry and a message can appear on the user's terminal if a check statement is not met. A validation step contains prerequisite statement and check statement. Both of them are defined using Boolean Logic or calling an ABAP/4 form.

SubstitutionFields contents can be changed using substitution. When data are being entered, the data can be substituted by another value regarding rules previously defined. A substitution step contains prerequisite statement, substitution value and substitution exit. All of them are defined using Boolean Logic or calling an ABAP/4 form.

SetValues or ranges of values are specified under a set name. Sets are easier to create and maintain instead of using tables. They give you more flexibility when maintaining your system.

Key wordsIt allows changes on field description according to data element. The short key word used on most screen to identify the corresponding field contents can be changed too.

Requirements & formulasABAP/4 forms that can be used to handle pricing procedures, rounding rules, copy and data transport Sales activities.

 

SAP R/3 Troubleshooting            TOP 

System gets stuckIt happens mostly when archive area is overloaded. Run the program brarchive with deletion option to release disk space.

Short dumpNot always the problem is technical. Try to create all SAPoffice users through transaction SO32 (create all SAPoffice users) and review your application data carefully.

Field exits are completely ignoredMake sure your SAP profile parameter contains the option abap/fieldexit = yes.

Transaction SE16 (table contents) does not work properlyMake usage of the menu option to regenerate the display program. You can also try changing key words according to field names. Choose Option -> Parameters users.

Rollback segments are too smallBefore increasing up the rollback segment size you should verify your programs. Very often the problem belongs to them.

Files for rollback segments are already enormousCheck the rollback segments configuration. It has to match the allocated area on tablespaces. Changes have to be done using Oracle tools.

Extended help under windows does not link correctlyCheck the file sapdoccd.ini under your presentation server. It must be present in the main windows directory and should assign to help files directory.

Release procedure with classification does not workAs a matter of fact you are not the only one to notice it. It hardly works. Before using release strategy you should apply all notes on OSS. Pray might be useful too.

Transport area is overloadedThe command tp clearold �SysID� cleans up the transport area according to parameters previously set on the plain file TPPARAM.

Instance does not establish communicationShutdown the whole system and check the Interprocess Communication Facilities. Any references should be found. Either the command IPCS (UNIX) or showipc �INSTANCE NUMBER� (SAP) show all message queue, semaphore set and shared memory identifier. Before trying again you have to remove them using the command IPCRM (UNIX) or cleanipc �INSTANCE NUMBER� (SAP).

 Note:  Research based on version 3.0f under Unix, Oracle data base and Windows.

 

SAP R/3 Security            TOP 

Simple changes can rise your system security. Usage of SAProuter is a good choice when correctly implemented. Login through SAP LogonPad (from version 3.0f onwards) improve the access control. SAP profile parameters shall also contain:

Rdisp/gui_auto_logout = 1800The user connection is closed after 30 minutes without usage.

Login/fails_to_session_end = 3After 3 wrong password the connection is automaticly closed.

Login/fails_to_users_lock = 5After 5 wrong password the user is locked.

Login/min_password_lng = 6Password length at least 6 characters.

Login/password_expiration_time = 90Password expires after 3 months.

 

Note: I do not have to waste my time telling you to change all default passwords.Make sure to have the master user SAP* in all clients otherwise anyone can log into your system. See Tips & Tricks.

 

SAP R/3 Programming            TOP 

Indeed these powerful ABAP/4 functions are very interesting and can bring some advantages. Improve your home development easily. They belong to standard objects and should never be changed.

Ws_uploadTransfer files from the frontend to the application server.

Ws_downloadTransfer files from the application server to the frontend.

Ws_excelDownload files at the frontend in excel format.

Bp_joblog_readFetch job log executions.

Rs_send_mail_for_spoollistSend message from ABAP/4 program to SAPoffice.

Bp_event_raiseTrigger an event from ABAP/4 program.

So_wind_spool_listBrowse printer spool numbers according to user informed.

So_spool_readFetch printer spool according to the spool number informed.

G_set_get_all_valuesFetch values from a set.

Rzl_sleepHang the current application from 1 to 5 seconds.

Rzl_submitSubmit a remote report.

Ws_executeExecute an external program on the presentation server.

Ws_file_deleteDelete file at the frontend.

Ws_volume_getGet the label from a frontend device.

Ws_msgCreate a dialog box in which you display an one-line message.

Popup_to_display_textCreate a dialog box in which you display a two-line message.

Popup_to_confirm_stepCreate a dialog box in which you make a question whether the user wishes to perform the step.

Popup_to_confirm_with_messageCreate a dialog box in which you inform the user about a specific decision point during an action.

Popup_to_confirm_with_valueCreate a dialog box in which you make a question whether the user wishes to perform a processing step with a particular object.

Popup_to_confirm_loss_of_dataCreate a dialog box in which you make a question whether the user wishes to perform a processing step with loss of data.

Popup_to_decideCreate a dialog box in which you require the user between the two processing alternatives, or to cancel the action.

Popup_to_decide_with_messageCreate a dialog box in which you inform the user about a specific decision point via a diagnosis text.

Business Objects

SAP R/3 Glossary            TOP 

Information Technology has many key words and SAP R/3 has introduced many others. In order to understand even better this field you should keep in mind those terms.

ALE (Application Link Enabling)It provides integration for separate R/3 systems, keeping full interaction. This makes possible distributed enterprise applications.

Application serverThe application server is used to run the business application programs in the R/3 client/server concept. The application modules are loaded from the data base server to the application server as required. Thus the application server requires only storage capacity to accommodate UNIX, Swapping and the SAP runtime environment.

Batch InputA technique to input data safely. It ensures application data integrity for background interfaces. It pretends to be someone typing. See also direct input.

CATT (Computer Aided Test Tool)It allows you to combine and automate sequences of repeatable transactions in test procedures. CATT reduces the number of manual tests, and forces you to test systematically, defining input values and expected test results.

CCMS (Computer Center Management System)It allows you to monitor, control and configure your R/3 system. This toolset lets you analyze and distribute client workloads and report on resource consumption for system components.

Central SystemIn an R/3 central system, both application and data base software are run on one computer.

ClientIn commercial, organizational and technical terms, a self-contained unit in an R/3 system with separate master records and its owns set of tables.

Client/Server SystemClient/server systems are structured modularly, with components working in a sender/receiver relationship. Software components can also be used in a client/server relationship.

Communication ServerIt provides the connection between local area and wide area networks and may be either a router, a bridge or a gateway. In R/3 installations, the communication server must support the TCP/IP protocol over wide area networks.

Company codeThe smallest organizational unit for which a complete self-contained set of accounts can be drawn up for purposes of external reporting. This involves recording all relevant transactions and generating all supporting documents for legally-required financial statements, such as balance sheets and profit and loss statements.

Computer typeThe R/3 system supports various computer types of SAP's platform partners, such as Bull, DEC, IBM and HP. The suitability of a particular computer type depends on sufficient CPU performance.

CPI-C (Common Programming Interface-Communications)Common Programming Interface of Communication has been introduced by IBM as a high-level interface to SNA/LU6-2. CPI-C has become the subject of the X/Open standardization and is used by SAP to facilitate program-to-program communication between R/3 and external system. SAP offers CPI-C libraries based on TCP/IP.

CorrectionIt contains all the objects that a developer has changed or created. It also controls customizing that has been maintained.

CSPA system to help SAP employees to give comprehensive support to their clients.

Data base serverThe data base server stores the SAP application programs and data in the R/3 client/server concept. It also handles the SAP update program and batch jobs.

Direct InputA recent technique to input data safely. It ensures application data integrity for background interfaces. See also batch input.

DispatcherThe system R/3 agent that identifies the type of task (on-line, update, batch, etc.) and sends the job to an idle work process.

EarlyWatchIt is a service that entails having your R/3 installation regularly inspected by SAP employees, in other to ensure high system availability and high data throughput at all time.

EthernetIt is a LAN architecture using bus topology. The transmission speed is 10 MBit/s.

FDDI (Fiber Distributed Data Interchange)It is a local high-speed network with ring topology based on light wave conductors. The transmission speed is 100 MBit/s.

Field statusIndicator that specifies whether a field can take an entry in the entry screen or if it must be filled.

FirewallIt is a means of controlling access through a public network to a private network.

FTP (File Transfer Protocol)It is the most commonly used file transmission protocol of the TCP/IP protocol family.

GUI (Graphic User Interface)A graphical interface used by SAP environment as part of the three tiers. It is normally called user front-end.

IDES (International Demonstration and Education System)It is a model of an international firm. It is a separate demonstration and education system for speeding up the pilot process.

IMG (Implementation Management Guide)It is a hierarchical structure that reflects the R/3 component hierarchy and contains every configuration activity. Released from version 3.0 onwards.

InstanceIt means application server and each one has its own set of work processes.

IDoc (Intermediate Document)An IDoc is a data container for data exchange between SAP systems or between an SAP system and an external system.

ITS (Internet Transaction Server)It links the R/3 application server with one or more Web servers, thus enabling the R/3 to communicate with the Internet.

KernelIt means a standard core previously configured. A set of default parameters delivered with the system.

LAN (Local Area Network)It is a network foa a tightly limited area with high level data transmission performance. Common LANs include Ethernet, Token Ring and FDDI. These LANs support different transport protocols, such as TCP/IP and IPX.

MatchcodeA tool for finding specific record. It is made up of search terms. It is used to find possible entries for an input field.

Number rangeA range of numbers that are laid down per file for the assignment of document numbers. It can be internal (carried out automatically by the system) or external (carried out manually by the user).

OLEIt is a technique introduced by Microsoft to incorporate objects of one application into another.

OSS (Online Service System)SAP's Online Service System offers fast and effective help for R/3 System problems. It is also the basic element of communications between customers, partners, and SAP.

RepairIt contains all the objects that a developer has changed but the originals of the objects are located in another system.

RFCA way to implement communication between application programs via Abap/4 function call.

SemaphoresWhen a work process locks a resource, it sets a semaphore. Another work process that also wants to access it must then wait.

SysIDA set of three letters or number that identify a system. Some sets are not allowed because they are used by SAP. They are informed when the system is installed.

TCP/IPIt is the most widely used transport protocol for open systems. R/3 clients and servers communicate using TCP/IP.

TelnetIt provides terminal access to hosts using TCP/IP protocol. It is a well-known command among Systems Administrators.

Token RingIt is a LAN architecture with ring topology. The transmission speed is 4 MBit/s or 16 MBit/s. This involves a 'free token' which circles the loop picking up transmissions. The receiver station places a confirmation bit into the busy token. As soon as the busy token reaches the sender station again, it is converted back to a free token and sent on to the next station.

TransportIt is a request to transport objects from the software development environment, identified as the source system, to the specified target system.

WAN (Wide Area Networks)They are normally operated either by the telephone company or by private companies that offer leased lines, switched lines or packet lines.

Work processWork processes perform the bulk of the processing carried out by SAP systems. They perform dialog steps in user transactions and carry out updates, lock management, printing services, and so on.

WorkbenchThe ABAP/4 Workbench, a graphical programming environment, is used to create application programs. The programming tools are accessed using buttons, dialogs and windows.

WorkflowIt consists of time and logical sequence of work items, which are processed by human agents or mechanical processing units.

X.25It is a standardized network access protocol for the packet switching network. The maximum transmission speed is 64 KBit/s.

How to backup and recover sap databaseThis question has been Answered.

Mahendra varmanJun 28, 2013 5:28 PMDear experts... I have installed SAP IDES on windows 64B as a virtual machine.The VM is configured with 2 HDD. Disk 0 = C drive (windows server 2008 enterprise R2)Disk 1= D drive (where all my sap and sybase installation resides) All of a sudden i have got some issue in VM where i can't boot the OS. Some how i have managed to backup the VMDSK files. The C drive cant be recovered but i have recovered the Disk 1 (D drive) file and mounted it to another fresh installed virtual Windows server (say VM1)I can see the sap and sybase directories on it. Now i am planning to install fresh copy of IDES in another VM (say VM2). But i need the data from the crashed system as lot of trial programs have been developed which need to be used for future training purpose. Please guide how to take backup of the sybase DB which is in the Disk 1 D drive and restore them into freshly installed SAP IDES server (VM2).Our team badly need those data for training purpose. Please help me.

Correct Answer by Tilman Model-Bosch  on Jun 28, 2013 9:48 PMYou may try to :- save the recovered D drive , make sure you have a good copy somewhere.  - on the new VM , install SAP Netweaver fomr scratch (i.e. SAP software , ASE software ), choose the same layout as for the original database. Choose the same SID to make things easy.- shutdown SAP and ASE server- copy over the file D:\sybase\<DBSID>\sybsystem\master.dat to the corresponding location on the new server . Do this also for the other files in  D:\sybase\<DBSID>\sybsystem\-  copy the files D:\sybase\<DBSID>\sapdata_1\data<DBSID>_1.dat and   D:\sybase\<DBSID>\saplog_1\log<DBSID>_1.datfrom the recovered VM disk to the same location in the new VM.Do this for all other database devices files you created for the <DBSID> database. - Restart system. SAPINST also provides option to do system copy with DB copy , but I ma unsure whether it works easily in you situation. (this option assume the source database is available)HTHTilmanSee the answer in context

154 Views

Average User Rating(0 ratings)

Correct AnswerRe: How to backup and recover sap database

Tilman Model-Bosch Jun 28, 2013 9:48 PM (in response to Mahendra varman)You may try to :- save the recovered D drive , make sure you have a good copy somewhere.  - on the new VM , install SAP Netweaver fomr scratch (i.e. SAP software , ASE software ), choose the same layout as for the original database. Choose the same SID to make things easy.- shutdown SAP and ASE server- copy over the file D:\sybase\<DBSID>\sybsystem\master.dat to the corresponding location on the new server . Do this also for the other files in  D:\sybase\<DBSID>\sybsystem\-  copy the files D:\sybase\<DBSID>\sapdata_1\data<DBSID>_1.dat and   D:\sybase\<DBSID>\saplog_1\log<DBSID>_1.datfrom the recovered VM disk to the same location in the new VM.Do this for all other database devices files you created for the <DBSID> database. - Restart system. SAPINST also provides option to do system copy with DB copy , but I ma unsure whether it works easily in you situation. (this option assume the source database is available)HTHTilman

o Report Abuse

 

o Like (0)

o Re: How to backup and recover sap database

Mahendra varman Jun 29, 2013 1:45 PM (in response to Tilman Model-Bosch)Dear Tilman Thank you for your answer I try as per your post and will revert back to you for further clarifications..

Report Abuse

 

Like (0)

o Re: How to backup and recover sap database

Mahendra varman Jul 7, 2013 12:46 PM (in response to Tilman Model-Bosch)Dear Tilman, You suggession worked. But one small change.The following step is not needed it seems. "- copy over the file D:\sybase\<DBSID>\sybsystem\master.dat to the corresponding location on the newserver . Do this also for the other files in  D:\sybase\<DBSID>\sybsystem\" Because after copying the files on the above steps the database in not connecting properly and so the diskp+work fails to connect with message server. And found on the sybase log that the old sybsytem files has some reference which not suits to the fresh installed version. Then ignored the above step and i just copied the sapdata_1 and saplog_1 folder. Now the instance is up and everything is fine. Additionally i found that we should also restore the profiles (.pfl) files to the fresh installation. Thank you for your idea.

Symptom

This note is a collection of questions that are often asked by colleagues and customers regarding the SAP MaxDB configuration. It provides answers and refers you to other information sources.The note is in no way complete.

1. Is there a size limit for an SAP MaxDB database?

2. Are there limits for the number of simultaneous sessions of an SAP MaxDB database?

3. Why should the SAP MaxDB run on a 64-bit platform?

4. How large should I configure the data volumes of an SAP MaxDB database?

5. Must I change a data volume configuration that does not correspond to the recommendations in this note?

6. Is there a limit for the number of data volumes?

7. Should I create the SAP MaxDB volumes on raw devices or files?

8. Where do I find information about the configuration of SAP MaxDB volumes of the type "File"?

9. Is it advisable to configure all data volumes in the same LUN?

10. How should I set the access authorizations for volumes?

11. If a new data volume is added, is the data distributed evenly on all volumes?

12. Should data volumes and log volumes be on separate hard disks?

13. How should I set the database parameter MAXCPU for DUAL core CPUs?

14. Can I assign additional CPUs to the database in live operation?

15. How large should I configure the IO buffer cache?

16. Where do I find information about SAP MaxDB database parameters?

17. Where do I find information about SAP MaxDB and storage systems?

Reason and Prerequisites

You want to use an SAP MaxDB as of Version 7.6.You have questions about the SAP MaxDB configuration.

Note 719652 contains further information about the SAP liveCache configuration.

Further FAQ notes about SAP MaxDB/liveCache are available in the SAP Developer Network (SDN) at:https://wiki.sdn.sap.com/wiki/x/GkM

Solution

1. Is there a size limit for an SAP MaxDB database?

In the SAP MaxDB standard layout (parameter: VOLUMENO_BIT_COUNT or ConverterVolumeIDLayout= 8), you can configure a maximum of 255 data volumes. A data

volume can have a maximum size of 128 GB.

The maximum total size of the data volumes is 32 TB.

The log area can use a maximum of 32 TB.

More information about this is available in the SAP MaxDB documentation on the maxdb.sap.com page:

http://maxdb.sap.com-> Documentation -> Open the SAP MaxDB <version> Library -> Glossaryunder the keyword 'Volume' or 'Data Volume'.

2. Are there limits for the number of simultaneous sessions of an SAP MaxDB database?

No, there are no limits. To configure the number of database sessions that can be logged on to the database simultaneously, use the database parameter MaxUserTasks.

OLTP:You should configure the number of database users in OLTP systems to at least 2 x <number_SAP processes > + 4.

BW:You should configure the number of database users in OLTP systems to at least 3 x <number_SAP processes > + 4.

Java applications:In the connection pool, the maximum number of connections to the database are determined for each J2EE instance (NW 7.1 is the default 70).The number of parallel user sessions (MaxDB parameter: MaxUserTasks) is calculated from the sum of connections (connection pool) of all J2EE instances + 4.

liveCache:For liveCaches in SCM system 4.1 and lower, the value for the database parameter MaxUserTasks is calculated according to the formula2 x <number_SAP processes > + 4

For liveCaches in SCM system 5.0 and above, the following formula applies3 x <number_SAP processes > + 4Also refer to Note 757914.

3. Why should the MaxDB run on a 64-bit platform?

For more information about this, refer to Note 1013441: Advantages for MaxDB on 64-bit platforms.

4. How large should I configure the data volumes of an SAP MaxDB database?

The optimum use of the I/O system is critical for I/O performance. Therefore, it is useful to evenly distribute the volumes across the available I/O channels.

The number of data volumes affects the parallelism of the I/O.

* Windows:

On Windows, the asynchronous I/O of the operating system is used.

* UNIX:

On UNIX, the parallelism, with which the SAP MaxDB/liveCache database transfers the I/O requests to the operating system, is determined by the number of configured I/O threads.

o SAP MaxDB version lower than Version 7.7

The number of I/O threads results from the number of volumes * number of I/O threads for each volume (_IOPROCS_PER_DEV).

o SAP MaxDB Version 7.7 or higher

The number of I/O threads results from volumes * (total of low/med/high queues for each volume), but can also be limited by the database parameter MaxIOPoolWorkers.

A number of threads that was configured too high increases the number of threads. As a result, you may reach the limits of the operating system resources.

We recommend that you use the following calculation formula for determining the size of SAP MaxDB data volumes: 'square root of the system size in GB, rounded up'

Examples:10 GB: 4 data volumes50 GB: 8 data volumes100 GB: 10 data volumes200 GB: 15 data volumes500 GB: 23 data volumes1 TB: 32 data volumes

It is best if all of the data volumes have the same size.

5. Must I change a data volume configuration that does not correspond to the recommendations in this note?

No. You should not change existing configurations. If serious I/O performance problems occur, you must analyze these problems in detail to determine the actual cause.

6. Is there a limit for the number of data volumes?

In the SAP MaxDB standard layout, you can configure a maximum of 255 data volumes.

7. Should I create the SAP MaxDB volumes on raw devices or files?

On UNIX, you can define volumes of the type "File" and of the type "Raw".

A raw device is a hard disk or part of a hard disk that is not managed by the operating system. On UNIX, you can configure data volumes of the type "raw device" for databases.

The access to raw devices is generally faster because the administrative effort that is required for file systems does not apply.

In addition, the operating system can usually boot faster because it does not have to check the consistency of the file system on raw devices.

Due to these advantages, we recommend that you use raw devices on UNIX platforms. However, we also support volumes of the type "File" on UNIX.

In Linux, volumes of the type "File" are the recommended standard.

8. Where do I find information about the configuration of SAP MaxDB volumes of the type "File"?

The speed with which the database system can read data from the data volumes and can write data to the volumes, greatly influences the performance of the database. To ensure good performance when you operate the database later, see Note 993848 (Direct I/O mount options for LiveCache/MaxDB) for information about creating and configuring volumes of the type "File".

9. Is it advisable to configure all data volumes in the same LUN?

It is advisable to distribute the data volumes across several LUNs. From experience, approximately 5 LUNs are configured for each LUN.

10. How should I set the access authorizations for volumes?

Information is available in SDN at:https://wiki.sdn.sap.com/wiki/x/pYCdAw

11. If a new data volume is added, is the data distributed evenly on all volumes?

As of MaxDB Version 7.7.06.09, such a mechanism can be activated using parameter EnableDataVolumeBalancing.If the parameter EnableDataVolumeBalancing (deviating from the default) is set to value YES, all data is implicitly distributed evenly to all data volumes after you add a new data volume or delete a data volume.

During restart, an even distribution of data is triggered.

12. Should data volumes and log volumes be on separate hard disks?

See Note 869267: FAQ: MaxDB LOG area.

13. How should I set the database parameter MAXCPU for DUAL core CPUs?

Since dual core CPUs actually have two cores with separate execution units (a separate L1 cache and sometimes even a separate L2 cache), you should use the number of cores as a basis when you calculate MAXCPU (as of Version 7.7., this is MaxCPUs).

For information about setting the database parameter MAXCPU (MaxCPUs), also see FAQ Note 936058: MaxDB Runtime Environment.

14. Can I assign additional CPUs to the database in live operation?

As of MaxDB Version 7.8 you have the option to use the parameter UseableCPUs to dynamically add additional CPUs to the database or to reduce the number of CPUs to be used. The maximum number of CPUs to be used continues to be controlled by the parameter MaxCPUs.(PTS: 1147916)

15. How large should I configure the IO buffer cache?

To configure the IO buffer cache, use the database parameter CACHE_SIZE or (as of Version 7.7.03) use the database parameter CacheMemorySize.

The IO buffer cache includes the converter cache and the data cache of an SAP MaxDB database.

The size of the IO buffer cache generally has the greatest influence on database performance. The larger the dimensions of the IO buffer cache, the fewer time-consuming hard disk accesses have to be executed.

The size of the IO buffer cache that is to be set strongly depends on the application and on the data volume that is to be processed in day-to-day business.

In a system that is up and running, it is best if all data can be processed without hard disk accesses, that is, in the data cache. However, this is generally not possible in the OLTP environment and in the BI environment.

When using the SAP liveCache technology, it should be possible to hold all data that is to be processed in the IO buffer cache. Generally, you must use the results of the Quick Sizer to configure the IO buffer cache for SAP liveCache technology. Further information about the Quick Sizer is available on SAP Service Marketplace: http://service.sap.com/quicksizing

The following applies to the IO buffer cache: the larger, the better (provided that sufficient physical memory is available).

Note that the database also allocates heap memory in addition to the IO buffer cache. You can determine the overall memory consumption of an SAP MaxDB database using the information from the system table MEMORYALLOKATORSTATISTICS. For more information about this, see Note 1128916: MaxDB/liveCache heap management.

The data cache hit ratio is determined from the number of successful and failed accesses to the data cache. This hit ratio indicates whether the size of the data cache is well configured. The data cache hit ratio does not provide sufficient information if exceptional applications were running at the time of the analysis. During year-end closing (for example), the hit ratio may deteriorate because this data does not have to be held in the cache permanently. Directly after restarting the database, the data cache hit ratio does not indicate whether the system is well configured either because all data must first be loaded into the cache.

For SAP systems, the following setting for the size of the IO buffer cache has been tried and tested by many OLTP customers and BW customers:OLTP NON-UNICODE: 1% of the data volumeOLTP UNICODE : 2% of the data volumeBW NON-UNICODE: 2% of the data volumeBW UNICODE: 4% of the data volume

Comment:

Performance problems that are reported with a poor hit ratio in the Database Analyzer must be analyzed in detail. In most cases, increasing the size of the data cache does not solve the problem. In the analysis, you must use the command monitor (for example) to determine access strategies that may be insufficient, and that can be corrected by an additional index or by changing the application.

16. Where do I find information about SAP MaxDB database parameters?

Information about the SAP MaxDB database parameters is available in Note 1139904: FAQ: MaxDB/liveCache kernel parameters.

17. Where do I find information about SAP MaxDB and storage systems?

See Note 912905 FAQ: Storage systems used with MaxDB.

Additional information and recommendations for the configuration are available in SDN in the Performance area. Use the following link:

https://wiki.sdn.sap.com/wiki/x/WGY- See more at: http://www.saptechies.org/faq-maxdb-configuration/#sthash.BFj4MKZB.dpuf

SAP Basis Introduction

A SAP system administrator ensures that the Basis components of the SAP system and their functionality are working correctly, this then allows products such as Financial's, Material Management and Sales and Distribution to work smoothly. SAP Basis could include the following

SAP Instance SAP database (Oracle, MaxDB, DB2, etc)

SAP user and authorization management

SAP system monitoring and performance

Backup and Restores (generally these are only the database and not the O/S)

Assist ABAP/JAVA developers

The various SAP components that belong to the application layer, such as Customer Relationship Manager (CRM), Advanced Planning & Optimization (APO) and SAP Netweaver Business Warehouse (BW) are all based on a shared Basis layer, the tasks and tools are all the same to the administrator. In my Basis section I will only be covering the ABAP layer of the SAP system.

I will try and do my best to explain everything using screenshot's and a detailed explanation, the SAP systems that I will using are both work and an IDES solution that we have configured, however you can download the freely available SAP Netweaver application server trail from SAP to learn SAP Basis. I will be only covering databases very lightly, I have other sections on Oracle (Oracle RAC) and MaxDB. I will be covering some of the configuration that a Basis would get involved in like the Transport Management System (TMS), SAP Router, etc in other sections.

Fundamentals of Basis

There are many tasks involved with maintaining a SAP solution,

TaskBasis

Functiondescription

SAP System Administrator X Monitors the SAP system performance, keeps the system tuned and running

User Administrator X Creates and manages user accounts

Authorization Administrator X Creates and manages SAP roles and profiles

Security Administrator X Guarantees the security of the SAP system, monitors for any intrusion or security breaches

Transport Administrator X Copies changes between systems and manages change requests.

Background Job Administrator

X Schedules, monitors and manages background jobs

Data Backup Administrator X Schedules, performs and manages backups and restores in all the related SAP filesystems

Disaster Recovery Administrator

X Creates, tests and plans disaster recovery of the SAP servers

Programmer Create and manages ABAP/Java programs

Database Administrator X Manages the specific database (Oracle, MaxDB, DB2, etc)

Operating System Administrator

Manages the operating system required for the hardware (Linux, Solaris, AIX, Windows Server, etc)

Network Administrator Manages network access and guarantees that users and SAP can communicate with each other

Desktop Support Specialist Manages the desktop used by the user, this also includes the SAP GUI, Database tools which are used to maintain the SAP systems.

Printer Operator Manages network and desktop printers

Facility Manager Manages the technical/physical infrastructure (data center, comm's suites, power supply, air conditioning, etc)

Depending on the size of the environment tasks could even be performed by one person, I have highlight the common Basis functions that a SAP system administrator would be required to perform.

The main tasks of a SAP administrator is, keep the system running, make sure its secure and make sure that you have backups, it would not be a good career move if you cannot restore a corrupted SAP system, and make sure that you periodically test your backups either on a spare system or during DR testing. With any solution try and keep the SAP configuration as simple as possible, try to use standard methods for example try to use standard backup tools, stand database configuration, this will help when you may require SAP support, complex solutions will only cause delays, plus if only specific personnel know the complex solution what happens when they leave the company. SAP in this regard will advise you on how a SAP solution should be installed and configured, they even offer a service to validate your solution making sure that it meets SAP requirements and that they can fully support your solution.

You should document all processes, procedures, hardware changes, configuration changes, checks, problems errors and so on, because SAP is so large and complex you cannot know everything or remember everything, documentation comes in handy when you are called in the middle of the night and are half asleep, it makes life so much easier just to pickup a documented process and follow that then to try and think on your feet, plus documented processes have the backing from your management team which should have been involved in authorizing the process. Management should insist on documentation with today's high turnover of staff, key people may have left the company meaning skills that were involved in the building of the SAP environment have now gone. The problem with documentation is keeping it up to date

and this also includes DR documentation, a process should be in place to make sure that the documentation is refreshed regularly.

I use checklists or a change control to make sure that every step in a change is processed, this should include a work plan, test plan and a back out plan, the reason is two fold, firstly not only you can run a checklist or a change control, if it is document well then any other administrator should be able to run the checklist/change control on your behalf, secondly you get to think about what you are actually doing, you could get someone else to review the checklist/change control and they might pickup a missed task. In some of the sections I will add my own checklists, feel free to use or modify them for your own environment.

When building the SAP environment you should think about single points of failure, which could lead to a service outage, try to consider the below points

Make sure that backups are taken regularly and that database archive logs are shipped to the DR system.

Ensure hardware redundancy is in place for example, dual power, data is mirrored between sites, dual networking, etc

Keep hardware replacements at hand, invoking DR is a major decision try to fix the environment first

Ensure that you have all the contacts ready in case of problems and that the system knowledge is available (online)

Make sure that you cross-train staff, be prepared for any staff member to leave the company

Consider outsourcing, not a popular topic but it an option.

Before we start looking at the SAP system here are a few technology terminology

Database ServerThis contains the SAP components and the database (Oracle, MaxDB, DB2, etc). An important point to remember is that the database server determines the time of the SAP application.

Application Server

This server contains the SAP application, in systems with two layers this server forms part of the database server, application servers can be setup for online users, for background processing or for both

Instance

An instance refers to an installation of SAP on a server, we can distinguish between a central instance

central instance - contains the database and only exists once in the environment

dialog instance - are the application servers, you can have more that one which can reside on different servers, they will all connect to the same database server

SystemThe system is the complete SAP installation for a System ID (SID), a system logically consists of a SAP central instance and the dialog instances for the SID. Physically it comprises of the database server and the application servers.

Client See client in SAP Basis Introduction for more details.

A typical SAP configuration would be something like below

Layer Physical Device SAP Instance What runs on this layer

Display (presentation)

Desktop/Laptop None SAP GUI

Application Several Application Servers Dialog SAP

Database A single database server Central Database (Oracle, MaxDB, DB2)

With a two layer configuration both the dialog and central instances are run on a single server.

SAP Architecture

I will touch lightly on the SAP architecture, first lets us discuss the overall picture, as I mentioned above the environment will consist of a presentation layer this generally means the SAP GUI, the application layer (SAP processes) and the central database, this can be seen below, the application and database could reside on the same server or different servers.

A user will use the SAP GUI to communicate to the SAP application, they connect to the dispatcher, the dispatcher connects the user to a work process which then communicates with the database, this can be seen as below

A high level picture looks like below, the central instance contains a dispatcher which communicates with a number of work processes, there is also a message server, SAP gateway, SAP buffers, etc.

A work process can be divided into different types, the type of work process determines the kind of task for which it is responsible in the application server, the individual tasks are distributed to the work process by the dispatcher. You can determine how many work processes SAP will have and what their types will be. The dispatcher starts the work process and only assigns them to tasks that correspond to their type. This means that you can distribute work process types to optimize the use of the resource on your application servers. The various types of work processes are

ProcessSM50 entry

Description

Dialog work DIA deals with requests from an active user to execute dialog steps ( I will discuss this in more detail below)

Update UPDUP2

executes database update requests, Update requests are part of an SAP Logical Unit of Work (LUW) that bundle the database operations resulting from the dialog in a database LUW from processing in the background.

There are two processes that are related to the update process

UPD - update process for making U1 (time-critical) database changes

UP2 - update process for executing U2 (not time-critical) database changes

Background BGD process programs that can be executed without user interaction (background jobs)

Enqueue ENQadministers a lock table in the shared memory area, the lock table contains the logical database locks for the SAP system and is an important part of the SAP LUW concept. There is only one lock table, you may therefore also only have one application with enqueue work process (I will discuss this in more detail below)

Spool SPOpasses sequential datasets to a printer or to optical archiving, each application server may contain only one spool work process

Lets have a look at the dialog work process in detail, the process consists of two software processors and a database interface

There is a difference between user interaction and processing logic, the user interaction is controlled by screens which also consists of a flow of logic, SAP contains a special language for programming screen flow logic, the screen processor executes the screen flow logic, via the dispatcher it takes over the responsibility for communication between the work process and the SAP GUI.

 

The actual processing logic of an application is written inprogramming language. The ABAP processor executes the processing logic of the application program and communicates with the database interface.

The database interface provides the following

Establishing and terminating connections between the work process and the database

Access to the database tables

Access to Repository objects (ABAP programs, screens, etc)

Access to catalog information

Controlling transactions (commit and rollback)

Table buffer administration on the application server

The diagram shows two different ways to access the database Open SQL and Native SQL.Open SQL statements are a subset of standard SQL that is fully integrated in ABAP, they allow you to access data irrespective of the database system. Open SQL consists of the Data Manipulation Language (DML) basically insert, update, delete and select. The tasks of the Data Definition Language (DDL) and Data Control Language (DCL) are performed by the ABAP dictionary and the authorization system.

Native SQL is loosely integrated into ABAP and allows access to all of the functions contained in the programming interface of the respective database system. Unlike Open SQL statements, Native SQL statements are not checked and converted but instead are sent directly to the database system.

The task of the message server is to inform all the servers (Instances) belonging to the SAP system of the existence of the other servers, details such as system load, enqueue status, update services are communicated about each instance.

The enqueue service is used to manage locks, below we can see two instances that may require the same object, to prevent corruption, logical locks are used to protect data, and locks are released when a process has finished with it. The enqueue work process manages the central lock table of the entire system in its memory, you can use transaction code SM12 to see the locks. Note that SAP locks are different to database

locks that are used by a specific database as each have there own way to deal with locks at the database level.

Behind the scenes a number of operating system processes are running which relate to the above, you can use transaction code SM50 to view the process from SAP point of view (see below for a screenshot of this), the below screenshot details the processes running on a linux server

Below are the processes running on a windows server

Here is a process overview screenshot (tcode SM50), you can clearly see the processes we have been talking about above.

Client

The client is probably as far as the system administrator will dive into the SAP FI world, you are expected to administer clients which includes creating, copying,

deleting and configuring. I kinda think of a client as a self contained system on its own when it comes to administration however I will briefly describe what a client is and what it does.

A client is by definition an organizationally and technically self-contained unit within SAP, so for an example, if you had two totally different business related companies you will probably have two clients one for each business, all the business management data is protected here because other clients data cannot be accessed. Althrough a client has access to all the tables the tables can be either

client dependant client independant

If the table has a MANDT field the table is said to be a client dependant table, which means that a client can only access data in that table that is related to that client, client dependant tables will always contain a MANDT field and will contain the client ID as we will see in the table T000 later. MANDT is short for MANDANT which is client in German.

You can view the table DD02L (use transaction code SE16) to find out if a table is client dependant or independant, look at the column clidep, if it has a X then the table is client dependant.

A client is identified within a system by a unique three-digit code (MANDT), try avoiding letters as this limits the functionality of the client to a considerable degree (in relation to transports and certain application modules). Three clients are normally delivered with the system

000 - contains the default settings with no application data, you should never make changes to this client and it can be used to create other clients but generally you customerize 001 to your own evironment, it is also used as a working client only for support pack upgrades or ABAP load generations (SGEN) and implementing other languages.

001 - is the same as 000 but generally you customize it for your own environment and thus you use this client when copying for new clients as it contains your environment settings, some users never touch this client and use it as a backup to 000, some may not have client 001

066 - early watch client is purely a service client that enables SAP to access remotely the customer system with regard to analyzing errors and performance, you must not change or delete this client.

Generally when SAP sets up a system they may setup additional clients, here are a few examples of a typical development SAP system

200 - customizing and development 210 - sandbox client

300 - reference client for integration and training

310 - training client

When you login to a SAP system you have to give the client ID this makes sure that you only have access to that clients data. You can obtain client information either by looking at transaction code SCC4 or a table called T000, first lets have a look at the transaction code SCC4, you can see that I have a number of clients configured on my system.

As mentioned above client information is stored in table T000, notice the MANDT which is the client ID.

Lastly I just want to talk about currency, when you configure a client you have to specify the currency, the FI department may mention something called a "Group Currency", the group currency is actually taken from the client currency. You should not change a clients currency once a client is in full use as this may have a big impact

of existing data in the system. I will talk about currencies in much more detail in my FI section.

I have a administration section which details how you create, delete and configure clients.

What is BASIS?

The full form of BASIS is “Business Application Software Integrated solution”. Basis is a set of programs and tools that act as an interface with

Database,Operating system, Communication protocols and business applications (such as FI,CO,MM,etc).

SAP applications such as FI,CO,PP etc. can run and communicate with each other across different Operating systems and Databases with the help of BASIS.

Nowadays Basis is known as Netweaver.

Alias of BASIS is SAP Application Server Technology and alias of netweaver is SAP Web Application Server.

After adding java stack (the applications which are developed in J2EE,BSP,JSP,etc..),enhanced security standard for business process.Both ABAP and

Java stack can be monitored from one platform. Netweaver supports standard protocols such as

HTTP,SMTP,XML,SOAP,SSO,WEBDAV,WSDL,WMLSSO,SSL,X.509 and Unicode format(representation of handling text).

We can say Basis is the operating system for SAP applications and ABAP.Basis provides services like communication with the operating system,database

communication,memory management,runtime collection of application data,web requests,exchanging business data etc…

Basis supports a number of known operating systems (Unix flavors,Microsoft windows server edition,AS400,z/OS,etc) and databases

(Oracle,DB2,Informix,Maxdb,Microsoft SQL Server,etc)..

 

As we know BASIS is a set of tools. This tool has the following different functionalities:-

System monitoring and administration tools

Common monitoring tool CCMS(Computing Centre Management System) to monitor alerts of R/3 system from an one place.

Server side scripting in ABAP and Javascript.

Use of Business server pages to build online stores and portals.

Database monitoring and administration utilities

Resource management like memory,buffer,etc.

Authorization and profile management tools for user management.

Internet access control to the system and business objects.

Transfer modifications in screen,program,layout from the development to production system for accuracy purpose by Transport Management

System.

Client server architecture and configuration.

Graphical User Interface designing for the presentation layer.

 

SAP Basis consultant’s responsibilities:-

SAP Basis is a middleware tool for applications, operating system and database.SAP Basis consultant should able to do the following tasks:-

SAP application server monitoring , ABAP dump and system log analysis.

Performance tuning

Database maintenance , Database backup schedule and restore

R/3,netweaver,solution manager installation ,etc..

SAP license maintenance.

SAP landscape , transport management system installations, etc

Client creating , client copying , client deletion, etc

Creating user, assigning roles , locking and unlocking users,etc

Background jobs scheduling , job monitoring , job deletion , etc

Profile and operation mode maintenance

Applying support patches, upgrading and installing add-ons

SNOTE applying and removing errors.

System copy,System refresh ,etc

This a generic list. There are many other responsibility that a Basis consultant shoulders. Everyday you learn something new!

Read more at http://www.saptraininghub.com/introduction-to-basis/#vhJzEUMHQGHt1mcW.99