BW specific task during R/3 upgradation from 4.7 to ECC 6.0

Hi Everybody,
We are planning R/3 upgrade from 4.7 to ECC 6.0. We are using BW 3.5 . So, Can anybody share BW 3.5 specific task during pre-upgrade as well as post-upgrade for ECC Upgrade.
Thanks & Regards,
Sushant N. Tiwarekar

Hello ALex,
There is not a must to upgrade also your solman 3.2 when you upgrade your satellites, only consider if you need the solman diagnostic or not and also that the new functionality in solman 4.0.
Which system is unicode, the satellite?
There is also not problems having a non-unicode solman with unicode satellites and the other, having a unicode-solman "linked" to unicode-satellites.
Hope this helps,
Dolores

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

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.

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

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

Upgrade from 4.6c to ecc 6.0

Hi,
We are doing a technical upgrade from 4.6c to ecc 6.0 without activating New GL. As a functional consultant, what should i look for? I know that we need to test the business processes and check Z programs but anything specific, plzz let me know.
What changes should be made in Asset Accounting?
Regards
Satya

Thanks for the reply.
What are the changes made in Asset accounting after upgrading?
I heard of RBE tool...how is it used for FI?? (u check for the mostly used transactions or what??)
Anyone, plzz answer..waiting for ur replies
Regards
Satya

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

ESS/MSS Upgrade from 4.6 to ECC 6.0 Question..

Hi Gurus,
During the upgrade SAP R/3 would be upgraded from 4.6C to ECC 6.0. The HR module on this R/3 has - Org Management, Benefits, Time Administration and Payroll. They use ESS based on ITS. My question is when they go from 4.6c to ECC 6.0 - would they have to let go the ITS based ESS transactions and go with Web Dynpro based ESS? If yes then what happens to all the customizations they have done to ITS based ESS transactions. Would they have to be redone on the Web Dynpro based ESS?
Thanks,
Soniya Singh

yes You need to do different customisations for the Web dynpro since ECC 6 is better with WD, ITS functionality wont work here. Please check the training material for the MSS which is very exhaustive.
But if you continue to use ITS then your old customisation should work but then again there will be changes..better to move wholly to WD

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

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.

Upgrade from 4.6b to ECC 6.0 abap changes?

Hi all,
Kindly can any one provide me documentation on upgrading from 4.6 to ECC 6.0 Related to changes in abap code, obsolet functions, etc.
It will be very helpful If you can help me.
Thanking you in advance,

ERP 6.0 has > 200.000 ABAP programs and function modules and other objects, having such "delta list" doesn´t make sense. Would you want to compare the programs one-by-one?
Between 4.6B and ERP 6.0 are many years of development and many many uncountable changes.
Please be a bit more specific what you want to check, then we may help.
Markus

HR Upgrade from 4.6c to ECC 6.0

Hi,
I am currently about to start a HR Upgrade project from 4.6c to ECC 6.0. Does anyone have the checklist of activities to be followed during upgrade process or any plan for upgrade process in detail. Anyone involved in upgrades pls do send across.
Regards
Jyothi

Hi,
We have recently upgraded from 4.6C to ECC 5.0. Checklist would be like...during upgrade you need to clear SPAU, there you may get cought in Schema, Rule, Functions,,you need to check there. Also check all User exits & BADI's.
After upgrade you need to check all user defined variants properly since some screen might have changed during upgrade. Also check WT characteristics, since some standard WT charactersistics have been changed.
Apart from this, there was no major issue in our upgrade. It went on smooth.
Hope this helps.
Thanks,
Sarika.

Upgrade from 4.0b to ecc 5.0

Hi all,
My company is upgrading from 4.0b to ECC 5.0. So, can anyone let me know what problems we would be encountering and what is the best method to resolve such problems.
I would like to know how both versions are mainly different ?
My company mainly works on SD, MM and FI, so is there anything is specific that I have to keep in mind while the upgradation?
Thanks,
Praveen.

check...
http://sap.ittoolbox.com/groups/technical-functional/sap-basis/about-upgrade-of-sap-40b-1384660

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.

BW specific task during R/3 upgradation from 4.7 to ECC 6.0

Similar Messages

Maybe you are looking for