Day 3 - Client Administration

Embed Size (px)

Citation preview

  • 8/19/2019 Day 3 - Client Administration

    1/32

     

    Client AdministrationClient Administration

  • 8/19/2019 Day 3 - Client Administration

    2/32

     

    Overview of Client

    A client is an independent business unit within an R/3 system

    It is the organizational and legal entity in the SAP system.

    SAP R/3

    SAP R/3

    100

    100 200

    200 300

    300

    Usr-1

    Usr-1 Usr-2

    Usr-2 Usr-3

    Usr-3 Usr-1

    Usr-1 Usr-2

    Usr-2 Usr-3

    Usr-3 Usr-1

    Usr-1 Usr-2

    Usr-2 Usr-3

    Usr-3

    c

    l

    i

    e

    n

    t

    u

    s

    e

    r

    In a physical SAP system there can be multiple clients in each ofthe system of SAP system landscape.

    A client has its own set user data. 

  • 8/19/2019 Day 3 - Client Administration

    3/32

     

    Overview of Client

     The main objective of the client is to eep the data isolatedAll the business management data is protected here because other clients can notaccess them. The data in a client can be only visible within that client; it can not

    be displayed or changed from another client. 

    !ata in the R/3 are classi"ed as #lient$dependent % #lient$independent.When the SAP obects are ust used by only one client! those are defined as client

    dependant data. "or e.g. #sers! $ustomizing etc. There are some obects asA%AP&' programs! which are used by all the clients in a SAP system. Thoseobects are called client independent data.

    To (now whether a table is client dependant or independent you can search for afield MANDT. The client dependant tables always include the client field )*A+,T-as a part of the primary (ey.

    A three di&it number identi"es a client."rom a technical viewpoint! this number is used as a (ey within tables thatcontain application data.

    SAP comes with some pre$con"&ured clients.With a standard installation! SAP delivers 000! 001 and 066 clients which shouldnot be changed&deleted from the system.

    $lient 000 is considered to be a SAP reference client and contains the clientindependent data of /&0. Special admin tas(s are performed here as user SAP1 or,,I$.

    $lient 001 is a copy of client 222 with the difference being that the data is client

    dependent. ,o not change any settings here. It should remain standard.

  • 8/19/2019 Day 3 - Client Administration

    4/32

     

    Overview of Client

    After a new installation both 222 and 223 clients are identical! but after anupgrade 222 will have additional customizing data. 4ot of customer sites does notuse 223 client at all.

    $lient 066 is there for SAP 5arly Watch service. This client enables SAP to

    remotely access the customer system. SAP provides this service to the customerto improve the system performance. $lient 266 should not be changed or deletedfrom the system.

    Apart from these 0 preconfigured clients! there could be some more clients fromSAP depending upon the Addon installed. "or e.g. if IS7I4 is being installed! all

    the IS7I4 related activities are done through client 065.

  • 8/19/2019 Day 3 - Client Administration

    5/32

     

    Overview of Client

    #ustomer$!e"ned #lients,uring a SAP System implementation! many different clients might be re8uired tofulfill different roles in the implementation procedure! depending upon the selected

    landscape .

    Client Name escri!tion

    200 CUST Customizing/Development

    210 SAND Sando!

    220 T"ST Customizing/Development Testing

    #00 $TST $ualit% Assu&ance Testing

    #10 T'N( "nd)use& T&aining

    *00 +',D +&oduction

    *10 ++'D +&e)+&oduction

  • 8/19/2019 Day 3 - Client Administration

    6/32

     

    Overview of Client

    #lient '(() #ustomi*in&/!evelopment +#,ST-All application customizing 9 system development are performed in this client.

    The system configuration of this client can be transported to T5ST! :TST! T/+!PP/, 9 P/7, clients

    This client is the source of most of the clients in the development! 8ualityassurance! and production environments.

    #lient '() Sandbo +SA0!-This is a general test client! initially created as a copy of the 223 or 222.

    It is refreshed periodically with a copy of the customizing&development testingclient

  • 8/19/2019 Day 3 - Client Administration

    7/32

     

    Overview of Client

    #lient 3(() 2uality Assurance Testin& +2TST-$opies of customizing changes are moved here for system testing. The testinghere is usually performed by a different team.

    The 8uality assurance team chec(s customizing! development! and SAP patches.

    This second level of testing ensures that everything has been successfullytransported.

    #lient 3() 1nd$user Trainin& +TR0-5ndusers are trained on the /&0 functionality in this client.

    7nce changes have been tested and signedoff in the 8uality assurance testingclient

  • 8/19/2019 Day 3 - Client Administration

    8/32

     

    Overview of Client

    @"rom the SAP /&0 version 0.2 onward! transaction code SCC4 can be used tomaintain T222 table.

    @Also you can choose Administration Client admin Client Maintenance from the initial screen to do the same.

     To create a client you have to maintain T((( table.

  • 8/19/2019 Day 3 - Client Administration

    9/32

     

    Client creation

    When the New Entry B button is pressed! the following screen comesC

     The st step to create a client is to de"ne it % mae it available inthe R/3.

  • 8/19/2019 Day 3 - Client Administration

    10/32

     

    Client creation

    The client nume&client nume&- namename 9 Cit%Cit% are entered first.

    Then .ogical s%stem.ogical s%stem is defined. SAP uses logical system concept in A45t entry standa&d cu&&enc%standa&d cu&&enc% can be defined according to the country.

    To enter a &ole o a client&ole o a client you must (now the obective of that client beforehand."or e>ample if this client will be used as a customizing client then customizingentry should be used from the options.

    In the ne>t field Canges and t&anspo&ts o& client)speciic oectsCanges and t&anspo&ts o& client)speciic oects! there arefour optionsC

    @If you want to use this client as a sandbo> client and you do not want to recordor create a change re8uest every time a change happens to the client then Changes W/O automatic recordingChanges W/O automatic recordingB is the right option.

    @If all the changes to the client should be recorded in a change re8uest then  Automatic recording of changes Automatic recording of changesB is the right option. Dou must choose this optionfor your master configuration client.

    Contd 33

    In the #lient creation screen all the re6uired items must be "lled.

  • 8/19/2019 Day 3 - Client Administration

    11/32

     

    Client creation

    @If No changes allowed No changes allowed B is chosen! then no changes will be allowed to this client.Dou must chose his option for clients in the production environment to protectyour system.

    @No transport No transport B option is used when you do not want any user to create atransport from this client.

    The Client)independent oect cangesClient)independent oect canges category determines if the clientindependent data maintenance is allowed in this new client. To choose the rightoption from this category! you must (now the definition of $lint independentcustomizing obects and repository obects. The e>amples of SAP repositoryobects are data dictionary obects! module pools and screens. $lient independent

    obects apply to all the clients. The factory calendar is an e>ample of clientindependent obect of customizing. The dropdown list contains following 'optionsC

    Changes to Repository and cross-client customizing allowed Changes to Repository and cross-client customizing allowed 

     No changes to cross-client customizing objectsNo changes to cross-client customizing objects

    No changes to Repository objectsNo changes to Repository objects

    No changes to Repository and cross-client customizing objectsNo changes to Repository and cross-client customizing objects The ne>t is +&otection4 Client copie& and compa&ison tool+&otection4 Client copie& and compa&ison tool. If this option ischosen! a client copy can not overwrite the newly created client. Dou should chosethis option for a mastercustomizing client or for an important client asproduction. The ' options areC rotection le!el "# No restrictionrotection le!el "# No restriction ! rotection le!elrotection le!el

    $# No o!erwriting$# No o!erwriting 9 rotection le!el %# No o!erwriting& no e'ternal a!ailability rotection le!el %# No o!erwriting& no e'ternal a!ailability 

    Contd 33

  • 8/19/2019 Day 3 - Client Administration

    12/32

     

    Client creation

    The access to the client can be further restricted by the following $hec( %o>esunder 'est&ictions'est&ictions.

     Allows CA(( processes to be started# Allows CA(( processes to be started# $ATT

  • 8/19/2019 Day 3 - Client Administration

    13/32

     

    Client Co!"

    $lient $opy is the mandatory first postinstallation steps for filling up the data innewly created $lients. Some imp notes before scheduling a client copyC

    "or the stability of the system! always schedule the client copy in the

    nighttime when the users are not wor(ing in the system.

    To avoid data inconsistency the users should not (eep on wor(ing in thesource or target clients when the client copy is going on.

    "or the best performance! always schedule the client copy in the

    bac(ground. 

    The value of ma>imum online runtime parameter ma>EwpErunEtimeB inthe instance profile might need to be increased for a large client copy.

    Proper authorizations is re8uired to run the client copy. As a basis systemadministrator you should have SAPEA44 profile to complete a client copysuccessfully. So SAP1 is recommended as it has all the authorizations neededby the client copy.

    Always chec( the Tablespace usage F in database portion before 9 aftere>ecuting a client copy and also at the time of $lient $opy process. 

    The main memory plays a significant role in the client copy. *a(e sure thatyou have enough memory to finish the client copy without any problem.

    If the client copy is loc(ed by another client copy run! then chec( the logbefore deleting the loc( entry in S*3? to remove the loc(.

  • 8/19/2019 Day 3 - Client Administration

    14/32

     

    Client Co!"

     The #lient #opy can be done in 3 ways

    1. Local Client Copy: Gere the data is copied into new $lient from a clientwithin the same system.

    2. emote Client Copy: In /emote copy the data is copied into the new clientfrom a /emote system.

    !. Client Transport: ,ata can also be filled into the newly created client! fromanother system by way of (ransport Re+uest .

     To do a #lient #opy into the new client7 "rst lo&in into the new

    client as user SAP8 with password PASS.

    "or the 4ocal copy follow the pathC

    Tools Administration Administration Client Administration ClientCopy Local Copy 

    Alternatively! you can also use the Transaction $ode SCCL for 4ocal $lient $opy.

    9ocal #lient #opy

  • 8/19/2019 Day 3 - Client Administration

    15/32

     

    Client Co!"

    1

    2

    #

    *

    1313 SelectedSelected

    +&oile+&oile

    5

  • 8/19/2019 Day 3 - Client Administration

    16/32

     

    Client Co!"These are data profiles that /&0 provides for copying clients. These basicallyindicate what (ind of data from the source you want to copy into the new client.The scope of the profile can be seen from the *enu path "ro#ile $isplay 

  • 8/19/2019 Day 3 - Client Administration

    17/32

     

    Client Co!"

    2323 Sou&ce Client4Sou&ce Client4 Specify the Source client from where the ,ata will be copied.

    #3#3 Sou&ce Client use& maste&s4Sou&ce Client use& maste&s4 you can define the client from which you wantto copy the user master records. The Source $lient #ser *asterB does not

    have to be same as source client. 

    *3*3 Test 'un4Test 'un4 %y selecting this flag! you can get the information about thestorage re8uirements or a complete table statistics. SAP recommend you torun the client copy using the test runB mode first. In test run phase!database updates are not performed.

    5353 Scedule as acg&ound o4Scedule as acg&ound o4 The client copy should be scheduled in the

    bac(ground after all the parameters are selected as shown in the last figure.Dou can run a client copy online! if you are ust copying the user masterrecords.

    When SAPEA44 profileis chosen for client

    copy! thisinformation & warningpopup screen comeswhich can be ignored.

    When SAPEA44 profileis chosen for clientcopy! thisinformation & warningpopup screen comeswhich can be ignored.

  • 8/19/2019 Day 3 - Client Administration

    18/32

     

    Client Co!"

    Select the %ac(groundServer from the list.

    +ormally it is thesame system wherethe client copy isbeing performed.

    Select the %ac(groundServer from the list.+ormally it is thesame system wherethe client copy isbeing performed.

    Sc%ed&le 'o( buttonis pressed

    Sc%ed&le 'o( buttonis pressed

    If all the info iscorrect press

    Contin&e

    If all the info iscorrect press

    Contin&e

  • 8/19/2019 Day 3 - Client Administration

    19/32

  • 8/19/2019 Day 3 - Client Administration

    20/32

     

    Client Co!"

    Specify an eistin& 5utput device

    Select the Printer from listSelect the Printer from list

    $lic( for $ontinue$lic( for $ontinue

  • 8/19/2019 Day 3 - Client Administration

    21/32

     

    Client Co!"

    #hec the #lient #opy 9o&

    Press for$ontinuePress for$ontinue

    If the $lient

    $opy is startedsuccessfullychec( theprogress by$lient $opy4og. The pathis (ools  

     Administration  Administration Client Administration Copy ,ogs or by the Tr.code SCC!.

    If the $lient

    $opy is startedsuccessfullychec( theprogress by$lient $opy4og. The pathis (ools  

     Administration  Administration Client Administration Copy ,ogs or by the Tr.code SCC!.

  • 8/19/2019 Day 3 - Client Administration

    22/32

     

    Client Co!"Re$startin& the #lient #opy

    If the client copy fails for some reason then you can restart the client copy in therestart mode after the fi>ing the problems. In this case the client copy will start

    e>actly from the same point where it failed.

    To do a /emote client copy! /"$ connection must be established between thetarget system and the source system. /"$ is 'emote 7unction Call3

    It is a SAP interface protocol that simplifies the programming of communicationprocesses between systems and manages the communication process! parameter

    transfer. The path for creating a new /"$ connection follow the pathC ToolsNetwor) *C $estinations or by the transaction code SM+,.

    Remote #lient #opy

    3. Select&5>pand3. Select&5>pand

    ?. Press tocreate

    ?. Press tocreate

  • 8/19/2019 Day 3 - Client Administration

    23/32

     

    Client Co!"

    3. 5nter the RC.estination

    ?. Connectiontype shouldbe # for /&0

    0. 5nter.escription

    9 thendoubleclic(to enter(arget ost0 9 )ys No

    '. ive 4ogon,anguage&Client& *ser&assword 

    H. Save the dataafter givingateway host

    6. Test the newconnection

  • 8/19/2019 Day 3 - Client Administration

    24/32

  • 8/19/2019 Day 3 - Client Administration

    25/32

     

    Client Co!"

    1313 SelectedSelected

    +&oile+&oile

    2323 Sou&ce destination4Sou&ce destination4 Gere enter the source /"$ destination name which iscreated earlier.

    *3*3 Test 'un4Test 'un4 %y selecting this flag! you can get the information about thestorage re8uirements or a complete table statistics. In test run phase!database updates are not performed.

    5353 Scedule as acg&ound o4Scedule as acg&ound o4 The client copy should be scheduled in thebac(ground after all the parameters are selected as shown in the last figure.

    #3#3 '7C s%stem cec4'7C s%stem cec4 This is to chec( the entered /"$ destination is properlyfunctioning or not.

    After performing all above mentioned tas(s! see the copy progress by the

    transaction SCC!.

  • 8/19/2019 Day 3 - Client Administration

    26/32

     

    Client Co!"#lient Transport

    Also (nown as $lient 5>port&Import.

    $lient $opy by Transport /e8uest is used when you have a client already createdand you want to bring two clients at par with each other.

    $lient 5>port & Import is another method of ma(ing a new client where in thereis no remote access between the two clients

     The followin& are the steps in the whole procedure) 

    7i&st te data &om te client in te sou&ce s%stem is e!po&ted &om tedataase to a t&anspo&t ile on a&d dis3 7o& tis %ou need to no8

    e!actl% 8at %ou 8ant to t&anspo&t and %ou use SA+ delive&ed p&oilesacco&dingl%3

    7i&st te data &om te client in te sou&ce s%stem is e!po&ted &om te

    dataase to a t&anspo&t ile on a&d dis3 7o& tis %ou need to no8e!actl% 8at %ou 8ant to t&anspo&t and %ou use SA+ delive&ed p&oiles

    acco&dingl%3

    te SA+ delive&ed T+ command is used o& te impo&t to te ta&get

    s%stem client dataase3

    te SA+ delive&ed T+ command is used o& te impo&t to te ta&get

    s%stem client dataase3

    Te post p&ocessing p&ocedu&e is &un te ta&get client to successull%complete te client impo&t3

    Te post p&ocessing p&ocedu&e is &un te ta&get client to successull%complete te client impo&t3 

  • 8/19/2019 Day 3 - Client Administration

    27/32

     

    Client Co!"

    To transport clients from one system to another! follow the pathC

    Tools Administration Administration Client admin Clienttransport Client e-port or by transaction SCC.

    3. )elect the predefined profile as per there+uirements

    ?. )elect the predefined

     profile

    0. 1'ecute in2ac3ground 

    The $lient 5>port progress can be viewed through SCC#.

  • 8/19/2019 Day 3 - Client Administration

    28/32

     

    Client Co!"

    0 Transports are created in &usr&sap&trans&cofiles. Those areC@9sid:;,9no: for the clientindependent data ample',000013 D"ample'=000013D"

  • 8/19/2019 Day 3 - Client Administration

    29/32

     

    Client Co!"

    "rom the 7S level! go to /us&/sap/t&ans/in directory. The se8uence ofimporting the client re8uests is $lient Independent ! $lient ,ependent and then

    $lient Te>ts.

    Performin& #lient Import

    :Client independent settings import

    tp addtoue& S>D;,nnnnn 9S>D: e.g. tp addtobuffer ,5J722223 :AS

    tp impo&t S>D;,nnnnn 9S>D: u? e.g. tp import ,5J722223 :AS uK

    :Client dependent setting import

    tp addtoue& S>D;Tnnnnn 9S>D: e.g. tp addtobuffer ,5JT22223 :AS

    tp impo&t S>D;Tnnnnn 9S>D: client@=== u? e.g. tp import,5JT22223 :AS clientL322 uK

    :Client Texts import

    tp addtoue& S>D;=nnnnn 9S>D: e.g. tp addtobuffer ,5JM22223 :AS

    tp impo&t S>D;=nnnnn 9S>D: client@=== u? e.g. tp import,5JM22223 :AS clientL322 uK

    Gere SI, is SI, of the server from which the client e>port was ta(en. NSI,O isthe SI, of the server where the client import has to ta(e place. uK is theunconditional mode option. MMM is the 0 digit client number where you intent tocopy.

  • 8/19/2019 Day 3 - Client Administration

    30/32

     

    Client Co!"

    In order to adapt the runtime environment to the current state of the data! thepost processing is done throughC

    Tools Administration Administration Client admin Clienttransport client import  or transaction SCC/ .

    Gere the transport from the last tp import is proposed. Please chec( the transportnumber and if every thing is according to the order then press enter and that willta(e care of the post processing activities. 

    Performin& Post Processin& job after #lient Import

  • 8/19/2019 Day 3 - Client Administration

    31/32

     

    eletin# a Client

    @"irst log on to the client to be deleted with the proper authorization to delete aclient.

    @$hoose path Tools Administration Client admin Special #&nctions$elete client  or transaction SCC+  

    !elete a #lient from SAP system

    After the client deletion process starts you can use SCC! log entries to chec( theclient deletion process. 

    When the clients are to bedeleted permanently!select this option.

    $lient deletion process canbe done online or in

    bac(ground.

    If you want to run a client delete process to findout information about all the tables that willbe deleted then it is the right option to use.

  • 8/19/2019 Day 3 - Client Administration

    32/32

     

    eletin# a Client

    In all the SAP releases so far you can use /0trans to delete a client. We have seensignificant timesaving in this way of deleting a client.

    The steps are as followsC

    3. 4og on to the system as an admin.

    ?. o to the /us&/sap/t&ans/in directory.

    0. use a standard editor and create a control filetC

    client&emove

    client @ === e.g. client L QQQR

    select

    '. then run the command at the command promptC

    '#t&ans )8 delcli3log )u 1 delcli3ctl 

    Gere delcli.logB is the name of the log file 9 delcli.ctlB is the name ofthe created control file .

    !elete a #lient usin& R3trans