SAP Post-Installation

Post-Installation Actions:
  1. Install the GUI (740) and define the connection entries
  2. logon to the System and create admin Users other then sap* and DDIC.
  3. Lock the sap* User and disable the sap* logon by setting the parameter login/no_automatic_user_sapstar=1 in RZ10.
  4. Execute SICK to check the Compatability between OS/DB and SAP Kernels.if sick results in error then OS/Patch,Update,DB/Patch, Update,SAP Kernel Update May be required.Ex: Windows 2008 SR1 Requires SP Update    Oracle patch sets (1) are not Supported by SAP(9.2.0.1/10.2.0.1/11.2.0.1/12.1.0.1 are not supported. Certain SAP Kernel has to be Updated to higher versions before start working on the system.It will also checks whether the memory,buffer and processes parameters are configured optimally.(Example Btc=0,enq=0,upd=0,spo=0 buffer pxa nill then system restart will thrown an error).
  5. Run SGEN to Compile the Programs and reduce the Compilation and Run time.it needs certain space in the database. Ensure that Database space is sufficient to run the SGEN.
  6. SE06:Standard Installation: The System is setup based on the Export Software Provided by SAP. it resets the Change Requests Number and Prepares the System to take part in the landscape.it reinstall the CTS(Change(correction))Transport System.
    Database Copy or Database Migration:The System is setup(built) based on the Backup/Export taken from the Existing System in the Landscape.It deletes all the transport routes,resets the number range,deletes TMS Configuration so that this can take part in the landscape.
  7. SE06(Global Settings: it is used to set the System Change Options. The System Settings are set to modifiable and not modifiable.Generally the Development,sandbox and Testing are set to Modifiable and Quality,Pre-Prod and Production Systems are set to Not-Modifiable.
  8. STMS:it is used to setup the Transport Management System.Transport Domain: There will be only one transport Domain that is used to Manage all the member systems in the Landscape.initially Development is configured as Transport Domain which can be moved to any other highly available system such as Quality and Production Systems.Execute STMS–>A pop-up window prompts to configure Transport Domain–>Save the Details–>A Transport Domain(DOMAIN_SID)is created.
  9. Kernel Update: it is the process of replacing the existing kernel executables with a new set of executable(downloaded from SAP Market Place).
  10. Kernel Release Upgrade:it is the Process of Deleting the Current release executable and replacing with new Kernel Release Executable.it is required to get support from SAP,get new Enhancements,security features etc..
  11. SLICENSE:it is used to update the license which is downloaded from SAP Market Place. The License is based on hardwarekey.hardwarekey changes whenever OS is reinstalled.The License key is digitally signed and it could not be reused.it contains the Installation Number,System Number,hardwarekey and License key along with Valid Date.Hardware Key: Specific to Operating System changes when every OS changes or reinstalled.Use Command saplicense -get to get the hardware key or from slicense transaction.License Key: it is a digitally signed Key from SAP. it is valid until 31.12.9999. it is applied through SLICENSE.Maintenance Certificate: it is valid for three months. it is used to maintain the system.SPAM/SAINT gets locked when this key is expired.
    Customer Key: it is a key provided by SAP when SAP Software is Purchased
    Installation Number: Each Customer key contains multiple Installation Numbers based on Products ex: SAP ERP,SAP SCM,SAP CRM,SAP Solution Manager,SAP Netweaver etc….
    System Number: it is generated during license key and specific to System.
    Developer Key: Each SAP ABAP Developer Requires a Developer Key to develop Objects in the SAP System(Y-Z)Object Access Key(SSCR(SAP Software Change Registration Key))Any Object(A-X) that requires modification by the Customer need to obtain SSCR Key.Migration Key: if there is a change in OS/DB then Migration key is required.
    Solman Key: it is required for Installations and Upgrades. From Netweaver 7.3 it is not required.
  12. SPAM/SAINT Update: it is used to Update the Tool. SPAM/SAINT Update is Cumulative like SAP Kernel. Download the Latest SPAM/SAINT Update from SAP Market Place.Upload through the Presentation Server(Front End) and Import the SPAM/SAINT Update. The SPAM/SAINT Transaction may need to run twice or thrice to complete the Update.Error: Load-Program-Lost(Not-Found) may Occurs because the exisiting SPAM Program is lost while applying SPAM/SAINT Update.
  13. SR13:Library Configurationclick on New Entries–Select Plainhtmlhttpvariant: Specify the NamePlatform:WN32Area: training|documentation     IWBTRAIN|IWBHELPServernames: help.sap.compath:erp2005_ehp_08/helpdatalangauge:en
    it provides screen|Transaction specific Help using menu “help” and Application Help.The path can belong to any version
  14. SM36: Scheduling the Standard House Keeping Jobs.Execute SM36–>Standard Jobs–>Default Scheduling.
  15. DB13:Schedule Database House Keeping Jobs.(dbstats,dbcleanup,dbcheck,dbbackup,logbackup)
  16. RZ10 to Import the Profiles: Execute Rz10–>utilities import profiles of active servers.
  17. Support Package Update using SPAM:it is used to apply support packages to ABAP,Basis,BW,ST-pI,PIBasis etc…
  18. SAINT-Add-ons Deployment using SAINT(GRC Virsa,ST-PI,PI-BASIS,Nakisa and other Third Party Add-ons)
  19. i18N(Internationalization To adopt the Languages)
  20. Set the Profile Parameters for languages zcsa/installed_languages(based on i18n)
  21. Import the Languages from SMLT
  22. Activate the Business Sets using SCPR20
  23. Activate the Business Functions using SFW5.
  24. SALE(Creating Logical Systems)Logical Systems are created in SALE using the Naming Convention<SID>CLNT<001<Client Number>.These are used to Identify the client uniquely in the landscape.as the Clients are represented in Numbers it will be difficult to transfer the data between clients using numbers.So,they are assigned with the Logical System Names.Each Logical System Name is Assigned to Client in SCC4/SALE.if the Logical System Name is Changed then the Entire Addressing Changes,so Do not Change the Logical System once assigned to the Client.Changing the Logical System Name:Use Transaction BDLS to Change Logical System Name.(it is mostly used during a System Copy of BW Systems)
  25. SCC4(Creating Client) Client is an Independent Business Entity which is used to Represent the Business or an Enterprise.
  26. SCCL Local Client Copy
  27. SM59 Define RFC Connections
  28. SCC9 Perform Remote Client Copy
  29. SCC8 Client Export
  30. STMS and SCC7 Client Import and Client (Import)Copy Post proccesing
  31. SCC3 Client Copy logs
  32. SCC5 Client Deletion
  33. SU25 Initialization of Profile Generator.
  34. RDDIMPDP/RDDNEWPP: schedule as a background job using User ID DDIC in Client ‘000’.

Comments

Post a Comment

Popular posts from this blog

SPOOL WORK PROCESS

Spool Process: It is the Only Process that is used to output the documents to a Printer, fax, email etc.. Spool Work Processes are created by using parameter risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...
Read more

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more