Upgrade from R/3 4.6C to ECC 6.00 : languages

Hi,
We're trying to upgrade from SAP R/3 4.6C to ECC 6.00 under NT environment, having Oracle as database. During the preparation phase, we got the following error, and in our current SAP system R/3 we have 2 additional languages NL and FR (EN and DE are already in), can you please explain why this phase is blocking in this step, and if I continue I've to do a full language import, thanks in advance.
The following language(s) could not be updated yet:
- French       for component EA-APPL
- French       for component EA-DFPS
- French       for component EA-FINSERV
- French       for component EA-GLTRADE
- French       for component EA-HR
- French       for component EA-IPPE
- French       for component EA-PS
- French       for component EA-RETAIL
- French       for component ECC-DIMP
- French       for component ERECRUIT
- French       for component FI-CA
- French       for component FI-CAX
- French       for component FINBASIS
- French       for component INSURANCE
- French       for component IS-CWM
- French       for component IS-H
- French       for component IS-M
- French       for component IS-OIL
- French       for component IS-PS-CA
- French       for component IS-UT
- French       for component LSOFE
- French       for component PI_BASIS
- French       for component SAP_ABA
- French       for component SAP_AP
- French       for component SAP_APPL
- French       for component SAP_BASIS
- French       for component SAP_BW
- French       for component SAP_HR
- French       for component SEM-BW
- French       for component ST-PI
- Dutch        for component EA-APPL
- Dutch        for component EA-DFPS
- Dutch        for component EA-FINSERV
- Dutch        for component EA-GLTRADE
- Dutch        for component EA-HR
- Dutch        for component EA-IPPE
- Dutch        for component EA-PS
- Dutch        for component EA-RETAIL
- Dutch        for component ECC-DIMP
- Dutch        for component ERECRUIT
- Dutch        for component FI-CA
- Dutch        for component FI-CAX
- Dutch        for component FINBASIS
- Dutch        for component INSURANCE
- Dutch        for component IS-CWM
- Dutch        for component IS-H
- Dutch        for component IS-M
- Dutch        for component IS-OIL
- Dutch        for component IS-PS-CA
- Dutch        for component IS-UT
- Dutch        for component LSOFE
- Dutch        for component PI_BASIS
- Dutch        for component SAP_ABA
- Dutch        for component SAP_AP
- Dutch        for component SAP_APPL
- Dutch        for component SAP_BASIS
- Dutch        for component SAP_BW
- Dutch        for component SAP_HR
- Dutch        for component SEM-BW
- Dutch        for component ST-PI
Please mount another Language Disk for these language(s).
If you do not have further Language Disk(s), you may
continue, but the languages mentioned above will be lost
after the upgrade. A full language import has to be
performed after the upgrade to reinstall the language(s).
? continue
? cancel

Hi Markus,
I've introduce the following information:
> MOUNT POINT 07 = S:\export\Data\CDLAN2
> MOUNT POINT 01 = S:\export\Data\KN_WINDOWS_X86_64_AUPG
> MOUNT POINT 06 = S:\export\Data\CDLAN1
> MOUNT POINT 05 = S:\export\Data\CD3
> MOUNT POINT 03 = S:\export\Data\CD1
> MOUNT POINT 08 = S:\export\Data\UMN_WINDOWS_X86_64
> MOUNT POINT 02 = S:\export\Data\KN_WINDOWS_X86_64
> MOUNT POINT 04 = S:\export\Data\CD2
And in mount point 06/07 we have the languages.
The content of the trace file is:
here's the complete trace:
2007/07/05 16:35:01 *****************************
2007/07/05 16:35:01 Checking directories ...
2007/07/05 16:35:01 Searching for Data Carrier labeled AOXUPGR
Adding path: S:\export\Data\KN_WINDOWS_X86_64_AUPG
2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64_AUPG ... no matching label
Adding path: S:\export\Data\KN_WINDOWS_X86_64
2007/07/05 16:35:01 Working on S:\export\Data\KN_WINDOWS_X86_64 ... no matching label
Adding path: S:\export\Data\CD1
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD1
Adding path: S:\export\Data\CD1\UPG1
Adding path: S:\export\Data\CD1\UPG2
Adding path: S:\export\Data\CD1\UPG3
Adding path: S:\export\Data\CD1\UPG4
Adding path: S:\export\Data\CD1\UPG5
Adding path: S:\export\Data\CD1\UPG6
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD1 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG4 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG5 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD1\UPG6 ... no matching label
Adding path: S:\export\Data\CD2
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD2
Adding path: S:\export\Data\CD2\UPG7
Adding path: S:\export\Data\CD2\UPG8
Adding path: S:\export\Data\CD2\UPG9
Adding path: S:\export\Data\CD2\UPG10
Adding path: S:\export\Data\CD2\UPG11
Adding path: S:\export\Data\CD2\UPG12
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD2 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG7 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG8 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG9 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG10 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG11 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD2\UPG12 ... no matching label
Adding path: S:\export\Data\CD3
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CD3
Adding path: S:\export\Data\CD3\UPG13
Adding path: S:\export\Data\CD3\UPG14
Adding path: S:\export\Data\CD3\UPG15
Adding path: S:\export\Data\CD3\UPG16
2007/07/05 16:35:01 Directory structure below S:\export\Data\CD3 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CD3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG13 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG14 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG15 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CD3\UPG16 ... no matching label
Adding path: S:\export\Data\CDLAN1
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN1
Adding path: S:\export\Data\CDLAN1\LANG1
Adding path: S:\export\Data\CDLAN1\LANG2
Adding path: S:\export\Data\CDLAN1\LANG3
Adding path: S:\export\Data\CDLAN1\LANG4
2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN1 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG1 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG3 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN1\LANG4 ... no matching label
Adding path: S:\export\Data\CDLAN2
2007/07/05 16:35:01 Resolving directory structure below S:\export\Data\CDLAN2
Adding path: S:\export\Data\CDLAN2\LANG5
Adding path: S:\export\Data\CDLAN2\LANG6
2007/07/05 16:35:01 Directory structure below S:\export\Data\CDLAN2 resolved
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG5 ... no matching label
2007/07/05 16:35:01 Working on S:\export\Data\CDLAN2\LANG6 ... no matching label
Adding path: S:\export\Data\UMN_WINDOWS_X86_64
2007/07/05 16:35:01 Working on S:\export\Data\UMN_WINDOWS_X86_64 ... no matching label
Regards,
A.Kamel

Similar Messages

Upgrade from R/3 4.7 to ECC 5.0

Hello Everyone
This is my very first post on SDN. I am going to do an upgrade from R/3 4.7 to ECC 5.0. Can anyone please tell me how do I start and procede, this will be my very first upgrade and I definitely need help!!!. I will be really thankful if anyone can give me any suggestions as to how to procede with the planning and then the actual upgrade. What documentation from the service.sap.com should I follow???........PLS help!!!

Dear Mir,
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/
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, 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.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh

Major considerations for the Upgrade from R/3 4.6c to ECC on HR Part.

Hi Experts,
We are doing an upgrade from SAP R/3 4.6c to ECC 6.0
What would be the impact on Personnel Administration and Organizational Management submodules of HR? and the major worries abt ESS and MSS. Currently my client is using ESS and MSS in portal that can retrieve the data from the Backend 4.6c system. while doing upgrade is there any prerequisites i need to met or is there any post upgrade activities for HR or is there Any dependencies?
Because there is a complete architecutre difference for ESS and MSS in both versions, so how can i manage the things without data inconsistencies?
Responses would be heighly appreciated.
Regards,
Srini

Hi Experts,
We are doing an upgrade from SAP R/3 4.6c to ECC 6.0
What would be the impact on Personnel Administration and Organizational Management submodules of HR? and the major worries abt ESS and MSS. Currently my client is using ESS and MSS in portal that can retrieve the data from the Backend 4.6c system. while doing upgrade is there any prerequisites i need to met or is there any post upgrade activities for HR or is there Any dependencies?
Because there is a complete architecutre difference for ESS and MSS in both versions, so how can i manage the things without data inconsistencies?
Responses would be heighly appreciated.
Regards,
Srini

Technical upgrade from 4.6C MDMP system to ECC 6.0 using CU & UC approach

Hi SAP Experts,
We are embarking on a project for Technical upgrade from SAP R/3 4.6C MDMP system to ECC 6.0 using the CU & UC approach for our Asian operations (comprising of India, Japan, Taiwan & Singapore).
Please share with me the Best Practices you followed in your projects, checklists, DOs, DONTs, typical problems you encountered and the possible safeguards, any other useful information, etc.
Since very little information is available from Organizations who have used the CU & UC upgrade approach successfully, I am raising this in SDN to share your experiences during the Technical upgrade.
All useful information will be surely awarded with suitable points.
Looking for your invaluable inputs which will be a BIG help for our project.
Best regards,
Rajaram

Hello Rajaram!:
It's a very big project, that you have to do in a lot of steps........
If you want sent me a email with the problems and you want.
Regards,
Alfredo.

Technical Upgrade from R/3 4.6 to ECC 6.0

Hi all i have a query regaring system upgrade:
Currently i have 2 systems R/3 4.6: Development(D1), Quality(Q1).
Now this systems needs to be upgraded to ECC 6.0.
First the D1 is going to be copied to a new development(D2).
Then D2 will be upgraded to ECC 6.0.
Here a unicode check and other required modification (code compatibility) to
all the customizing and workbench objects is to be done.
Now a copy of Q1 is to be done in new Quality(Q2).
My requirement is to determine all the transported requests from D1 to Q1 and
then transport the same from D2 to Q2 so that the unidcode complaint objects are transported and they overwrite in the new quality system.
Is this process feasible? If yes, How?
Please suggest.

Hi Himansu,
I am making the assumption that you will as the final step upgrade your production to ECC 6.0 and then transport the Unicode corrected ABAP's from your Q2 environment into Prod, and then D2 and Q2 will become your new production support path while D1 and Q1 is removed. Is this assumption correct?
If so, then the next assumption for your plan is your reason for doing this is to keep the production support path D1->Q1->P1 intact while you are performing the upgrade and Unicode program testing in D2 and Q2.
I am also assuming that you are not doing a unicode upgrade/conversion at the same time, you are just making the code Unicode compliant to prepare for a future Unicode upgrade.
If so your plan will work just fine. To say it a little differently, here are the steps
1. Copy D1 to D2
2. Upgrade D2 to ECC 6.0
3. Run UCCHECK to test your code for compliance and to identify objects that need remediation
4. Fix the code that need fixing, and put it in transports with Q2 as your target system
5. Copy Q1 to Q2
6. Upgrade Q2 to ECC 6.0
7. Transport the converted code from step #4 to Q2
8. Perform thorough acceptance testing of the converted code
Now you can plan for your production cutover. While the above steps occurred, you either had a freeze on any changes to the production landscape, or you manually captured changes that was done in D1 in D2. The upgrade project is complex in itself and will need significant user testing assuming that it is only a technical upgrade with no additional or modified functionality.
If your D2 and Q2 was kept in sync, you can now upgrade your P1 system to ECC 6.0 (no need to copy), and configure your transport routes so that D2 and Q2 are now the new production support systems, then you transport the items in step #4 above from Q2 to the upgraded P1.
Regards
John
[SAP Unicode|http://www.sapunicodeupgrade.com|SAP Unicode]

Upgrade from SAP 4.7 EE to ECC 6 while working with CRM 4.0

Hi All,
Presently we are using R/3 version 4.7 EE with CRM 4.0 and now we are planning to upgrade R/3 4.7 to ECC.6.0. My question is, are there any problems working on CRM 4.0 with ECC 6.0 and what are the limitation we face when we work on CRM 4.0 with ECC 6.0 ?. Please provide some inputs on this ASAP.
Thanks in advance,
J M.

Hi,
There is no problem to work on CRM 4.0 with ECC 6.0.
I am using from long time CRM 4.0 with ECC6.0
BR,
Darshan..

Error in upgrade from 4.6 to ecc 6.0

Hi all,
We are upgrading from SAP 4.6 c to ecc 6.0 anr we are getting the following messages
UPGRADEPHASE XPRAS_UPG
1PEPU203X> Messages extracted from log file "SAPR700WG4.ORD" < Long text:
Cause
During the upgrade, a message relevant for postprocessing was writte to a log file. This message is not dealt with until the end of the entire upgrade. The upgrade continues.
System Response
The upgrade stops in phase CHK_POSTUP. To create the reference to the original log file, this message is generated by R3up.
What to do
Note the messages following this message and proceed according to the instructions.
A2PESEEF_BADI 103 BAdI implementation "Z_PMORDER_CONFIRM" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "Z_PMORDER_UPDATE" must still be migrated
A2PESEEF_BADI 103 BAdI implementation "ZWORKORDER_UPDATE" must still be migrated
1PEPU203X> Messages extracted from log file "SAPR700ZG1.ORD" < Long text: see above
A4PECOM_PRODUCT 063 Execute the upgrade report "COM_PRODUCT_UPGRADE"
UPGRADEPHASE JOB_RDDNTPUR
1PEPU203X> Messages extracted from log file "RDDNTPUR.ORD" < Long text: see above
3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
Long text:
Cause
A runtime object was found for a table which is unknown in the ABAP Dictionary. The table contains data, which is why, as a precaution, the runtime object was not deleted. Since there is a runtime object, this means the table was once create in the ABAP Dictionary. The fact that the table can no longer be found in the ABAP Dictionary could be due to the following reasons:
It is a customer-specific table which was created when the correction system was switched off.
Depending on the history of your system, there may also be SAP tables which were not deleted completely, or for which only the runtime object was delivered without the related definition in the ABAP Dictionary
System Response
What to do
RESET N1
Customer-specific tables
If it is a customer-specific table, and you still need the data, try to restore the table in the ABAP Dictionary.
Note the specified table type
when you do this (transparent table, pool table, and so on). The table may still, for example, be contained in the version database.
You can access version management through the menu "Utilities" in the in the ABAP Dictionary (transaction SE11).
You may also still have a copy of the system that still contains the table definition. You can also display the runtime object and create the table according to the field names, types and lengths specified in the definition. You can display the runtime object in the menu "Extras" of the database utility (transaction SE14).
Tables in the SAP namespace
Search for notes on these tables in OSS using the key words RDDNTPUR and TG447.
3PETG447 Table and runtime object "STGLTRAN" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "STSLEVNTSV" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "STSLTOBJSV" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "STSLTRANSV" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "TIBAN_ACTIVE" exist without DDIC reference ("Transp. table")
Long text: see above
3PETG447 Table and runtime object "ZPH_RESS_STATUS" exist without DDIC reference ("Transp. table")
Long text: see above
Please suggest what to be done in these cases.
Thanks

Hi,
I think you have some BADIs or other enhancements donne in 4.6, whn tried to migrate to 6.0 causes this. Pls check whether all these objects are available/changed in 6.0.
Regards.
Renjith Michael.

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

Upgrading from 4.7 to ECC 6.0 And GTS 2.0 to a newer version

Hi everyone,
I am new to SAP SD, I am involved in upgrading from R/3 4.7 to ecc 6.0 and GTS 2.0 to a newer version. Can somebody tell me the major differences in these two vesions and also some link through which I can get some info. It is very urgent.
Thanks.

Dear Paranidharan Gandhi,
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/
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, 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.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

Any changes (SAP HR upgradation from 4.7 to ECC 6.0)

Hi
could some one tell the major changes while upgrading from SAP HR 4.7 to ECC 6.0, like
1. changes in reporting
2. data structures
3. user exits
4. infotypes.
Many thanks
Chinni

I have questions experts:
1. In case of upgrade / implementation of ECC6 what are the important consideration from testing point of view for all SAP HR Modules
2. MSS and ESS is implemented for Performance Appraisal. One role and 3000 to 4000 users (Managers) and employee portion of Performance appraisals is in ITS as a URL service to the BSP page. This will be migrated to WebDynpro from ITS , could you please let us know what are the important functional parameters we should consider for the above activity
I could not get apt information after searching the link
http://solutionbrowser.erp.sap.fmpmedia.com/
Please help me out in getting the solution

Upgrade from 4.6c to ECC6.0

Hi Experts,
I have an query. W have a client who is currently on 4.6 c . Its in upgrade study mode. So according to the client they are using inbuilt Business connectors in 4.6c.
1)So i want to know was business connectors part of 4.6 c.?
2)So when we go for upgade from 4.6c to ecc 6.0 . will the business conectors be available in SAP without using XI.
3) If 2nd is not possible then if we use XI as an integration tool then how we gonna upgrade from 4.6c business connectors to ecc 6.0
Kindly help me on this.
Regards
Saras Jain

hi,
>> If 2nd is not possible then if we use XI as an integration tool then how we gonna upgrade from 4.6c business connectors to ecc 6.0
as far as only upgrade from 4.6 to 6.0 is concerned (i.e only within sap systems) that can be done without xi also. but integration landscape of the client will most likely have systems ither than sap. is it rite? then u can propose to integrate those systems with SAP using XI. as it will be very helful. If there are SAP and non-sap systems in landscape then the advantages of XI for integration become multifold.
hope it helps,
regards,
latika.

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

Unicode error while upgrading from 4.6 to ECC 6.0

Dear All,
I am getting unicode errror while upgrading from 4.6 to ECC 6.0, when iam trying to open downloaded file in excel.
In debugging, error occurs while executing statment "CALL METHOD OF obj_ex_sheet " in the code given below:
FORM open_downloaded_file_in_excel            *
FORM open_downloaded_file_in_excel.
DATA:
    lv_ole_books       TYPE ole2_object,
    lv_ole_sheets      TYPE ole2_object,
    lv_subrc           LIKE sy-subrc,
    lv_title(70)       TYPE c,
    lv_text1(70)       TYPE c,
    lv_text2(70)       TYPE c.
start excel
CREATE OBJECT obj_ex_sheet      'EXCEL.SHEET'.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
CALL METHOD OF obj_ex_sheet     'Application' = obj_ex_app.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_app.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
SET PROPERTY OF obj_ex_app 'Visible' = 1.
open data file: main file
CALL METHOD OF obj_ex_app        'Workbooks' = lv_ole_books.
CALL METHOD OF lv_ole_books      'Open'       = obj_ex_wbook
    EXPORTING #1 = gv_filename
              #2 = 2
              #3 = 0
              #4 = 1
              #5 = 0
              #6 = 0
              #7 = 1.
IF sy-subrc NE 0.
    lv_subrc = sy-subrc.
    FREE OBJECT obj_ex_wbook.
    FREE OBJECT obj_ex_app.
    FREE OBJECT obj_ex_sheet.
    PERFORM error_handling_ms_excel USING lv_subrc.
ENDIF.
FREE OBJECT lv_ole_books.
CALL METHOD OF obj_ex_wbook      'Worksheets' = lv_ole_sheets.
CALL METHOD OF lv_ole_sheets     'Item'       = obj_ex_wsheet
    EXPORTING #1 = 1.
FREE OBJECT lv_ole_sheets.
GET PROPERTY OF obj_ex_wsheet    'UsedRange' = obj_ex_usedrange.
CALL METHOD OF obj_ex_usedrange 'AutoFormat'
    EXPORTING #1 = 18.
SET PROPERTY OF obj_ex_wsheet    'Name'       = sy-tcode.
FREE OBJECT obj_ex_usedrange.
PERFORM free_ole_objects.
CALL FUNCTION 'FLUSH'
       EXCEPTIONS
            OTHERS = 0.
ENDFORM.
regards,
Divya

hi,
In the OPEN DATASET STATEMENT ADD THE ENCODING ADDITION IN TEXT MODE.
Regards,
Balakumar.G
Reward Points if helpful.

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

Upgrade from R/3 4.6C to ECC 6.00 : languages

Similar Messages

Maybe you are looking for