Skip to Content
avatar image
Former Member

Transport request SPDD and SPAU


I just can't understand the manual..

We have upgraded our dev system, made the changes in SPDD and SPAU.

In se09 the tasks are released but not the requests, right?

In the /usr/sap/DEV/EHPI/abap/bin there is a file, umodstat.lst


SPDD 701 000002 000000 0

SPAU 701 000160 000000 0

This can't be the transport requests?? Meaning the request numbers are not in the file..?

When I'm now in progress of upgrade TST I get the question including transport request from previous upgrade, the installation program looks for the file umodstat.lst in /usr/sap/trans/bin - but the file is not there ofcourse.

Should I manually move the file from /usr/sap/DEV/EHPI/abap/bin to /usr/sap/trans/bin??

Or should i release the request in dev-system, will the file then be created in /usr/sap/trans/bin ?

I also have the opportunity to manually type request number, but when the request are not released it can't be found ofcourse.

The manual says,

"You must release the tasks of the SPDD transport request. You must not release this transport request; instead you must flag it for transport in transaction SPDD."

I just don't understand..

Please advice!

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • May 06, 2010 at 05:34 AM

    Dear Carl,

    It is important that the transport in transactions SPAU or SPDD is

    selected in each case using the "Select for transport" button and that

    the individual tasks are released after the comparison. You must not

    release the request itself as R3up does this automatically at the end of

    the upgrade.

    If you want to use adjustment transports for SPDD or SPAU from the first

    upgrade in a system landscape, you must include the same Support

    Packages in all upgrades of the 'receiving systems' and the Support

    Package level of the source release must be the same.

    The PREPARE then checks whether or not the specified adjustment

    transports 'match' the objects to be reconciled that were found in the

    relevant system. However, a 100% match is very rare, so requests that do

    not match perfectly can also be used to facilitate the adjustment in the

    subsequent systems.

    If there is no central transport directory for upgrade predecessor and

    successor systems, Note 51046 enables you to use this function.

    Kindly refer the following SAP Notes for detailed understanding on this:

    610311 - Importing modification adjustment in second upgrade

    556992 - FAQ: Upgrade PREPARE

    51046 - Transport transfer; Central transport directory

    I hope this helps you out.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      Yes I did, I don't have the exactly errormessage..but it was something about "not started" or "not running". My guess was that I had to have the installationprogram up and running to be able to manually do the trick? I have started to clean up my system, due to lack of discspace. Therefore I'm not able to start the installation program again, there are some directories and files missing since the installation.

      We have a working transportsystem/landscape.

      I've just finished a second system, with the same issue. So I guess we're doing something wrong. I've sent a question about this to SAP.

      In spdd we select the two tasks (one spau and one spdd) in "select for transport", but the EHPI doesn't release the requests and the file umodauto.lst is not created. This new installation went just fine, so my thoughts about from the last run is not valid. That installation had a lot of problems and we had to restart the system a couple of times.

      Btw, anyone know what's the difference between "OCS" and "Upgrade" in the "select for transport" menu?

      Thanks for all your help!


  • avatar image
    Former Member
    May 10, 2010 at 02:19 PM

    Hi Carl,

    we have to make sure that the developers has to mark the Transport request as select for transport in SPDD and SPAU transaction once they have completed the modifications.

    the thing they have to mark the transport request with select for transport option as imentioned above in SPDD and SPAU transaction. u need not release the transport request becasuse SAPup will release the request after the upgrade automatically.

    then the entries will be created in Umodauto.lst file like the below in the direcotry /usr/sap/put/bin/umodauto.lst file.

    SPDD 701 000002 000000 0

    SPAU 701 000160 000000 0

    for your second upgrade u need to include the SPDD request in PREPARE so that u need no to modify the SPDD objects again in second system. it will save the lot of time for the second and third system upgrade.

    you can transport the SPAU request after upgrade also or in middle of upgrade as well....

    Inclusion process in Second upgrade:

    U have to copy the cofiles and datafiles of the SPDD request to the second system /usr/sap/trans/cofiles and /usr/sap/trans/datafiles if you are not using common buffer... if you are using common trans directory then no need.

    copy the Umodauto.lst file from DEV system to quality /usr/sap/put/bin and /usr/sap/trans/bin.

    then you quality system prepare will identify the SPDD and SPAU requests automatically and ask to include the same in upgrade.

    hope the above suggestions will clear you queries.. personally i would like to include only SPDD request in upgrade and i will transport the SPAU request later. but you include the both it's no harm including both the requests with upgrade.

    Prerequisites to include SPDD and SPAU:

    1) the trarget support pack levels should be same in all the systems.

    Conclusion: if your SPDD and SPAU requests are not create proprly then please dont use in second system. create new SPDD and SPAU requests this time make sure to create proper request types for the Production system upgrade.


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Srini,

      We are upgrading from 4.7 to ECC. Once we do SPDD, SPAU adjustments in Dev, keep them in one transport request. While doing upgrade in Quality, we will move the transport request to quality to do the adjustments automatically. But if I find new object which are modified during upgrade and any new objects are flagged during Quality upgrade, how do we clear it?? Because with transport request we will clear n objects, but n+1th object should be handled somehow during Quality upgrade. How can we take care of those cases??

      Upgrade experts, I need your help ASAP. Kindly help me out.