Information on impact on interfaces due to upgrade from 4.7 to ECC 6.0

Hi friends,
We are upgrading from 4.7 to ECC 6.0. We have some interfaces with the SAP system in our current version.I need information on which of these interfaces will be affected due to Upgrade of the system to ECC 6.0
Mentioned below is the list
SAP R/3 --- CRM 5.0
SAP R/3 --- Xi PAY
SAP R/3 --- Vertex
SAP R/3 --- TEKRF
SAP R/3 --- Virsa
SAP R/3 --- WTX
SAP R/3 --- SOLMAN
It would be really helpful if you can just provide the initial impact analysis for these interfaces due to upgrade.Points will be rewarded.
Thank in advance.
Regards,
Pawan.

Hi
there are several oss-notes available which explain how to transfer your text customizing to the new procedure. This happens if you are uppgrading from a release 4.6c or lower. If you are already in 4.7, there should be no problem with text determination.
Regards
Rauno

Similar Messages

Impact on Custom / Std IDOC after upgrading from 4.7 to ECC 6.0

I am in Upgrade project (4.7 to ECC 6.0).
What will be the impact of the existing Custom and Std IDOC after upgrading from 4.7 to ECC 6.0 and if any impact, what are precautionary steps to be taken to work as it is.
Will there be any Impact on ALE also ?
Thanks & Regards
Khaleel

closed.

Impact of ERP Upgrade from 4.6C to ECC

Hi All,
What is the impact and variations/additons with Impact of ERP Upgrade from 4.6C to ECC from Varinat configuration side.
BR,
Krishna

hi krishna,
You may loose some of the variants becasue of changes happened during upg for ECC600.I have faced certain problems.
I know in the upgrade there is a phase(RSUVAINT(2) not sure) which does a backup of all variants and restores in the end.
regards,
vamshi.

ISU upgrade from 4.6C to ECC 6.0 (CIC)

Hello there
We are currently going for an upgrade from 4.6C to ECC 6.0
Can anyone of you provide some insight on whether the frontoffice and other configuration in 4.6C have any kind of impact on ECC 6.0? Basically I can see that there are new functionalities in ECC6.0 for CIC . But will the current config lin 4.6C like action box , move in/out processes, owner allocation etc will be impacted after the upgrade?
Thanks
Gautam

Hi Gothic,
We are also planning to upgrade this month from 4.6C to ECC 6.0. It would be very nicce if we can share the information and the experineces.
We will do the upgrade in a pilot system.
We will have a new hardware with windows server 2003 64 bit and oracle oracle 10.2.0.2.0. than we will install oracle and SAP 4.6C and after that we want to export the Database from the production system to the pilot system. after that we upgrade the pilot system to ECC 6.0 to test first.
I do not know if there is an easyer way to do the upgrade or at least the test. Maybe a homogenouse system copy...?
Best regards
Atik

Top-Down Distribution - tcode KE28 (release upgrade from 4.6 to ECC 6.0)

All,
we are performing a release upgrade from 4.6 to ECC 6.0 and we have a problem with the tcode KE28.
The variant already set up in the system don't match with the selection fields present in the screen, and the following message is shown:
Message no. KG346
The variant does not adhere to the current Customizing setup
We have saved the variant again, and no problem are present, but the error message refers also to Customizing setup.
Is there a section in the Customizing where it is possible set up the field to show in the initial screen or the new fields (All Valuation Views, Legal Valuation View and Profit Center Valuation View) are due to the release upgrade?
If yes, do you know the transaction/path?
Thanks in advance for your collaboration.
Regards,
Jody Mancini.

Hi Satish,
Now i am sending some URL for Functional upgrade
May be those are all useful toyou
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/transactionsChangedinECC6.0
http://solutionbrowser.erp.sap.fmpmedia.com/Default.aspx
https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/
Regards
Surya

What are the key points to beconsider while upgrading from 4.7 to ECC 6.0

hai
What are the key points to beconsider while upgrading from 4.7 to ECC 6.0
please provide sufficient material
points will be rewarded
regards
v.sridhar

Hi Sridhar,
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional perspective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
After opening the site, please select the Source Release Version which is 4.6 b Then Select the Target Release Version which is "mySAP ERP 2005" or ECC 6.0
Select the Solution Area like Financials, Human Capital Management, Sales....
Select module like MM, PP, SD, and QM.....
Click on Search
then it displays the Release Version and the Delta Functionality. Which can be downloaded to a word document if required.
And also check the release notes of ECC 6.0 in service.sap.com.
When you are upgrading from 4.6C to ECC6
Nothing major, follow the same process you'd follow if you were updating PI service packs in R/3 or enhancing data sources. Empty queues in RSA7 and lbwq. Also empty setup tables through lbwg as the upgrade doesn't like it if these tables contain data. This is all on the R/3 side (although you empty RSA7 by running each delta TWICE in BW).
To transfer queues from lbwq to rsa7, execute jobs through LO cockpit (lbwe).
Some of your data sources could also be using sm13 instead of lbwq, so do check it out as well.
For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't require solution manager key. It only having ABAP stack.
4.6C supports NONUNICODE.
Major difference is ECC6 is netwear product having WASJAVA+ABAP
secondly support unicode apart from this we have other diff. you can get form master guide from service.sap.com/instguides.
Please go through the link that is shown here and if there is any doubts then feel free to ask.
Major difference is ECC6 is net weaver product having WASJAVA+ABAP
secondly support Unicode apart from this we have other diff. you can get from master guide from service.sap.com/instguides
For installing ECC 6.0 you required a solution manager key. With out solution manager key you cannot install ECC6.0.
For ECC 6.0 is called net weaver component here you have ABAP+JAVA stack.
ECC6.0 supports UNCODE.
For installing 4.6 you don't required solution manager key. It only having ABAP stack.
4.6C supports NONUNICODE.
Please also Refer sdn thread and make a small search where u can find lot of information Reg this
olution Browser would give the differences (Features):
http://solutionbrowser.erp.sap.fmpmedia.com/ Give source and target versions.
Release Info:
ECC 6.0:
http://help.sap.com/saphelp_erp2005/helpdata/en/43/68805bb88f297ee10000000a422035/frameset.htm
Refer below and search for posts on this topic on sdn
There are so many differences between the version in different objects
I
These are the some of the settings that are differed in the two versions and in that two objects
Please visit the following links:
http://service.sap.com/erp
http://solutionbrowser.erp.sap.fmpmedia.com/ (Functional prespective)
http://service.sap.com/instguides --> mySAP Business Suite Applications --> mySAP ERP --> mySAP ERP 2005 --> Upgrade
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/LOVC/LOVC.pdf
For Functionality Differences pls refer to the below site -
http://solutionbrowser.erp.sap.fmpmedia.com/
Upgrade from 4.6c to 6.0 ECC
upgrade from 4.7 to ecc 6.0
Please Do Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Table Enhancement Category during upgrade from 4.7 to ECC 6.0

When our sandbox was upgraded from 4.7 to ECC 6.0, Basis had the ABAP developers change the Enhancement Category on about 400 tables, some of which were custom tables. The enhancement category was previously u2018not classifiedu2019 on these tables.
Is this really necessary? Has anyone not changed the enhancement categories on tables that were flagged during the upgrade? Also, what happens if we select the wrong enhancement category?

Jane,
This is what SAP says,
Short Text
Enhancement Category Selection
Definition
Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
Cannot be enhanced
The structure must not be enhanced.
Can be enhanced or character type
All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
Can be enhanced or character-type or numeric
The structure and its enhancement must not contain any deep data types (tables, references, strings).
Can be enhanced in any way
The structure and its enhancement may contain components whose data type can be of any type.
Not classified
This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

Steps to follow in Upgrade from 4.7 to ECC 6.0

Hi ,
As part of Upgrade from 4.7 to ECC 6.0 , Basis team completed Prepare module.
Now Prepare module report says there are some modifications need to be done .
Do i need to make the changes to the adjustments populated in SPDD/ SPAU transaction code before basis team goes for Upgrade ?
If changes are applied to the modifications populated in SPDD / SPAU. How i need to transport these objects ?
Please let me know the steps need to take in transport of these objects .
Cheers,
Reddy

Dear,
Transaction SPDD allows you to adjust modifications to ABAP Dictionary objects during an upgrade, the upgrade will stop at the begin of ACT_700 phase, so you can logon to shadow instance and perform the adjustments in SPDD.
About transaction SPAU that allows you to adjust programs, function modules, screens, interfaces, documentation, and text elements after an upgrade.
You have the option to include the SPDD request from previous upgrade,
The PREPARE includes the ADJUSTPRP phase for this purpose. In this
phase, the system searches the global transport directory for comparison
requests from previous upgrades and offers these for inclusion in the
upgrade. If you do not have this request, you may go ahead with the upgrade
and the proceed with the SPDD / SPAU adjustments during the upgrade.
Please refer to the following SAP Notes for more details:
68678 Exporting modification adjustment for 2nd upgrade
610311 Importing a modification adjustment in 2nd upgrade
124522 Importing a modification adjustment in 2nd upgrade
I hope this helps.
Lucio Rodrigues

Requirements for upgradation from 4.7 to ECC 6.0

Hi Guru's,
Can anybody explain what are the steps required for upgradation from 4.7 to ECC 6.0, technically and functionally. If any body have documents regarding the same, please share.Full marks will be awarded.thanx in advance....

Hi
You have to aware of all related program like BDC's , Screens related errors and all dictionary related problems.
Some function modules may become obsolete, and some screens will change
abnd some new fields will be added in the new versions etc.
Also take care of SPAU and SPDD tcodes.
You should be able to know about Unicode concept in sap.
chk this
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
also chk these 2 notes in service.sap.com
Technical Upgrade is only a version upgrade without any functionality changes.
The objects that are needed to be upgraded are:
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
You can refer to the below links for more information on technical upgrade:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/2e/6d66647d9011d396b60000e82de14a/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Reward points if useful
Regards
Anji

SAP Upgradation from 4.5B to ECC 6.0

Hi all,
We need to upgrade from 4.5B to ECC 6.0. Gathered all the information abt. the 4.5 B system...Its on AIX using ORACLE.
I want to know few more info. with your help. i have access to the system through GUI, but didnt have OS level access..
1.) How to know whether the system is CLUSTER configured, any transaction?
2.) I didnt find any Upgradation Guide particular to AIX, can u pls. guide me the path for that in SMP?
3.) How to check whether its using any third party tools(Like Fire Fighter...etc) and any usage types configured(Like PI, BI...)
please guide me in knowing the above through GUI?
Thanks,
Subbu

Hi,
Roadmap is the recomended way to manage the Upgrade project, but this will not make anything automatic. If you don´t have the knowledge and time to configure the project in Solman then just follow the Upgrade Guide. In this Roadmap is included Technical and Funtional processes and it is an excellent starting point for the project but as already said, if don´t have the knowledge or any other person from the team either, then don´t worry much about it althoug it is imperative that a good Project is designed before starting the process either using MS Project or any other software, after the first tests you will have to adjust times for next upgrades.
Buy the way in the upgrade guide there are some sections specially dedicated to AIX but most parts of the process are the same for any OS/DB combo. Basically check prerequisites, do prepare, fix what ever is necesary and then run upgrade process.
Read the Upgrade Guide 2 or 3 times to get a clear Idea on what should be done before, during and after the upgrade process, read all related notes and have them printed in case of any problem.
AND you should have access to OS level, if you don´t then when doing Prepare or Upgrade then you won´t be able to look at the logs and that is Vital during the process. Also need to have access to SAP directories to check and change files like copying upgrade DVD's, upgrading R3trans, TP, etc so explain that to them or make one of them to be next to you.
Good Luck

LONGPOST.LOG Errors during Upgrade from 4.6C to ECC 6.0

Dear all,
We have received the below errors during our upgrade from 4.6C to ECC 6.0.
Basically we have received three types of errors:
1.
4PETG065 RSUPGDEC: Table/structure "BAPE_VBAK" (component "SD-SLS" ) enhanced illegally: Error "2"
2.
A2PESEEF_BADI 103 BAdI implementation "/IRM/BADI_SDDOCFLOW" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZZ_MG_MASS_NEWSEG" must still be migrated A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
3.
3PETG447 Table and runtime object "/SSF/DHEAD" exist without DDIC reference ("Transp. table")
3PETG447 Table and runtime object "/SSF/DTAB" exist without DDIC reference ("Transp. table")
3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
Can anyone help us how to solve this issues.
Thanks & Regards
Senthil

Hi,
Senthil following are ans to ur questions
1. After the SPAU remediation is completed, should I manually release the transport or should I start the upgrade and the upgrade will release that transport?
Ans : Once your SPAU remediation is completed you should release the requests and then start the upgrade of the DEV system.
2. How do we import this SPDD & SPAU transport in the QA and PRD, I mean at what stage of the upgrade we need to specify/ include this transport?
Ans : Now when you start the QA or PRD upgrade at that time you come across a phase during PREPARE called ADJUSTPRP.
Refer following note for further information --
SAPNote 124522 - Importing a modification adjustment in 2nd upgrade
3. Suppose the QA & PRD has more objects to adjust than our Dev box, and this transport will not take care of the delta objects, so in that case how should we remediate, we need to create an other transport request in QA and then it will become two transports?
Ans : First of all this should not be the scenario where you have more modified objects than that in DEV. As all the modfications should take place in DEV first and then should be transported to QA and then PRD. But in such case what you can do is complete the upgrade of QA system and then you are still having 14 days to complete the SPAU objects. So you can make another request which can be transported as a post upgrade activity once the upgrade is completed in production. For SPDD you will have to take care of the SPDD objects if there are different than those in DEV during the ACT_700 phase only or else you might risk data.
This is the reason why SAP always asks you to follow a proper transport path.
4. If our dev box has more objects for remediation than our QA & PRD, then will these objects be also imported into the QA & PRD box?
Ans : Yes, thats why you should be very sure about the SPAU objects that you have found in DEV. You need to compare the objects with QA and PRD and then only make the modifications.
I hope i have answered all your queries.
Regards,
Suhas

Transactions missing in Role After Upgrade from 4.6c to ECC 6.0

Hello Friends,
I did multiple searches on this question but it was unsuccessful. We are upgrading from 4.6c to ECC 6.0. We are testing roles to make sure the migrate properly.
Irrespective of su25. There are transactions that are not obsolete and are missing in ECC 6.0
For example if I have a role called FIROLE. Which has 20 tcodes in 4.6c. When we upgrade to ECC 6.0 8 tcodes will be missing. This is not because the tcodes become obsolete.
What is the best way to approach this. Should we be testing each role?
Thanks!

Hello Imran,
transactions can be 'obsolete' also if they still exist.....
If the application developers create new functionality, new look,.... in new transactions but still let the 'old' ones in the system.
Just think about the ME2*-transactions..... The developer can decide, that such new transactions should replace the old ones after upgrade in the roles or let the old ones as they are.
You can get an overview about replaced/obsolete transactions by reviewing table PRGN_CORR2 (make sure, that you have the latest version, according to [SAP Note 991377|https://service.sap.com/sap/support/notes/991377] !!!). SU25 gets its information from that table.
b.rgds, Bernhard

Documents related to upgrade from 4.6C TO ECC 6.0

Hi all,
can anyone send some documents related to upgrade from 4.6C TO ECC 6.0
my emil id is
[email protected]
THANKS
VENKI

Hi Venki,
Please check for the following links for the information on Upgradation from 4.6C to ECC6.0
Upgrade Procedure/Support Packages:
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
SAP Upgrade guide:
http://www.thespot4sap.com/upgrade_guide_v2.pdf#search=%22upGRADE%20STEPS%20-%20SAP%22
Upgrade information centre:
Upgrade Information Center [original link is broken]
For Functionality Differences pls refer to the below site - http://solutionbrowser.erp.sap.fmpmedia.com/
From ABAP's perspective, the link below helps you:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
For technical upgrade inputs, check:
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/2007/05/07/upgradeFROMR3TOmySAPERP-PARTII&
https://wiki.sdn.sap.com/wiki/display/profile/UPGRADEFROMR3TOmySAPERP-PARTIII
I am sending you a mail too.Please check it.
Reward if found useful.
Regards
Sayee

Interview questions on upgrades from 4.7 to ECC

Hi,
Can any one please post some potential areas/questions that will be asked for upgrade projects from 4.7 to ECC6.0
Points will be awarded.
Thanks

Hi Frank,
this is good question, why because sap upgrades from 4.6b to ecc 6.0 is very risky.
take one example , in 4.5b , me21n application having 620 screen where as in ecc 6.0 having 9000 screen . that time we will take care of it.
check the obsolete function modules , 4.5b , having ws_upload, ws_download.... use cl_gui_frontend_services , under these having differnt type of methods.
once you change the code in ecc , go to tranx : SLIN check the error where it is exact.

Error during Upgrade from 4.6c to ECC 6.0

Hi All,
We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table. Please kindly help as early as possible. The upgrade process is stuck.
Regards
Anil Kumar K

Hi Anil,
Is this issue fixed? Can i know how you fixed it?
replied to your message Re: How to adopt the index changes during upgrade.
Thanks,
Somar

Information on impact on interfaces due to upgrade from 4.7 to ECC 6.0

Similar Messages

Maybe you are looking for