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

Similar Messages

ECC upgrade impact on BI

Hi Gurus,
We are currently on BI7 but the R/3 version is 4.7. The R/3 is going to be upgraded to ECC6 shortly. I know this is going to have an impact on BI7 since some of the tables & fields are going to be standard, which might have been customized earlier. Can u give suggestions on the impact on BI and what care needs to be taken from a BI perspective during the ECC upgrade. Also, any doc or pointers which talks about such impact on BI. Points will be awarded accordingly. Thanks for the help in advance.
Ud

Hi,
the following are the activities that I can think of Pre- and Post ECC Upgrade on the BI box.
Pre-Upgrade
- ensure that the Delta queue is cleared in RSA7
- check the PI in ECC6.0
- stop all loads from BW
Post-upgrade
- run Init w/o Data Transfer for deltas
- check extraction for full & delta loads
- replicate all data sources in ECC
- activate all rules thru programs
Other than this, is there any other activity a BW consultant has to do. Also, would it make any difference to our upgrade approach if the BW system is BW3.5 or BI7? our system is on BI7 currently.
Additionally, what SAP Notes will have to be applied pre and Post ECC upgrade.
Would the ECC upgrade have any impact on BI Unicode conversion?
Also, I am still worried about the change to Data Sources post-upgrade to ECC as we have a lot of customization. how do i find out which fields in the Data Sources have been standardized in ECC?
Reponses highly appreciated and points duly awarded.
Uday

ECC Upgrade impact on BDC's

Hi All,
My question is regarding transaction level changes resulting dfrom ECC upgrade.
We are upgrading ECC 4.7 to ECC6.0. There are certain BDC's already working in 4.7 and I need know the transction level changes so as to see impact on BDC pragrams.
I have already tried using SPAU and SPDD for modifications.
Is this kind of information maintained on help or service-marketplace portals? I checked but could not get the information.
Thanks and Regds,
Gaurav

Hi Gautham,
The table u suggested gives details on trasnaction names.
Also the link you have given is about the various issues related to BDC in upgradation process.
My question is different as to find out the changed at transaction level like ...field changes.... mandatory.....sequesce of fields....
is this kind of incormation maintained in any help or service marketplace folders....
I have already tried SPAU and SPDD but don't want to do that for number of transactions.
Regds,
Gaurav

SAP ECC upgrade - Impact to GRC

Hi Forum guru's,
We have a client that is currently using all 4 components of GRC AC Version 5.3 running on ERP 4.7. The client will be upgrading shortly to ECC6 and I would like to ascertain some important tasks required from a GRC functional point of view and the components that will be the most impacted.
1) New connectors will be created for each component.
2) RA&R: Re-upload of auth objects and full re-generation of rules.
3) ERM: New connectors to be added to the current landscapes and roles uploaded.
4) SPM: Component to be fully re-configured on the new system
5) CUP: Existing workflows will apply as they do not use the "system" as the initiators.
Is there any other important steps from a functional point of view that I am missing?. Please advise.
Rgds,
Prevo

Hello Prevo,
1) New connectors will be created for each component.
-> Not required. Existing Connectors created in each of the component of GRC for 4.7 system will work. Just need little modifications.
2) RA&R: Re-upload of auth objects and full re-generation of rules.
-> Right.
3) ERM: New connectors to be added to the current landscapes and roles uploaded.
-> No new connectors required and can use the existing connector after little modification.
4) SPM: Component to be fully re-configured on the new system.
-> Upgrade of RTA component will upgrade the SPM component as well.
5) CUP: Existing workflows will apply as they do not use the "system" as the initiators.
-> right.
To enable AC5.3 to be used with ECC system, you will need to install the RTA of 5.3 for ECC 6.0 system. You can download this RTA from the SAP service market place and then install them. This will ugprade your existing RTA component installed for SAP 4.7 to RTA for ECC6.0.
You can follow instructions on Upgrade guide for more information about the upgrade. Also, there are SAP Notes available which you can use.
Regards, Varun

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

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

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.

Put Together A Data Archiving Strategy And Execute It Before Embarking On Sap Upgrade

A significant amount is invested by organizations in a SAP upgrade project. However few really know that data archiving before embarking on SAP upgrade yields significant benefits not only from a cost standpoint but also due to reduction in complexity during an upgrade. This article not only describes why this is a best practice but also details what benefits accrue to organizations as a result of data archiving before SAP upgrade. Avaali is a specialist in the area of Enterprise Information Management. Our consultants come with significant global experience implementing projects for the worlds largest corporations.
Archiving before Upgrade
It is recommended to undertake archiving before upgrading your SAP system in order to reduce the volume of transaction data that is migrated to the new system. This results in shorter upgrade projects and therefore less upgrade effort and costs. More importantly production downtime and the risks associated with the upgrade will be significantly reduced. Storage cost is another important consideration: database size typically increases by 5% to 10% with each new SAP software release – and by as much as 30% if a Unicode conversion is required. Archiving reduces the overall database size, so typically no additional storage costs are incurred when upgrading.
It is also important to ensure that data in the SAP system is cleaned before your embark on an upgrade. Most organizations tend to accumulate messy and unwanted data such as old material codes, technical data and subsequent posting data. Cleaning your data beforehand smoothens the upgrade process, ensure you only have what you need in the new version and helps reduce project duration. Consider archiving or even purging if needed to achieve this. Make full use of the upgrade and enjoy a new, more powerful and leaner system with enhanced functionality that can take your business to the next level.
Archiving also yields Long-term Cost Savings
By implementing SAP Data Archiving before your upgrade project you will also put in place a long term Archiving Strategy and Policy that will help you generate on-going cost savings for your organization. In addition to moving data from the production SAP database to less costly storage devices, archived data is also compressed by a factor of five relative to the space it would take up in the production database. Compression dramatically reduces space consumption on the archive storage media and based on average customer experience, can reduce hardware requirements by as much as 80% or 90%. In addition, backup time, administration time and associated costs are cut in half. Storing data on less costly long-term storage media reduces total cost of ownership while providing users with full, transparent access to archived information.

Maybe this article can help; it uses XML for structural change flexiblity: http://www.oracle.com/technetwork/oramag/2006/06-jul/o46xml-097640.html

Data Archiving - System Prerequisites

Hi,
We are planning to ARCHIVE some of the tables to reduce the TCO. (Total cost of Ownership)
In this regard, I would like to know the following:
On the Basis side, I want to check for any prerequisites etc (like Minimum SP LEVEL, Kernel version, Import Notes to be applied etc)
Are there any document which clearly talks about these prequisites for preparing the System in order to be able to carry out the Archive work without any issues.
(Note: We are not using ILM solution for Archiving)
I am mostly concerned with the SAP Notes that are considered to be the prerequisites.
Best Regards
Raghunahth L
Important System information :
Our system version is as follows :
System -> ERP 2005 (Production Server)
OS      -> Windows 2003
DB      -> Oracle 10.2.0.2.0
SPAM    -> 7.00 / 0023
Kernel -> 7.00 (133)
Unicode -> Yes
SP Info:
SAP_BASIS 700(0011)
SAP_ABA 700(0011)
PI_BASIS 2005_1_700(0003)
ST-PI 2005_1_700(0003)
SAP_BW 700(0012)
SAP_AP 700(0008)
SAP_HR 600(0003)
SAP_AP 700(0008)
SAP_HR 600(0013)
SAP_APPL 600(0008)
EA-IPPE 400(0008)
EA-DFPS 600(0008)
EA-HR 600(0013)
EA-FINSERV 600(0008)
FINBASIS 600(0008)
EA-PS 600(0008)
EA-RETAIL 600(0008)
EA-GLTRADE 600(0008)
ECC-DIMP 600(0008)
ERECRUIT 600(0008)
FI-CA 600(0008)
FI-CAX 600(0008)
INSURANCE 600(0008)
IS-CWM 600(0008)
IS-H 600(0008)
IS-M 600(0008)
IS-OIL 600(0008)
IS-PS-CA 600(0008)
IS-UT 600(0008)
SEM-BW 600(0008)
LSOFE 600(0008)
ST-A/PI 01J_ECC600(0000)
Tables we are planning to archive
AGKO,     BFIT_A,     BFIT_A0,     BFO_A_RA,     BFOD_A,     BFOD_AB,     BFOK_A,     BFOK_AB,     BKPF,     BSAD,     BSAK,     BSAS,     BSBW,     BSE_CLR,     BSE_CLR_ASGMT,     BSEG_ADD,     BSEGC,     BSIM,     BSIP,     BSIS,     BVOR,     CDCLS,     CDHDR,     CDPOS_STR,     CDPOS_UID,     ETXDCH,     ETXDCI,     ETXDCJ,     FAGL_BSBW_HISTRY,     FAGL_SPLINFO,     FAGL_SPLINFO_VAL,     FAGLFLEXA,     FIGLDOC,     RF048,     RFBLG,     STXB,     STXH,     STXL,     TOA01,     TOA02,     TOA03,     TOAHR,     TTXI,     TTXY,     WITH_ITEM,          COFIP,     COFIS,     COFIT,     ECMCA,     ECMCT,     EPIDXB,     EPIDXC,     FBICRC001A,     FBICRC001P,     FBICRC001T,     FBICRC002A,     FBICRC002P,     FBICRC002T,     FILCA,     FILCP,     FILCT,     GLFLEXA,     GLFLEXP,     GLFLEXT,     GLFUNCA,     GLFUNCP,     GLFUNCT,     GLFUNCU,     GLFUNCV,     GLIDXA,     GLP0,     GLPCA,     GLPCP,     GLPCT,     GLSP,     GLT0,     GLT3,     GLTP,     GLTPC,     GMAVCA,     GMAVCP,     GMAVCT,     JVPO1,     JVPSC01A,     JVPSC01P,     JVPSC01T,     JVSO1,     JVSO2,     JVTO1,     JVTO2,     STXB,     STXH,     STXL,     TRACTSLA,     TRACTSLP,     TRACTSLT,
in addition we have some Z Tables to be archived.

Hi,
Pre-requisites for search OSS notes or BC Sets depends upon the program that is used in archive, delete or read.
If there is no proper selection criteria in write variant selection,
If the program is getting terminated due to long processing time,
If percentage of data archived for your selection is less even after data meeting minimum criteria,
If system allows user to change archived data,
With all the above scenarios we will search for OSS notes. If SAP has released BC sets then we will implement these.
If you have any problem while archiving and based on the archiving experience if you think that some of the oss notes will help then take a call on implementing it.
With the tables you have mentioned i can say that archiving objects such as FI_DOCUMNT, FI_SL_DATA, EC_PCA_ITM, EC_PCA_DATA, CHANGEDOCU, ARCHIVELINK.
You have to search any latest release BC sets or OSS notes for your system application.
-Thanks,
Ajay

Business Intellience and Data Archiving

Once you have implemented Data Archiving, what are the possible ways of allowing BI standard and custome extractors to look at both SAP ECC online and archived data (the archived data sits on Open text). How do you deal with BI complete reload and refresh requirement for a specific data if the data has been already been archived?

Is there any addiotional things we need to do at info source level after activating the content? Selecting the correct data source etc.
If there is a enhancement to the extraction structure then what all steps manually we need to do at info source level? When we replicate the data source which has been enhanced, will it create the infoobjects automatically so that they can be used in infosource communication structure?
As I am new to the system, I am running in to all these questions.
Appreciate any help in step by step how things will work.
Thanks.

ECC upgrade

we are performing the ECC upgrade with unicode conversion from 620 system which has db size 7.24TB
1. do any one performed this on similar huge database?if yes give details
2. since db size is high do we need to go for CUUC or upgrade with unicode in two projects
3. how to calculate the downtime apart from the OSS note provided by SAP which is purely theoritical
4. what are the major challenges during export,import

Hi,
I'm going to do Productive Upgrade from 4.6C to ECC 6.0 next week with a 7.4 TB Oracle Database and I have already done 5 tests using a copy from Production database let me give answers your questions:
1. do any one performed this on similar huge database?if yes give details
Yes, R/3 4.6C to ECC 6.0 on HP/UX 11 and Oracle 10.2.0.2.
You will find upgrade info that says the database size is not that critical and this is true as long as you do some fixes before the actual upgrades (of course after real live test upgrades with a PRD copy). The last Upgrade test we did we achieved 7 hours and 31 minutes of downtime not including post upgrade that will be the longest part of the whole process. In our downtime we had to include a lot of support packages and this system has some specific industry solutions that makes thinks harder. The first test run used 117 hours. SAP assesment service is really recomended in this kind landscapes and they helped us to do some cleanup of unused tables or unused data that let us move in the second test to 20 hours and with some other investigation and trials by our own we achieve the final 7:31 time and espect to get a lower time during Production Upgrade because the PRD server and DB server are more powerfull . Downtime depends a lot in Hardware and here the servers are running on servers with 8 1.6 Itanium CPU's and 32Gb of RAM, EVA system for DISKS.
2. since db size is high do we need to go for CUUC or upgrade with unicode in two projects
I will strongly recomend to do it in two projects unless you have a long time that you could use to achieve all this in one step or in case your post upgrade is really short.
3. how to calculate the downtime apart from the OSS note provided by SAP which is purely theoritical
The only way to calculate downtime is to actually doing a test upgrade on a PRD copy. This is also what SAP people will tell you.
4. what are the major challenges during export,import
I can´t answer this as we did not went to Unicode.
Good Luck during your upgrades,

BW Extractors During ECC Upgrade

All, We are moving from 46B to ECC. One of the open questions we have is what needs to be done during the upgrade prepare phase with the extractors from our BW system.
We are using the downtime minimized approach, so the prepare phase will start several days prior to the start of upgrade downtime. Here is the question: We have 50+ delta extractors running that pull data from the ECC system to BW. SAP has told us that during the prepare phase (this is during system uptime) we will need to turn off the extractors and clear the delta queues prior to the prepare phase running. But they are also telling us that we COULD turn them back on after prepare is complete but before the downtime starts but that they do not recommend it.
Any experience with BW extractors and an ECC upgrade? Since we are starting the ECC prepare phase several days prior to the start of downtime for the upgrade, we are trying to determine whether we will be without BW feeds for that entire time or only during the downtime.
Thanks!

> Thanks for the reply. So you see no reason to have
> the extrators off the entire time between when
> RSVBCHK is run during prepare and when it is run
> during the downtime?
No - I don't see it. We used that procedure when we went from 4.6 to 4.7 and it worked - we didn't have any data loss.
> We will have approximately 48 hours between the
> prepare and the start of downtime and obviously the
> business would prefer to have the extracts available
> during this time.
RSVBCHK doesn't just check for the BI deltas but for cancelled update tasks too and some more things.
You must though make sure that nobody creates any more deltas (thus no more production) after you passed RSVBCHK during UPGRADE OR make sure, someone is around at a later point before you shutdown the system and load the data out of the R/3 system. You must make sure that all deltas are loaded before you enter MODPROF_TRANS, if you still have delta there, it will be lost.
Markus

Customer exit is not functioning after ECC upgrade/support package

It seems our customer exit is not functioning after ECC upgrade/support package. I tried to activate the project again, no use. please help. Thanks! (see below for the enhancement info)
COZF0002 Change purchase req. for externally procured component
EXIT_SAPLCOZF_002
INCLUDE ZXCOZU02
*& Include           ZXCOZU02
CONSTANTS: lcc_eban(25)   TYPE c VALUE '(SAPLCOBC)EBAN'.
FIELD-SYMBOLS: <fs_eban>   TYPE eban.
DATA: l_fkstl TYPE prps-fkstl.
Move values from the LUW to the Internal Table
ASSIGN (lcc_eban) TO <fs_eban>.
If the field symbol is "NOT' empty then proceed
IF ( <fs_eban> IS ASSIGNED ).
if WBS work order, get cost center from PRPS
IF ( caufvd_imp-auart = 'ZM05' ).
    SELECT SINGLE fkstl INTO l_fkstl FROM prps
      WHERE pspnr = caufvd_imp-pspel.
    IF ( sy-subrc = 0 ).
      WRITE l_fkstl TO <fs_eban>-zzfistl.
    ENDIF.
if not WBS WO, move cost center minus leading zeros to funds center
ELSE.
    WRITE caufvd_imp-kostl TO <fs_eban>-zzfistl.
ENDIF.
ENDIF.

Did you mean set a break point in the follow code?(Include ZXCOZU02), I tried set a break point in this code, but It didn't stop .
*& Include ZXCOZU02
CONSTANTS: lcc_eban(25) TYPE c VALUE '(SAPLCOBC)EBAN'.
FIELD-SYMBOLS: <fs_eban> TYPE eban.
DATA: l_fkstl TYPE prps-fkstl.
Move values from the LUW to the Internal Table
ASSIGN (lcc_eban) TO <fs_eban>.
If the field symbol is "NOT' empty then proceed
IF ( <fs_eban> IS ASSIGNED ).
if WBS work order, get cost center from PRPS
IF ( caufvd_imp-auart = 'ZM05' ).
SELECT SINGLE fkstl INTO l_fkstl FROM prps
WHERE pspnr = caufvd_imp-pspel.
IF ( sy-subrc = 0 ).
WRITE l_fkstl TO <fs_eban>-zzfistl.
ENDIF.
if not WBS WO, move cost center minus leading zeros to funds center
ELSE.
WRITE caufvd_imp-kostl TO <fs_eban>-zzfistl.
ENDIF.
ENDIF.

CS-MARS, data archiving issue.

Hello at all.
I'm using CS-MARS-20.
Reimaged, restored and upgraded to software version 6.1.8, I'm not able to start data archiving successfully.
I have configured data archiving using a remote SFTP server, click Apply, Start and Activate: data archiving status is running, service is enabled and remote server is available.
But MARS doesn't archive nothing!
Using another SFTP remote client with the same account used from appliance, I can create folders, files and remove.
Any ideas?
Thanks.
Regards.
Andrea

Now we are moving to a NFS solution.
Data archiving status is running, archiving service is enabled and remote server is available but events, incidents and configuration are not exported.
I can use CLI (pnexp command) to export configuration successfully.
Any ideas?
Why data archiving doesn't work?
Thanks.
Andrea

Upgrade impact of converted Legal Entities

Customer: Aviva
Sr 3-2921431541
Aviva has a requirement to rationalise the number of Legal Entities and on the day that some of these Legal Entities are no longer valid transactions in the sub-ledgers under the old Legal Entities need to be converted to the new Legal Entities in the GL.
An option that is being considered is that IDT is used as part of the Sub-Ledger (AP & AR) Transfer process to the GL. When the sub-ledger transactions are transferred to the GL Interface Table the Legal Entity (Segment 1 - a Balancing Segment) will be converted from the old Legal Entitiy to the new Legal Entity using IDT. The Request ID may also need to be blanked to allow this to happen.
Ratification Required in this context
Will the difference in LE between sub-ledger and GL impact any data migration process used when upgrading from R11i to R12?
Thanks
Hans

Hi Hans
I see following issues from SLA perspective.You might take opinion from GL/Legal entity team/AP for unseen repercussions from their end
1) Since subledgers are not updated with new entity id in 11i,reconciliation between SLA trial balance report and GL balances in R12 would not be easy as sublegders would migrate data with old entity id in SLA tables.
Customer would have to take care of discounting old entities while reconciliing.
2) Since reports are some times run with account flexfield parameter ,a report with same flexfiled parameter in SLA would not return same data in GL.
For ex GL account analysis 180 char would show different data from SLA Account analysis report.
Point 1 and 2 are usually used by customer to ensure successful upgrade happened but in this scenario actual issue would be covered by legal entity mismatch.
3) I assume that if legal entity is obselete corresponding bsv would also be disabled.In that situation subledgers like AP which use businessflow feature would be affected i.e. when 11i invoice with old bsv is paid in R12 ,payment would not account as liability line of payment would be invalid as liability ccid is copied from that of Invoice.Same issue can happen with Accounting reversal feature which is used both by AP/AR.
If old bsv is still valid even then unnecessary balancing lines/intercompany lines could be generated.Customer should think about defining alternate ccids.
However best solution could be to ensure that subledgers prior to upgrade are corrected for Bsvs such that discrepany between Subledgers and GL is resolved prior to upgrade.
Thanks
Preeti

ECC upgrade impact on data archival

Similar Messages

Maybe you are looking for