Programs, Transactions,
THREE SYSTEM LANDSCAPE
Multi System Landscape:
OFF SHORE INDIA
US
EUROPE In a multi system landscape the development (object) is performed at off sore (Common Development Environment) and the objects are transported
DEV QAS DEV
PRD QAS DEV PRD QAS PRD DEV QAS
onto different landscapes. Geographically the objects are customized locally according to local customize settings (Measurements, Time Tax etc…)
Other Systems in Landscape: Apart from the three system landscape SAP also allows to include the following systems in the landscape.
1. Testing 2. Sand Box 3. Training
4. Pre Production System 5 Pay Roll or Migration system
Note: SAP allows 8 systems in the landscape for a single installation number.
Applying License : Each system needs to be applied license so that
runtime issues are resolved by SAP.
Go to Transaction slicense
The license key depends upon Hardware key o f the machine and installation number.
In earlier versions where this T-Code is not available use command “suplicnese-get” to get the hardware key.
Note: Hardware varies depending upon the O/S. Ex: 32-Bit, 6t4-Bit O/S and SAP component
Go to market place with authorization to generate license keys and click on the tab license keys Click on the option request license key select the installation number provide the following details:
1. System ID 2. Host Name
3. INR (Instance Number) 4. OS
6. Data Base
Now SAVE the information to generate the license key.
Normally license generation will take around 1 hour. The license key can be downloaded from the same screen. Alternatively SAP also sends over the E- mail.
The license key is a number of 24 digits but now SAP is sending the license by encrypting in the text format.
License can be installed in Two Types:
Click on Install New License Specify the Instance Number System Number and Key
Click on New License and specify the path of the text file.
User Master Data Application Data Company
When the system is installed it can be accessed with 000, 001 and 066 clients.
Client: A client is an individual business entity or a company having its own User Master data, Application Data and Customizing Data.
Client is represented by a Field MANDT in the database.
The tables with fields MANDT are called as Client specific tables. 400 300 200 EWA 066 001 000
Cross Client
Customizing
Standard Objects or
400 200 EWA 066 001 000Cross Client
Customizing
Standard Objects or
500 EWA 066 001 000Cross Client
Customizing
Standard Objects or
Client field MNADT is a data separator i.e. the user’s needs to specify the client number to logon to the client specific data.
000 Client: It is a default client or template client which is provided by SAP. No changes are allowed in this client. As this client is SAP client it is
commonly updated by applying Support Packages, Patches, Add-on’s and languages etc…..
It is used to setup Transport Management System (TMS) and run Standard Jobs. No customizing data, Application Data and User Master Data (Except for the Super Users) is allowed.
001 Client: It is a backup client for 000 client as per initial plans of SAP. But 000 is continuously updated where as 001 is not. So the purpose is deviated in the current versions like SOLMON, NETWEAVER systems. 001 is considered as production client.
066 Client: Early watch client. It is used by SAP to logon remotely and generate Early Watch Alerts. As per “SLA” (Service Level Agreement) SAP sends two early watch reports per annum.
Client Creation: As the standard clients provided by SAP are not used for production use we need to create our own clients and define client roles Clients are displayed, created and modified in the transaction SCC4. Go to SCC4 Click on New Entries Specify the Client Number Add description Save.
Client Number: it is a3 digit ID which varies from 000 to 999 which means all together we can create 1000 client s in SAP.
Client is represented by Field MANDT in the database.
Note: The clients are available in the table “T000”. This is the only Cross Client Table with the MANDT field.
Click on New Entries and specify the name of the clients, specify the client numbers specify the name of the city.
This is used to differentiate between clients in the landscape. Logical systems are created in transaction SALE.
SALE: System application linking and Enabling.
SALE is used to define the logical systems that are used for communicating or transferring data.
Systems are using naming convention.
Ex: DEVCLNT555, QASCLNT555, PRDCLNT555
Note: Do not try to change the logical system name. Once it is assigned to a client. In order to change logical system i.e. assigned to a client use
transaction BDLS.
This BDLS transaction is generally used after performing a SYSTEM COPY from production system.
QASCLNT000 Client Copy PRDCLNT000
PRDCLNT000 to QASCLNT000 (We need to change)
Go to SAVE Go to BASIC settings Select logical system Define logical system Click on New Entry Specify logical system name (QASCLNT000) Click on SAVE 500 EWA 066 001 000
Cross Client
Customizing
Standard Objects or
500 EWA 066 001 000Cross Client
Customizing
Standard Objects or
It will prompt you to create a change request Specify the logical system name Select the logical system name Select the currency Specify the client Role
Client Role: It specifies the role of the client in the landscape. There are various client roles defining the implementation.
Development System: In the system landscape development system the first client i.e. going to be created as Master Client, Parent Client, Golden Client. It is represented by CUST i.e. customizing role.
This is only the client in the landscape where changes are made. The changes in the landscape will be carry forwarded to other clients in the landscape. No changes are allowed in other clients.
Changes and Transport for Client Specific Objects: 1. Changes without automatic recording
2. Automatic Recording of Changes 3. No changes allowed
4. Changes without Automatic Recording, No transports allowed Cross Client Object Changes:
1. Changes to repository and cross client customizing allowed. 2. No changes to cross client customizing objects
3. NO changes to repository objects
4. No changes to repository and cross client customizing Protection Client Copier Tool and Comparison Tool: Protection Level 0: No restriction
Protection Level 1: NO over writing
Protection Level 2: No over writing and No external availability CATT and eCATT restrictions:
eCATT and CATT allowed
eCATT and CATT allowed only for trusted RFC
eCATT allowed but FUN/ABAP and CATT not allowed
eCATT allowed but FUN/ABAP and CATT only for trusted RFC. Restrictions:
Locked due to client copy
Protection against SAP upgrade Cross Client Customizing:
Changes to Repository and Cross Client customizing allowed: In this
particular client the changes made to cross client and repository objects is allowed
Changes only to repository Objects: Repository objects only can be modified. DEV:
Client C.S CCC & REP Protection
CUST ARC YES 0
TEST CWR NO 1
SAND CWRT NO 1
QAS:
Client C.S CCC & REP Protection
CUST NO NO 2
TEST NO NO 2
SAND NO NO 2
PRD:
Client CS CCC & REP Protection
CS Client Specific
CCC Cross Client Customizing REP Repository Objects
Protection Protection Level Protection Level:
Level-0: No restriction i.e. no restriction. This client is allowed for over writing and available for client copy
Level-1: No overwriting i.e. the client is not allowed to be over written by other client
Level-2: This option is provided to not to allow client copy and client comparison
Note: Based on requirements we may need to change this protection level and cross client object changes even in the production system.
Note: Don’t try to change these options of preproduction and production without approval. Changes to these tables are logged with Data and Time along with User Name.
Ensure that necessary approvals are obtained from the customer to change the client settings.
eCATT and CATT not allowed: It is used to upload the data into the system. We need to specify whether they are allowed or not. Depending upon the requirement we may allow or disallow all the clients. But in production client it should be set to not allowed.
Test Client: It is used to test the scenarios that are configures in CUST client. Changes are moved from CUST to TEST using transaction SCC1. SAND CLIENT: It is used to configure the scenarios based on customer requirement. It will serve as a play ground environment. For the consultants no changes are carry forwarded.
QTST Client: This client issued for integration testing and consolidation testing. Changes that re made in CUST client are transported to QTST client. (Tools like mercury, ecatt are used to test the integration between modules along with stress and load testing).
TRNG Client: It is used to training end users before they work on the production system.
MIGE and Prep (pay roll): These are optional clients that are created based on requirement. Migration client is used to migrate the data from legacy system. Preproduction client is used to check the behavior of changes before they work.
Payroll Client: As we can’t run the pay roll on the production system (Test Payroll n-number of times) payroll client is created and it is run at various frequencies.
Prod Client: It is used by the end user to perform the business. It is more critical client and no other system in the landscape is allowed to carry the business.
Pre Requisites of Client Copy: 1. Switch off active log files.
2. There should be enough space in the database. For this execute
RSSPACECHECK and RS1TABLESIZE to identify the space and memory requirement.
3. Choose 000 client for initial client copies. However business clients are also allowed for client copy based on protection level.
4. To perform client copy always login into Target Client and copy the data from Source Client.
5. Client copy consumes time, so schedule in the background
6. Choose Profile to specify the data to be copied from source client (Application Data, User master Data, Customizing)
Ex: SAP_ALL, SAP_USER, SAP_CUST, SAP_APPL
7. Define RFC destination between two systems to perform Remote Client Copy
8. Check the space in TRANS directory to perform client export. 9. Perform a TEST RUN before actual client copy
10. Client copy logs are displayed in Transaction SM37/ SCC3.
11. It is not recommended to login to source client and modify the objects during the client copy.
12. During client copy the number of tables does not increase. Only the entries in the table increases under the entry “MANDT”.
13. Remote client copy has to be performed between same systems (Same Version, Same Patch Levels) not possible for different R/3 system.
If DB tables having field MANDT then these are specific to client.
If there is no MANDT field in the tables these are shared tables for all clients. Desc SAPDEV.usr02 (Describe DB tables)
Select MANDT , Count (*) from SAPDEV.usr02 group by mandt; Select count (*) form SAPDEV.usr02;
Select count(*) from sapdev.tbdls; Select count (*) from sapdev.tadir;
Select BNAME from SAPDEV.usro2 where MANDT=’800’; Select * from SAPDEV.usr02 where MANDT=”789”; Select MANDT form DEV.T000;
Local Client Copy:
It is performed between two clients with in the same system.
1. Create a client (SCC4 for create client) and logon to the target client 2. Go to Transaction SCCL
3. Select Source Client
4. Select Test Run to check the source 5. Select Profile
6. Select start immediately and schedule in background
7. Go to SCC3 to check the logs (To monitor the client copy process) Remote Client Copy:
It is performed between two clients with in two different systems in the landscape
1. Create a client
2. Go to SCC9 of the target system 3. Specify the profile
4. Specify the RFC destination
5. Start in the background mode. However we can start immediately Client Export and Import:
It is used to perform the client copy between the systems which are not in the landscape
It is performed in 3 steps.
1. Client Export: Use Transaction SCC8 to export the client to O/S level. This process generates transport requests in the \usr\sap\trans directory.
2. Copy the files to target system and import them using FTP and transaction STMS
3. Client Import: Go to Transaction SCC7 and perform client import Based on client export profile KX, KO, KT files are created in
\usr\sap\trans\cofiles and RX, RO, RT files are created in \usr\sap\trans\data directory.
KO, KX,KT are called as cofiles or control files Ro, RX, RT are called as Data Files
Copy the files using FTP\normal copy\DVD into target system \usr\sap\trans\cofiles and \usr\sap\trans\data directories. Go to STMS. Add the request and Import
Go to SCC7 to perform post client Import activities Standard Clients
000 (Template) 001 (Backup Client) 066 (Early watch)
Clients
DEV QAS Migration/ Legacy PRD
CUST TEST SAND BOX QTST TRNG PREPROD PROD
Client Deletion:
SCC4: Delete the entry from table T000. SCC5: Permanent Deletion
To lock and unlock a client: Go to SE37
Reports: The following reports can be used to lock and unlick the clients. Sccr_lock_client- lock client
Sccr_unlock_client- unlock client
Note: Profile SAP_CUST is used initially to setup Golden Client but later this golden client can be used as a source client to copy to another client with other peofiles.
Client Deletion: Clients are deleted using SCC5. But they cannot leave any space in the Database i.e. by deleting a client we cannot get any free space in the database. We need to reorganize the database.
Locking and Unlocking Clients: Use these two reports to lock and unlock the clients.
SCCR_LOCK_CLIENT and SCCR_UNLOCK_CLIENT
(or) we can manually use tp to lock clients. Use transaction SE37 for lock and unlock clients.
Client Comparison: While applying client specific patches i.e. CIN(Country India Version) use transaction SCMP to compare between two clients and to adjust the changes between two clients.
Setting up Library:
I order to get the screen context help we need to install the library and setup in SR13.
Go to SR13 to set up the library
There are four types of libraries available 1. HTML Helo
2. Dynamic Help 3. Plain HTML Help 4. HTML HTTP Help. F1-Field Help
F4-Field Possible Value Help
HTML Help: It occupies lesser space when compared to other library formats. It is viewed using micro soft help viewer. It is in the compressed format.
Plain HTML: It is installed on the file serve and help is displayed in the HTML format.
HTML HTTP: It is installed on the web server and requires web browser to execute.
Click on New Entries and provide the Following Details: 1. Name of the O/S
2. Variant 3. Training
4. Path of the library up to help data drive directory 5. Specify the language
6. Select the default check box 7. Save the entries
Scheduling House Keeping Background Job:
Importing Profiles:
RZ10 It is used to set the parameters for Work processes, Memory, Buffers etc…
Go to RZ10Utilities Select Import Profiles of Active Server DB13: Schedule an offline Backup so that we can test the Backup mechanism
Scheduling Database House Keeping Jobs:
Select check and verify database optimizer statistics, Adopt extents etc… Go to DB13 Select the Date It displays all the above tasks. Select each of them and schedule with different times.
Operation Modes: These are used to adjust the Work Process between Dialog and Background work processes.
Use transaction RZ04 and SM63 to configure Operation Modes.
Note: Ensure that the systems configured to solution Manger to configure the business scenarios as per the project plan.
SMSY, Solar1, solar2, Solar_project_admin Applying Support Packages:
Go to Transaction SPAM
Creating Users: Create users and assign SAP_ALL, SAP_NEW (Take out the critical Transactions like SU01, RZ10, RZ03, PFCG etc…)
DEVELOPMENT
Customizing: This is a process of modifying the system according to the requirements of the customer.
This is performed in the transaction SPRO. (SAP project customizing). This is the process of keying the entries into the table.
Customizing consists of the Following: 1. Crating Company
2. Crating Country
3. Crate Currencies, Measurements, Time Settings etc…
For example below are some of the customizations that we will do indifferent modules:
FI: We create Vendors, Customers, Cost Centers, Account Receivables, Payables, banks, Tax, Asset management, Description etc…
SALES: Sales Organizations, Sales Divisions, Sales Areas, Distribution Channels, Billing, Shipping etc…
MM: Purchasing, organizations, Inventory, Stores, Plants, Storage locations, Ware Houses, Goods, Invoice etc…
Exits or User Exits or Customer Enhancements:
It provides additional functionality to the SAP system. Exits can be searched. Transaction SMOD (Search Modifications) and CMOD (Create Modifications) are used to create the modifications.
There are various types of exits: 1. Field Exit
2. Screen Exit 3. Menu Exit
4. Function Module Exit
The exits are identified by Functional consultants and logic is programmed by developers.
Support Packages, patches and Notes:
Support Packages are provided by SAP to provide the bug fixes, functional enhancements and resolve run time issues.
Development
:If the customer requirements are not satisfied then we may need to develop the Programs, Reports, Transactions, Menus, Screens, Scripts and Functional Modules.
Programs and Reports: All the customer objects has to be created in
customer name space. /Company name/ (or) Y-Z in order to create programs the developer needs to register in the market place (developer License are charged separately).
Create user in SU01 and register this user in the market place. Get developers and key in the registration key before developing or modifying first program.
It will not prompt for the key later programs.
• Programs are created, modified and displayed in Transaction SE38. Transaction: It provides an easy way to navigate to the program.
Go to Transaction SE93 and create a transaction using the above created programs. Provide Program Name and Screen Number to define a
Transaction in the customer name space.
MENU: Menus are defined in Transaction SE41.
SCREEN: Screens are designed in the transaction SE51.
Scripts or Forms: These are available in SE71 and can be modified by copying in to customer name space.
Ex: PO script, Invoice, Delivery Order, Quotation, Sales etc…
Function Modules: These are used in the programs for modularization i.e. frequently and logis is turned in to functional Modules.
Domain: It is the least granular field in database which has its types and property like Data Type and Size. It is created in transaction SE11.
It is used to keep the fields uniquely in the database i.e. all the location follow the same format.
It is a field in the database like Location, name, Currency etc… It specifies type and Length.
Data Element: It is also defined in SE11 but it is specific to a field pointing to a domain. It is nothing but domain with a meaningful name.
Ex: District- Location, City- Location, Country-Location, State-Location TABLE: It consists of ROWS and COLUMNS.
Columns are Data Elements and ROWS consists of Data. Screen & Menus: SE51, SE64