SAP Library - Find your answers

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