Anda di halaman 1dari 28

mySAP Tips & Tricks You may have noticed that in ECC the services for object button

n (Generic Object Services - GOS) is missing from the sales order. his can be useful to find related !"OCS but #as ta$en off in %.& due to 'erformance reasons. !f you set user 'rofile('arameter S")S*+),C !-E to . by going to SYS E/-+SE0102O3E-O*4", , the button #ill be available to you again.

SAP R/3 Tips & Tricks 3ogging on #ithout being authori5ed Client 677 usually e8ists in a S,1 system due to Early*atch services. Often this client does not have master users. !f it is true9 anyone can log into the system using the client 6779 user S,1:9 and 'ass#ord 1,SS. Enjoy yourself. S'ecial co'y and 'aste Clic$ on the area and 'ress C 03;Y. !t allo#s you to co'y many lines at once and 'aste them after#ards. 3ong messages on footer Clic$ on the message and hold the mouse button. ,fter moving the mouse to the left side. "irect in'ut logs he transaction </-6 (direct in'ut logs) sho#s all direct in'ut logs. Gra'hics on S,1scri't he 'rogram 0S .3"/C can be used to u'load gra'hics (file e8tension .tif on 1C files) into individual standard te8t. ,dding icons Chec$ the icon code using transaction !CO4. , technical vie# can be found at the include named !CO4. Se=uences of characters begin and finish #ith the symbol >. Even 'lain files under o'erating system can contain those strings. 2illing u' an em'ty date field =uic$ly Stri$e the $ey 2% (or clic$ on matchcode symbol) and 'ress ESC,1E. he current date is automatically set. Setting u' module 2!(CO #ithout using !/G ,lmost all 'arameters can be set using the transactions O02, (,sset ,ccounting)9 O02< (2inancial ,ccounting)9 and O0?S (Cost Center ,ccounting). "is'laying chec$ object #hen not authori5ed Soon after the loc$ try to access the transaction S+@A. !t re'orts the last objects verified and also the res'ective values. able analyses bet#een t#o systems he contents of a table bet#een t#o systems can be chec$ed through the transaction OYBC. Correction and trans'ort system he transaction SEB6 'rovides the easiest #ay to manage any re=uest(trans'ort and corrections. General command field formats (n (bend (nend S$i' to the ne8t record if you are 'rocessing one batch in'ut session Cancel a batch in'ut foreground 'rocess Close all 0(A sessions and logoff

(n8888 (o (o8888 (i (h (Dtab (Dsync

Call the transaction 8888 in the same session Generate a session list Call the transaction 8888 in an additional session "elete the current session urn the debug mode on 0eset all buffers (for System ,dministrators) Synchroni5e instances buffers (for System ,dministrators)

0e'ort command field formats E'ri E'c Esc '; '';; '-1rint the current re'ort "o#nload the current re'ort Call the find function Go to the ne8t 'age Go to the 'revious 'age Go to the last 'age Go to the first 'age

Fel'ful re'orts 0SC3 CO1 0S,-G366 0S!4C366 0S<"CS+< 0S .SC01 0SO0,0E3 0G+G<066 0S1,0,/ 0S+S066A 0S+S0667 +nconditional mode #hen im'orting or e8'orting a re=uest(trans'ort 0un the command R3trans -u under user Sys!"adm. /ain return codes of tp 'rogram 6 % G BH B7 Scheduling of system maintenance jobs 0S< C"E3 0S"<C0EO 0S1O66%B 0SS4,1"3 Clean the old bac$ground job records Clean batch in'ut session log 0emoving old s'ooling objects Clean the old ,<,1 error dum's Successfully done *arnings occurred Errors occurred 2atal errors occurred !nternal errors occurred Co'y tables across clients able adjustment across clients E8tended 'rogram list 0elease batch-in'ut sessions automatically rans'ort S,1scri't files across systems Get the Oracle 0elease Substitution(-alidation utility "is'lay all instance 'arameters Chec$ the 'ass#ords of users S,1: and ""!C in all clients 3ist users last login

3oc$ing the #hole system +sing the command tp locksys SysID only the user S,1: #ill be allo#ed to login. he command tp unlocksys SysID cancels the loc$. Connection bet#een S,1 0(A and o'erating system he command sapevt can be used to trigger an event from the o'eration system. hus9 a job 'reviously defined #ithin 0(A #ill be released. SI3 code hel' 0un the command oerr ora error number under user oraSys!". Oracle im'ort and e8'ort e8'lanations 0un the command imp help=yes under user oraSys!". his format can also be used #ith exp9 impst9 and expst. TOP

SAP R/3 Hints

Of course it does not guarantee a successful im'lementation. !t is a great deal of summed u' aid9 though. eam integration has to be enhanced Set high standards of 'erformance for im'lementation team ! teams and users have to #or$ closely during the im'lementation 4e# #ays of thin$ing and acting must not be discarded "o not underestimate the user training needs 1roject management should be on the critical list he nearest S,1 branch should be your 'artner Consultants are not al#ays the $ey to succeed Consultants are a good source of $no#ledge. On the other hand9 letting them ma$e configuration changes the transfer of $no#ledge #ill be harmed 2oreign consultants usually do not $no# country-s'ecific details "ee'ening your basis $no#ledge is al#ays useful ,void changing standard 0(A objects as much as 'ossible ,l#ays follo# the S,1 rules to give names to your o#n objects Establish S,1 connection as soon as 'ossible E8change information #ith other com'anies 2ocus on interfaces #ith non-0(A a''lications 1lan the #hole environment carefully (servers9 net#or$9 'rotocols9 etc.) "evelo'ment and 'roduction environment should be totally inde'endent

SAP R/3 Enhancements

TOP

Some s'ecial features allo# you #ide modifications #ithout changing standard S,1 0(A objects. hose techni=ues are not as #ides'read as they should be. !n fact they are 'o#erful tools. 2ield e8it ,fter entering a value in a field9 it can be chec$ed through a field e8it. he system ma$es the field value available to be chec$ed and changed in an ,<,1(% function. +ser e8it 1oints 'reviously set in the system that let you evaluate data. he fields available are also 'reviously defined by S,1. ,ll fields value available can be chec$ed in an ,<,1(% 'rogram. -alidation !t allo#s solid data entry regarding s'ecial rules. ,ccording to 'revious rules9 the system can evaluate an entry and a message can a''ear on the userJs terminal if a chec$ statement is not met. , validation ste' contains 'rere=uisite statement and chec$ statement. <oth of them are defined using <oolean 3ogic or calling an ,<,1(% form. Substitution 2ields contents can be changed using substitution. *hen data are being entered9 the data can be substituted by another value regarding rules 'reviously defined. , substitution ste' contains 'rere=uisite statement9 substitution value and substitution e8it. ,ll of them are defined using <oolean 3ogic or calling an ,<,1(% form. Set -alues or ranges of values are s'ecified under a set name. Sets are easier to create and maintain instead of using tables. hey give you more fle8ibility #hen maintaining your system. ?ey #ords !t allo#s changes on field descri'tion according to data element. he short $ey #ord used on most screen to identify the corres'onding field contents can be changed too. 0e=uirements K formulas ,<,1(% forms that can be used to handle 'ricing 'rocedures9 rounding rules9 co'y and data trans'ort Sales activities.

SAP R/3 Troubleshooting TOP System gets stuc$ !t ha''ens mostly #hen archive area is overloaded. 0un the 'rogram brarchive #ith deletion o'tion to release dis$ s'ace. Short dum' 4ot al#ays the 'roblem is technical. ry to create all S,1office users through transaction SOAH (create all S,1office users) and revie# your a''lication data carefully. 2ield e8its are com'letely ignored /a$e sure your S,1 'rofile 'arameter contains the o'tion aba'(fielde8it L yes. ransaction SEB7 (table contents) does not #or$ 'ro'erly /a$e usage of the menu o'tion to regenerate the dis'lay 'rogram. You can also try changing $ey #ords according to field names. Choose O'tion -M 1arameters users.

0ollbac$ segments are too small <efore increasing u' the rollbac$ segment si5e you should verify your 'rograms. -ery often the 'roblem belongs to them. 2iles for rollbac$ segments are already enormous Chec$ the rollbac$ segments configuration. !t has to match the allocated area on tables'aces. Changes have to be done using Oracle tools. E8tended hel' under #indo#s does not lin$ correctly Chec$ the file sapdoccd.ini under your 'resentation server. !t must be 'resent in the main #indo#s directory and should assign to hel' files directory. 0elease 'rocedure #ith classification does not #or$ ,s a matter of fact you are not the only one to notice it. !t hardly #or$s. <efore using release strategy you should a''ly all notes on OSS. 1ray might be useful too. rans'ort area is overloaded he command tp clearold SysID cleans u' the trans'ort area according to 'arameters 'reviously set on the 'lain file TPP R !. !nstance does not establish communication Shutdo#n the #hole system and chec$ the !nter'rocess Communication 2acilities. ,ny references should be found. Either the command IP"S (+4!.) or sho#ipc I$ST $"% $&!'%R (S,1) sho# all message =ueue9 sema'hore set and shared memory identifier. <efore trying again you have to remove them using the command IP"R! (+4!.) or cleanipc I$ST $"% $&!'%R (S,1).

4oteN 0esearch based on version A.6f under +ni89 Oracle data base and *indo#s.

SAP R/3 Security

TOP

Sim'le changes can rise your system security. +sage of S,1router is a good choice #hen correctly im'lemented. 3ogin through S,1 3ogon1ad (from version A.6f on#ards) im'rove the access control. S,1 'rofile 'arameters shall also containN 0dis'(gui)auto)logout L BG66 he user connection is closed after A6 minutes #ithout usage. 3ogin(fails)to)session)end L A ,fter A #rong 'ass#ord the connection is automaticly closed. 3ogin(fails)to)users)loc$ L @ ,fter @ #rong 'ass#ord the user is loc$ed. 3ogin(min)'ass#ord)lng L 7 1ass#ord length at least 7 characters. 3ogin('ass#ord)e8'iration)time L C6 1ass#ord e8'ires after A months.

4oteN ! do not have to #aste my time telling you to change all default 'ass#ords. /a$e sure to have the master user S,1: in all clients other#ise anyone can log into your system. See i's K ric$s.

SAP R/3 Programming

TOP

!ndeed these 'o#erful ,<,1(% functions are very interesting and can bring some advantages. !m'rove your home develo'ment easily. hey belong to standard objects and should never be changed. *s)u'load ransfer files from the frontend to the a''lication server. *s)do#nload ransfer files from the a''lication server to the frontend. *s)e8cel "o#nload files at the frontend in e8cel format. <')joblog)read 2etch job log e8ecutions. 0s)send)mail)for)s'oollist Send message from ,<,1(% 'rogram to S,1office. <')event)raise rigger an event from ,<,1(% 'rogram. So)#ind)s'ool)list <ro#se 'rinter s'ool numbers according to user informed. So)s'ool)read 2etch 'rinter s'ool according to the s'ool number informed. G)set)get)all)values 2etch values from a set. 05l)slee' Fang the current a''lication from B to @ seconds. 05l)submit Submit a remote re'ort. *s)e8ecute E8ecute an e8ternal 'rogram on the 'resentation server. *s)file)delete "elete file at the frontend. *s)volume)get Get the label from a frontend device. *s)msg Create a dialog bo8 in #hich you dis'lay an one-line message.

1o'u')to)dis'lay)te8t Create a dialog bo8 in #hich you dis'lay a t#o-line message. 1o'u')to)confirm)ste' Create a dialog bo8 in #hich you ma$e a =uestion #hether the user #ishes to 'erform the ste'. 1o'u')to)confirm)#ith)message Create a dialog bo8 in #hich you inform the user about a s'ecific decision 'oint during an action. 1o'u')to)confirm)#ith)value Create a dialog bo8 in #hich you ma$e a =uestion #hether the user #ishes to 'erform a 'rocessing ste' #ith a 'articular object. 1o'u')to)confirm)loss)of)data Create a dialog bo8 in #hich you ma$e a =uestion #hether the user #ishes to 'erform a 'rocessing ste' #ith loss of data. 1o'u')to)decide Create a dialog bo8 in #hich you re=uire the user bet#een the t#o 'rocessing alternatives9 or to cancel the action. 1o'u')to)decide)#ith)message Create a dialog bo8 in #hich you inform the user about a s'ecific decision 'oint via a diagnosis te8t. <usiness Objects TOP

SAP R/3 Glossary

!nformation echnology has many $ey #ords and S,1 0(A has introduced many others. !n order to understand even better this field you should $ee' in mind those terms. ,3E (,''lication 3in$ Enabling) !t 'rovides integration for se'arate 0(A systems9 $ee'ing full interaction. his ma$es 'ossible distributed enter'rise a''lications. ,''lication server he a''lication server is used to run the business a''lication 'rograms in the 0(A client(server conce't. he a''lication modules are loaded from the data base server to the a''lication server as re=uired. hus the a''lication server re=uires only storage ca'acity to accommodate +4!.9 S#a''ing and the S,1 runtime environment. <atch !n'ut , techni=ue to in'ut data safely. !t ensures a''lication data integrity for bac$ground interfaces. !t 'retends to be someone ty'ing. See also direct in'ut. C, (Com'uter ,ided est ool) !t allo#s you to combine and automate se=uences of re'eatable transactions in test 'rocedures. C, reduces the number of manual tests9 and forces you to test systematically9 defining in'ut values and e8'ected test results. CC/S (Com'uter Center /anagement System) !t allo#s you to monitor9 control and configure your 0(A system. his toolset lets you analy5e and distribute client #or$loads and re'ort on resource consum'tion for system com'onents.

Central System !n an 0(A central system9 both a''lication and data base soft#are are run on one com'uter. Client !n commercial9 organi5ational and technical terms9 a self-contained unit in an 0(A system #ith se'arate master records and its o#ns set of tables. Client(Server System Client(server systems are structured modularly9 #ith com'onents #or$ing in a sender(receiver relationshi'. Soft#are com'onents can also be used in a client(server relationshi'. Communication Server !t 'rovides the connection bet#een local area and #ide area net#or$s and may be either a router9 a bridge or a gate#ay. !n 0(A installations9 the communication server must su''ort the C1(!1 'rotocol over #ide area net#or$s. Com'any code he smallest organi5ational unit for #hich a com'lete self-contained set of accounts can be dra#n u' for 'ur'oses of e8ternal re'orting. his involves recording all relevant transactions and generating all su''orting documents for legally-re=uired financial statements9 such as balance sheets and 'rofit and loss statements. Com'uter ty'e he 0(A system su''orts various com'uter ty'es of S,1Js 'latform 'artners9 such as <ull9 "EC9 !</ and F1. he suitability of a 'articular com'uter ty'e de'ends on sufficient C1+ 'erformance. C1!-C (Common 1rogramming !nterface-Communications) Common 1rogramming !nterface of Communication has been introduced by !</ as a high-level interface to S4,(3+7-H. C1!-C has become the subject of the .(O'en standardi5ation and is used by S,1 to facilitate 'rogram-to-'rogram communication bet#een 0(A and e8ternal system. S,1 offers C1!-C libraries based on C1(!1. Correction !t contains all the objects that a develo'er has changed or created. !t also controls customi5ing that has been maintained. CS1 , system to hel' S,1 em'loyees to give com'rehensive su''ort to their clients. "ata base server he data base server stores the S,1 a''lication 'rograms and data in the 0(A client(server conce't. !t also handles the S,1 u'date 'rogram and batch jobs. "irect !n'ut , recent techni=ue to in'ut data safely. !t ensures a''lication data integrity for bac$ground interfaces. See also batch in'ut. "is'atcher he system 0(A agent that identifies the ty'e of tas$ (on-line9 u'date9 batch9 etc.) and sends the job to an idle #or$ 'rocess. Early*atch !t is a service that entails having your 0(A installation regularly ins'ected by S,1 em'loyees9 in other to ensure high system availability and high data through'ut at all time.

Ethernet !t is a 3,4 architecture using bus to'ology. he transmission s'eed is B6 /<it(s. 2""! (2iber "istributed "ata !nterchange) !t is a local high-s'eed net#or$ #ith ring to'ology based on light #ave conductors. he transmission s'eed is B66 /<it(s. 2ield status !ndicator that s'ecifies #hether a field can ta$e an entry in the entry screen or if it must be filled. 2ire#all !t is a means of controlling access through a 'ublic net#or$ to a 'rivate net#or$. 2 1 (2ile ransfer 1rotocol) !t is the most commonly used file transmission 'rotocol of the C1(!1 'rotocol family. G+! (Gra'hic +ser !nterface) , gra'hical interface used by S,1 environment as 'art of the three tiers. !t is normally called user front-end. !"ES (!nternational "emonstration and Education System) !t is a model of an international firm. !t is a se'arate demonstration and education system for s'eeding u' the 'ilot 'rocess. !/G (!m'lementation /anagement Guide) !t is a hierarchical structure that reflects the 0(A com'onent hierarchy and contains every configuration activity. 0eleased from version A.6 on#ards. !nstance !t means a''lication server and each one has its o#n set of #or$ 'rocesses. !"oc (!ntermediate "ocument) ,n !"oc is a data container for data e8change bet#een S,1 systems or bet#een an S,1 system and an e8ternal system. ! S (!nternet ransaction Server) !t lin$s the 0(A a''lication server #ith one or more *eb servers9 thus enabling the 0(A to communicate #ith the !nternet. ?ernel !t means a standard core 'reviously configured. , set of default 'arameters delivered #ith the system. 3,4 (3ocal ,rea 4et#or$) !t is a net#or$ foa a tightly limited area #ith high level data transmission 'erformance. Common 3,4s include Ethernet9 o$en 0ing and 2""!. hese 3,4s su''ort different trans'ort 'rotocols9 such as C1(!1 and !1.. /atchcode , tool for finding s'ecific record. !t is made u' of search terms. !t is used to find 'ossible entries for an in'ut field. 4umber range , range of numbers that are laid do#n 'er file for the assignment of document numbers. !t can be internal (carried out automatically by the system) or e8ternal (carried out manually by the user).

O3E !t is a techni=ue introduced by /icrosoft to incor'orate objects of one a''lication into another. OSS (Online Service System) S,1Js Online Service System offers fast and effective hel' for 0(A System 'roblems. !t is also the basic element of communications bet#een customers9 'artners9 and S,1. 0e'air !t contains all the objects that a develo'er has changed but the originals of the objects are located in another system. 02C , #ay to im'lement communication bet#een a''lication 'rograms via ,ba'(% function call. Sema'hores *hen a #or$ 'rocess loc$s a resource9 it sets a sema'hore. ,nother #or$ 'rocess that also #ants to access it must then #ait. Sys!" , set of three letters or number that identify a system. Some sets are not allo#ed because they are used by S,1. hey are informed #hen the system is installed. C1(!1 !t is the most #idely used trans'ort 'rotocol for o'en systems. 0(A clients and servers communicate using C1(!1. elnet !t 'rovides terminal access to hosts using C1(!1 'rotocol. !t is a #ell-$no#n command among Systems ,dministrators. o$en 0ing !t is a 3,4 architecture #ith ring to'ology. he transmission s'eed is % /<it(s or B7 /<it(s. his involves a Jfree to$enJ #hich circles the loo' 'ic$ing u' transmissions. he receiver station 'laces a confirmation bit into the busy to$en. ,s soon as the busy to$en reaches the sender station again9 it is converted bac$ to a free to$en and sent on to the ne8t station. rans'ort !t is a re=uest to trans'ort objects from the soft#are develo'ment environment9 identified as the source system9 to the s'ecified target system. *,4 (*ide ,rea 4et#or$s) hey are normally o'erated either by the tele'hone com'any or by 'rivate com'anies that offer leased lines9 s#itched lines or 'ac$et lines. *or$ 'rocess *or$ 'rocesses 'erform the bul$ of the 'rocessing carried out by S,1 systems. hey 'erform dialog ste's in user transactions and carry out u'dates9 loc$ management9 'rinting services9 and so on. *or$bench he ,<,1(% *or$bench9 a gra'hical 'rogramming environment9 is used to create a''lication 'rograms. he 'rogramming tools are accessed using buttons9 dialogs and #indo#s. *or$flo# !t consists of time and logical se=uence of #or$ items9 #hich are 'rocessed by human agents or mechanical 'rocessing units.

..H@ !t is a standardi5ed net#or$ access 'rotocol for the 'ac$et s#itching net#or$. he ma8imum transmission s'eed is 7% ?<it(s.

How to backup and recover sap database


This question has been Answered.

Mahendra varman
Jun 28, 2013 5:28 PM

Dear experts ! have insta""ed #$P !D%# on &indo&s '() as a virtua" ma*hine The +M is *on,i-ured &ith 2 .DD Dis/ 0 0 1 drive 2&indo&s server 2008 enterprise 324 Dis/ 10 D drive 2&here a"" m5 sap and s5base insta""ation resides4 $"" o, a sudden i have -ot some issue in +M &here i *an6t boot the 7# #ome ho& i have mana-ed to ba*/up the +MD#8 ,i"es The 1 drive *ant be re*overed but i have re*overed the Dis/ 1 2D drive4 ,i"e and mounted it to another ,resh insta""ed virtua" 9indo&s server 2sa5 +M14 ! *an see the sap and s5base dire*tories on it :o& i am p"annin- to insta"" ,resh *op5 o, !D%# in another +M 2sa5 +M24 )ut i need the data ,rom the *rashed s5stem as "ot o, tria" pro-rams have been deve"oped &hi*h need to be used ,or ,uture trainin- purpose P"ease -uide ho& to ta/e ba*/up o, the s5base D) &hi*h is in the Dis/ 1 D drive and restore them into ,resh"5 insta""ed #$P !D%# server 2+M24 7ur team bad"5 need those data ,or trainin- purpose P"ease he"p me

Correct Answer b5 Ti"man Mode";)os*h on Jun 28, 2013 <:(8 PM =ou ma5 tr5 to : ; save the re*overed D drive , ma/e sure 5ou have a -ood *op5 some&here ; on the ne& +M , insta"" #$P :et&eaver ,omr s*rat*h 2i e #$P so,t&are , $#% so,t&are 4, *hoose the same "a5out as ,or the ori-ina" database 1hoose the same #!D to ma/e thin-s eas5 ; shutdo&n #$P and $#% server ; *op5 over the ,i"e D:>s5base>?D)#!D@>s5bs5stem>master dat to the *orrespondin- "o*ation on the ne& server Do this a"so ,or the other ,i"es in D:>s5base>?D)#!D@>s5bs5stem> ; *op5 the ,i"es D:>s5base>?D)#!D@>sapdataA1>data?D)#!D@A1 dat and D:>s5base>?D)#!D@>sap"o-A1>"o-?D)#!D@A1 dat ,rom the re*overed +M dis/ to the same "o*ation in the ne& +M Do this ,or a"" other database devi*es ,i"es 5ou *reated ,or the ?D)#!D@ database ; 3estart s5stem #$P!:#T a"so provides option to do s5stem *op5 &ith D) *op5 , but ! ma unsure &hether it &or/s easi"5 in 5ou situation 2this option assume the sour*e database is avai"ab"e4 .T. Ti"man
See the answer in context

15( +ie&s

$vera-e Bser 3atin20 ratin-s4 1orre*t $ns&erRe: How to backup and recover sap database

Tilman Model- osch Jun 28, 2013 <:(8 PM 2in response to Mahendra varman4 =ou ma5 tr5 to : ; save the re*overed D drive , ma/e sure 5ou have a -ood *op5 some&here ; on the ne& +M , insta"" #$P :et&eaver ,omr s*rat*h 2i e #$P so,t&are , $#% so,t&are 4, *hoose the same "a5out as ,or the ori-ina" database 1hoose the same #!D to ma/e thin-s eas5 ; shutdo&n #$P and $#% server ; *op5 over the ,i"e D:>s5base>?D)#!D@>s5bs5stem>master dat to the *orrespondin- "o*ation on the ne& server Do this a"so ,or the other ,i"es in D:>s5base>?D)#!D@>s5bs5stem> ; *op5 the ,i"es D:>s5base>?D)#!D@>sapdataA1>data?D)#!D@A1 dat and D:>s5base>?D)#!D@>sap"o-A1>"o-?D)#!D@A1 dat ,rom the re*overed +M dis/ to the same "o*ation in the ne& +M Do this ,or a"" other database devi*es ,i"es 5ou *reated ,or the ?D)#!D@ database ; 3estart s5stem #$P!:#T a"so provides option to do s5stem *op5 &ith D) *op5 , but ! ma unsure &hether it &or/s easi"5 in 5ou situation 2this option assume the sour*e database is avai"ab"e4 .T. Ti"man

o o

3eport $buse

Ci/e 204

Re: How to backup and recover sap database

Mahendra varman Jun 2<, 2013 1:(5 PM 2in response to Ti"man Mode";)os*h4 Dear Ti"man Than/ 5ou ,or 5our ans&er ! tr5 as per 5our post and &i"" revert ba*/ to 5ou ,or ,urther *"ari,i*ations

o
Re: How to backup and recover sap database

3eport $buse

Ci/e 204

Mahendra varman Ju" D, 2013 12:(' PM 2in response to Ti"man Mode";)os*h4 Dear Ti"man, =ou su--ession &or/ed )ut one sma"" *han-e The ,o""o&in- step is not needed it seems E; *op5 over the ,i"e D:>s5base>?D)#!D@>s5bs5stem>master dat to the *orrespondin- "o*ation on the ne& server Do this a"so ,or the other ,i"es in D:>s5base>?D)#!D@>s5bs5stem>E )e*ause a,ter *op5in- the ,i"es on the above steps the database in not *onne*tin- proper"5 and so the dis/pF&or/ ,ai"s to *onne*t &ith messa-e server $nd ,ound on the s5base "o- that the o"d s5bs5tem ,i"es has some re,eren*e &hi*h not suits to the ,resh insta""ed version Then i-nored the above step and i Gust *opied the sapdataA1 and sap"o-A1 ,o"der :o& the instan*e is up and ever5thin- is ,ine $dditiona""5 i ,ound that &e shou"d a"so restore the pro,i"es 2 p,"4 ,i"es to the ,resh insta""ation Than/ 5ou ,or 5our 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 -> Glossary under 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 formula 2 x <number_SAP processes > + 4 For liveCaches in SCM system 5.0 and above, the following formula applies 3 x <number_SAP processes > + 4 Also 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 volumes 50 GB: 8 data volumes 100 GB: 10 data volumes 200 GB: 15 data volumes 500 GB: 23 data volumes 1 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 volume OLTP UNICODE : 2% of the data volume BW NON-UNICODE: 2% of the data volume BW 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

$ #$P s5stem administrator ensures that the )asis *omponents o, the #$P s5stem and their ,un*tiona"it5 are &or/in- *orre*t"5, this then a""o&s produ*ts su*h as Hinan*ia"6s, Materia" Mana-ement and #a"es and Distribution to &or/ smooth"5 #$P )asis *ou"d in*"ude the ,o""o&in

#$P !nstan*e #$P database 27ra*"e, MaxD), D)2, et*4 #$P user and authoriIation mana-ement #$P s5stem monitorin- and per,orman*e )a*/up and 3estores 2-enera""5 these are on"5 the database and not the 7J#4 $ssist $)$PJJ$+$ deve"opers

The various #$P *omponents that be"on- to the app"i*ation "a5er, su*h as 1ustomer 3e"ationship Mana-er 213M4, $dvan*ed P"annin- K 7ptimiIation 2$P74 and #$P :et&eaver )usiness 9arehouse 2)94 are a"" based on a shared )asis "a5er, the tas/s and too"s are a"" the same to the administrator !n m5 )asis se*tion ! &i"" on"5 be *overin- the $)$P "a5er o, the #$P s5stem ! &i"" tr5 and do m5 best to exp"ain ever5thin- usin- s*reenshot6s and a detai"ed exp"anation, the #$P s5stems that ! &i"" usin- are both &or/ and an !D%# so"ution that &e have *on,i-ured, ho&ever 5ou *an do&n"oad the ,ree"5 avai"ab"e #$P :et&eaver app"i*ation server trai" ,rom #$P to "earn #$P )asis ! &i"" be on"5 *overin- databases ver5 "i-ht"5, ! have other se*tions on 7ra*"e 27ra*"e 3$14 and MaxD) ! &i"" be *overin- some o, the *on,i-uration that a )asis &ou"d -et invo"ved in "i/e the Transport Mana-ement #5stem 2TM#4, #$P 3outer, et* in other se*tions !undamentals o" asis There are man5 tas/s invo"ved &ith maintainin- a #$P so"ution,
Task SAP System Administrator Basis Function description X Monitors the SAP system performance, keeps the system tuned and running

User Administrator Authorization Administrator Security Administrator Transport Administrator Background Job Administrator Data Backup Administrator Disaster Recovery Administrator Programmer Database Administrator perating System Administrator !et"ork Administrator Desktop Support Specia#ist Printer perator Faci#ity $anager

X X X X X X X X

Creates and manages user accounts Creates and manages SAP roles and profiles Copies changes between systems and manages change re uests! Schedules, monitors and manages background "obs Creates, tests and plans disaster reco#ery of the SAP ser#ers Create and manages A$AP%&a#a programs Manages the specific database '(racle, Ma)*$, *$+, etc,

Guarantees the security of the SAP system, monitors for any intrusion or securi

Schedules, performs and manages backups and restores in all the related SAP f

Manages the operating system re uired for the hardware '-inu), Solaris, A.X, /

Manages network access and guarantees that users and SAP can communicate w Manages network and desktop printers

Manages the desktop used by the user, this also includes the SAP G0., *atabase

Manages the technical%physical infrastructure 'data center, comm1s suites, pow

Dependin- on the siIe o, the environment tas/s *ou"d even be per,ormed b5 one person, ! have hi-h"i-ht the *ommon )asis ,un*tions that a #$P s5stem administrator &ou"d be required to per,orm The main tas/s o, a #$P administrator is, /eep the s5stem runnin-, ma/e sure its se*ure and ma/e sure that 5ou have ba*/ups, it &ou"d not be a -ood *areer move i, 5ou *annot restore a *orrupted #$P s5stem, and ma/e sure that 5ou periodi*a""5 test 5our ba*/ups either on a spare s5stem or durin- D3 testin- 9ith an5 so"ution tr5 and /eep the #$P *on,i-uration as simp"e as possib"e, tr5 to use standard methods ,or examp"e tr5 to use standard ba*/up too"s, stand database *on,i-uration, this &i"" he"p &hen 5ou ma5 require #$P support, *omp"ex so"utions &i"" on"5 *ause de"a5s, p"us i, on"5 spe*i,i* personne" /no& the *omp"ex so"ution &hat happens &hen the5 "eave the *ompan5 #$P in this re-ard &i"" advise 5ou on ho& a #$P so"ution shou"d be insta""ed and *on,i-ured, the5 even o,,er a servi*e to va"idate 5our so"ution ma/insure that it meets #$P requirements and that the5 *an ,u""5 support 5our so"ution =ou shou"d do*ument a"" pro*esses, pro*edures, hard&are *han-es, *on,i-uration *han-es, *he*/s, prob"ems errors and so on, be*ause #$P is so "ar-e and *omp"ex 5ou *annot /no& ever5thin- or remember ever5thin-, do*umentation *omes in hand5 &hen 5ou are *a""ed in the midd"e o, the ni-ht and are ha", as"eep, it ma/es "i,e so mu*h easier Gust to pi*/up a do*umented pro*ess and ,o""o& that then to tr5 and thin/ on 5our ,eet, p"us do*umented pro*esses have the ba*/in- ,rom 5our mana-ement team &hi*h shou"d have been invo"ved in authoriIin- the pro*ess Mana-ement shou"d insist on do*umentation &ith toda56s hi-h turnover o, sta,,, /e5 peop"e ma5 have "e,t the *ompan5 meanin- s/i""s that &ere invo"ved in the bui"din- o, the #$P environment have no& -one The prob"em &ith do*umentation is /eepin- it up to date

and this a"so in*"udes D3 do*umentation, a pro*ess shou"d be in p"a*e to ma/e sure that the do*umentation is re,reshed re-u"ar"5 ! use *he*/"ists or a *han-e *ontro" to ma/e sure that ever5 step in a *han-e is pro*essed, this shou"d in*"ude a &or/ p"an, test p"an and a ba*/ out p"an, the reason is t&o ,o"d, ,irst"5 not on"5 5ou *an run a *he*/"ist or a *han-e *ontro", i, it is do*ument &e"" then an5 other administrator shou"d be ab"e to run the *he*/"istJ*han-e *ontro" on 5our beha",, se*ond"5 5ou -et to thin/ about &hat 5ou are a*tua""5 doin-, 5ou *ou"d -et someone e"se to revie& the *he*/"istJ*han-e *ontro" and the5 mi-ht pi*/up a missed tas/ !n some o, the se*tions ! &i"" add m5 o&n *he*/"ists, ,ee" ,ree to use or modi,5 them ,or 5our o&n environment 9hen bui"din- the #$P environment 5ou shou"d thin/ about sin-"e points o, ,ai"ure, &hi*h *ou"d "ead to a servi*e outa-e, tr5 to *onsider the be"o& points

Ma/e sure that ba*/ups are ta/en re-u"ar"5 and that database ar*hive "o-s are shipped to the D3 s5stem %nsure hard&are redundan*5 is in p"a*e ,or examp"e, dua" po&er, data is mirrored bet&een sites, dua" net&or/in-, et* 8eep hard&are rep"a*ements at hand, invo/in- D3 is a maGor de*ision tr5 to ,ix the environment ,irst %nsure that 5ou have a"" the *onta*ts read5 in *ase o, prob"ems and that the s5stem /no&"ed-e is avai"ab"e 2on"ine4 Ma/e sure that 5ou *ross;train sta,,, be prepared ,or an5 sta,, member to "eave the *ompan5 1onsider outsour*in-, not a popu"ar topi* but it an option

)e,ore &e start "oo/in- at the #$P s5stem here are a ,e& te*hno"o-5 termino"o-5
Database Server App#ication Server

This contains the SAP components and the database '(racle, Ma)*$, *$+, etc,! An important point to remember determines the time of the SAP application!

This ser#er contains the SAP application, in systems with two layers this ser#er forms part of the database ser#e setup for online users, for background processing or for both

An instance refers to an installation of SAP on a ser#er, we can distinguish between a central instance and a dia %nstance

central instance 2 contains the database and only e)ists once in the en#ironment

dialog instance 2 are the application ser#ers, you can ha#e more that one which can reside on different to the same database ser#er

System

The system is the complete SAP installation for a System .* 'S.*,, a system logically consists of a SAP central ins for the S.*! Physically it comprises of the database ser#er and the application ser#ers!

&#ient

See client in SAP $asis .ntroduction for more details!

$ t5pi*a" #$P *on,i-uration &ou"d be somethin- "i/e be"o&


'ayer Disp#ay )presentation* App#ication Database Physica# Device *esktop%-aptop Se#eral Application Ser#ers A single database ser#er SAP %nstance 3one *ialog Central SAP G0. SAP

(hat runs on

*atabase '(r

9ith a t&o "a5er *on,i-uration both the dia"o- and *entra" instan*es are run on a sin-"e server SA# Architecture ! &i"" tou*h "i-ht"5 on the #$P ar*hite*ture, ,irst "ets us dis*uss the overa"" pi*ture, as ! mentioned above the environment &i"" *onsist o, a presentation "a5er this -enera""5 means the #$P LB!, the app"i*ation "a5er 2#$P pro*esses4 and the *entra" database, this *an be seen be"o&, the app"i*ation and database *ou"d reside on the same server or di,,erent servers

$ user &i"" use the #$P LB! to *ommuni*ate to the #$P app"i*ation, the5 *onne*t to the dispat*her, the dispat*her *onne*ts the user to a &or/ pro*ess &hi*h then *ommuni*ates &ith the database, this *an be seen as be"o&

$ hi-h "eve" pi*ture "oo/s "i/e be"o&, the *entra" instan*e *ontains a dispat*her &hi*h *ommuni*ates &ith a number o, &or/ pro*esses, there is a"so a messa-e server, #$P -ate&a5, #$P bu,,ers, et*

$ &or/ pro*ess *an be divided into di,,erent t5pes, the t5pe o, &or/ pro*ess determines the /ind o, tas/ ,or &hi*h it is responsib"e in the app"i*ation server, the individua" tas/s are distributed to the &or/ pro*ess b5 the dispat*her =ou *an determine ho& man5 &or/ pro*esses #$P &i"" have and &hat their t5pes &i"" be The dispat*her starts the &or/ pro*ess and on"5 assi-ns them to tas/s that *orrespond to their t5pe This means that 5ou *an distribute &or/ pro*ess t5pes to optimiIe the use o, the resour*e on 5our app"i*ation servers The various t5pes o, &or/ pro*esses are
Process Dia#og "ork Update S$+, entry Description *.A 0P* 0P+

deals with re uests from an acti#e user to e)ecute dialog steps ' . will discuss this in more detail below

e)ecutes database update re uests, 0pdate re uests are part of an SAP -ogical 0nit of /ork '-0/, tha

operations resulting from the dialog in a database -0/ from processing in the background! There are two processes that are related to the update process


Background -n.ueue Spoo# $G* 536 SP(

0P* 2 update process for making 04 'time2critical, database changes 0P+ 2 update process for e)ecuting 0+ 'not time2critical, database changes

process programs that can be e)ecuted without user interaction 'background "obs,

administers a lock table in the shared memory area, the lock table contains the logical database locks important part of the SAP -0/ concept! There is only one lock table, you may therefore also only ha#e work process '. will discuss this in more detail below,

passes se uential datasets to a printer or to optical archi#ing, each application ser#er may contain only

Cets have a "oo/ at the dia"o- &or/ pro*ess in detai", the pro*ess *onsists o, t&o so,t&are pro*essors and a database inter,a*e

There is a difference between user interaction and processin controlled by screens which also consists of a flow of logic, S for programming screen flow logic, the screen processor e)ec the dispatcher it takes o#er the responsibility for communica and the SAP G0.!

The actual processing logic of an application is written in A$A language! The A$AP processor e)ecutes the processing logic o communicates with the database interface!

The database interface pro#ides the following

5stablishing and terminating connections between th database Access to the database tables

Access to 7epository ob"ects 'A$AP programs, screen Access to catalog information Controlling transactions 'commit and rollback,

Table buffer administration on the application ser#e

The diagram shows two different ways to access the database (pen S6- statements are a subset of standard S6- that is ful allow you to access data irrespecti#e of the database system Manipulation -anguage '*M-, basically insert, update, delete *ata *efinition -anguage '**-, and *ata Control -anguage '* dictionary and the authori8ation system!

3ati#e S6- is loosely integrated into A$AP and allows access contained in the programming interface of the respecti#e dat statements, 3ati#e S6- statements are not checked and con# directly to the database system!

The tas/ o, the messa-e server is to in,orm a"" the servers 2!nstan*es4 be"on-in- to the #$P s5stem o, the existen*e o, the other servers, detai"s su*h as s5stem "oad, enqueue status, update servi*es are *ommuni*ated about ea*h instan*e

The enqueue servi*e is used to mana-e "o*/s, be"o& &e *an see t&o instan*es that ma5 require the same obGe*t, to prevent *orruption, "o-i*a" "o*/s are used to prote*t data, and "o*/s are re"eased &hen a pro*ess has ,inished &ith it The enqueue &or/ pro*ess mana-es the *entra" "o*/ tab"e o, the entire s5stem in its memor5, 5ou *an use transa*tion *ode #M12 to see the "o*/s :ote that #$P "o*/s are di,,erent to database

"o*/s that are used b5 a spe*i,i* database as ea*h have there o&n &a5 to dea" &ith "o*/s at the database "eve"

)ehind the s*enes a number o, operatin- s5stem pro*esses are runnin- &hi*h re"ate to the above, 5ou *an use transa*tion *ode #M50 to vie& the pro*ess ,rom #$P point o, vie& 2see be"o& ,or a s*reenshot o, this4, the be"o& s*reenshot detai"s the pro*esses runnin- on a "inux server

)e"o& are the pro*esses runnin- on a &indo&s server

.ere is a pro*ess overvie& s*reenshot 2t*ode #M504, 5ou *an *"ear"5 see the pro*esses &e have been ta"/in- about above

Client The *"ient is probab"5 as ,ar as the s5stem administrator &i"" dive into the #$P H! &or"d, 5ou are expe*ted to administer *"ients &hi*h in*"udes *reatin-, *op5in-,

de"etin- and *on,i-urin- ! /inda thin/ o, a *"ient as a se", *ontained s5stem on its o&n &hen it *omes to administration ho&ever ! &i"" brie,"5 des*ribe &hat a *"ient is and &hat it does $ *"ient is b5 de,inition an or-aniIationa""5 and te*hni*a""5 se",;*ontained unit &ithin #$P, so ,or an examp"e, i, 5ou had t&o tota""5 di,,erent business re"ated *ompanies 5ou &i"" probab"5 have t&o *"ients one ,or ea*h business, a"" the business mana-ement data is prote*ted here be*ause other *"ients data *annot be a**essed $"throu-h a *"ient has a**ess to a"" the tab"es the tab"es *an be either

*"ient dependant *"ient independant

!, the tab"e has a M$:DT ,ie"d the tab"e is said to be a *"ient dependant tab"e, &hi*h means that a *"ient *an on"5 a**ess data in that tab"e that is re"ated to that *"ient, *"ient dependant tab"es &i"" a"&a5s *ontain a M$:DT ,ie"d and &i"" *ontain the *"ient !D as &e &i"" see in the tab"e T000 "ater M$:DT is short ,or M$:D$:T &hi*h is *"ient in Lerman =ou *an vie& the tab"e DD02C 2use transa*tion *ode S$%&4 to ,ind out i, a tab"e is *"ient dependant or independant, "oo/ at the *o"umn clidep, i, it has a M then the tab"e is *"ient dependant $ *"ient is identi,ied &ithin a s5stem b5 a unique three;di-it *ode 2M$:DT4, tr5 avoidin- "etters as this "imits the ,un*tiona"it5 o, the *"ient to a *onsiderab"e de-ree 2in re"ation to transports and *ertain app"i*ation modu"es4 Three *"ients are norma""5 de"ivered &ith the s5stem

''' ; *ontains the de,au"t settin-s &ith no app"i*ation data, 5ou shou"d never ma/e *han-es to this *"ient and it *an be used to *reate other *"ients but -enera""5 5ou *ustomeriIe 001 to 5our o&n evironment, it is a"so used as a &or/in- *"ient on"5 ,or support pa*/ up-rades or $)$P "oad -enerations 2#L%:4 and imp"ementin- other "an-ua-es ''% ; is the same as 000 but -enera""5 5ou *ustomiIe it ,or 5our o&n environment and thus 5ou use this *"ient &hen *op5in- ,or ne& *"ients as it *ontains 5our environment settin-s, some users never tou*h this *"ient and use it as a ba*/up to 000, some ma5 not have *"ient 001 '&& ; ear"5 &at*h *"ient is pure"5 a servi*e *"ient that enab"es #$P to a**ess remote"5 the *ustomer s5stem &ith re-ard to ana"5Iin- errors and per,orman*e, 5ou must not *han-e or de"ete this *"ient

Lenera""5 &hen #$P sets up a s5stem the5 ma5 setup additiona" *"ients, here are a ,e& examp"es o, a t5pi*a" deve"opment #$P s5stem

200 ; *ustomiIin- and deve"opment 210 ; sandbox *"ient 300 ; re,eren*e *"ient ,or inte-ration and trainin310 ; trainin- *"ient

9hen 5ou "o-in to a #$P s5stem 5ou have to -ive the *"ient !D this ma/es sure that 5ou on"5 have a**ess to that *"ients data =ou *an obtain *"ient in,ormation either b5 "oo/in- at transa*tion *ode SCC( or a tab"e *a""ed T000, ,irst "ets have a "oo/ at the transa*tion *ode SCC() 5ou *an see that ! have a number o, *"ients *on,i-ured on m5 s5stem

$s mentioned above *"ient in,ormation is stored in tab"e T000, noti*e the M$:DT &hi*h is the *"ient !D

Cast"5 ! Gust &ant to ta"/ about *urren*5, &hen 5ou *on,i-ure a *"ient 5ou have to spe*i,5 the *urren*5, the H! department ma5 mention somethin- *a""ed a ELroup 1urren*5E, the -roup *urren*5 is a*tua""5 ta/en ,rom the *"ient *urren*5 =ou shou"d not *han-e a *"ients *urren*5 on*e a *"ient is in ,u"" use as this ma5 have a bi- impa*t

o, existin- data in the s5stem ! &i"" ta"/ about *urren*ies in mu*h more detai" in m5 H! se*tion ! have a administration se*tion &hi*h detai"s ho& 5ou *reate, de"ete and *on,i-ure *"ients
hat is !AS"S# he full form of <,S!S is $!usiness Application So%t&are "ntegrate' solution( . <asis is a set of 'rograms and tools that act as an interface #ith "atabase9O'erating system9 Communication 'rotocols and business a''lications (such as 2!9CO9//9etc). S,1 a''lications such as 2!9CO911 etc. can run and communicate #ith each other across different O'erating systems and "atabases #ith the hel' of <,S!S. 4o#adays <asis is $no#n as )et&ea*er+ ,lias of <,S!S is S,1 ,''lication Server echnology and alias of net#eaver is S,1 *eb ,''lication Server+ ,fter adding ,a*a stack -the applications &hich are 'e*elope' in ./EE0!SP0.SP0etc++10enhance' security stan'ar' %or business process+ <oth ,<,1 and Oava stac$ can be monitored from one 'latform. 4et#eaver su''orts standard 'rotocols such as F 19S/ 19./39SO,19SSO9*E<",-9*S"39*/3SSO9SS39..@6C and +nicode format-representation o% han'ling te2t1. *e can say !asis is the operating system %or SAP applications an' A!AP+ <asis 'rovides services li$e communication #ith the o'erating system9database communication9memory management9runtime collection of a''lication data9#eb re=uests9e8changing business data etcP <asis su''orts a number of $no#n o'erating systems (+ni8 flavors9/icrosoft #indo#s server edition9,S%6695(OS9etc) and databases (Oracle9"<H9!nformi89/a8db9/icrosoft SI3 Server9etc)..

As &e kno& !AS"S is a set o% tools+ This tool has the %ollo&ing 'i%%erent %unctionalities34 System monitoring and administration tools Common monitoring tool CC/S(5omputing 5entre 6anagement System ) to monitor alerts of 0(A system from an one 'lace. Server side scri'ting in ,<,1 and Oavascri't. +se of <usiness server 'ages to build online stores and 'ortals. "atabase monitoring and administration utilities 0esource management li$e memory9buffer9etc. ,uthori5ation and 'rofile management tools for user management. !nternet access control to the system and business objects. ransfer modifications in screen9'rogram9layout from the develo'ment to 'roduction system for accuracy 'ur'ose by Transport 6anagement System+ Client server architecture and configuration.

Gra'hical +ser !nterface designing for the 'resentation layer.

SAP !asis consultant7s responsibilities34 S,1 <asis is a middle#are tool for a''lications9 o'erating system and database.S,1 <asis consultant should able to do the follo#ing tas$sN-

S,1 a''lication server monitoring 9 ,<,1 dum' and system log analysis. 1erformance tuning "atabase maintenance 9 "atabase bac$u' schedule and restore 0(A9net#eaver9solution manager installation 9etc.. S,1 license maintenance. S,1 landsca'e 9 trans'ort management system installations9 etc Client creating 9 client co'ying 9 client deletion9 etc Creating user9 assigning roles 9 loc$ing and unloc$ing users9etc <ac$ground jobs scheduling 9 job monitoring 9 job deletion 9 etc 1rofile and o'eration mode maintenance ,''lying su''ort 'atches9 u'grading and installing add-ons S4O E a''lying and removing errors. System co'y9System refresh 9etc his a generic list. here are many other res'onsibility that a <asis consultant shoulders. Everyday you learn something ne#Q

0ead more at htt'N((###.sa'traininghub.com(introduction-to-basis(RvhO5E+/FIGFtBmc*.CC

Anda mungkin juga menyukai