ECC 5 upgrade from 46B

Hi,
I am trying to upgrade 46B to ECC5, when I run Prepare for Initialization module, it says Error: SAP_BASIS is too old? can any one explain me on this as I can't find any document on this?
with many thanks,
Venkat

Hi All,
can any one tell me what is the minimum package levels for baiss/abap and Application before upgrading to ECC5? surprisingly I can't find this info anywhere..
any expert advise would be greatly appreciated.
with thanks,
Venkat

Similar Messages

Upgrade from 46B to ECC 6.0

I'm planning to do an upgrade from 46B oracle 9i to ECC 6 oracle 10g.
Is there someone who did it whith those version.
I was wondering, do I have to apply all the sp from 46b before migrating to ECC 6?
Somebody could help me?
Thanks

Hi,
You need to follow the steps carefully.
You first need to upgrade Oracle to 10g and then you need to upgrade your kernel to 46D_ext from 46D as 46D_ext ortace libraries support oracle 10g libraries and hence need to be very careful.
You can follow certain notes like :
SAPNote 932722 - Upgrade to Oracle 10.2 during a database copy
SAPNote 976457 - Oracle 10g Support on Windows: 4.6D-Based SAP Systems
Once you upgrade oracle and are able to start and work on SAP system (with Oracle 10.2.0.2 and 46D_ext kernel) then you can start the upgrade.
Rest of the upgrade is similar to a normal upgrade.
Regards,
Suhas

SAP ECC upgrade from EHP6 to EHP7

Is GTS upgrade from NW 7.2 to GTS 7.3 to be mandated as ECC is getting upgraded from ECC 6.0 EHP6 to EHP 7 . Why?

Hi John,
Your statement looks a bit misaligned.. There is no GTS 7.3 version, the SAP Netweaver 7.3* application server on which SLL_LEG GTS component sits.
The underlying Netweaver AS versions between ECC and GTS systems can be different BUT what needs to be the same is the GTS plugin component in ECC and GTS components in GTS system itself, as best practice they should also be on the same support pack level.
If the ECC upgrade from ehp6 to ehp7 requires you to upgrade SLL_PI gts plugin component in ECC, then in this case you should upgrade SLL_LEG component in GTS system to the same version.
I personaly dont think its required, but check Service markeplace for, PAM Product-availability-matrix and other ehp 7 requirements..
Hope this helps,
Branio

ECC Upgrade from ECC 5.0 to ECC 6.0 EHP4 - impact on XI 3.0

Hi,
We are palnning for upgrade our ECC System from ECC 5.0 to ECC 6.0 EHP4. We do not have any plan of upgrade on XI, which is on XI 3.0.
After ECC upgrade please provide the impact on XI 3.0 ?
Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
Thanks.

>>Will XI 3.0 able to work with ECC 6.0 without any change or any change is required in the XI configuration level, please specify?
As far as I know, no change is required in XI configuration.
Regards,
Praveen Gujjeti.

IDoc segment version issue in ECC upgrade from 5.0 to 6.0

Hi experts,
we are in the process of upgrading our ECC environment from 5.0 to 6.0. We have quite a few interfaces which use ORDERS/Invoice Idocs in customised form. In ECC5.0 environment, we had developed a Z segment in the ORDERS Idoc and the segment release was set as 640. Everything worked fine in ECC5.0.
In upgraded environment, SAP has released new version of some segments. one of those is E1EDP01. This segment has 2 new versions in ECC6.0 environment - 007 and 008. This change in the version changes the data in the IDoc and hence interface goes in error at the EDI provider.
We have tried to use 640 as the IDoc segment release in the partner profile of the IDocs. This still gives us an issue because the 007 version of the segment E1EDP01 has release 620 and hence the Idoc picks up 007 version instead of 006 version as desired. When we change the partner profile with Segment release in the IDoc type as 46C, it gives us an issue in the Z segment saying that the IDoc segment is not released in 46C and the Idoc goes in error.
has any one faces such situation in the past? if yes, please throw some light.
Thanks in advance.

Please let me know if your issue was resolved. I have similar issue now.
Thanks,
Sailaja

Upgrade From 46B to ECC6 SR3 - XPRAS_UPG errors

Hello,
I ugrade a system from 46B to ECC6 SR3.
Windows 2003 SP1 32bits / MSSQL 2000 SP4.
During the XPRAS_UPG phase, i have an error in the post-import method RS_SHIP_AFTER_IMPORT for the transport SAPK700ZH1.
The log is the RDDEXECL job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server xxx were synchronized
Incorrect input for activating transported shadow IPacks
Job cancelled after system exception ERROR_MESSAGE
Have you already encountered this problem?
Thanks,
Alexandre

The problem is solved.
It was due to an empty entry in table rsbasidoc.
Alex

Tcode V23 - Program SDSPESTA - ECC Upgrade from 5.0 - ECC 6.0

As I was testing transaction V23 I was prompted with a information message "Execute selection report SDSPESTA first".
As I was investigating this program I had some questions - what is this program doing? I understand it is refreshing header status data in tables VBUK and VBUP since statuses are newly added fields in 6.0. However when investigating the status from 5.0 to 6.0 the tables were properly populated with the correct information. What is the purpose of this program then?
Also - I ran this program for ONE sales order in TEST MODE only, and now I do not get the informational message anymore when running V23. Is only running for one order in test mode sufficient to not recieve the message anymore? If not, how do you run this program? Wide open to update all orders?
Please advise.

Posted in wrong forum. reposted in Business Process forum.

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

Err while initiating travel form in pr05 after upgrade from ECC5.0 to 6.0

Hi gurus,
I was trying to simulate a trip in pr05. the err "err while initiating travel form" prompt up while initiating. This err only occurs after our ecc upgrade from 5.0 to 6.0. Before it was fine with Standard Travel Form.
Does anyone of you know what's the problem? Any help you would provide will be highly appreciated!
Rgs, Michelle

Hello Michelle,
There is already a possibility to use the HTML form for Travel
Request and Travel Plan BUT is only possible after you apply the
Support Package 09 for EA-HR (SAPKGPHD09).
In table TA20SWITCH you can use the Attribute HTMLFORM_R_P and there
define an entry "X".
This functionality is ONLY delivered with Support Package 09.
Regards,
Raynard

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

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.

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

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

ECC 5 upgrade from 46B

Similar Messages

Maybe you are looking for