on 07-08-2013 1:04 PM
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 :
Technical Details :
This is SAP CRM upgrade from 5.2 to 7.0 EHP2 using SUM1.0 SP07
Note : We have referred the below
http://scn.sap.com/thread/1678601
SAP note : 68678, 51046
Thanks, Ganesh
Hello
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
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
/dataexport/SUM/abap/data
Please suggest on the below two points:
"./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
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
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am some object in sap abap.. Wanted to know which I have to reset original. Or something else.. If anyone is ready to help me kindly tell me
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for coming to SAP Community for answers. Please post your question as a new question here:
https://answers.sap.com/questions/ask.htmlSince you're new in asking questions here, check out ourtutorial about asking and answering questions (if you haven't already), as it provides tips for preparing questions more effectively, that draw responses from our members. Please note, that your post here won't be answered.
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.
Regards,
Jens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.