ECC 6.0 Upgrade Issue !!

Dear All,
I have come across a FM MSQ_READ_TABLE_STATISTICS_HIST which exist in SAP 4.6 , but not in ECC6.0.
Secondly I am not able to get the replacement of FM TZ_SYSTEM_TO_LOCAL.
Can anyone tell me what are the replacments for the above Function Modules.
Thanks and Regards,
Rachit Khanna

Hi Khanna,
i dont' have system for 4.6C in ECC u can try like readstastics* then search for the function modules which is relacement of u r FM.
For the FM TZ_SYSTEM_TO_LOCAL in this Fm documentation the replacement for this use the 'CONVERT' statement.This function functionality i is the system time is also in locaal time zone.
Hope this may help you.
Thanks,

Similar Messages

4.6C to ECC 6.0 upgrade - Issue with Virsa Compliance Calibrator

The issue is that phase IS_SELECT during the PREPARE is not detecting VIRSA as an add-on. This of course will result in VIRSA not being upgraded and the system will be unstable ( note 989368 ). Also, I can't choose to delete the add-on either.
We installed the compliance calibrator before SAP purchased VIRSA. So, the tool was installed through transports, not SAINT. I assume this is why phase IS_SELECT is not seeing the tool.
Any ideas?
-Scott

Received a reply from SAP. Since VIRSA was installed through STMS the IS_SELECT phase will not see the add-on. I had to do the ECC 6 upgrade as normal and then install VIRSA 4.0 for SAP 700 systems through SAINT.
I had to clear SPDD and SPAU as much as possible for /VIRSA/* objects. However, there were six objects I could not clear. This did not cause any issues.
Notes 1006083 and 985617 are needed for this procedure.
Thanks for all the suggestions.
-Scott

SAP 4.6C to ECC 6.0 Upgrade.Issues in Workflows

Hi Gurus
Can anyone please enumerate the list of issues likely to arise
when sap is upgraded from 4.6C to ECC 6.0.

There is a wonderfule document in SDN related to upgrade from 4.6 to ECC 6.0. Please check that it is self explanatory and is of great help.
Check this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/103b1a61-294f-2a10-6491-9827479d0bf1
Thanks
Arghadip
Edited by: Arghadip Kar on Jul 23, 2008 12:53 PM

ECC 6.0 EHP-4 upgrade Issue in phase MAIN SHDRUN/ALTNTAB FILL were negative

Hi Basis Expert,
while doing ECC 6.0 EHP-4 Upgrade in MAIN_SHDRUN/ALTNTAB_FILL phase we are getting the following issue please help us.
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: BATCH JOB RDDNT2MT FAILED: Error(s) found in the log(s), accumulated in "ALTNTFI.ELG".
We check the shadow instance is up and we can log in to the system. Check ST22 and SM21 notice no error.
Check the JOB RDDNT2MT (SM37) successfully running and all the job finish without any error.
Hope anybody can share a bit your experience on this issue. we try search the note and find the forum but no luck.
Thanks

Hi,
> 2EETG011 "No shadow system""(environment parameter)""auth_shadow_upgrade"
> 2EETG011 "No shadow system""DB-connect not against shadow tables !"
>
It looks from your log that shadow system is not able to connect to database. Please check your shadow system. Check below link as well:
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/ecc-6-upgrade-issue-in-phase-altntab_fill-1556272
Thanks
Sunny
Edited by: Sunny Pahuja on Oct 15, 2010 1:27 PM

Screens not working in ECC 6 after upgradation from 4.6c.

Hi,
The custom developed screens which where developed in 4.6c version is not working properly in ECC 6 after upgradation.Do i have to make any more changes for this .? If anyone have an idea please help me in this issue.The custom developed things are an extended functionality we have done to r/3.
Regards,
jinesh kumar c.

Hi,
Check the Transportatation Logs in STMS for the programs/screens and check whether they are successfully tranported or not?
Because some times we get Dynpro errors for transportation of the screens.
Reward if useful.
regards,
Anji

ST-PI upgrade issue in IS_SELECT

I am running PREPARE on a 4.6C (Linux/DB2) > ECC 6.0 upgrade and have recieved the warning that 'Add-on ST-PI is toohigh for this upgrade".
I have downloaded the 'ST-PI 2008_1_710' patches (SAPKITLRE1, SAPKITLRE2, SAPKITLRE3) into /usr/sap/put and used SAPCAR to extract them to the EPS/in box.
While running the the IS_SELECT phase I select the 'upgrade from Saint packages' and the upgrade program indicates that it reads the EPS/in directory but does not find any matching SAINT package.
What is the correct procedure?
I am running SAPup version 7.00/3, build 25.024.

This:
"Looks like 1 important file is missing
2008_1_700 KITLRDG.CAR SAPKITLRDG for 2008 ST-PI Target release
or
2005_1_700 KITLQIG.CAR are to be placed in EPS/in and select
"Upgrade with SAINT Package".
https://service.sap.com/sap/support/notes/1228899
Regards
Srikanth M
Seemed to have worked.
I am again unfortunately stuck with the the same issue with the ST -A/PI add on.
I have a source release of 01M_R3_46C and does not recognize the 01M_ECC600 ,01M_BCO700 , 01M_BCO710 packages I extracted.

Error in WBS Element Hierarchy load after ECC 6.0 Upgrade

Hi All,
After ECC 6.0 Upgrade in R/3, we are doing test load in a Test server. While doing, we have encountered an issue with 0WBS_ELEMENT Hierarchy load. The message in the monitor is like below.
"Node ID 00014240 has not been included in the hierarchy
Message no. RH207"
When I run the same hierarchy in another system which is not upgraded , it works fine.
Anybody has faced similar kind of issues and can throw some light on this issue?
Thanks,
Mohan

Try activating the Heirarchy in R/3 and re-trigger the load, error is very specific to structure of the hierarchy. there is a possibility that this Hierarcy could have got inconsistent after the upgrade.
Thanks,
Amit

ECC 6.0 UPGRADE - BW 3.10

We are planning to upgrade our source system from 4.6C to ECC 6.0. We are on BW 3.10 ( But planning to upgrade to BI 7.0 once after ECC 6.0 upgrade)
Would like to know,
1. Do we need apply any plug-in requirements to accommodate the ECC 6.0 compatibility?
2. Will the existing BW 3.10 work without any issue with ECC 6.0?
( We are not going to do any change with new Business content available with ECC 6.0)
3. What are the other precautions, we need to take in order to work BW 3.10 with ECC 6.0?
Advance Thanks.

refer replies here:
Re: ECC 6.0 Upgrade with BW 3.5

ECC 6.0 Upgrade from 4.7 - EDI Interfaces

Hi Gurus,
Need your inputs on what are the precautions to be taken during ECC 6.0 Upgrade related to EDI Interfaces. with SAP upgrading from 4.7 to ECC 6.0, do you see any precautions need to be taken considering the middle ware involvement. Also, is there any changes in IDOC Structures in ECC 6.0 which my cause issues related mapping with middleware.
Please suggest.
Thanks & Regards,
C.L. Narasimhan "CLN"

Hi,
generally, a release upgrade, delivers new idoc/message types or new releases of existing idoc/message types.
So, taking this in mind, you shouldn't have problems for the mapping of the messages, because the versions of the basic idoc, once released, cannot be changed.
You might have some application problems related to the inbound interfaces, but this is part of the game...the testing phase will highlight whether the problem exists.
A known problem is that the upgrade removes all the customer specific entries in the system table EDIFCT.
Further details are provided in the OSS note [https://service.sap.com/sap/support/notes/865142]
Regards,
Andrea

Upgrade issues OBIEE 10g to 11g along with OBIA upgrade

Hi,
I have to upgrade OBIEE 10.1.3.4.1 to OBIEE 11.1.1.5 along with OBIA 7.9.6.1 to 7.9.6.5(Informatica 8.6.1 to 9.0.1) at my client location and I have very little knowledge on it. and want to know/have help documents for upgrade.
And if anyone in the forums involved in upgrade please list the errors/issues occured during upgrade and after upgrade.
1. OBIEE 10g to 11g upgrade issues??
2. OBIA OBIA 7.9.6.1 to 7.9.6.5 upgrade issues along with 10g to 11g??
3. Informatica 8.6.1 to 9.0.1 upgrade issues??
4. DAC upgrade issues??
any response for my questions is appreciated.
Thanks
Jay.
Edited by: Jay on Apr 11, 2012 9:11 AM

HI Jay,
We cannot explained thread list here, If you get any errors plz post me,will try to help out.
This is oracle document link - This document has given step by step with screen shots upgration for 10g to 11g ,Please refer the below link.
http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/upgrade/upgrade_to_11g.htm
http://obieemanu.blogspot.in/2011/05/rpd-upgration-from-10g-to-11g.html
http://docs.oracle.com/cd/E21764_01/upgrade.1111/e10125/ua_command_line.htm#ASMAS149
Award points it is useful.
Thanks,
satya

Report generation toolkit upgrade issues

I have created multiple vi's in that utilize the previous report generation toolkits specifically using the Generate Report Get Data to Modify.vi and the Generate Report Set Modified Data.vi. Obviously the report reference has now changed in 8.6's version of the report generation toolkit and these vi's do not exist in the 8.6 library anymore. What vi's do I need to replace these functions with to make this code work. Can anyone tell me what the work around is to solving this problem. This is a picture of the code.
BJD1613
Lead Test Tools Development Engineer
Philips Respironics
Certified LV Architect / Instructor
Attachments:
code.JPG ‏92 KB

Hi BJD1613,
The Report Generation VIs on the LabVIEW Palettes mutate properly. However, you may run into upgrade issues if VIs distributed with LabVIEW, but not available in the Palettes are used in the code. Hence, I would caution against using them for the same reason.
In this case, the specific references do exist in the report generation classes; however, since they are private, they cannot be accessed by VIs outside the respective classes. A temporary workaround for now is mentioned in the following KB 4OOCSJ4M Getting References in Report Generation Toolkit 1.1.3 with LabVIEW 8.6.
This was reported to R&D (CAR# 123064) for further investigation

SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

Basis Gurus
   I am working on upgrade from R/3 4.6C to ECC 6.0.
ECC 6.0 upgrade completed( still in non Unicode). Now I am in the process of Unicode conversion.
I have used following methods for the upgrade.
1. Combined Upgrade & Unicode conversion(CU & UC)
2. Resource minimized( as I am doing it in Sandbox).
As I understand I need to perform the DB export and Import now for the unicode conversion.
According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
and then install Unicode system and import the same data file.
My understanding was, when I choose, Resource minimized, I need to run Export and import
in the same system.
Can you please help me , whether I need another Unicode system for import ??
Graham

Hi,
Dont get confused with upg strategy and unicode conversion.
In general Upgrade strategy (either downtime-minimized/resource minimized)
In unicode conversion you have export/import(exp/imp) of data concept
In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
It can be done in 2 ways.
If you dont have addtional server for unicode conversion
       1)you can either do exp on same hardware and take bakup and do import using the exp dump.
       2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
Hope this is clear.
Regards,
Vamshi.

EHP Upgrade Issue - Java Stack

Hi,
Our Source System at NW 7.0 SP13 and we are upgrading the system to EHP1 SP03.
Upgrade failed at Downtime > DEPLOY_ONLINE_DEPL phase.
Error log:
Sep 9, 2009 10:11:51 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Sep 9, 2009 10:11:51 PM [Error]:             com.sap.sdt.jspm.unattended.RequestController.addContextInfo(RequestController.java:178) [Thread[main,5,main]]: Deployment of queue sapjup-queue completed with error
JSPM version is 7.01.3.0.15. Current JSPM log directory is /usr/sap/XPD/JC00/j2ee/JSPM/log/log_2009_09_09_16_09_42.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.SAPJupJSPMRapiAdapter.createAndLogRapiException(SAPJupJSPMRapiAdapter.java:698) [Thread[main,5,main]]: The deployment of the queue failed.
Sep 9, 2009 10:11:51 PM [Error]: com.sap.sdt.sapjup.tools.sapjupjspm.deploy.SAPJupJSPMDeployer.deployList(SAPJupJSPMDeployer.java:68) [Thread[main,5,main]]: Could not execute deployment of stack file /usr/sap/trans/EPS/in/XPD.xml.
Sep 9, 2009 10:11:51 PM [Error]:      com.sap.sdt.j2ee.phases.PhaseTypeDeploymentManager.execute(PhaseTypeDeploymentManager.java:519) [Thread[main,5,main]]: Error while executing DeploymentManager phase with action deploySlot. Check the log files for the specified action.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase UPGRADE/DEPLOYMENT_BASED_UPGRADE/DEPLOY_ONLINE_DEPL has been completed.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2009/09/09 22:09:42.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2009/09/09 22:11:51.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:02:08.248.
Sep 9, 2009 10:11:51 PM [Info]:                         com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
I went through the following link , proceeded with option 2, But still getting same error.
Portal Upgrade Issue
Please advise the resolution for the issue I have.
Thanks in advance
Regards
Srinivas
Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM
Edited by: Srinivas Dasari on Sep 10, 2009 5:48 AM

Issue resolved

ECC-600 EHP4 upgrade with VIRSAHR 520 700 - PREP_EXTENSION/ADDON_QCALC

Hi
We are getting following error at phase PREP_EXTENSION/ADDON_QCALC in the ECC 6.0 upgrade:
3 ETN256 You want to install the following add-on components:
3 ETN248 Component: "VIRSAHR" rel. "520_700", Support Package
level: "0" (component type "A")
3 ETN248 Component: "VIRSANH" rel. "520_700", Support Package
level: "0" (component type "A")
2 ETN085X"2. Adding Add-on Installation Queue" " " " " " "
3 ETN262 Calculating queue part for add-on "VIRSAHR" rel. "520_700"
3 ETN490 Use the Add-On installation package "SAPK-523EXINVIRSAHR"
(type &4"AOX") for Add-On &2"VIRSAHR" rel.&3"520_700"
3 ETN245 The following import prerequisites of OCS Package "SAPK-
523EXINVIRSAHR" have not been met:
3 ETN264 In the (alternatively) Requirement set "01":
3WETN491 Required software component "SAP_HR" rel."600" is not installed2WETN543 OCS package "SAPK-523EXINVIRSAHR" does not match the current
software component vector
1 ETN214X."**************************************************"
We have alreacy checked note 1002147, which clearly states that we have to include SAPK-523EXINVIRSAHR in the upgrade. SAP_HR is part of the upgrade.
We have included SAP_HR and other Support Package as per the queue generated by Solution Manager, but we did not include VIRSAHR & VIRSANH Packages until we got to this phase. We then included these support packages in eps\in directory, but we are now getting this error now.
Any ideas?
Regards
Chandu

Hi
This is what the solution provided by SAP Support:
Quote:
we have finally found the problem, it's a bug in the package upload
functionality used by the upgrade. The consequence of this bug is that
Support Packages whose EPS files (.PAT files) have a certain string in
the name, namely the string 0000000 after the _ and before .PAT
extension, are not properly uploaded to the ABAP system and hence are
not visible or known to the upgrade.
This bug will be fixed in the next upgrade tool fix, but in the meantimeyou can use the following workaround:
Check your EPS/in directory after the CAR/SAR Archives of the SPs are
extracted and rename all .PAT and .ATT files, which have a name like
*_0000000.PAT (or *_0000000.ATT), by changing the string 0000000 to
9000000. For example, for the VIRSANH SP SAPK-52302INVIRSANH rename the
file VS30020106486_0000000.PAT to VS30020106486_9000000.PAT
Afterwards, the upgrade will upload the informations about the SP
properly and the SP can be included into the upgrade.
Files:
31/01/2007 07:32 329 VS30020106486_0000000.ATT
31/01/2007 07:32 554,073 VS30020106486_0000000.PAT
If these two files are renamed to e.g.
VS30020106486_9000000.ATT
VS30020106486_9000000.PAT
the affected VIRSANH SP2 is uploaded correctly by the upgrade
functionality and the SP inclusion of the VIRSANH SPs works.
Sorry, as of now I cannot promise you a date when the tool fix will be
available. I have found this bug only today in the evening (german time)and will discuss this with the responsible colleagues tomorrow.
Afterwards, I will know more...
Unquote:
Hope this helps. We have decided against upgrading to 530_700 as it will involve upgrading GRC system and also new version has lot of new functionalities, which we like explore it after the ECC upgrade.
Also, I would not suggest deleting VIRSAHR as all the config and customising done for VIRSAHR will be lost.
Regards
Chandu
Edited by: Chandu Cheeti on Jan 17, 2010 11:19 AM

Upgrade issues list needed

Hi,
We're currently on 4.6b and going to upgrade to ECC6 with unicode I'm trying to compile a list point taken care converting to unicode from ABAP technical point of view. Does anyone have such a list?
Some points i shortlisted are :
1) Use GUI_UPLOAD and GUI_DOWNLOAD rather than WS_UPLOAD and WS_DOWNLOAD.
2) Structures or table headers that contain non-character data need to be identical when moving, comparing, selecting into, updating from, etc.
3) OPEN DATASET filename IN TEXT MODE FOR INPUT ENCODING DEFAULT.
I know there are others. Any help would be appreciated.
aRs

Check the below links
http://www.sapfans.com/forums/viewtopic.php?t=268386&highlight=upgrade+issues
http://www.sapfans.com/forums/viewtopic.php?t=263434&highlight=upgrade+issues
http://www.sapfans.com/forums/viewtopic.php?t=261051&highlight=upgrade+issues
http://www.sapfans.com/forums/viewtopic.php?t=253316&highlight=upgrade+issues

ECC 6.0 Upgrade Issue !!

Similar Messages

Maybe you are looking for