SAP Upgrade 4.6C to ECC 6.0 EHP5 system customer is using Data Archiving

Dear All,
I am planning to do SAP Upgrade from 4.6C to ECC 6.0 EHP5, in the source system customer is using SAP DATA ARCHIVING. As per some of the SAP Notes before downtime phase we need to disable all the dataarchiving jobs .
1) My question is do we need to do any presteps before starting the upgrade related to SAP DATA ARCHIVING ?
2) After the upgrade if customer wants to use the old archiving objects etc... whether they will able to do it. For this do we need to raise any message with SAP regrading the dataarchiving before the upgrade
Please let me know if you have any ideas on the above questions.
Thanks & Regards
Ravikiran

Hi,
I would suggest you to do the data archiving after upgrade project or finish data archiving before upgrade project. As lots of new archiving objects has been delivered in ECC.
Also, its true that before starting downtime project you need to stop all your jobs. Also, SAP has recently introduced new retention management technique for data archiving starting from EHP4 onwards to manage data archiving more efficiently. If you are interested, you can explore this further on http://sdn.sap.com/irj/sdn/ilm or http://service.sap.com/ilm.
Thanks
Sunny

Similar Messages

Need knowledge on sap upgrade 4.7 to ecc 6.0 in abap reports and sap query

please give me some ideas and useful links on sap upgrade 4.7 to ecc 6.0 in abap reports and sap query

Hi Jaya,
Not very clear with your question.
Are you looking for changes in areas od ABAP reports & SAP query when we upgrade SAP from 4.7 to ECC 6.0 ??
If the response is YES, then please refer to SAP solution browser www.sapsolutionbrowser.com
Define source release and target release .
You will get module wise details on new features for target release.
Hope this helps.
Regards,
Deepak Kori

Error in SAP Upgrade 4.6C to ECC 6.0 in CONFLICT_CHECK Phase

Hi All,
I am doing an SAP Upgrade frm SAP 4.6C SR2 to ECC 6.0 SR2. When it enters the CONFLICT_CHECK we are facing the following error. i am performing this on Production system. Your immediate help is highly appreciated.
#---- MASKING file CONFLCHK.LOG from E:\usr\sap\put\log
#---- TIME: 20091212095249
1 ETQ201XEntering upgrade-phase "CONFLICT_CHECK" ("20091212094722")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '22', GwService = 'sapgw22'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPR3
4 ETQ399   auth_shadow_upgrade=0
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
2 ETQ160 Starting conflict check
4 ETQ010 Date & Time: 20091212094722
4 ETQ230 Starting RFC Login to: System = "CPA", GwHost = "DERSHASKFI140", GwService = "sapgw22"
4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SPDA_CONFLICT_CHECK" by RFC
2EETQ360 RFC of "spda_conflict_check" failed:
2EETQ361 code/exception : SYSTEM_FAILURE
2EETQ362 key             : RFC_ERROR_SYSTEM_FAILURE
2EETQ364 message         :
2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ                    .
4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "SPDA_CONFLICT_CHECK" by RFC failed (error-status "-2")
4 ETQ239 Logging off from SAP system
4 ETQ010 Date & Time: 20091212094903
4 ETQ010 Date & Time: 20091212094903
Hemanth

Hi,
> 2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ
Have you checked tablespace have sufficient space ?
Thanks
Sunny        .

SAP Upgrade 4.7ee to ECC 6.0

Dear experts
we are planing SAP Upgrade 4.6 C to ECC 6.0 on windows 2003 Server with Oracle Database please anybody explain prerequests and post upgrade activities and upgrade phase's.
what are the phase's are inportant...to monitor
Regards
Bandla

Hi Bandla,
Please check this beautiful [WiKi|https://www.sdn.sap.com/irj/scn/wiki?path=/display/erp6/learning+map].
Regards,
S.Manu.

SAP Upgrade 4.6C to ECC 6.0

Hi,
We are performing the SAP security upgrade from 4.6C to ECC 6.0 for our client.
In the 4.6C landscape the DEV, QAS & PRD systems are not in sync. To add, the upgraded DEV system has already been built in the ECC 6.0 landscape. This has resulted in the DEV ECC 6.0 system not containing all the roles which are present in the 4.6C production system.
My question is how do I bring all the roles & authorizations from the production environment in 4.6C into the DEV ECC 6.0 system so that I am assured I have the correct outputs when I run the SU25 step in the DEV ECC 6.0 system?

Hi,
You have not followed the upgrade cycle. You should have done onne test upgrade by copying the Production database.(system copy). Then you would have copied all the application data as well as roles. Then you should have done the upgrade.
Anyway now you have one option. You have the Quality server. Now move all the roles to quality server and then do the upgrade. Else copy the production data and then do the upgrade. This is will reduce your efforts while doing production upgrade. If helpful please do award points.

Pipeline withdrawal fails after SAP upgrade 4.6B to ECC 6.0

Hi experts,
our customer has been using Water as a pipeline material for years now, but after upgrade to ECC 6.0, we receive error message M7009 (Special Stock P not defined) when trying to perform a goods issue to process order for this (same) article.
Strangely, the error message only comes up when we use COR6 or MIGO's 'Goods issue to order' or 'to reservation', and not when we do 'goods issue other', manually take movement type 261 P, and check.
Now since the only difference I can see at this point is the absence of the Reservation tab in MIGO, I assume the reservation has something to do with this error.
Any ideas?

Hi,
before confirming production order via Co15, in goods movements, there is storage location populated for this material. If I delete SL for it, then goods movement is succesfully done.
In ecc 5.0, SL is also populated but it is working fine.
Any idea?
Edited by: Alberto Emilio Gallardo Doñate on Apr 22, 2010 12:21 PM

Write custom logic for data archiving using Open text(SAP archiving)

Hi,
We are currently doing archiving for sales documents and billing documents using Open text. As part of this we need to have a search functionality based on Sales document,customer number, customer address etc...
since customer address doesn't exist in sales order tables we need to write logic so that the document gets archived and retrieved using the address.
can you please help me out in how and where to write logic for this...can this be achieved?
i observed an area on Attribute Object for a Node which gives an option for Event and User exit. can this be used..if so how?
Thanks,
Anil

hi,
please write more detailed information what do you really need...

ECC upgrade impact on data archival

Friends,
We are working on the data archival SAP version 4.7, parallely ECC upgrades activities are going on. We are working on the archive tools like transactions SARA, SARI etc as part of archiving. Not sure on what changes to the features will be available in the ECC6.0 version and its impact on already archived files. Can somebody give some inputs/direction?
thanks
Nalinikanth.

Hi,
Retrieval of Archived data
1. SAP system support to retrieve data archived from 4.7 system by ECC system. There is no negative impact in retrieving archived data of deferent version in ECC system.
Advice to take back ups of Field catalog, Archive infostructure in case it is Custom or any additional field added to standard structure.
2. Some changes in Archive index is there in ECC system -
In ECC system, if you want to retrieve archived data from FB03 then activate and fill the Archive infostructure, Archive build index will not work.
This method remains same for Material document and other documents
In ECC system SAP recommends to use Archive system instead of building archive index table such as ARIX_BKPF...
Archive Program
1. All the BC sets to upgrade archiving process are been implemented in ECC system, so you can see some changes in the Write program, Delete program.. or for some archiving object you may also see addition of preprocessing program..
For example: MM_EKKO in initial released 4.7 version didn't had preprocessing job, Write job variant had option of company code to archive purchase order. Later BC set was released with upgraded programs with Preprocessing program and in Write variant with selection of Purchase organization instead of Company code.
If you have already implemented latest release of BC sets then in ECC 6.0 will not have any changes otherwise some minor changes you can see.
Please specify which archiving object with program you are concern with.
Store Function
1. In ECC system, SAP has filled up a long standing gap of storing archived data of different company code in separate content repository. This is very much useful when you want to store the archived data of different organization units in different storage repository. This also easy to get rid of data that has completed total retention period from the storage system.
Remain other functionality remains the same. Please let me know if you have any concern about archiving object that you are using.
-Thanks,
Ajay

SAP upgradation ?

hii
What will be the major work for MM consultant in SAP upgradation (4.5 to ECC 6.0).
What is the latest version of SAP??
Explain in more detail about MM consultant roles and responsibilities n SAP upgradation (4.5 to ECC 6.0).
Thanks

Normally upgradation project is basis driven project. Basis guys will prepare the system taking into consideration of all the aspects of the system. This itself is project called upgrade. Upgrading project mostly involves testing with the existing system with the new system. SAP already released the release notes for this Upgrading ECC 6.0{example 4.6C to ECC 6.0}. (1).Functional consultant have to do unit test/Integration test/Regression test in new system based on the business process documents prepared for your present system. (2).Functional consultant mostly encounter Interface issues (If exist)/Authorization issues/Enhanced naming issues/Usage issues. (3).Example:In older version you have to do external configuration for CIN. However .In ERP 2005, It is already in built. Hence Knowledge of CIN will be more than sufficient to manage the CIN issues. (4). More over Functional consultant must be very confident in the business process. Unless you will receive many UAT issues. (5). Whenever Functional consultant do unit test and Integration test, use user id to.When you do regression testing, get the user id from user copy all the roles from the user id and create new id. Using this new id you do the Regression testing. This will avoid many problems. (6). Another Important, big issue is patch work information. For example After release of 46C, SAP released many patches for 46C.However these patches are all not updated in to your present 46C system. These patches are already in built in ECC 6.0, hence you will get diff.result when you do testing. If such a case, advices the user about the patch work, and proceed. In most of my cases, SAP enjoyed with 46C without patch scenario, but in ECC6.0 they started to complain, b'cas the new patches.
Check this link for further details:
Re: upgrade from 4.7 to 6.0
Edited by: Afshad Irani on Aug 9, 2010 11:35 AM

2009 SAP Upgrade Survey Results

A new survey which was conducted by Panaya, Inc suggests that most SAP customers are moving ahead with their current plans for upgrading their SAP systems to SAP ERP 6.0, despite the economic downturn. 152 European and North American SAP customers and system integrators participated in the survey.
According to the survey, nearly three out of every four projects remain on schedule, and only 11% are delayed beyond 2009. At the same time, 28% of the companies that are not delaying the upgrade are looking to complete the project with a lower budget.
A free copy of the complete survey results is available for download at the Panaya website
[2009 SAP Upgrade Survey|http://www.panayainc.com/sap-upgrade-survey.html]

Hi Kim,
Thanks for your inputs,
I have used CRM_SURVEY_SUITE to create the survey and would like to analyse the same.
I checked the CRM - BW cubes
1. CRM Survey: Results - 0SVY_DATA_1
2. CRM Survey: Answers - 0SVY_ANSWER_TEXT
but the surveys ID are not getting updated .
can you tell me the cubes in which the Survey ID and the results can be updated.
Thanks,
Satish

SAP Upgrade from 4.7 to ECC 6.0 connected to BW 7.0 Best Practices

We are upgrading SAP R/3 4.7 to ECC 6.0. We have been running live in a BW 7.0 environment. We have done some enhancements for 2LIS_11_VAITM - Sales Document Item Data and 2LIS_13_VDITM - Billing Document Item Data datasources. We currently have a test instance that has been upgraded to ECC6.0.
What are the best business practices for testing BW to insure data transfer and enhancements are working correctly?
Eg. Should we connect the ECC6 instance to BWD and test there OR upgrade R/3 TST that is connected BWD and test there OR Upgrade QAS and test in BWQ.
Thanks in advance . . .
Edited by: RWC on May 4, 2011 6:26 PM

Hi RWC,
the plug-in will change slightly, you may notice differences in the screens of RSA2 and others after the upgrade.
Regarding best practices: In a recent upgrade our project team decided to create a parallel landscape with a new, additional Dev and QA on the R/3 side.
We connected these new systems to a BW Sandbox and the BW QA.
We identified all datasources, transfer rules and infopackages in use in production and recorded them with related objects onto transports in BW Dev. Before the import into BW Sandbox and BW QA we adjusted the system name conversion table to convert from old R/3 Dev to new R/3 Dev in order set up all the required connections for testing with the upgraded R/3 systems.
After the go LIVE of the upgrade we renamed the old R/3 Dev system in BW Dev and ran BDLS to convert everything (speak to your Basis team). That way we made sure not to lose any Development and we got rid of the old R/3 Dev system.
Take a look at this post for issues we encountered during this project and test everything you load in production.
Re: Impact on BI 7.0 due to ECC 5.0 to ECC 6.0 Upgrade
Best,
Ralf

WCF-SAP Adapter throwing errors after SAP Upgrade from ECC 5 to ECC6 Release 640 to 700

Hello Everyone,
We were able to communicate(Send and Receive Idoc's) to SAP via WCF-SAP Adapter in BizTalk 2010.
SAP Servers were upgraded to ECC5 to ECC 6 and we started facing below issue communicating on send and receive both.
I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDP01006GRP   IDOCTYP: ORDERS05
Release: 700    CIMTYP: . Ensure that your message xml validates against the operation schema.
Server stack trace:
   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
   at Microsoft.BizTalk.Adapter.Wcf.Runtime.
Thanks,
Vikingss

I am aware that there is a hotfix available but that is more on the Receive Side from SAP. Nevertheless I installed the hotfix but issue still persists. Any suggestions will be highly appreciated.
For this issue, you can contact Microsoft support directly(http://support.microsoft.com).

Step by Step procedure of SAP upgrade + Oracle upgrade from 4.6C to ECC 6.0

Hi Chaps,
Could you please provide the step by step procedure of end to end SAP Upgrade which includes oracle database upgrade as well..and post upgrade process tooo....
Thanks
Keshav

There is nothing like that.
Each system is different, each application is different; on top of that it would be WAY too much to post here.
Get your upgrade guides:
http://service.sap.com/instguides
--> SAP Business Suite Applications
--> SAP ERP
-> SAP ERP 6.0
--> Upgrade
--> Upgrade Documentation - SAP ERP 6.0 SR3
Here choose your OS and platform and read all the notes. Be prepared to use a week just for technical preparation and documentation/notes checking before you even doubleclick on something.
For the Oracle Upgrade use
http://service.sap.com/instguides
--> Other Documentation
--> Database Upgrades
--> Oracle
Markus

SAP SRM 7.0 with ECC EHP 4 components to execute scenario

Hi All,
I am new to SAP SRM 7.0.Could you please let me know that what are all the components needs to be in place to execute the technical scenarios and business scenarios.I had an hands on experience on SAP SRM 5.0 with ECC 6.0 backend.
Some where i read that there are lot of configuration changes when we integrate SRM 7 with ECC EHP 4.Do we need to have PI 7 for executing Centralized contract and plan driven procurement scenario?Please guide me to have some exposure towards higher version.Thank you in advance.
Best Regards,
praveen

Hello,
You can refer the INSTALLATION AND UPGRADE INFORMATION , Master guides etc maintained at the below mentioned location which will answer all your query's here.
Goto URL http://service.sap.com/srm-inst and then navigate to SAP SRM --> SAP SRM Server 7.0 .
Best Regards,
Rahul

SAP Data Archiving in R/3 4.6C and ECC 6.0.

Hi Guys,
Need some suggestions,
We currently working on SAP R/3 4.6 and have plans to upgrade it to ECC 6.0,
In the mean time there is an requirement for SAP Data Archiving for reducing the database size and increase system performance.So wanted to know if its better to do Data Archiving before upgrade or after. Technically which will be comfortable, Also wanted to know if any advanced method available in ECC 6.0 compared to SAP R/3 4.6.
Please provide your valuable suggestion.
Thanks and Regards
Deepu

Hi Deepu,
With respect to archiving process there will be no major difference in 4.6 and ECC 6.0 system. However you may get more advantage in ECC6.0 system because of Archive routing and also upgraded Write, Delete programs (upgraded program will depend on your current program in 4.6 system). For example In 4.6 system for archive MM_EKKO write program RM06EW30, archiving of purchase document is based on company code in the selection criteria and there is no preprocessing functionality. In ECC 6.0 you can archive by purchase organization selection criteria and preprocessing functionality will additional help in archiving of PO.
In case if you archive documents in 4.6 and later upgrade it to ECC 6.0, SAP system will assure you to retrieve the archived data.
With this i can say that going with archiving after upgrade to ECC 6.0 system will be better with respect to archiving process.
-Thanks,
Ajay

SAP Upgrade 4.6C to ECC 6.0 EHP5 system customer is using Data Archiving

Similar Messages

Maybe you are looking for