Background jobs in SAP

BACKGROUND JOB PROGRAM SCHEDULE
SAP_COLLECTOR_FOR_JOBSTATISTIC RSBPCOLL Daily
SAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00 Hourly
SAP_REORG_ABAPDUMPS RSSNAPDL Daily
SAP_REORG_BATCHINPUT RSBDCREO Daily
SAP_REORG_JOBS RSBTCDEL Daily
SAP_REORG_JOBSTATISTIC RSBPSTDE Monthly
SAP_REORG_SPOOL RSPO0041 Daily
SAP_REORG_UPDATERECORDS RSM13002 Daily
DBA: CHECKPOINT RSDBAJOB Weekly
BACKGROUND JOB INFO
SAP_COLLECTOR_FOR_JOBSTATISTIC Generates runtime statistics for background jobs
SAP_COLLECTOR_FOR_PERFMONITOR Collects data for the performance monitor
SAP_REORG_ABAPDUMPS Deletes old ABAP short dumps
SAP_REORG_BATCHINPUT Deletes old batch input sessions
SAP_REORG_JOBS Deletes old background jobs
SAP_REORG_JOBSTATISTIC Deletes old data from the job runtime statistics
SAP_REORG_SPOOL Deletes old spool data
SAP_REORG_UPDATERECORDS Deletes old update requests
DBA: CHECKPOINT

SSO Connection Test

SSO Connection Test

Login into Portal system

Select the system administration

System configuration

Right click on the system objectàopen àConnection test

Select the property category :Connector

Click on sae

--

Login into the portal system

Select the system administration

Support

Sap application

Sap transactions

Select system

Enter t-code

Click on go

SSO Configuration in SAP

1.Create the Backend Systems object in Portal.

2.Login into the url :http://hostname:50000/irj/portal

3.Click on System Administration

4.Click on System Configuration

5.Right Click on Portal ContentàNEWàSystems(Portal Template)

6.Select the Template SAPSystems using dedication Application serveràNext

7.Select the System name :xxxxxx and SID:XXx

8.Click on NextàFinish

9.Select the Close the WizardàOk

10.Right click on the systemsàOpen àObject

11.Select the Property category as connector

Application host:xxxxx

Gateway host:xxxxx

Gateway service:xxxxxx

Logical system name:xxxxxxx

Remote Host type:xxxx

SAP Client:xxx

SAPSystem ID:SID

SAP System number:00

Select the system type as :SAP –R3

Click on Save

-----------------------

Create system Alias name

Login into the portal system

System configuration

Rt click on system object

Open

System aliases

Aliase name :xxxxx add

Click on add

Click on save

=-----

Select the log on method for system object

Rt click on system object

Open object

Select the property category as user management

Logon method is sap Logon ticket

Click n save

Download portal certificate

Logon to portal systems

System administration

System configuration

Select the key store administration

Download verify .cer file

Save it on your desktop

Import portal certificate into the backend system

Login into the backend system

Enter the t-code Strustsso2

Select the certificate tabàClick on importàBrowse that verify .cer fileàClick on ok

Add to certificate list

àClick as Add to ACL

System ID(Portal System) :XXX

Client:xxx

Owner:

Issuer:

System number :XX

Click on Ok

Click on save

Set the following parameters in the backend systems

àLogin into RZ10

àSelect Instance Profile

àExtended maintenance

àDisplay

Parameter name:Login/Accept_SSO2_ticket

Parameter val:1

Parameter name:login/create_SSO2_ticket

Parameter val:2

Restart the backend systems to effect the parameters

Portal monitoring in SAP

Login into Portal system

System Administration

Monitoring

Request Summary

Java Trace in NWA

NWA-->Analysis-->Performance-->Select Application Profile-->Start Trace

Java Patch Extension

.SCA-Software component Archive
.SDA-Software deployment Archive
.EAR-Enterprises Archive

Log Configurator in SAP

Log Configurator in SAP
To increase the Trace(Log level for Java Systems)

Security Levels:Debug,Path,Info,Warning,Error,Fatal,None,All

JCO RFC In SAP

JCO RFC In SAP

To Establish communication between ABAP+JAVA Systems.

Config Tool in SAP

Config Tool  in SAP

To Make the changes in the configuration parameters in the Java Engine

To Launch the config Tool

Usr\sap\<SID>\JC<INS>\J2ee\Config tool

Configtool.bat –Windows

Configtool.sh –Unix

1.No Authentication is required to launch the config tool(No User ID and Pwd required)

Pre-requisites to launch Config tool

1.Database must be running

2.J2ee Engine running will be optional

Configtool contains Managers and services

Config Tool is used for change the JVM settings for Java System

Add server process and remove the server process,Increase the thread count by using the config tool

Config tool contains secure storage area .It maintains Administrator and schema user password.

Config tool maintains UME(User management engine ) settings

Any parameter /service changes done then you must restart the J2ee to effect the parameter changes .

We can find out total no.of users in all our systems like SAP,.NET,mainframe .This can find in the Active device by using the LDAP Protocol in configtool

It is an offline tool.We can use this tool even J2ee engine is down.

We can Add max server process in a host will be 0-16 depending on hardware

Restart JAVA Stack through ABAP in SAP

• Login into SAP System
• Enter t-code :SMICM
• Administration
• J2ee Instance
• Send Soft Shutdown with/without Restart

During JAVA install or Refresh Users recreated

Reset the password for the following users from the default client. These users will be recreated during the JAVA Install.

J2EE_ADMIN
J2EE_GUEST
SAPJSF

Create a Control file in Oracle -SAP

Logon the target system as ora<source_system_sid>
su – ora<s-sid>
sqlplus “/ as sysdba”
alter database backup controlfile to trace;
exit

Export License Key in SAP

Create a Control File with below code

export.ctl
               file 'R:\<Folder name>\SLICENSE_DATA'
               delete from LICENSE_DATA
               select * from LICENSE_DATA
               delete from LICENSE_HASH
                select * from LICENSE_HASH
                delete from SAPLIKEY
                 select * from SAPLIKEY
                  delete from SLICORDER
                  select * from SLICORDER

SM02 Sample Message Post in SAP during outage hrs

IMPORTANT : <SAPSID> System will be unavailable from 10-Oct-2014 at 5pm CST to 15-Oct-2014 at 10am  CST for a System Refresh. Please, plan your work accordingly.

Pre-Refresh T-codes

Pre-Refresh t-codes

E070L Table
Take a Screen shot of the transport number entries from SE14.

SMLG:Capture Logon Groups

RZ12:Capture RFC Server Groups

SCOT:Capture SMTP Node configuration (for each client)

WE20 and WE21 :Capture the partner profile for each client

SE61:Capture the Logon Screen text

AL11:Capture the full path of Z-Directories

STRUSTSSO2 :Capture the certificates nd ACL List

SMT1:Capture the trusted system connectionos and test if the RFC's are working fine before Refresh

SCC4:Capture the swttings for each working client

SPAD Export:Take printer Export

SLicense :Take Screen shot

SCC8:User master export

PLC error while printing in SAP

PLC error while printing in SAP

Update printer drivers this will resolve the issue

How To edit the UME properties in 7.3 through configtool

1.Start the config tool

2.Config tool located under  j2ee folder

3.go to switch to configuration editor mode.

4.Go to configurationsàdestinationsàRFC-àPropertysheet<Destination name>àAdd the details of the backend server

How to reset Number range buffer in SAP

SM56 is the t-code to reset number range buffer in sap

go to SM56 and number range buffer-->Reset

How to change the SYSTEM_PF parameter value

1.When error code is 7 returning by TP, while performing export/import,Transport requests

1.Goto STMS

2.click on overviewàsystems

3.Go to Transport control

4.Add a row by clicking insert row icon

5.Add the System_pf parameter and save

6.To take effect new parameter system needs to be rebooted.

How to change the abap/buffersize parameter in sap

1.Enter RZ10 t-code

2.Select instance profile

3.extended maintenance radio button need to be selected

4.click on display

5.Find abap/buffersize parameter

6.Double click on it

7.Click on change/Edit mode

8.Give new param value

9.Click on copy

10.Go back

11.Go back

12.Save Profile

13.it will asks some condition click no

14.it will asks some condition click no

15.It will asks activate profile yes or no click on yes

16.this will create a backup profile with old values  at os level and new values will effective after restart.

User master Export and Import in SAP

1.First you need to login into Source system

2.Enter SCC8 select server ,target system as source system

3.check checkboxes immediately and  no printer dialog box.

4.click on schedule in background.

5.It will generate a transport request .

6.The request status in import queue will be cannot be imported.

User master import

1.Login into target system

2.enter stms_import.

3.Add the transport request or check in buffer if it exists

4.Click on import.

5.enter  t-code  SCC7 and perform post import steps in  background.

SAP NOTES and its categories

 SAP NOTES and its categories

SAP Maintains a knowledge base f problems and resolutions which are accessed from market place. www.service.sap.com/notes.SAP provides resolutions in the form of a note which is a number.Note can be searched on number (if we know)or we can search with the problem code,error number etc.

Note provides info.Reg the problem, as follows

1.Problem

2.Pre-Requisites

3.Cause of the problem

4.Solution,Corrections,attachments and note may redirect one or more number of notes.

Notes of 3 types

1.Informative note

Which consists of details to solve the problem

2.Corrective note

This provides changes to the data dictionary elements or repository objects.

3.Manual note:

Some of the steps will be present in notes to solve the issue.

If there is  a repository changes i.e program  code change can be done using SNOTE.If there are any changes in data dictionary elements or customizing (key entries) to provide entries manually in tables which are detailed in attachments.

àto change repository objects we need ACCESS KEY

àWhile correcting the program SSCR Key note required.SAP Software change request.

Client Export/Import

Prerequisites

1.Space on usr drive should be minimum 50GB to 100GB on both source as well as target system. This space is required as the requests which re created during client export will be saved in usr drive.Those requests again moved to the target system,hence the same amount of space required on target system.

2.Temporary database size should be minimum 3GB

3.Space on target system for data files should be 600GB

4.Log file size n target and source system should be more than 50GB.If required backup pf the same to be taken frequently.

5.Parameter PHYS_MEMSIZE should be 70% of the Physical Memory size.

6.During client export and import,it is important to suspend the background jobs on both servers source and target systems.

7.If the system is not in landscape.TMS needs to be configured on the system.

Client Export

1.Logon to the source client enter scc8.Choose the required profile. And click on target system.

2.Click on Schedule in background

3.if SAP_ALL  Profile is selected then change documents are not copied from the source system to target system as per profile SAP_ALL    click ok.

4.Click on Immediately and unclick No Printer Dialog and schedule job

5.Click continue.

6.The popup which appears will show the requests which are going to be created.

7.Click on OK.

8.The pop up screen appears on confirmation for the background job.

9.go to SCC3 and check the log for the same.

10.Detailed log in SCC3

11.In log , the requests numbers will be shown once the detailed analyzing is thru.

12.RO*,RT*,RX* files would be created in data file.RO* is for cross client,RT* is for client specific data and RX* for forms and Text.RO* will not be available if we choose the profile SAP_ALL while exporting the data.In the snapshot logs only RT* and RX* as the profile chosen for export was SAP_ALL.

/usr/sap/trans/data

13.KT* and KX* files would be created in data file

/usr/sap/trans/cofile

14.Log files can be viewed in .\trans\log folder

15.Finally the client export will complete  as per logs.

16.The data file size would be 15 GB Approx takes 8hrs.

/usr/sap/trans/data

Client import

1.Logon to the Target system àExecute STMS

2.Add the requests KT00009 and KX00009 into queue.SID of the source system to be aced along with this.EX:RK1KT00009.

3.Import should be on sequential basis

First KT* and KX* ,if KO is available then KO* imported first.Here KO* will not be available as the profile chosen is SAP_ALL.

4.Other requests àAdd

5.Enter the Request no.Click yes

6.Check the queue

7.Click on  ‘Import Request’ and the following screen appears

08.Enter the target client and click on import.

09.Import will start on the target system now.

10.Monitoring the import.Enter t-code DB02 and check for DB Growth.

11.Goto \usr\sap\trans\temp\RP11T00009.tmp file to see the current status of  import.

Also SLOG file which will give the phase of the import. This file would also give you the import parameters being considered for this import.

12.Once the first request is imported successfully and then import the next request.

13.Add the next request RP1KX* into the queue and start the import.

14.Now the second request starts importing and completes.

Client Import –Post processing

1.Enter the t-code SCC7 and by default you will see the RP1T* transport appears there for Post processing activity.

2.Click on the background job option, Click on continue

3.Check for logs SCC3.

4.once SCC7 complete successfully, DB Consistency check to be done, the complete CUA needs to be reconfigured., All transports  requests which are imported in quality server after production client export needs to be imported again on quality server and background jobs needs to be checked.

Remote Client Copy

Prerequisites:

All  prerequisites of local client copy with some of the points below

RFC connections should be established between the servers

Procedure

1.Create a new client in Target system.

2.RFC Connections should be established from target to source server.

3.Logon to new client and enter SCC9 and select client profile and source client

4.Schedule as background job.

5.Logs can be displayed in SCC3.

Local Client Copy

Prerequisites:

1.Check the source client size by entering t-code SE38 and run report rstablesize and check enough space is available on the target system.
2.Lock all the users in the source client.
3.Client copy must be started from target system,so login into the target system using sap* and pass.
4.Ensure that transport management system is configured and working fine.
5.Minimum 2 background jobs should be available ,otherwise pause all background jobs by enter t-code -SE38 and run RSBTCTRNS1 report.To Reschedule all job back into normal run RSBTCTRNS2 report.
6.RDDIMPDP job should be run in background,otherwise run report RDDNEWPP.
7.TEMP and TRANS directories should be have three times of client size free space.

Procedure:
1.Create client by enter t-code SCC4 and assign logical system name.
2.Assign client settings according to the role of the client in landscape.
3.Logon in new client with sap* user and password pass
4.If password pass is not working then change
login/no_automatic_user_sapstar=0 and restart the application server.
5.Enter SCCL for local client copy and give desired profile and source client
6.Schedule as a background job due to it is long running job.
7.Logs can be displayed in SCC3.

How to Create Logical System Name in SAP

Enter BD54 and give logical system name as below syntax
<SID>CLNT<client number>
Give the description of logical system name and save.

Configuring Transport Routes

Configuring Transport Routes

Prerequisite

Before configuring the transport routes all the systems should already be added to the transport domain.

Configuration:

We can configure the transport routes in Domain controller only and can distribute & activate in all SAP systems in the transport domain.

Transport route configuration consists of

1.System Attributes

2.Consolidation Routes

3.Delivery routes

4.Target Groups

SAP Provides 2 editors for configuring transport routes

1.Graphical editor

2.Hierarchical List Editor

Steps to configure Transport Routes:

1.Call STMS in Transport Domain controller system.

2.Click on hierarchical list editor graphical symbol

3.Choose menu gotoàGraphical Editor

4.Now you can find three systems in this graphical editor

5.Goto Edit mode

6.Click on Add transport Route

7.Place mouse pointer on DEV,now click and drag to QAS.Now one dialog box appears

8.Choose Consolidation radio button and go to Transport layer option.Now click on Nike Symbol.

STMS Configuration

STMS Configuration

Below is the details for a three system landscape and we want to configure Transport management  system

1.SID:IDS,hostname:SAPIDES(PRD)

2.SID:QAS,Hostname:RADSAP

3.SID:DEV,Hostname:MYS-705894

Prerequisite:

We have to define RFC Connection between these three Systems(T-code:SM59)

Analysis:

Now we have to decide which ne should be our Transport domain Controller.SAP recommends the Transport Domain should have the following attributes.

àHighly available

àHighly Secure

àHighest Possible Release

The Transport Domain Controller Should normally be configured ina production system or quality assurance system.

Configuration (Domain Controller)

1.Logon to the SAP System(Client:000;User:SAP*)on which you want to configure the Domain Controller(QAS)here.

2.Enter the t-code STMS.

3.Enter the name of Transport Domain name(Cannot contain blank characters)& short description.

4.Now click on save button of the dialog box

Note:

Once saved & other systems are added you cannot change the DOMAIN NAME without reconfiguring the entire transport domain.

5.Following is displayed in initial screen You are logged onto the domain controller.

6.Go to menu OverviewàSystems.

7.Automatically the following configurations are updated in SAP System.

.The user TMSADM will be created

.RFC Destinations required for the TMS are generated.

.TMS Configuration will be stored in the Transport directory.

.Transport Profile for Transport control program tp is generated.

Now once the Transport Domain is configured proceed adding other system to the Domain Controller.

Configuration inclusion of SAP Systems in Transport Domain

This occurs in 2 steps

1.Adding the SAP system into the Transport Directory.

2.Confirm the system inclusion in the Domain Controller.

1.Adding SAP Systems to the Transport directory.

      1.Logon to the system(Client:000;User:SAP*),the one which you want to add to the transport domain.

2.Call the t-code STMS.

NOTE:

If the SAP Systems have a common directory TMS proposes to add the SAP System to the transport domain when you call STMS

3.The dialog box TMS: Include system in Transport Domain appears, displaying the Transport Domain name and the address at of the domain controller.

 4.Click on save .the following performed automatically

1.Creates the user TMSADM

2.Generates RFC destinations required for TMS.

3.Sends the address data to the domain controller.

4.sends the profile parameter for configuring the transport control program to the domain controller.

5.For security reasons the domain controller must confirm the inclusion of SAP System.

6.Confirm the system inclusion in the domain controller.

1.Now logon to the domain controller and call t-code STMS.

2.Goto menu overview àSystems

3.The coloumn status shows its waiting to be included.

4.Position the cursor on the SAP system.Go to SAP systemàApprove

Now the same way you can include the DEV system in transport Domain

When the 2 systems added to Transport domain check the consistency of transport groups.

1.To check this choose menu gotoàTransport groups

2.It’ll display screen: Display TMS configuration: Transport Groups

3.Choose menu Configuration .-àCheck Transport Groups

4.It’ll display a screen.

5.Green color means Group is assigned correctly.

6.Red color means error occurred.

SPOOL Access Methods

Local Access Method:
The spool wp and the host spool resides in the same machine i.e wp transfers the spool request to the spool system locally.
select L for unix based system (Local Print method)
Select C for Windows (Which uses direct operating system call)
Select F :Front end printing

Remote Access Method
The formatting by spool workprocess is performed on remote system

Specify U :Unix operating system where formatting is performed on the remote machine(Print server )using Berkeley protocol.

Specify S :For windows operating system.It will transfer the formatting to remote system using SAP Specific protocol SAPLPD.

Third Party BTC Job Schedulers

Third Party BTC Job Schedulers

1.Control-M Scheduler

2.Redwood Scheduler

3.Tidel Scheduler

4.SAP Job Scheduler

5.Maestro Scheduler /IBM

JOB Status in SAP

JOB Status in SAP:

1.Scheduled:This job is defined but time to execute is not specified.
2.Released:The time to execute is specified
3.Ready:The time to run the job is reached
4.Active:Background processing the task
5.Cancelled:The job is cancelled
6.Completed:The job is completed or finished.

SM66 in SAP

SM66 -Global Work Process Overview

Click on select Process.The major advantage f this is it displays the memory consumed by work process.

Work Process Status in SAP

Work Process Status in SAP

Waiting:The process is waiting "Available" to serve the user request.

Stopped:The process is stopped due to an error

Running:The process is executing the task

On Hold:The user request is on hold by process for waiting certain resources on the other systems(RFC,CPIC).

Shutdown:The process is killed /shutdown but restart mode set to NO.

PRIV MODE:The process goes into Heap mode.It will be completed only after the task completion/timeout.

SLEEP MODE:The work process goes into sleep mode waiting for resources(RFC Problem)

SAINT(SAP Add -on Installation) Installation in SAP

SAINT Installation

Transaction SAINT allows you to install and upgrade an Add-On / Plug-Ins, such as an Industry Solution, from the SAP system. To install or upgrade an Add-On / Plug-Ins, it can be necessary to import Add-On Support Packages and CRTs. Transaction SAINT deals with this.

For Example, Plug-Ins are PI_2005, PI_Basis, ST_PI, ST_A/PI

For Example, Add-On are Solutions, SDPs, IBUs 

Reason: The customer requires functions that are not included in the SAP standard, but which are offered by an Industry Solution. An Industry Solution brings new objects and additional Customizing into the system, it CAN modify existing SAP standard objects and change existing Customizing

A CRT can be required to correct conflicts between the SAP standard and an Industry Solution or an IS Support Packcage

You must take the following prerequisites and settings into account to import Add-Ons / Plug-Ins with transaction SAINT:

SAINT - Prerequisites and Settings

·         • The required IndustrySolutions, Support Packages, and CRTs must be available.

·         • There must be enough space in the file system.

·         • The import should be performed during a time of low operation.

·         • The newest SPAM/SAINT update is required.

·         • TMS/CTS must be configured.

·         • No aborted Support Packages or IS in the system.

·         • Use client 000 for importing; only a display function is available in all other clients.

·         • System authorizations for SAINT.

·         Note: You require the authorizations S_TRANSPRT and S_CTS_ADMIN to be able to run SAINT. These authorizations are part of authorization profile S_A.SYSTEM.

Applying SAP Add-Ons / Plug-Ins

Login into 000 client with user DDIC .

Start the update of Add-ons using T-Code SAINT 

Goto, Installation packages → Load Package → From Front End / From Application Server

If the compressed files are on your front end server and are smaller than around 10 MB, you can transfer these files to the application server and decompress them directly from the Support Package Manager.

Select the Package and continue to Install

The displayed packaged must be imported when installing the add-on

- choose (CONTINUE) to import the queue

- Chose (BACK) to go back to the add-on selection

How To apply SAP Support packs

How To apply SAP Support packs

SAP Support package's are used to enhance the functionality or bug fixing in the program, it contains a collection of error corrections. You can only import complete Support Packages and in a specified sequence. Each correction in a Support Package is documented in an SAP Note.

We can Download the Support Packages from SAP Service Market Place (SMP) -> https://service.sap.com/swdc 

Before applying support package there are certain prerequisites which need to be checked.

Support package applied once cannot be reverted back, always apply support packages to the level n-1, since developments still goes on with the latest patch level

    Ex:- If the latest patch release are 54 better to have the patch 54-1=53

Each Support Package is valid for only one release (but for all databases and operating systems) and requires an exactly defined number of predecessors. The upgrade of the following release or correction release contains all the Support Packages of the previous versions that were available up to the delivery of the upgrade.

The following types of Support Packages are available:

SPAM/SAINT Update

A SPAM/SAINT Update (PAT) contains updates and improvements to the Support Package Manager and the SAP Add-On Installation Tool.

Component Support Package

A Component Support Package (CSP) is valid for one software component (SAP_BASIS, SAP_HR, SAP_APPL, Add-On Software Component...) and contains quality improvements for Repository and Dictionary objects in this software component only.

In addition to these improvements, Support Packages for the SAP_HR component also contain adjustments due to legal changes.

Below are the some of the Software Components and its Naming conversation of Support Package

. SAP_APPL (SAP R/3 Support Package):           SAPKH<rel><no>
. SAP_BASIS (Basis Support Package):               SAPKB<rel><no>
. SAP_ABA (Application Interface SP):                SAPKA<rel><no>
. SAP_HR (SAP R/3 HR Support Package) :        SAPKE<rel><no>
. SAP_APO (APO Support Package):                  SAPKY<rel><no>
. SAP_BW (BW Support Package):                     SAPKW<rel><no>
. SAP_CRM (CRM Support Package):                SAPKU<rel><no>
. SAP_SRM (SRM Support Package):                 SAPKU<rel><no>
. SAP_SEM (SEM-BW Support Package):          SAPGKS<rel><no>

Prerequisites for applying support patches

1.       SPAM and SAINT version should be latest.

2.      Go through the OCS (online correction support) note before doing support package. 

3.      There should not be any aborted packages which were applied earlier.

4.      Login to 000 client with user like DDIC.

5.      Suspend all background jobs using report BTCTRNS1 except background jobs like RDD* jobs.

6.      There should be at least two background work process reserved for this process.

7.      Check for enough space in eps/in directory (os level) \\usr\sap\trans\eps\in take successful backup.

8.     Functional and technical consultants should be around for applying changes to data dictionary and repository objects

9.      Take the database backup before going to apply support packages

10. There should be enough space in tablespace (DB02) (If any tablespace is > 90% add data file )

11.   Apply patches in the sequence defined in the composite note. Patches can be applied individually or bundled together.

12.  Patches can not be revert by consultant, only SAP can revert the patches by developing a negative patches if required.

13. Schedule downtime before going to apply support packages. Notify user through email or by creating a message SM02 transaction.

14.  Lock all user’s, except BASIS Admin users, DDIC and SAP* for Make sure no user should be logged on while performing support package.

15. In order to avoid network congestion the files which are more than 10MB has to be applied through “Application sever”. Patches which are less than 10MB can be applied through “Front end”.

16.  “tp” version should be latest  and also upgrade the Kernel version.

17.   Support package should be applied in the sequence of landscape, First in Dev system and next apply in QAS for the consistency test and finally in PRD system.

18. Note: You require the authorizations S_TRANSPRT and S_CTS_ADMIN to be able to run transaction SPAM. These authorizations are part of authorization profile S_A.SYSTEM.

Steps to applying SAP Support packages

1. Click on Package level to know the existing level of the support packs and the add-ons. 

2. Go to transaction SPAM and Load the support packages from frontend if it is < 10 MB. The support packages which are in the form of .car will be decompressed into eps/in directory.  

If the size is > 10mb, copy the support packages to /trans  directory and uncar the support packages using the below command 

cmd>cd usr\sap\trans

       > sapcar –xvf <filename>.car

The command SAPCAR will decompress the CAR file and put two files (with extensions .ATT and .PAT in the /usr/sap/trans/EPS/in directory.

3. Click on "Display/define"

4. A box will appear with the Support Package categories, Click on the category for the support packages that you uploaded and it will list them in order. You can apply them individually or the whole list at one time.

click import queue (or) Click on truck icon.àsupport package à5. Go to

6. Click on continue after importing in to the Queue.

7. Click Continue..

8. Note :- While applying support packages it triggers two phases SPAU and SPDD 

SPDD

When the support packages contains any changes in the data dictionary then this phase is invoked.

SPAU

When the support packages contains the changes related to repository objects SPAU phase is invoked.  it prompts whether to keep to existing changes modified by notes or adapt to changes.

Modification Adjustment During Import of Support Packages

Use : - If SAP modified objects that have also been modified by the customer, a modification adjustment is executed in the transactions SPDD and SPAU during import of Support packages.

Procedure

As far as the modification adjustment is concerned, you use the common procedure described below to import Support Packages:

·         Create two change requests in the Workbench Organizer (transaction SE09), one for the modification adjustment with transaction SPDD and the other one for the modification adjustment in transaction SPAU.

·         Create a task for each developer who is involved in the modification adjustment.

·         The developers must use transactions SPDD and SPAU to determine whether to retain or delete the modifications.

·         After modification adjustment is finished, the developers must release their tasks.

·         Use transaction SPAM to access the SAP Patch Manager.

·         Choose Patch -> Import Patch Queue. A confirmation dialog window appears.

·         Choose Enter to finish the import process of the Support Package.

·         Release the change requests that result from the modification adjustment using transactions SPAU and SPDD. At a later time, you can use the change request of transaction SPAU to import the modification adjustment after this patch queue has been imported into other SAP Systems within the system landscape. You cannot use the change request of transaction SPDD to avoid the required SPDD adjustment during import into other systems. You must always re-adjust the Dictionary manually. However, you should still transport the change request to ensure that identical modifications are made in all SAP systems. Before importing the change request resulting from the modification adjustment with transaction SPAU or with transaction SPDD during import of a patch queue into the subsequent systems, import the patch queue itself.

9. It prompt you the Queue is imported successfully and ask to confirm the queue.

10. Go to -> SPAM -> Support Package -> Confirm the Queue

This shows the support package has implemented for the one of the queue and you need to do the same as for the other queue (software components).

Post processing for support package   

1. Check if any alerts or error messages in SICK and SM21.

2. Release all the background jobs (BTCTRNS2).

3. Unlock all the users.

4. Run SGEN ( SGEN compiles all programs.SGEN reduces abap load on the system).

5. Take a successful backup.

Problems While Applying Support Packages

·         Tablespace overflow.

·         Max extents reached.

·         Archive struck.

·         Kernel outdated.

·         SPAM/SAINT outdated.

·         No enough space in eps/in directory.

·         "tp" could not connect to database (Execute R3trans –d which will generate trans.log)

·         STMS configuration should be consistent.

·         "tp" and "R3trans" is outdated or obsolete or corrupted which needs to be updated.

·         Check environmental  variables.

·         RDDIMPDP job not scheduled

·         Objects conflict b/w the packages

·         Inconsistent in TMS

·         Background jobs is terminated with memory related issue