SAP Library - Find your answers

The latest SAP Support Packages are Scheduled and listed in the following link:-

https://websmp206.sap-ag.de/ocs-schedules

Support packs are stored in tables PAT01 and PAT03.

The .att and .pat files are the support package itself. Support packages should be
extracted in the transport directory (usually /usr/sap/trans). When extracted, they reside
in the "EPS/in" directory from which they can be applied in the SAP system via the Support
Package Manager (transaction SPAM).

To open a service connection for support from SAP AG, please go through the follow link:-

http:\service.sap.com\serviceconnection

SAP provides with Support Packages as part of the software maintenance for all the components. Support packages are applied to correct errors in programs, bug fixes, updates.

There are two kinds of Support Packs

ABAP Support Packages and Java Support Packages


ABAP Support Packages contains error correction and latest updates for ABAP Components. The support packs needs to be imported in the SAP system through Support Package Manager (SPAM), in a sequential order.

In ABAP Support Packages we have Component Support Packages, Add-On Support Packages, Conflict Resolution Transports (CRT), SPAM/SAINT Updates.

Java Support Packages contains error correction and latest updates for JAVA Components.
The support packages are available in the form of Software Component Archives (SCA) and are applied through Java Support Package Manager (JSPM)

Java Support Packages are available as of SAP Web Application Server 6.20.

Support Package Stack are a group of Support Packages and patches for a specific product version that must be applied in the specific combination.

The current SAP Support Package Stack Level of SAP ERP 6.0 is SP Stack 13 released on 06/2008.

Please go through the follwing link for latest SAP Support Package Stack Level :-

https://websmp210.sap-ag.de/sp-stacks

To view the SAP Support Package Stack Schedule (Calender View), please go through the following link:-

https://websmp206.sap-ag.de/ocs-schedules

Click on "SAP Support Package Stacks" --> "SP Stack Information" --> "SP Stack Schedule "

Keyword: BASIS
Title : Maintenance Transaction with Installation of a Support Package Stack

Apply Support Packs To My SAP SYSTEM

How can I apply support packs to my 4.7 IDES SYSTEM?
SAP"- SAP R3 4.7EE,
DATABASE : ORACLE 8.1.7
OS : WINDOWS 2003 SERVER
What is the step by step procedure and how to apply in r/3?

You have various issues with your setup:

- Oracle 8.1.7 is not supported under Windows 2003
- Oracle 8.1.7 is out of maintenance since three years

During SP application you will maybe run into problems that can't be
fixed since your installation is just too old and unsupported. *-- Markus

As mentioned, it's true that it won't get supported on Oracle 8. The best combination would be with 9i

Any How I have mentioned the steps below to apply for patches.

To Apply Support packs first up all you need to download the patches. When you have the downloaded the file i.e.. (*.car ) patch file then you can extract and apply it in two ways.

1. Go to command prompt through cmd (if you are using windows) and go to the folder where you have download these files ( could be in \downloaded folder\ ) type this command on command prompt without quotes "sapcar -xvf .sar". Now it will create a folder called EPS and a folder called IN inside EPS. Go to this folder and it will show two extracted files with extension " .att " and " .pat ". Copy this two files into yours trans\eps\in folder which could be something like \usr\sap\trans\eps\in folder.Then type spam on your session and navigate to Support Package\Load Package\From Application Server and it will ask for Path confirm it Say " YES"Select the patch imported and double click on it and then click on small truck Icon and it start Import.

2. Type Spam on session then navigate to Support Package\Load Package\From FrontEnd \ and Navigate to path where you have downloaded the *.SAR file of Support Pack.Now it will open a popup window and then click on decompress button ( It is front-End process for extracting or decompressing .sar file in .pat and .att extension ) After that click on Display-Define button on right hand side.) Select the BASIS or ABAP patch ( whichever you are applying *) what ever you are after and import it in queue. After that click on Small truck Icon in menu i.e.. (import Queue) and it Starts importing.

How can I apply support packs to my 4.7 IDES SYSTEM?
SAP"- SAP R3 4.7EE,
DATABASE : ORACLE 8.1.7
OS : WINDOWS 2003 SERVER
What is the step by step procedure and how to apply in r/3?

You have various issues with your setup:

- Oracle 8.1.7 is not supported under Windows 2003
- Oracle 8.1.7 is out of maintenance since three years

During SP application you will maybe run into problems that can't be
fixed since your installation is just too old and unsupported. *-- Markus

As mentioned, it's true that it won't get supported on Oracle 8. The best combination would be with 9i

Any How I have mentioned the steps below to apply for patches.

To Apply Support packs first up all you need to download the patches. When you have the downloaded the file i.e.. (*.car ) patch file then you can extract and apply it in two ways.

1. Go to command prompt through cmd (if you are using windows) and go to the folder where you have download these files ( could be in \downloaded folder\ ) type this command on command prompt without quotes "sapcar -xvf .sar". Now it will create a folder called EPS and a folder called IN inside EPS. Go to this folder and it will show two extracted files with extension " .att " and " .pat ". Copy this two files into yours trans\eps\in folder which could be something like \usr\sap\trans\eps\in folder.Then type spam on your session and navigate to Support Package\Load Package\From Application Server and it will ask for Path confirm it Say " YES"Select the patch imported and double click on it and then click on small truck Icon and it start Import.

2. Type Spam on session then navigate to Support Package\Load Package\From FrontEnd \ and Navigate to path where you have downloaded the *.SAR file of Support Pack.Now it will open a popup window and then click on decompress button ( It is front-End process for extracting or decompressing .sar file in .pat and .att extension ) After that click on Display-Define button on right hand side.) Select the BASIS or ABAP patch ( whichever you are applying *) what ever you are after and import it in queue. After that click on Small truck Icon in menu i.e.. (import Queue) and it Starts importing.
*-- Deepanshu Sharma
* Note :- Basis patch starts with KBxxxx.sar and Abap Patch start with KAxxxx.sar likewise.
* Note :- If you are applying all support pack it may ask you to increase your spam level (SUPPORT PACK MANAGER).

How to Upload a support Package:

- Download the support packs from NET to the usr\sap\trans\tmp directory.

- Unpack the support packs using the following command car -xvf .CAR

This command unpacks the files that need to be imported into your SAP instance into the usr\sap\trans\eps\in directory.

- Log into client 000 as user DDIC
- Call transaction SPAM

- Once in transaction SPAM, go to menu option Support Package->Load Packages->From Application Server. It will ask you if you want to upload the files - click the green check mark on the box that appears to upload the files.

- Another screen will appear listing the files that you uploaded successfully - just click on the Back arrow to get back to the SPAM screen.

- On the SPAM screen, click on the Display/Define button.
- 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.

- To apply individually, select the first one in the list and then hit the green check mark at the bottom left of the box. Then on the SPAM screen, go to menu Support Package->Import Queue.

- Confirm that you want to import the support package.
- Once it is done importing, you have to confirm the queue by clicking on the
Confirm Queue button - this will turn the yellow light in the Status area to green.

After Applying you have to regenerate using SGEN transaction.

Support Packages Procedure

PRE-STEPS:

Set Profile parameters as follows:

(Not needed if running hotpacks in background)

rdisp/max_wprun_time = 0

rdisp/gui_auto_logout = 0

Bounce(Restart) SAP to put changes into effect.

If .CAR files are not there
go to the site and download the latest .CAR files of the concerned layer.
FTP these .CAR files to /usr/sap/trans. Then to unpack them , cd /usr/sap/trans and “CAR –xvf xxxx.CAR” it will put them in EPS/in

cd /usr/sap/trans/EPS/in

grep BASIS *.ATT |grep CRT <>

Ensure transports are not run into the system via the automated transport tool, or it will clear out the buffer and mess up the hotpack installation

Put a hold on the Backup Job, Remember to release the job after hotpack installs.

Log onto client 000 on the main instance and go to transaction SPAM

Import Hotpacks from the application server to let SPAM know about them:

Support Package ->Load packages ->From application server

Apply latest SPAM patch – currently patch level SAPKD00000:

Support Package ->Import SPAM update

Remember to confirm queues after they complete successfully.

When it runs in background you need to monitor the job for errors and press refresh on the spam screen. If it stops for error checking.. Goto STATUS>Queue and it will prompt you for an action.

Goto->Import logs->queue to see the logs

Whenever you get a SPAU/SPDD message in queue status and transports are imported successfully click on “modify adjustment”->click on Import button -> click on confirm queue

If there is an error saying that the object is in repair go to se01

SPDD/SPAU Hotpacks stop processing while you attend to the spdd/spau steps. You will

Need to restart the hot packs, by selecting the IMPORT queue Icon.

Expand, save as text file, and email the list to SAPBasis or project team. Double-click on each object, ensure the proposal matches the current version, click on Accept Proposal, green arrow back, click on Return to Standard, create a transport, release the transport, green arrow back and hit continue to resume processing hotpacks.

Only save and send final SPAU list after last batch of support packages.

1^st : in SPAU, go to adjustment filter tab, unclick “Adjusted” button. Go to Display Options tab and click on “Last transport requests”. Execute and save list as text file. 2^nd : in same SPAU view already created for list 1, position your cursor on the “Last transport request” title line and click on the “expand subtree” icon (green plus sign with down arrow). Save list as text file and email both lists.

Green arrow back and hit continue to resume processing hotpacks.

Put profile parameters back: (If you made change in pre-Steps)

rdisp/max_wprun_time

rdisp/gui_auto_logout

Bounce SAP to put into effect.

Reapply mods/OSS notes with modification assistant within SPAU.

Run SGEN after you have installed Hotpacks:

Goto transaction:SGEN

Select (Regeneration after Upgrade).. Select Continue

Run the process in background.. Runs over an hour long

Handling tickets is called Issue Tracking system. The errors or bugs forwarded by the end user to the support team are prioritized under three seviority High, Medium and Low. Each and every seviority as got its time limits before that we have to fix the error.

The main job of the supporting consultant is to provide assistance on line to the customer or the organisation where SAP is already implemented for which the person should be very strong in the subject and the process which are implemented in SAP at the client side to understand, to analyse, to actuate and to give the right solution in right time. This is the job of the support consultant.

The issues or the tickets (problems), which are arised, are taken care of on priority basis by the support team consultants.


The work process in support projects is given below for your reference.

1. The customer or the end user logs a call through any tool (MARVEL) or by mail (RADIX).

2. Each one of the support team is a part of support group.

3. Whenever a customer logs a call he /she has to mention to which work group (by name).

4. Once the calls came to the work group the support consultant or the team needs to send an IR (Initial Response) to the user depending upon the priority of the calls. (Top, High, Med, Low, None)

5. Then the error is fixed, debugged by the support consultant or the team. Then after testing properly by generating TR (Transport Request through the basis admin)

6. Then it is informed to the end user/customer/super user about the changes, which have moved to the production server, by CTS process.

These are the process. In summary, what I understand is that if any configuration or customization is required to solve the issue, then the consultant have to work on DEV Client, then the end user will test it in the QA client and after approval the BASIS consultant has to transport it to the PRODUCTION client.

An example:

Tickets in SD can be considered as the problems, which the end user or the employee in the company face while working on R/3. Tickets usually occur during the implementation or after the implementation of the project. There can be numerous problems, which can occur in the production support, and a person who is working in the support has to resolve those tickets in the limited duration, every ticket has the particular deadline alert so your responsibility is to finish it before that deadline.

To begin with, we should give “TICKET” to you for not knowing it.

Here is an eg of a ticket raise:

End user is not able to

1. Create Sales order for a customer from a New plant, since shipping point determination is not happened. (Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further like DELIVERY, BILLING).

He raises a ticket and the priority is set in one of the below:

1. Low 2. Medium 3. High.

Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done for the new plant.

You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the TICKET is closed. What I have given is a small example. You would get some real issues with severity HIGH in your day-day support.
http://yasosap.wordpress.com