Skip to Content
author's profile photo Former Member
Former Member

SPDD & SPAU transport requests missed in the second system upgrade

Hi Friends,

We have completed SAP upgrade on development system and performing the Test system upgrade now.

We wanted to automatically transfer the SPDD & SPAU changes transports to next system upgrade automatically generated from

development system to Test and production systems.

However, in Test system upgrade the SPDD & SPAU changes transport request number inputs to be given in "configuration stage" is missed

and we are now at pre-processing stage, the SUM tool is prompting to adjust the SPDD changes manually.

Can you suggest, at this stage is it possible to go back and give the SPDD transport requests captured in dev system ?

Please see my below observations and suggest.

Below Are the observations :

  • Data and co files are not available in trans directory for DEV system SPDD transport request. However we can see the transport status at SAP level "SIDK900896"
  • File umodauto.lst is not available in previous installation directory "/dataexport/SUM_OLD/abap/bin" and also in trans directory.

Technical Details :

This is SAP CRM upgrade from 5.2 to 7.0 EHP2 using SUM1.0 SP07

Note : We have referred the below

SAP note : 68678, 51046

Thanks, Ganesh

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Jul 08, 2013 at 03:27 PM


    Yes you can do it.

    For that you need to transfer the cofiles and datafiles to the transport directory of the shadow instance.

    If there is no cofile and data file then check the status of the transport request used for SPDD

    Then you will use SAPup to import it into the shadow system

    K900896.SID to /dataexport/SUM_OLD/abap/cofiles

    R900896.SID to /dataexport/SUM_OLD/abap/data

    Follow this SAP Note

    Note 610311 - Importing modification adjustment in second upgrade



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Reagan,

      I think the Data and cofiles will generate after i release them in DEV system.

      these files will be generated at normal transport path right ? (/usr/sap/trans/CRM/cofiles )

      our current Quality shadow system path is

      /dataexport/SUM/abap/cofiles and

      Please suggest on the below two points:

      • Target directory for copying data and cofile is Quality shadow system path right ?.

      • After copying the data and cofiles I need to execute the below commad suggestd in SAP note 68678.

      "./SAPup export TA=SIDK900896 TYPE=SPDD LOG=EXP.LOG REL=720"

      SAP Note 610311 is not applicable to us as our target release is SAP_BASIS is 731.

      Thanks, Ganesh

  • Posted on Jul 08, 2013 at 04:28 PM

    Hello Ganesh

    I believe /dataexport/SUM is the file system you are using for the upgrade.

    If yes then you need to move the cofile and datafile to the /dataexport/SUM/abap/cofiles and /dataexport/SUM/abap/data

    Make sure they have correct ownership and permissions

    su - sidadm

    cd /dataexport/SUM/abap/bin

    ./SAPup importshd SIDK900896

    Once done connect to the shadow instance and call Tx SE38 and run report UPGACTKORR

    The SAP Note is the guide.

    Note 610311 - Importing modification adjustment in second upgrade



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 08, 2013 at 02:08 PM

    Hi Ganesh,

    first of all, have you flagged the SPDD and SPAU transports in the DEV system? You have to release all tasks of the transport but do not release the transport, this will be done by SUM/SAPup.

    I you have done this correct, the umodauto.lst will be modified with the entries of the target release and the name of the transports, like this:

    SPDD 731 SIDK900896

    SPAU 731 SIDK900898

    You will find the umodauto.lst file in /usr/sap/trans/bin not in the SUM directory!

    If you didn't flag the transports, than release them manually and modify the umodauto.lst with the correct entries. But you can also manually type in the transports in SUM for the next upgrade. there is no difference if the umodauto will be read or the manually specified transport. The import will be automatically done by the SUM.

    But please note: Always double check your SPDD and SPAU! Not all systems are 1:1 copies with the same objects.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Jens,

      Thanks for the reply.

      The umodauto.lst is not available in /usr/sap/trans/bin and usr/sap/trans/CRM/bin

      Note :In our landscape the parameter trans_dir is pointing to usr/sap/trans/CRM/bin.

      Agree, we have to release the tasks,

      However any idea why this file is missing here? Is it due to the task was not released during the SPDD update in shadow system .

      Please suggest the below,

      when this file umodauto.lst will get create ? Is the SUM tool create this file during the upgrade?

      Thanks, Ganesh

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.