10. Support packages and upgrades
The above activities are major tasks and require more analysis and pre planning before the system (SERVER) starts working for the designated work (Development, Testing, Production).
As part of this the following activities are configureda dn checked
1. SICK(SAP installation Consistency Check). Check the consistency of the system by executing transaction SICK and seed for any errors. This cab done by logging in as SAP* with 000 client and pass word 06071992 (Default). This password can be changed during the installation.
2. SE06: It is used for performing the post installaion activities. SE06 has 2 options:
1. Perform installtion activities (Post installtion activities)
2. DB configuration ( this is used to set the change the trapsport sustem or correctin transport sustem)
SE06 enables the CTS (change transport suystem or correction transport)
3. SE03: click on the system change option in SE06. This option is used for setting the system change option i.e either to modifiable or
notmodifiable. If the system is set to modifiable then the software component s can be modifiable. This option is se set only to
Development and Sand Box systems.
210. If the system is set to not modifiable all the software component are not allowed to change. This options is only set for Quality and Production systems
4. Configuring the Transport management system:
211.
212. SAP system landscape : 213. It defines the flow of objects between the systems. Inorder to achieve the high xonsistency and stability SAP recimmends t use more than one system in the landscape. 214.
215. Single System landscape : In this only one system will be there for the entire landscape which is used for all the purposes(Development, Qualtity and Production) 216. 217. 218. 219. 220. 221. Single System Landscape Quality Production
222.
223.
224.
225. Disadvantages: The objects which are used by developers will not be allowed to eited by the tester and production users. The system is not consistent either for development quality pr production. No production for single system. 226. Ex: It is used to setup demo, desk and training systems. 227. It is a resource minimized setup. 228.
229. Two System landscape : it is the least recommended landscape by SAP where developers and quality activities are performed in one box and production activities are carried out in another box. Production server is consistent but inconsistency between quality and development. 230. 231. 232. 233. 234. 235.
Three System Landscape:
Development
Two System landscape
Productio n
Developme nt and Quality
Three System Landscape
Production Quality
This is the optimized landscape recommened by SAP where development, quality and production actions are carried out in individual systems (or) boxes.
Development System: This system is used to develop the objects and customizing activities are carried out. This system is usedd by functional consuoltants, ABAP development team and BASIS team. No end user and production user can logon to the system.
Quality system: The objects whch are modified (or) customized in DEV system will be tested in this system. This system is utilized by the qulaity team, training team and BASIS consultants.
Production System: The objects which are development modified customized in development boxx (or) system are transported to quality and qullity approved objects are moved to production system. The system is only allowed for end user. The restricted actions can be given to ABAP and functional tools. Each user created in the system are accountable for license.
Note: For each system we can configre upto 8 systems in the landscape. 8 different systems in a typical landscape are:
1. Pre production 2. Pay roll 3. Migration 4. Sand box 5. Development 6. Quality 7. Production 8. Training
Transport domain controller: As part of post installation activity (TDC) transport domain controller needs to be configured on a high availability system. As this is only one system I the landscape we will configure development system as TDC. TDC manages all the systems in the landscape.
Configuring TDC:
1. Logon to 000 client
2. Goto transaction STMS (SAP transport management system)
3. If STMS is not configured within a domain then a pop up box will be displayed to configure the domain. If the STMS is already configured POP UP BOX will be displayed to create another domain (or) oncluding the domain.
4. Specif the name of the domain 5. Specify the description and save 6. Domian controller is created
Defining landscape: As we don’t have quality and production system in the landscape we need to define them as virtual systems.
Defining the virtual system:The systems which are going to be deployed in future can be configured as virtual systems. Virtual systes name should be exactly the same as of the real time systems.
Including the systems in the domain: 1. Delete the virtual system
2. Logon to the real system which is replacing real virtual sstems. (Logon as client 000)
3. Go to transaction “STMS” POP UP BOX will be displayed. Select “include in the domain” specify domain name in the domain sytem 4. A request for inclusion is sent to TDC
5. Logon to the TDC goto STMS selecty systems there will be a system waiting for approval
Note: A communication user TMSADM will be created and RFC destinaltion between the TDC and member system is established.
Domain.cfg is updated
Domain.cfg is stored in \ \usr\sap\trans\bin
It consists of domain settings lie details of TDC and members. It is updated whenever there is achange in the landscape.
Transport Group: The group of systems which share the same transort directory are said to be in one group.
Transport Layer: It is a path defined to transport the objects. SAP transport layer is by default . The name of it is trapsport layer.
Transport Routes: Transport routes define the flow of objects between systems. There are two types of routes. They are
1. Consolidation Route: The route between development and quality systems is called as consolidation system
2. Delivery Routes: It is the route between quality and production systems
Development system is also called as Integration sytem Quality system is also called as Consolidation system Production system is also called as Delivery system
Defining the Transport Groups:
Log in to TDC in client 000 Go to STMS Select transport groups We have the option of defining the routes in 2 ways.
1. Graphical Editor 2. Text Editor
Select the type of the landscape(Single, Two or three sytem landscape) Specify the systems in the landscape sav and activate and distribute the
configuration.
5. RZ10:Import profiles of all active servers onto the database. Goto RZ10 select the profile import in to DB
6. Install License: In order to install the license we need to obtain license key from SAP market place.
7. Inputs required to get the license key are 1. Customer Number 2. Installatio Number 3. Host Name 4. SID 5. Instnace number 6. H/W Key
In order to get the H/W key goto transaction SLICENSE (or) at command level saplicense –get
Get the key from market place and install using slicense transaction. Initial license is valid for 30 days and when license is installed the expiry date DD:MM:YYYY
8. Install Library: Goto SR13 specify the tyoe of HELP (HTML help file, HTML, HTTP< Dynamic Help). The library can be installed on a file server or on a web server. Go to SR13 define language define variant (IWB.Help, Documentation)
Repository Objects: The objects which are shifted by SAP are called as Repository Objects. These are also called as “SAP standard objects”.
9. Client Creation and Copy:
Client: Client is an independent business entity which represents an organization in SAP R/3 system. Client is represented by field MANDT. It is used as a data seperator i.e. the user will be displayed the data belonging to the client logged on.
By default there are three clients 000, 001 and 066
Client 000: It is a template client which consists of all the configurations like company code, cost center, project center, sales, purchase etc. It is continuously updated by applying the support packages, patches etc… It is the most updated client. But it is not allowed for any customizing and it is eligible for client copy to set up our company.
Client 001: It is a backup of 000 client. But it is not updated continuously. There is a variation between 000 and 0001 i.e. 0001 is not updated continuously. No 001 for 7.0 version.
Client 066: It is an early watch alert client used by SAP to generate early watch alert report to the customer.
In client 066 the report serve as recommendation to fine tune the system interms of expensive reports, transactions, SQL statements and users.
Need for client copy: In order to adapt SAP systme to the requirements of the
customer we need to perform customizing. But customizing is not performed in 000 client as it is a template client and client 001 is a back up client. In order to perform customizing we need to define our own client. When the client is defined it doesn’t consists any data, so we need to copy data from the existing clients. Client 000 is eligible for client copy because it is continuously updated.
Client dependant data/ client soecific data: The data which is visible only in that client is called as client specific data. Ex: User master Data, Application data, Customizing Data
1. The Purchase Orders whicha re created in a client are not visible in another client.
2. The users which are created in one client cannot login to another client.
3. The application like invoices, delivery notesa are client specific i.e. if you perform customizing in one client it is not visiblw in another client. Note: The customizing which is performed in one clietn won’t effect the other clietns.
Client independent data/ cros client data: The data which is visible across all the cliet is called as cross client data (or) client independent data.
Ex: Calanders, Measurements, Time Zones, Timings, Currency.
If we perform customizing to the above it will be effective in all the clients. CCC: (Cross Client Customizing): The above one is known as cross client customizing.
Repository Data:All the SAP standard objects are referred as repository objects (reports, Functional Modules, Programs, Transactions) etc…
The changes t repository data will effect the entire R/3 system. Some times it may mall function and the system will be crashed. Because of applying chages, patches etc.
Note: While changing the repository objects follow SAP recommendations and most of “Repository Objects” are locked for editing. If there is a need to modify the repository objects we need to obtain key from SAP.
Customizing: It is the process of keying entries to the templates.
Ex: Company name and address entries, sales organizations, employee datga applications such as material master data, vendor master data, customer master data.
Customizing is performed in “ SPRO” .
User Exits/ Customer Enhancements: These provide an additional functionality to the existing structure (SAP objects). There are variou types of exits.
1. Field Objets 2. Menu Exits 3. Screen Exits
4. Functional module exits
Exits are identified in transaction” SMOD” and exits are created in “CMOD” CMOD: Create modification
SMOD: Search Modification
Applying the Support Packages and Patches: I order to fix the bugs (or) to have the enhance functionality support packages, patches are applied from time to time. SPAM is the tcode for applying the support packages.
Development: These activities are carried out by ABAP development team. In order to develop our own programs SAP restricts to develop n th ename space” Y” and “Z”. The developers who are working in the object needs to be registered I the market place an obtain a developer key.
Programs a dn reports are dedveloped I SE38 Transactions are developed in SE93
Screen are developed in SE51 Menu’s are created in SE41
Forms are created in SE71 Functional Modules in SE37
Repository objects like classes packages are created in SE80 These activities are purely done by the ABAP team.
Changing the SAP Standard objects: In order to modify SAP standard objects we need to obtain object access keys from market place. These are also referred as SSCR.
SSCR: SAP software change registration
In order to modify the repository objects we need to get the following 1. Developer Key
2. SSCR key
Client Creation: Clients are created based on the following requirements as a post installation activity to set up demo, testing, tracing, production, quality clients. (SE06, SE16, SM30, SE03)
Set up a client simulating production client. Client is created in SCC4. In order to create client we need to specify the following inputs.
1. Client number (Variable in between 000 to 999. Bu it should be used from the SAP reserver numbers. It should be unique in the system. 2. Specify the client number
3. Describe the client 4. Currency of the client 5. Location of the client
6. Roll of the client (Demo, Customizing, Testing, Production…) 7. Specify client specific customizing is allowed or not
8. Specify cross client customizing and repository chanes are allowed or not
9. Protection level 0, 1, 2
By default from 000 999 total 1000 clients can be created.
Logical System: In order to distinguish between various clients of different systems logical systems are defined and assigned to clients.
Defining Logical System:
Go to SALE Tcode (SALE: SAP Application linking and Enabling) Click on sending & Receiving system for further information click on logical system click on define logical system logical system click on define the logical system click on new entry.
Specify the name of the logical system. The naming conventions for logical system are <SID>CLNT<CLINTNO>
Ex: DEVCLNT200, QASCLNT200, PRDCLNT200 (Upper Case letters)
Client Role: SAP defines client role to be specify the functionality of the client.
1. SAND BOX: It is a play ground where functional consultants will customize the requirements of the customers. It is represented as “SAND”. The changes which are performed in the system are not carry forwarded. This client is allowed for only client specific customizing.
2. Customizing Client: It is represented by CUST. It is also called as Master Client, Golden Client. This is the only client where client carry forwarded. This is the only client where changes are initiated and carried forward. This is the only client where client specific cross client and repository objects are modified.
Note: Other than this client no clients are allowed to modify objects.
3. Testing Client: It is represented by TEST. This client is used for testing the customization which is performed in cust client. Transactions SCC1 is used to copy the change request from CUST client.
Note: SCC1 is used to copy transport requests between the clients within the system. This client is used to test the modules which are customized and if the consultants approves it will be released.
4. Quality Testing Client: It is represented by QTST. This client is used to test integration between modules cross client object test and repository object test. It is also assured that all the objects are tested for quality stress etc… Testing tools are deployed to test the objects in this client. Note: Each of the objects need an approval to move into production.
5. Training Client: It is represented by TRNG. It is used to train the end users of the company
Note: Changes to ATST and TRNG are made by using transport request 6. Production Client: It is represented by PRD. This is the only client where
the company data is populated by end users and production operations are carried out. Most critical client and to be secured in the landscape. Most critical client sensitive info (financial, pay roll, client) data
migration.pre production client can be created additionally based on customer requirements.
Change options available for clients (Client Specific Settings): Recording: It means saving the changes to a change request.
1. Automatic Recording of Changes: The changes which are performed in this client are automatically recorded to a change request.
2. No Changes allowed: changes are not allowed in this client.
3. Change without Automatic Recording: Changes will not be recorded to change request.
4. Changes without automatic recording, no transport allowed: Changes without automatic recording to change request and changes cannot be transported. Cross-Client Object changes: Changes to repository and cross client customizing allowed: The changes are allowed in CUAT client (or) master client (or) Golden Client.
Protection Level: 0: No Restrictions. Client is allowed for client copy and client comparison is allowed. Client can be overwritten.
Protection Level 1: No overwriting by client copy
Protection Level 2: It is neither allowed for a client copy not for comparison between two clients.
eCATT & CATT allowed:
Restriction: The client should be always protected against upgrade unless we perform an upgrade
Note: When the client is created an entry in table T000 is created without any data. We can logon to the client using USERID: SAP* and Password: pass in that particular client for client copy.
1. Local Client Copy 2. Remote Client Copy 3. Client import and Export Pre Requisites of Client Copy:
1. Users should be working in the source client, reserve at least 2 background processes for client copy. Dialog process can also be used.
2. Logical system name should be defined and assigned to a client
3. There should be enough space in the DB (Table Space and enough disk space)
4. RFC connection should be defined between two clients to perform “Remote Client Copy”
5. Enough space should be there in “Trans Directory” to perform client transport 6. The sized of the client can be determined by using report “RSSPACECHECK” 7. Select the profile determine the type of the data to be copied from source
client to target client.
8. Ensure that source and target clients are of in same versions in terms of O/S, DB, R/3.
Note: BD48: Changing the logical system name
Note: Size of the table can be determined using the reports RSTABLESIZE and RSSPACECHECK. These reports can be executed in SA38 T-Code
Local Client Copy:
Go to SCCL (SCCL is the tcode used for local client copy)
Before client copy we have to create the client. This can be done using the table SCC4.
Go to SCC4 from which we can create an entry in the table “T000” (List if clients present in the system). Make entry for the client number, description, logical
system name, application server… and click on save. This will create the client entry i.e. client without any data in it.
Now Logon to the “Target Client” go to SCCL select the profile
Profile: It defined the type of data to be copied from the source client. We should use SAP defined profiles that starts with “SAP”. (Ex: SAP_APPL)
Note: repository objects will not be copied during the client copy (Local or remote) Select the source client from which the copy has to be performed.
By selecting the “Test Run” we can perform a resource check. Simulation reads the extra data andif there are any problems with DB like space, and then simulation terminated the copy.
Go to SCC3 for detailed log of the client copy.
Remote Client Copy:
It is performed in transaction scc9.
Select the profilego to profile select the source destination Repository objects can be copied
Client specific data is copied
RFC connections are defined in SM59. specify the system name
Specify the host name
Schedule it in the Background mode (or) dialog mode Perform a test run for simulation
Then select RFC