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.

Similar Messages

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.

Schema error after upgrade from 4.6C to ECC 5.0

Hi all,
We have recently upgraded from 4.6C to ECC 5.0. We are having problem in payroll run. When I did a syntax check in schema, I got "UDPM" rule doesn't exist. I checked, this rule is present in 4.6C. This is the standard rule. If I am right, it should have come with upgrade right?
or SAP has changed this? From where Can I get the info about this?
Also similar error I got in Function 'USTAX' parameter 3 is not allowed. If I remove that parameter, I don't know what is the implication of that.
I checked for SAP notes. I did not find anything.
Please let me know if any of you have come with such situation.
Thanks in advance.
Sarika.

Hi Sarika,
We are also in a similar transition i.e. 4.6C to mysap Ecc5.0 . But we are on Canadian Payroll.
I had search OSS and got a PDF document regarding " Upgrading to SAP R/3 Enterprize - A User Guide to Canadian mysap HR Customers" . U may be can find a similar one for US payroll. I can give u mine, but it wont be of any use as it is for Canadian Payroll.
In Canadian mysap Upgrade , the function P0224 has been replaced by function KXDTM . Although P0024 is still in used in Schema K00T for conversion purposes.
Regards,
Jay Gandhi

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

Unicode error while upgrading from 4.7 to ECC 6.0

Hello all,
I am upgrading our SAP from 4.7 to ECC 6.0. while doing so we had folllowing error in the adjoinig statement of Search.
Error : Table I_VBLS must have a character line type (data type C,N,D,T or string)
Statement :
W_TMP10 = I_VBLS-VBELN.
SEARCH I_VBLS[] FOR W_TMP10 STARTING AT 1
IF SY-SUBRC NE 0.
   EXIT.
ENDIF.
Now I tried to remove this error by putting a loop on internal table I_VBLS and inside it concatenating the header line with a Field symbol and after that to a string variable. Then I used SEARCH statement for the same string. but unfortunately this is changing the functionality of the program by large extent. Does anybody know the exact code snippet to replace search Internal Table
Edited by: Aalhad Deshpande on Feb 23, 2009 3:18 PM
Edited by: Aalhad Deshpande on Feb 23, 2009 3:19 PM

Hi,
Try to use this method.
CALL METHOD CL_ABAP_CONTAINER_UTILITIES=>FILL_CONTAINER_C
E:G :-
        WRITE crlf TO i_linea-linea2.
In this case also their are not mutually convertable. try to use this method and let me know
        CALL METHOD CL_ABAP_CONTAINER_UTILITIES=>FILL_CONTAINER_C
          EXPORTING
            IM_VALUE               = crlf
          IMPORTING
            EX_CONTAINER           = i_linea-linea2
          EXCEPTIONS
            ILLEGAL_PARAMETER_TYPE = 1
            others                 = 2.
Regards,
Sathish

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.

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

Issues during technical upgrade from 4.6c to ecc 6.0

Hi
We are doing a technical upgrade from 4.6C to ECC 6.0. Some transactions in QM module when tested in ECC 6.0 test client give a abap termination message (or dump) and certain transactions like qs42,46, qa18, qs34 etc do not get executed (error = no entry foound for......) and similarly in PP-PI module transactions like C203 have similar problems, even though master data does exist. What should I look for? Can somebody pl. give details on configuration checks and the OSS notes from a functional point of view for a technical upgrade?
For certain transactions I get the error message - "Central system of distribution SM-P06CLNT430_TRUSTED is unreachable RFC destination SM_P06CLNT430_Trusted does not exist" - what does this mean?
thanks
BE

Hi,
1. Have you done successfull installation from 4.6C to ECC 6.0 at the time of PrePare ans SAPUP?
2. Check SP' for QM and PP-PI modules from http://service.sap.com/sp-stacks.
3. Configure RFC connections correctly, SM_<SID>CLNT<No>_Trusted automatically created, not manually.
http://service.sap.com/notes --> search for RFC trusted connections for Ecc 6.0
http://service.sap.com/upgrade.
Regards,
Srini Nookala

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.

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

Re : Roles of Functional Consultant in upgradation from 4.6b to ECC 6.0

Hi
I need the Roles of Functional Consultant and Technical Consultant in upgradation from 4.6b to ECC 6.0.
Thanks
Anto

Dear Anto,
In Technical SAP,Upgrade from 4.6 to 6.0- the role of any fucntional consultant would involved integrated with the technical Consultant.
The phase starts with the technical Patches apply to the latest stack level which will done by the BASIS Consultants.
Once the System preparation is happened, the next phase is with SPDD phase, Thru this transaction the dictionary Objects-Database elements, database tables and structures of teh latest system can be
compared with the old system.
This results in the version modification results between the old and New versions. During this phase the involvement of the Functional Consultant needed for the tech guy, to identify the functional chnages between the two version (Old and New). Which helps for him either to Reset to Original(ie., adopting the new one) or Adopt Modification in previous system(ie., adopting to older functionality)
Once this is done, the System Upgradation will be done by the BASI, the system will be replaced with new system. At teh end of this phase SPAU phase starts, which inturn reults with version difference in the field namely, Programs, Reports, Screens, Messages, Notes an Function Modules. Here too the involvement of functional consultant neede to determine either reset to original or to go with Adopt modification from the older design, as explained earlier.
At teh end of the, moreover the functional consultant role involved in testing the Entire processes and transactoin in the system for system dump and bugs, in necessity to correct teh same and results with nil errors in production client.
Also the Zprograms invloved in the older versions, needs to be examined for the actual need, and to be justified with adoption in the newer version or by adopting to the updated functionality in the newer version.
Hope this may give better clarity in the involvement of the Functional Consultant in the Updgrade project.
Njoy SAP
Regards,
-Saravanaganesh

Roles of Functional Consultant in upgradation from 4.6b to ECC 6.0.

Hi
I need the Roles of Functional Consultant and Technical Consultant in upgradation from 4.6b to ECC 6.0.
Thanks
Anto

In Technical SAP,Upgrade from 4.6 to 6.0- the role of any fucntional consultant would involved integrated with the technical Consultant.
The phase starts with the technical Patches apply to the latest stack level which will done by the BASIS Consultants.
Once the System preparation is happened, the next phase is with SPDD phase, Thru this transaction the dictionary Objects-Database elements, database tables and structures of teh latest system can be
compared with the old system.
This results in the version modification results between the old and New versions. During this phase the involvement of the Functional Consultant needed for the tech guy, to identify the functional chnages between the two version (Old and New). Which helps for him either to Reset to Original(ie., adopting the new one) or Adopt Modification in previous system(ie., adopting to older functionality)
Once this is done, the System Upgradation will be done by the BASI, the system will be replaced with new system. At teh end of this phase SPAU phase starts, which inturn reults with version difference in the field namely, Programs, Reports, Screens, Messages, Notes an Function Modules. Here too the involvement of functional consultant neede to determine either reset to original or to go with Adopt modification from the older design, as explained earlier.
At teh end of the, moreover the functional consultant role involved in testing the Entire processes and transactoin in the system for system dump and bugs, in necessity to correct teh same and results with nil errors in production client.
Also the Zprograms invloved in the older versions, needs to be examined for the actual need, and to be justified with adoption in the newer version or by adopting to the updated functionality in the newer version.
Hope this may give better clarity in the involvement of the Functional Consultant in the Updgrade project.

Depreciation Run Error while Upgrading from SAP 4.6C TO ECC6.0

Hi
We are upgrading from 4.6c to ECC 6.0. In ECC 6.0 we need to make the Number Range Interval as "Internal" and Batch Session tick to be removed from the Depreciation Document Type.
While executing depreciation run, it got terminated and I have done the above changes. After that I have restarted the Depreciation. I have got the following error Message.
Message(s) during check of document ERROR00001
Message no. AAPO511
S:/SAPDMC/LSMW_AUX_020:006 20
Message no. /SAPDMC/LSMW_AUX_020006
If any body aware solution, kindly reply to this message
Thanks
siva

Check this useful links
Key differences between SAP 4.6 - ECC 6.0
http://sap.ittoolbox.com/groups/technical-functional/sap-hr/difference-sap-ecc60-with-sap-r3-3161113
LE/WM functionality difference between 4.6c and ECC 6.0
differences between SAP R/3 ECC 6 & SAP R/3 4.6C in Material management mod
Upgrade from SAP R/3 4.6 C to ECC6.0 - To find obselete and new tcodes
Upgrade from SAP R/3 4.6 C to ECC6.0 - To find obselete and new tcodes

Upgrade from 4.6c to ECC

We are upgrading from 4.6C to ECC.
We have evaluated the UCCHECK results.
I wanted to know is there any other places we might need to change our codes except those indicated in UCCHECK, SPAU and SPDD transactions?
Can we assume that the list provided by other transactions will be complete?
THanks in adv.

This note tells about many more things.
So it means we cannot be sure that after doing the changes mentioned in transactions UCCHECK, SPDD, all programs will not give syntax errors, at least?
Thanks in adv.

Error in upgrade from 4.6 to ecc 6.0

Similar Messages

Maybe you are looking for