This action might not be possible to undo. Are you sure you want to continue?
SAP BC for beginners
Tweet Posted by Steve SOUMAH in SAP BC for beginners on Jul 15, 2012 10:28:03 PM
1.1 Client overview
Filter Blog By date: • A client is a self-contained unit in commercial, organizational, and technical terms, with its own user master data and set of table key ranges. • Data from different clients is kept separate at the kernel level. SQL statements executed by an application use the client number in the where-clause. Although a table may contain data from several different clients, the where-clause limits access to particular clients. • Examples of client-specific data include: User master data – such as parameters, authorization, user groups Customizing data – such as organizational units, assignments, and document types Application data – such as business transaction data, and material master data • The SAP client concept can integrate several companies or subsidiaries in a single client – by using company codes and the SAP authorization concept. • Company codes define the smallest corporate organizational units for which a complete self-contained set of accounts can be drawn up for external reporting. • The SAP authorization concept enables the parent company to access all subsidiaries for report purposes, while subsidiary-specific data is protected against access from other subsidiaries through company code definition. Recent Posts Client copy Start and stop an SAP Central instance : WINDOWS / SQLSERVER part I Start and stop an SAP Central instance : WINDOWS / SQLSERVER part II Start and stop an SAP Central instance : WINDOWS / SQLSERVER part III Start and stop an SAP Central instance : UNIX / ORACLE By tag: July 2012 June 2012 May 2012
bc beginner beginners client copy sap
• Data of a SAP System can be divided into two categories: ◦ Client-specific data is data affecting only one client, such as user master and application data. ◦ Cross-client data is data affecting the whole system environment, such as cross-client Customizing data and all Repository objects. • The ABAP Dictionary is a data dictionary that is part of the ABAP Repository: ◦ Each piece of ABAP Dictionary information is entered only once and is then available anywhere in the system at any time. The ABAP Dictionary automatically supplies all new or changed information, thus providing current runtime objects and ensuring data consistency and security. ◦ The SAP runtime environment consists of all ABAP programs required during execution. The ABAP
Generated with www.html-to-pdf.net
Page 1 / 4
1. • The difference beetween the remote client copy and the client export / import lies in the way the data is transfered : ◦ In remote client copies the data is transfered immediately across the network using RFCs. ◦ This combination of early binding and late binding ensures that the active integration of ABAP Dictionary information does not affect system-wide performance. 1. • The objects from the ABAP dictionnary like ABAP reports. • Suspend background jobs : This can be done using report BTCTRNS1.you can exclude tables from the client copy using report RSCCEXPT. ◦ Client export / import also to perform client copies beetween different SAP instances. cross client customizing.2 Local client copy Local client copy is performed using Tcode sccl. All performance-critical information is stored in the runtime objects and is always kept up-to-date. Runtime objects. such as programs and screens. Generated with www. These objects can only be transported through transport requests accross the instances.interpreters in the runtime environment do not use the original of an ABAP program. the data dictionnaries beetween the source and target systems should be the same.1 Client copy pre requisites The client copy should be performed on a low system activity timeframe. are automatically regenerated (late binding) when a time stamp comparison between the object and the ABAP Dictionary detects a difference.2. 1. the data is exported in files to the transport directory.2 Client Copy • SAP delivers 3 client copy methods : ◦ Local client copy in order to perform client copies inside a given instance. ◦ Using client export/import. • For remote client copies.html-to-pdf. application data and client dependant customizing. • Client copy tools let you copy the following data types : users data. Rather. they use a copy generated once only during runtime (early binding). in case of client copy beetween a production and development system . You have to be sure that your target client will still be usable and consistent compared to your needs depending on the table excluded. Therefore. table definitions and so on . are not handled by the client copy tools. If not. To have a consistent client copy you should not have any activity on the source system.net Page 2 / 4 . ◦ Remote client copy in order to copy client beetween different SAP instances. The import is done in a second time. it is recommended to : • Disconnect and lock dialog users.2. The jobs will be released afterwards using report BTCTRNS2.
◦ Log on to the target system ◦ Create an entry for your new target client using scc4 ◦ Log on to this new target client with user SAP* and default password pass. • The client import during which data is imported in the target client.net Page 3 / 4 . You must have enough space in the /usr/sap/trans file system to perform the client export. ◦ Schedule the client copy in background ◦ The client copy logs are available in scc3.The client copy logs are available using tcode scc3. the client copy will be canceled. An RFC must have been declared in sm59 to access the source client. ◦ Start the client copy using transaction sccl. ◦ Select the source client ( select the right rfc destination ) and the copy profile. Still. The network must have good performances in order for the client copy to be as fast as possible.4 Client Export / import The copy is performed in 2 steps : • The client export during which the source client is exported to files in /usr/sap/trans/date | cofiles. You have to make sure that this will not have any impact on the target client usability. Local client copy steps : 1. If these are not identical. Remote client copy steps : ◦ Log on to the target system ◦ Create an entry for your new target client using scc4 ◦ Log on to this new target client with user SAP* and default password pass. ◦ Start the remote client copy tcode : scc9. it is possible to exclude the tables that are not the same using RSCCEXPT.2. ◦ Schedule the client copy in bacground ◦ The client copy logs are available in scc3.3 Remote client copy This method uses RFCs.html-to-pdf. 1. But this must be done carefully as it can have a negative impact on the data consistency in the target client. NOTE :The first step is the dictionnary comparison beetween the source and target system. Client import/ : • 1st step : export Generated with www.2. ◦ Select the source client and the copy profile.
◦ Log on to the target system ◦ Create an entry for your new target client using scc4 ◦ Log on to the source system / source client.release_jive_sbs_5_0_1_1 Follow SCN Generated with www. Request <S-SID>KT<number> will hold the client dependant data.1. revision: 201110261520.0. • 3rd step : post import phase: ◦ Once the import is done. ◦ Start the stms transaction ◦ Display the target system’s import queue. ◦ The import logs can be seen in stms. request <S-SID>KX<number> (client dependant).2c99f0c. request <S-SID>KT<number> (client dependant). 1038 Views Tags: sap. ◦ Select the transport requests generated by the client export and import theses transport requests on the target client. start the scc7 Tcode to perform the post client import actions. client.html-to-pdf. ◦ The transport requests will be imported in the following sequence : request <S-SID>KO<number> (client independant). Request <S-SID>KX<number> will also hold some client dependant data. ◦ The system automatically detects these are client export transport requests and automatically performs the import of the 3 requests. ◦ Start Tcode scc8 ◦ Select the target system and export profile ◦ Schedule the export in background ◦ The transport request containing the client export are then shown ◦ Depending on the choosen export profil there can be up to 3 transport requests created : Request <S-SID>KO<number> will hold the cross client data. ◦ The log will be available in scc3. • 2nd Step : import ◦ Log on to the newly created target client using SAP* and password pass.net Page 4 / 4 . bc.1 . beginners Tweet Comments 3 Comments Jive Software Version: 5. copy. ◦ Schedule the post import job.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.