SPAU/SPDD and SUM

[wjvanveen]

We are using SUM to do the upgrade.

In the SUM tool, you have to specify the transports that hold the results after executing SPDD and SPAU.

Then SUM will automatically use this transports during the upgrade of the target system.

The original SPDD/SPAU transport is still on the development system, hanging there.

Also it is hard to see if the content of the SPDD/SPAU has been imported.

The SUM logging shows some info, so it is different from the other/normal transports with import logging.

What is the procedure for these transports that hold stuff from SPDD/SPAU?

- remove transport?

- just remove transport from import queue and leave it there?

- still move it over across the landscape to production?

- just leave it?

[former_member265124 · Accepted solution]

Hi Walter,

We need to check this issue directly in your system, so please raise an incident to SAP under

BC-UPG-TLS-TLA component to analyse the issue.

Thank you.

Regards,

Maha

[wjvanveen]

I probably did not state my question correctly.

After golive (upgrade) on all target systems (also production), we still have two transport requests (SPDD/SPAU) that are available on our development system. The content of these transport requests has already been imported on the target systems (also production) via the SUM tool during upgrade on the target systems. These transports were created on the shadow system.

These two transport requests have been released/exported on the development system, but have never been imported into the target systems. Which sounds logical as the content has already been imported via the SUM tool.

I would expect, to avoid issues/confusion, that we need to remove these transports request.

[former_member265124]

Hi Walter,

Can you check the following documents which gives step-by-step procedure to mark the SPDD and SPAU transport request for next upgrade:

http://scn.sap.com/docs/DOC-49584

http://scn.sap.com/docs/DOC-44106

Also, in PREP_INTEGRATION/ADJUSTPRP phase, SUM tool would have prompted for SPDD and SPAU transport request.

To automatically maintain your modifications in your system during the procedure, the program searches in file /usr/sap/trans/bin/umodauto.lst for transport requests from previous update runs.

Kindly check the /usr/sap/trans/bin/umodauto.lst file to check if the SPDD and SPAU transport requests are present.

Thank you.

Regards,

Maha

[wjvanveen]

Thanks for the comments, but after SUM is finished, I am still stuck with SPDD/SPAU transports on my development environment. These transports are never transported, but just remain there as a sitting duck.

[former_member265124]

Hi Walter,

For the SPDD and SPAU handling during upgrade, please refer to the SAP KBA:

1970888 - HowTo:SPDD/SPAU handling during the Update/Upgrade

Thank you.

Regards,

Maha

[Sriram2009]

Hi

What are the steps which your are followed in development system, in the same way you can follow the other systems in your landscape, during the phase SPDD / SPAU you have to import the transport request in the target system.

Regards

SS

[wjvanveen]

Hi,

In the 'old' way:

- Do upgrade on DEV and create TR for SPDD and SPAU

- Release TR for SPDD and SPAU

- Do upgrade on TST and import TR for SPDD and SPAU

- etc.

In the 'new' way:

- Do upgrade on DEV with SUM and create TR for SPDD and SPAU

- Release TR for SPDD and SPAU

- Do upgrade on TST with SUM and let SUM import the content of SPDD and SPAU in the shadow instance. The 'original' TR for SPDD and SPAU is NOT imported anymore on TST, ACC, PRD.

Regards,

Walter

[Sriram2009]

Hi Walter

In Dev system are your getting two time SPDD / SPAU  (One is original & shadow instance) ?

Could you refer the link about the SUM steps

SAPBasisphilosopher: Different Phases of Upgrade :SUM Tool

Regards

SS