Upgrade 4.7 to ECC 6.O (FI/CO)

Dear All,
Can please someone suggest what are the best approach or step should be taken care while upgrade 4.7 to ECC 6.0 from FI and CO prospective, is any best practice available in that context .
Thanks for Help.
N
Moderator: Please, search SDN

Hi,
basically you focus on ECC 6 has new gl ledger concept which is different for 4.7
version in the folloiwng manner & Tax structure also. In ecc6.0 its different form 4.7.
1. It enables Business area posting - Segment reporting made easy
2. Profit centre accounting is through new GL
3. Split of entry to post assets and liabilities to respective profit centres. (Balance sheet items)
4. Enables commitment of FM

Similar Messages

Recommandations for upgrading from 46C to ECC 6.0

Hello
Our SAP system landscape is actually in 46c and is only composed of 3 servers with almost 40 users declared (25 actives) on production system. Modules FI/CO HR MM are actually implemented.
We plan to upgrade the system to ECC 6.0 between March and August of 2009. The evaluation of the upgrade should begin as soon as possible. Do you think it can be possible to realise the upgrade alone, without the help and expertise of a SAP consultant? Do you think the delay for preparing the upgrade is suffisant?
Thank you.

As suggested earlier, refer to Master and technological guides for reference.
also for information, the upgrade can fall under any below scenarios.
1. Strategic Business Improvement
Focus on functionality extension and improvement
Enablement of new and optimized business processes and scenarios based on new ERP core functionality
2. Functional/Retrofit Upgrade
New functionality to be implemented as part of the upgrade, modification clearing
Focus on reduction of system complexity
3. Technical Upgrade
Focus on pure technology upgrade
Retain functionality used
Review Usage of custom developments
As per the requirement. knowledge and experience the decision can be made.

Error in upgrade from 46c to ecc 6.0

hi experts,
we are facing an error at the time of upgrade from 46c to ecc 6.0 in the phase JOB_RSUPGAIMEXE.
did anyone face this error anytime during upgrade on windows plotform?
Please let us know your comments..
regards
raghu

Hello,
Can you please look in the /put/log directory and copy the error from the appropriate log file. You should find a log file with a name similar the to upgrade phase that is causing the error.
Thanks
N.P.C

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

SAP Security Upgrade 4.6C to ECC 6.0

Hello Gurus,
we are upgrading our systems to ECC 6.0 from 4.6C.
in SU25 step, do i need to manually go into every role and find the differences in Field values ?
there are more than 2500 roles and its becoming tedious task.
Is there any easy or other procedure available for the same ?
Regards,
Chaitanya

There are many tricks you can use to shave a role upgrade down to about 2 day's work, but day 1 is during the implementation design way back when to consider upgrades much later on...
Just knowing that you have 18k roles and 2500 turned red in step 2a is not enough infos to give you any efficient advice (I am not talking about your time... ;-).
What is however obvious is that between 2a and 2c there is 2... ah...?!?! That is your next closest catalyst, but dont hit the "accept SAP data" button unless you have not done any changes in SU24!
Some other key figures for upgrades are:
- Number of roles with distinctly different menus.
- Number of changed auths which are not copies.
- Number of manual auths needing manual adjustments.
- Obsolete and disabled objects.
- Security patches for unnoticed missing auth-checks.
- Cut-over, development freeze and parallel maintenance time period.
Cheers,
Julius

Upgraded our system from ECC 6 to 6.04 (EHP4).

Dear All,
We have upgraded our system from ECC 6 to 6.04 (EHP4).
There are many request in old development server which are in local request now .
We want to transport those requests to new development server which is upgraded one.
Can any one let me know is there any standard way of transporting these requests from old Development system (6)to new one(6.04).
Thanks
Anuradha

Hi Sahil,
Looks like latest EHP installer concentrate more on downtime minimize strategy. We have only 3 options available as follows.
1. Standard resource use
2. High resource use
3. Manual selection
Please take a look at below thread. Let's see what other experts comment on this.
/thread/1458520 [original link is broken]
Thanks,
Siva Kumar
Edited by: Siva Kumar Arivinti on Nov 19, 2011 7:57 PM

Warning codes generated in UCCHECK   - Technical Upgrade - 4.0b to ECC 6.0

Hi SDN'ers ,
I am currently working on Technical Upgrade project from 4.0 b system to ECC 6.0 system . I am facing a
problem relating to the analysis of the warnings displayed whehn we run the UCCHECK for the client inventory by
checking the "Display lines that cannot be analyzed statically" option under the Selection-screen block
"Statements that cannot be analyzed statically" .Based on the warning codes generated during UCCHECK, they can
be classified into 12 different categories given below in the list ( Viz. ABB,MESSAGEG!C,MESSAGEG!D......MESSAGEG!P).The same are given below in the end
I want to know
- Which are the warning codes which need resolution so that the program does not encounter any runtime
errors or during Integration testing ?
- Do all the offset related errors (For example ;variable A = B+offset(length)
or variable A+offset(length) = B ) need resolution so that the program gives no runtime error.
- Also, do all statements where length is calculated using STRLEN also need changes ? I have seen offset length related warnings come under MESSAGEG!M warning code.
The objective of this is to make sure that the upgraded system ECC 6.0 in Australia ,when rolled out to
non-English speaking geographies in APAc such as Malaysia,Japan or China would only need translations and no ABAP Coding effort even when using languages such as Japanese which have double byte characters.
S.No.     Error Code     Message
1     ABB     Syntax Check Aborted
     ABB Total
2     MESSAGEG!C      check at runtime. at runtime.
           statement because of untyped or generic operands. It can only carry out this
          The system could not perform a static convertibility check on the current
     MESSAGEG!C Total
3     MESSAGEG!D      out this check at runtime. It can only carry out this check at runtime.
           to a table line because of untyped or generic operands. It can only carry out
          The system could not perform a static check on convertibility from a work area
     MESSAGEG!D Total
4     MESSAGEG!E      check at runtime. at runtime.
           defined by a "DATA" statement. .
           statement because of untyped or generic operands. It can only carry out this
          Field "ELEMENTN" is unknown. It is neither in one of the specified tables nor
          The system could not perform a static comparability check on the current
     MESSAGEG!E Total
5     MESSAGEG!F      operand "<FELD1>" for the current statement. .
     MESSAGEG!F Total
6     MESSAGEG!G      current statement on incompletely typed operand "<DATA>". .
     MESSAGEG!G Total
7     MESSAGEG!H      for the incompletely typed operand "<S>". . - - - - - - - - -
          The system cannot perform a static check on a character-type field data type
     MESSAGEG!H Total
8     MESSAGEG!I      incompletely-typed operand "<A>" in the current statement. .
          The system cannot perform a static check on a character-type data type for the
     MESSAGEG!I Total
9     MESSAGEG!J      "<%_1_SYSINI>" in the current statement to check whether the operand can be
          The system cannot perform a static check on incompletely-typed operand "VALUE"
     MESSAGEG!J Total
Early response wil be highly appreciated.

Hi Karthik
>
> 1) SPDD adjustments are done in which phase? PREPARE or UPGRADE?
>
SPDD is done in Upgrade ->Phase ACT_700
> 2) Are here special cases where the adjustments need to be done before running the UPGRADE phase?
>
At ACT_700 phase stop the upgrade and take a backup of the DB and the PUT<DIR> before starting the SPDD activity.
Make sure there are no pending tp request. Either release them or delete them.
All phase need to be completed successfully in PREPARE, before starting UPGRADE
Cheers
Shaji
Edited by: Shaji Jacob on May 5, 2008 9:23 PM

SAP R/3 System analysis before upgrade 4.6C -- SAP ECC 6.0

Hello!
Before the upgrade from R/3 4.6C to ECC 6.0 I would like to execute SAP R/3 system analysis.
The following functions should be included in this program:
- detailed analysis of system modifications (effort driver and risk factor during an Upgrade)
- comparison against a SAP ERP 6.0 reference system
- extension SAP tools, including RBE and conflict lists (SPAU/SPDD)
- syntax analysis of program code with respect of adjustement need
- quality control of own development
- control of amount of transports within different company areas
- control of user information, such a user type, logon date, etc.
- basic control, whether a sufficient authorization concept is available
- Identification of objects that should be considered for the archiving in oder to decrease the db-size
My question are:
- which tasks can be convered with SAP standard transactions what are the names of the transactions?
- which effort do I investigate for these tasks?
Thank you very much!
regards

Dear Thom,
To know the functionality changes u can refer http://solutionbrowser.erp.sap.fmpmedia.com/
http://www.sap.com/solutions/business-suite/erp/pdf/BWP_ERP2006_Upgrade.pdf
http://service.sap.com/releasenotes and http://service.sap.com/upgrade for functional changes.
Need to consider the following things:
For Reportsits custom developed program so unless there is any kind of change in requirement from the client regarding the layoutnothing needs to be changedI think it will work fine in ECC 6.0 toexcept few things may needs to be changed..so you need to discuss whether they want the reorts as it is right nowor want to change the layout (adding some new info/fields etc) of any reportso u need to modify the program for thoseand estimate accordinglyfor a medium complexitys Report dev it takes approx 9 pd (FRSTDSCoding+Unit Testing)so to modify it will be less than that (depending upon the scope of changes)
Now say for Batch Inputs(interface/Data Migration) using BDCyou need to see how many BDCs are thereagain if the field lengths and layouts are not changingthen no need to change anything (except the main thing..you need to change the obsolete function modulesthere are some in 4.6 c like for data upload ws_upload_*** is there 4.6C but obsolete in ECC6.0there are some new with enhanced functionality so you need to modify the BDCsand many cases it happens that the whole transaction screen changes for processin that case better to develop new BDCsso you have to consider those parameterlook into and estimate accordinglymodifying a BDC should not take more than 1 PD
Now say for Formsthere was no Smart form in 4.6Cform printer was there..though the same option is there in ECC 6.0 too..but better to go for/should go for Smart formin that caseits complete new devso estimate accordinglya medium complexitys form should take 8 PD (FRSTDSCoding+Unit Testing)you can take it as 10 PD tooeven if client wants to keep it is as it was in older versionyou have to redevelop the layout in ECC 6.0 againas form printer is even client dependentmaximum you can copy the program associated with that form in the new version tooand your effort will be savedagain you have to consider if clients wants to change the layout too
Now for enhancementso in that case u need to see individual casesfor a medium complexity enhancement it should take max 15 PD (FRSTDSCoding+Unit Testing)
One more important thing is that the Unicode Compatibilitythis needs to be done.needs to change the code (variable name) accordingly.also Version management tool is used for the standard programs
Also pls find the following forums:
Re: Data Migration from 4.6C to ECC 6.0
List of transations supported in SAP 4.6c and not in ECC6.0
Re: Upgradation from 4.6C to ECC 6.0
Re: what's the advantage to upgrade 4.6c to ECC5.0...
RE: Help required regarding to upgrade from R/3 4.6c to mySAp ERP 2005
Upgrade batch inputs from 4.6C to mySAP ERP 2005
/thread/317225 [original link is broken]
Upgrade from SAP R/3 to ECC 6.0
Hope it will help you.
Thanks,
Atin
<b><b>Reward points if it helps.</b></b>

Upgrade from 46C to ECC 6

Hello:
We are planning to begin technical upgrade in SAP, from 46C to ECC 6.0.
I have the next landscape:
-Current SAP (CS): SAP 46C with Oracle 8.1.7 and Solaris 8
-New Server (NS): Without SAP, 40% more of capacity, with Oracle 10.2 and Solaris 10 already installed.
We want to install SAP ECC 6.0 in NS and get the data from CS.
Which is the best and easy way to do this? SAP manuals are quite generic. I have two ideas but I would like your comments:
1st way
1. Homogeneous copy of CS
2. I install ECC 6.0 in NS with the option to import data generated in 1. (is this possible??)
3. Finish installation and aditional configurations. I begin to test.
2nd way
1. Homogeneous copy of CS
2. I install 4.6C in NS with the option to import data generated in step 1. (Not sure if 4.6C will accept Solaris 10 and Oracle 10.2).
3. I suppose I don't need to reconfigure after installation and import.
4. I do necessary tests. At this point I would have 46C on the new versions of Solaris and Oracle.
5. I begin the SAP upgrade to ECC 6.0 in NS
6. .... The remaining processes indicated by SAP
Thanks for your attention.

> -Current SAP (CS): SAP 46C with Oracle 8.1.7 and Solaris 8
> -New Server (NS): Without SAP, 40% more of capacity, with Oracle 10.2 and Solaris 10 already installed.
The database software is usually installed during the run of sapinst/R3setup, not before. You may run into problems if you pre-install Oracle (environment, necessary database options not set etc.)
The easiest way would be do to a system copy.
I would then
- install the latest Oracle instantclient
- install the latest kernel 46D_EX2 kernel
Markus

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        .

Short dump in MIGO and VL02N when upgrading from 46C to ECC 6.0

Hello,
We are doing an upgrade from R/3 46C to ECC 6.0 and we face a shortdump in trx MIGO (upon saving the document).
DBIF_RSQL_INVALID_REQUEST
a BKPF_INSERT in program SAPLF005
The same shortdump happens when doing a Goods Issue on the SD side.
Looking at the program, this is not modyfied so I guess it is a standard SAP error.
OSS however, up to know did not respond to my message and there does not seem to be a SAP Note on this issue!
Anyone had this problem before. How did they solve it.
Thanks for any reply,
Aart

Posted in another forum

SAP HR Upgrade 4.6b to ECC 6.0

Dear All,
Presently i am in preparation phase of SAP HR Technical upgrade (4.6 B to ECC 6.0) from ABAP side.
I have stepwise process details but i don't have experience in Upgrade projects.
so Pls help me with
1. Check list to start with
2.Issues faced during upgrade
3.Precautions to be taken
4.Major objects to check
/ Lalit

Hi Lalit,
You need to start with the SPDD, SPAU and UCCHECK activity.
1. Then in the remediation part you need to check the syntax of all the programs. The issue were faced like some z-programs used some sub-routine in standard includes. So there maybe a change in the parameters, that you need to check.
2. The z-functions you need to check whether they are ok.
3. Some standard schema and functions have been change you need to check that.
4. Some transactions are removed and given alternative transactions.
5. Includes for some of the user exits have been changed you need to replace the code.
6. Payroll cluster version has been changed you need to run the conversion program.
Let me know if you need any more info.
Br/Manas

HR Upgrade 4.6c to ECC 6.0

Hi,
I encounter this problems during a technical upgrade for HR from 4.6c to ECC6.0. There are some tables which were being prompted as obsolete:
PB0004
PB0017
PB0019
PB0021
PB0081
PB0179
PB0374
PB0486
PB0186
Question: 1. Are these tables to be created/migrated in ECC 6.0?
2. If not migrated, how would it affect the customized program in ECC 6.0 after the programs are migrated?
Thanks for replying.

Hi Carlos,
I've had some experience with Payroll , but mainly singapore payroll. Which country of payroll are you running currently?
Also, could you please rephrase your questions, as I do not quite get them.
As far as I know, there shouldn't be any conversion of the wagetypes. When the system is upgraded from 4.6c to ECC6.0, there will be a SPAU list for your to digest (good luck). As for wagetypes wise, all will be copied to your new ECC6 client. There's no conversion needed.
However, you will have to test thoroughly for all business scenarios of payroll. Calculate each payroll result, and make sure all valuation, calculation and wage types are generated as per the previous configuration and as per customer's existing requirement.
All the best!
Regards,
elaine

Custom program - unknown warning messages after upgrade (4.6c to ECC 6.0)

Hi,
At work, we are currently upgrading from 4.6c to ECC 6.0
One of the custom (z) programs that was moved is displaying warning messages, and preventing the user from viewing a report.
The warnings appeared in ECC 6, but were never there in 4.6c. The warning message is "Restrict your selection". However, no matter how much criteria is entered, the warning message still appears.
The program code uses no messages or error handling, and the messages show up on the initial selection screen, after hitting execute.
However, just for testing, I copied the program to my own z program and it works fine.
Why is this happening with the original program? While creating a new program with copied code fixes the problem, I donu2019t understand why this would be happening in the 1st place.
Any ideas?

So what the zprogram does? what tables are involved in the report, if possible post a link to your code.
Regards
Karthik D

Upgrade 4.7 to ECC 6.0 : Batch input

Hello,
We have an upgrade project from R3 4.7 to ECC 6.0.
I'm looking for information regarding SAP technical advise for interfaces, data update, data creation.
We use batch input. Does this technic still available in ECC 6.0 ? Should we use Idoc, BAPI ?
I need also some advise regarding performance, monitoring...
Are transactions like MB01, VL01 still available ?
Rgds
Gilles

Hi Gilles,
batch input in ECC60 stil available
please look at the online dokumnetation:
http://help.sap.com/erp2005_ehp_03/helpdata/EN/37/a9b0588c884843a1e489ea450a2fef/frameset.htm
the transactions mentioned by you are available in ECC60
I think it is worth reading the online documentation
under
help.sap.com.
Kind regards
Imre Takácsi-Nagy
Senior Support Consultant II.
SAP Global Support Center Austria
Netweaver WEB Application Server ABAP / JAVA

Upgrade 4.7 to ECC 6.O (FI/CO)

Similar Messages

Maybe you are looking for