SAP IS-UT /FI-CA component Upgrade from 600 to 640.
Hi Experts, i have been trying to download the 640 release components of FI_CA & IS-UT from MOPZ but am not able to find the 604 upgrade components in the mopx ABAP section if i tried to go under...
View ArticleRe: Upgrading IS-UT from 600 to 605
Thanks for the post with the Answer kameswar..it realy saved my day...thatx a lot.
View ArticleRe: Table REPOLOAD - START_CALL_SICK after kernel upgrade.
Thanks to all for your support. I've decided to restore the kernel installed by SUM during the upgrade 740 patch 24 (which is not affected from any problem) and continue with follow up activities. As i...
View ArticleRe: Error in phase MAIN_NEWBAS
Has anyone received an update or a fix from SAP? Thanks!Tommye Horton
View ArticleRe: Error in phase MAIN_NEWBAS
No Tommye SAP has moved the request to the development team and they seems to be working on it but no update as of date ThanksDeepak
View ArticleRe: Error in phase MAIN_NEWBAS
It is a bug of SUM SP10 Patch 0 and will be fixed in SUM SP10 Patch 1. The error is in method TRANSITION_START of class CL_CRR_BASE_SCENARIO. The coding try.....endtry.if lv_cur_btc_status =...
View ArticleRe: SAP IS-UT /FI-CA component Upgrade from 600 to 640.
When you create the stack file under "Select Stack-Dependent Files" you have the option to select FI-CA and IS-UT. RegardsRB
View ArticleClik here to view.
Re: Error in phase MAIN_NEWBAS
Hi Sascha, Thank you for the information. I tried the fix you posted above (see attached image), but it did not work for me. I tried restarting the system and SUM, but the error still persists....
View ArticleRe: Error in phase MAIN_NEWBAS
In which phase you got the error? if its in the step before execution then no need to restore the DB just reset the upgrade from SUM and start again with SUM version 9.
View ArticleRe: Error in phase MAIN_NEWBAS
Sunil, the error occured during during the Execution roadmap step (downtime).
View ArticleRe: in 7.3 to 7.31 upgrade the step PREP_INITS/SCANDIR_UPG1 is in running...
HI Deepak, Thanks I have made trans dir and other dvd direcotyr localy mounted and started upgrade it is going fine
View ArticleSevere error(s) occurred in phase MAIN_SHDRUN/TP_ACTION_CP2SINI! in NW7.31
Hi Experts , I am Preprocessing phase of upgrade in our PI7.3 to PI7.31 (ABAP+ JAVA) stack upgrade in step MAIN_SHDRUN/TP_ACTION_CP2SINI! i am facing an error .. I have repeated phase couple of time...
View ArticleRe: in 7.3 to 7.31 upgrade the step PREP_INITS/SCANDIR_UPG1 is in running...
Hi Yogesh, As the issue is resolved now, you may close this thread. Regards,Deepak Kori
View ArticleRe: Severe error(s) occurred in phase MAIN_SHDRUN/TP_ACTION_CP2SINI! in NW7.31
Hi Yogesh, Refer below SAP notes1730439 - Inconsistent DDIC objects after Transport of Bus.Functions1763094 - SFW: wrong causing object in SFW worklistHope this helps.Regards,Deepak Kori
View ArticleRe: Severe error(s) occurred in phase MAIN_SHDRUN/TP_ACTION_CP2SINI! in NW7.31
HelloFirst update the TP and R3trans filesWhat do these files say ?/usr/sap/SUM/abap/log/SAPEBBF731.XS1TP00.ECO RegardsRB
View ArticleRe: Severe error(s) occurred in phase MAIN_SHDRUN/TP_ACTION_CP2SINI! in NW7.31
Hi Benjamin, I have done that and tried again but no luck i am sending output of that file you said.. Please check output meanwhile working solution suggested by deepak .. 3 ETW685Xstart copying of...
View ArticleRe: Severe error(s) occurred in phase MAIN_SHDRUN/TP_ACTION_CP2SINI! in NW7.31
Hi Deepak, Looks like this can help to resolve issue but when i am going there to apply it though snote it says you can not do that becuase upgrade is running .. Any solution on this . RegardsYogesh
View ArticleRe: Severe error(s) occurred in phase MAIN_SHDRUN/TP_ACTION_CP2SINI! in NW7.31
You will not be able to fix this issue with the help of the SAP note 1314178 - Inconsistency in runtime object: Table with buffered view as it is not valid for your release and doesn't bring any...
View ArticleRe: Severe error(s) occurred in phase MAIN_SHDRUN/TP_ACTION_CP2SINI! in NW7.31
Thanks for reply Both this issue is a BUGS in SUM SP10 , sap going to provide correction on it soon, meanwhile they asked me to use SUM SP09 .. THanksRegardsYogesh
View Article